Announcing more specific prefixes is one way to do it, like others have said.
Another technique is to prepend your ASN 2 to 4 times in your announcement to the secondary provider. I have seen advice saying that you do not want to conditionally announce a prefix only when the primary path is down. That just leads to more flapping of your announcements and can get you into other ISPs flap dampening suppression of your prefixes. That can mean that your network is unreachable 30 minutes after your initial problem is resolved. If you're not paying per byte on the secondary, I would try to use prepends to reduce the amount of inbound traffic on that path to 25-50% of path capacity. If a reasonable number of prepends won't encourage enough traffic in the big path, then add a more specific announcement. You wouldn't have to announce all of your space with more specifics, just enough that your smaller path is not over utilzed. What will work for you depends on specifics of your pipes, internal architecture, and who your providers are. On June 30, 2015 10:04:21 PM CDT, Josh Luthman <[email protected]> wrote: >Is it possible to push all of the traffic to one interface while >leaving >both peers operational? > >I'm looking for a failover to be used only if for some reason my >primary >connection isn't working. I'm not sure if this would include simply >losing >the BGP peer or if there's another way to detect problems/outage with >the >primary. > >My reasoning behind this is that the secondary connection is much >smaller >(bandwidth). It is enough to carry the customers during a the >primary's >outage, but I would prefer to avoid day to day traffic on this link. > >Josh Luthman >Office: 937-552-2340 >Direct: 937-552-2343 >1100 Wayne St >Suite 1337 >Troy, OH 45373 >-------------- next part -------------- >An HTML attachment was scrubbed... >URL: ><http://mail.butchevans.com/pipermail/mikrotik/attachments/20150630/0123a7ef/attachment.html> >_______________________________________________ >Mikrotik mailing list >[email protected] >http://mail.butchevans.com/mailman/listinfo/mikrotik > >Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >RouterOS -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.butchevans.com/pipermail/mikrotik/attachments/20150701/270f72ba/attachment.html> _______________________________________________ Mikrotik mailing list [email protected] http://mail.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
