Hi all,
Any Sprint BGP admins on this list can offer any thoughts on why Sprint
connected networks are preferring my Sprint connection when they should be
preferring my Verizon?
I (Healthy Directions) am AS16387, two blocks 63.73.158.0/24 and
63.78.31.0/24, being announced by sprint and Verizon, preferred to
Verizon(DS3) over Sprint 3MB.
Verizon BGP admins think everything is ok, have not heard back from BGP4 at
sprint.
Any thoughts appreciated, off-list contact welcome.
Edward
They will almost always prefer their IBGP to any learned routes. Why send
traffic to a transit network and skew their I/O peering numbers when you can
handle it yourself. I doubt you will change their mind.
Robert D. Scott Robert@ufl.edu
Senior Network Engineer 352-273-0113 Phone
CNS - Network Services 352-392-2061 CNS Phone Tree
University of Florida 352-392-9440 FAX
Florida Lambda Rail 352-294-3571 FLR NOC
Gainesville, FL 32611 321-663-0421 Cell
They will almost always prefer their IBGP to any learned routes. Why send
traffic to a transit network and skew their I/O peering numbers when you can
handle it yourself. I doubt you will change their mind.
http://onesc.net/communities/as1239/
uhm, prepend and/or localpref fiddling...
-chris
I see you're prepending the heck out of your announcement to Sprint...but Sprint is apparently still prefering to use their internal/customer route to you rather than send your traffic across the internet.
If you really want Sprint to not use your 3MB circuit unless the Verizon one is down, have a look at https://www.sprint.net/index.php?p=policy_bgp
You probably want to lower their localpref for your routes.
Edward Brookhouse wrote:
Hi all,
Any Sprint BGP admins on this list can offer any thoughts on why Sprint
connected networks are preferring my Sprint connection when they should be
preferring my Verizon?I (Healthy Directions) am AS16387, two blocks 63.73.158.0/24 and
63.78.31.0/24, being announced by sprint and Verizon, preferred to
Verizon(DS3) over Sprint 3MB.
They will prefer to send you traffic over their direct connection over that of a peer.
You can influence this by sending them a community to lower your local preference within their network.
Export community 1239:80 to Sprint and clear your outbound BGP session with them. See if that does the trick.
However, you might get better performance by keeping Sprint direct customers on the Sprint link under normal circumstances, but have the rest of the Internet come over your Verizon link. If the Sprint customer traffic (only) doesn't fill your pipe from them, then you'll likely get shorter paths and lower latency by taking it direct.
To do this, don't export 1239:80 but instead export 65004:0 which will cause Sprint to prepend to the rest of the Internet but route their customer traffic to you directly.
Thanks All - problem resolved.