12-15-2014 10:31 AM - edited 03-05-2019 12:22 AM
I'm testing Cisco Cloud Services Router in a virtualized environment. See the attached image for the topology I've setup. Basically I have 3 CSR's and one vShield Edge that are talking eBGP to each-other.
The problem I'm having is that sometimes, the Cisco CSR will advertise a route back to the peer it learned the route from.
CSR(T) advertises 192.168.1.0/24, and Edge(S) advertises 192.168.0.0/24, so that Source and Target VM can communicate. CSR (1) and (2) sit between CSR(T) and Edge(S) and re-advertise the routes learned.
If CSR(T) is peered ONLY with one of the middle CSR's (1 or 2, but not both), then everything is fine. When I have it peered to both at the same time, then CSR(T) advertises 192.168.0.0/24 back to both CSR(1) and CSR(2).
CSR(1) is doing something similar - advertising 192.168.1.0/24 to CSR(T) and advertising 192.168.0.0/24 to Edge(S). CSR(2) is configured nearly identically but isn't doing that.
I'm just wondering under what circumstances will a Cisco BGP speaker advertise a route back to the peer it learned it from. It seems like it should never do that. Is there a bug in the Cisco BGP code that I'm running into?
12-17-2014 11:44 AM
On CSR(T) and CSR(1) I added route maps to prevent it from advertising those routes back to the peers that it learned them from.
On CSR(2) I have a route map that adds a MED of 100 to the advertisement to CSR(T)
12-21-2023 10:04 PM
all the BGP peers on 1 router should be in different update groups. you can try removing send-community command in BGP from 1 of the peers and check
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide