Symptom

ebgp dmz link bandwidth information is not propagating properly to the MP-iBGP peer. 5 ebgp peers (combined dmz weight of 5000000) >>>>>>>>>>> tor-182.w0569 >>>>>>>>>>>>>>>>>> mp-ibgp (afi l2vpn evpn with ?advertise vpnv4? command) >>>>>>>>>>>>>>>>>>>> tor-53.w0569 ++ There are 5 path to reach 10.4.166.58 from tor-182.w0569 over 5 ebgp peers. Weight for each path is 10000000. 5 links = 50000000 RP/0/RP0/CPU0:tor-182.w0569#show route vrf BMIU 10.4.166.58 Wed Feb 24 14:56:43.747 UTC Routing entry for 10.4.166.58/32 Known via "bgp 577", distance 20, metric 0 Tag 65000, type external Installed Feb 22 17:29:06.525 for 1d21h Routing Descriptor Blocks 10.5.244.211, from 10.5.244.211, BGP external, BGP multi path Route metric is 0, Wt is 10000000 10.5.245.19, from 10.5.245.19, BGP external, BGP multi path Route metric is 0, Wt is 10000000 10.5.245.43, from 10.5.245.43, BGP external, BGP multi path Route metric is 0, Wt is 10000000 10.5.245.51, from 10.5.245.51, BGP external, BGP multi path Route metric is 0, Wt is 10000000 10.5.245.91, from 10.5.245.91, BGP external, BGP multi path Route metric is 0, Wt is 10000000 No advertising protos. ++ This combined weight will be sent as a bgp extended community to the remote PE. When we check this on remote PE tor-53.w0569, we should expect to see 50000000. Instead, we see 40000000: RP/0/RP0/CPU0:tor-53.w0569#show bgp vpnv4 unicast vrf BMIU 10.4.166.58/32 Wed Feb 24 15:08:38.126 UTC BGP routing table entry for 10.4.166.58/32, Route Distinguisher: 142.119.132.12:8 Versions: Process bRIB/RIB SendTblVer Speaker 110282591 110282591 Local Label: 100012 Last Modified: Feb 22 17:23:28.857 for 1d21h Paths: (8 available, best #1) Advertised to update-groups (with more than one peer): 0.1 Path #5: Received by speaker 0 Not advertised to any peer 65000, (Received from a RR-client), (received & used) 10.55.96.212 (metric 40) from 10.55.96.212 (10.55.96.212) Received Label 105211 Origin incomplete, localpref 100, valid, internal, multipath, import-candidate, imported, reoriginated Received Path ID 0, Local Path ID 0, version 0 Extended community: LB:577:40000000 RT:577:4849 Source AFI: L2VPN EVPN, Source VRF: default, Source Route Distinguisher: 10.55.96.212:2

Conditions

ebgp peer flap due to any reason like a interface flap or any external reason

Workaround

clear bgp xxxx xxxx * soft should clear the issue as correct bandwidth is propagated to the peer.

Further Problem Description