Loading...
Loading...
BGP RR not setting cluster-id at neighbor config/creation, thus routes from affected client are not reflected/advertised to other clients. From bgp debug : RP/0/RP0/CPU0:Aug 25 10:27:10.465 CDT: bgp[1084]: [default-upd] (ip4lu): No unreachable (cluster id not set for RR client:172.16.70.7) sent to sub-group 0.2 (Regular) with 172.17.64.191/32 - already withdrawn This is a timing condition and be verified from sh bgp neighbor for affected rr-client : BGP neighbor is 172.16.70.7 Remote AS 65108, local AS 65108, internal link Description: iBGP-Peer Remote router ID 172.16.70.7 <<<< MISSING : Cluster ID 172.31.189.7 BGP state = Established, up for 4d17h
Prior to hitting this condition, a l2vpn evpn neighbor with RR client and advertise vpn4/vpnv6 config must have been removed : neighbor 10.0.0.1 remote-as X address-family l2vpn evpn route-reflector-client advertise vpnv4 unicast advertise vpnv6 unicast Failed commit due to incomplete config might also cause this.
process restart bgp
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.