I'm currently having BGP running with 2 ISPs on 2 routers at 2 data centers as a failover setup with AS Prepending applied on a /24 advertisement on the router at the second data center. I have a 1Mb connection going to this data center through an ISP which has AT&T as their backbone network.
The thing is I try every single internet router out there to do a "show ip bgp *.*.*.*" and I get the right answer which SomeAS# 1stISP-AS# My-AS#, but if I use ATT's router to do a "show ip bgp" I get ATT-AS# 2ndIPS-AS# My-AS# My-AS# My-AS# My-AS# My-AS# <-- Prepending applied here.
I thought that AS-Prepending applied to the advertisement going through the 2nd ISP made the advertisement going through the 1st ISP the preferred path, shouldn't the 2nd ISP see this path also and ignore the path with AS Prepending applied until the connection to the 1st IPS fails?
Just because you see it does not mean it is the best path. For example, if you go to something like
and do a
sh ip bgp regexp
you will see a list of the network blocks for the asn and all of the valid paths to the asn, but only one will be listed as the best. The far left as * listed and this means that this is a valid path to that network block. What you will need to look for will be a *> as this represents the valid and best path for the network block.
It depends somewhat on how many times you prepend your AS to the second ISP (and depends somewhat on how many ASes are between ISP-2 and ISP-1). If there are enough ASes between ISP-2 and ISP-1 (each AS gets added to the path as the advertisement is propagated) then the path may be equal or shorter for ISP-2 to come directly to you. It may also be that ISP-2 has set things up so that they route directly to their customers (and perhaps they pass that to ATT).
Rick is right, insufficient AS path length on the prepended path is 4) in the list.
Rick, I believe nothing ISP1 does internally with the BGP update would allow it to make it less preferable in the ATT AS, as long as ISP1 announces the update at all.
Ah this gives option
5) ISP1 sets f.e. LocPref if the update is received from ATT and does not announce the shorter path to ATT. Thinking twice, this comes down to option 4) because the shorter path is out there in the internet, hence in case 5) it would reach ATT through other provider AS.
My point has less to do with ISP-1 making the route less attractive to ATT and more with the possibility that ISP-2 might make it more attractive (pass some community to ATT that identifies this as from my customer, for example) and ATT makes it decision based on this. I am not sure that this is really the case - but it is one scenario which would explain the observed behavior.
it is highly unlikely that ATT uses static routes. My idea is, that your ISP1 sets Local Preference on all BGP updates learned from ATT. This would make it the prefered path and would explain that ISP1 will not announce the best path back to ATT.
So my suggestion now is to talk to ISP1 and ask for assistance. In case they announce your network with the shorter path to ATT all your issues should go away.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...