Symptom

in this case PE1 receives a route from PE2 in routing table but doesn't add any ext community in the routing table due to which type 5 lsa gets generated. For one nexus device we can see that ext community is present in the routing table PE-2%MNG-MNG-D1-500# show ip route 10.179.250.0/24 detail IP Route Table for VRF "MNG-MNG-D1-500" '*' denotes best ucast next-hop '**' denotes best mcast next-hop '[x/y]' denotes [preference/metric] '%' in via output denotes VRF 10.179.250.0/24, ubest/mbest: 1/0 Extended Community: 0x08 18 00 05 00 00 00 00 02 00 80 00 00 00 00 00 03 00 80 01 55 cd 23 01 *via 172.16.1.3%MNG-MNG-M1-ILO-501, Vlan2, [20/101], 1w1d, bgp-12663, external, tag 12663 client-specific data: 30 PE-2# show bgp vpnv4 unicast 10.179.250.0/24 BGP routing table information for VRF default, address family VPNv4 Unicast Route Distinguisher: 12663:23201 BGP routing table entry for 10.179.250.0/24, version 249 Paths: (1 available, best #1) Flags: (0x000002) on xmit-list, is not in urib Advertised path-id 1 Path type: internal, path is valid, is best path AS-Path: NONE, path sourced internal to AS 77.77.77.77 (metric 41) from 77.77.77.77 (77.77.77.77) Origin incomplete, MED 101, localpref 100, weight 0 Received label 20 Extcommunity: RT:12663:11000 RT:12663:12201 OSPF DOMAIN ID:0x0005:0x000000000200 OSPF RT:0.0.0.0:3:0 OSPF ROUTER ID:85.205.35.1 While on another nexus device which is a peer of PE-2 extended community is not present in the routing table. PE-1%MNG-MNG-D1-500# show ip route 10.179.250.0/24 detail IP Route Table for VRF "MNG-MNG-D1-500" '*' denotes best ucast next-hop '**' denotes best mcast next-hop '[x/y]' denotes [preference/metric] '%' in via output denotes VRF 10.179.250.0/24, ubest/mbest: 1/0 *via 172.16.2.3%MNG-MNG-M1-ILO-501, Vlan4, [20/101], 1w1d, bgp-12663, external, tag 12663 client-specific data: 30 PE-1# show bgp vpnv4 unicast 10.179.250.0/24 BGP routing table information for VRF default, address family VPNv4 Unicast Route Distinguisher: 12663:24201 (VRF MNG-MNG-M1-ILO-501) BGP routing table entry for 10.179.250.0/24, version 102 Paths: (2 available, best #2) Flags: (0x80c0002) on xmit-list, is not in urib, exported, has label vpn: version 258, (0x100002) on xmit-list local label: 18 Path type: internal, path is valid, not best reason: Weight Imported from 12663:23201:10.179.250.0/24 AS-Path: NONE, path sourced internal to AS 77.77.77.77 (metric 41) from 77.77.77.77 (77.77.77.77) Origin incomplete, MED 101, localpref 100, weight 0 Received label 20 Extcommunity: RT:12663:11000 RT:12663:12201 OSPF DOMAIN ID:0x0005:0x000000000200 OSPF RT:0.0.0.0:3:0 OSPF ROUTER ID:85.205.35.1 Advertised path-id 1, VPN AF advertised path-id 1 Path type: redist, path is valid, is best path AS-Path: NONE, path locally originated 0.0.0.0 (metric 0) from 0.0.0.0 (99.99.99.99) Origin incomplete, MED 101, localpref 100, weight 32768 Extcommunity: RT:12663:11000 RT:12663:12201 OSPF DOMAIN ID:0x0005:0x000000000200 OSPF RT:0.0.0.0:3:0 OSPF ROUTER ID:85.205.35.2

Conditions

Workaround

no work around

Further Problem Description