Solved! Go to Solution.
On my static route, I actually have the AD set to 250, which means that the iBGP route should be more preferred than the static route, should it not?
Hi, I would have to lab this up, but I cant do it now. Way too late for me here on the east coast...
But I believe that what is messing you up is the fact that youre originating a route with the network statement and static route on the MSFC when you dont have to. I guess you are doing that because you want the MSFC to advertise that internal network to an external BGP peer.
If thats the case, you dont need to do that because the prefix learned through iBGP will automatically be advertised to the eBGP neighbor.
Like I said, I would have to test this in a lab, but you may want to remove the network AND the static route statement and see what happens.
make sure you clear all the BGP neighbors after doing so.
Sorry for the confusion earlier. I spoke too soon...
This post was edited, so if you read it more than a minyte ag, re-read it.
I understand that the IBGP prefix will automatically be advertised to the EBGP neighbour. The reason I have the static route in there with the high AD is so I have a route of last resort. Basically, if the IBGP route becomes unavailable, or is withdrawn internally, I don't want to flap the prefix towards my EBGP neighbour. The static, high AD route prevents that possibility of flapping.
"The static, high AD route prevents that possibility of flapping."
So you would rather advertise a false route to your eBGP neighbor and blackhole the traffic destined for that prefix?
That is because local originate has weight 32768 by default, it will never use the path learned from 10.47.26.5. To make it work you need to set the weight to higher than 32768 on the inbound direction of peer 10.47.26.5, so that way it will prefer route from 10.47.26.5.
Yes, if I set the weight higher, that path will certainly become the best path, but at that point, then the local-AS community will prevent that route from being announced to EBGP speakers.
As I said previously, I tag the routes learned from the FWSM with the local-as community to stop long prefixes from being announced to EBGP speakers.