Symptom
BGP decoding for EVPN RT-2 with AC-ID extcomm (extcomm id 0x060e) is not supported
Conditions
In below output, can see "0x060e:0000.0000.0001" is not decoded to show the ac-id value on both paths
RP/0/0/CPU0:PE1#show bgp l2vpn evpn bridge-domain bd100 [2][0][48][000a.000b.000c][32][5.5.5.69]/136
Wed Jan 17 12:14:34.477 EST
BGP routing table entry for [2][0][48][000a.000b.000c][32][5.5.5.69]/136, Route Distinguisher: 192.168.0.1:100
Versions:
Process bRIB/RIB SendTblVer
Speaker 115 115
Local Label: 28100
Last Modified: Jan 16 14:43:14.000 for 21:31:20
Paths: (2 available, best #1)
Advertised to update-groups (with more than one peer):
0.2
Path #1: Received by speaker 0
Advertised to update-groups (with more than one peer):
0.2
Local
0.0.0.0 from 0.0.0.0 (192.168.0.1)
Second Label 28120
Origin IGP, localpref 100, valid, redistributed, best, group-best, import-candidate, rib-install
Received Path ID 0, Local Path ID 1, version 113
Extended community: Flags 0xe: SoO:192.168.0.1:100 0x060e:0000.0000.0001 RT:10:10 RT:100:100
EVPN ESI: 0100.0000.acce.5500.0100
Path #2: Received by speaker 0
Not advertised to any peer
Local
192.168.0.3 (metric 2) from 192.168.0.3 (192.168.0.3)
Received Label 28100, Second Label 28116
Origin IGP, localpref 100, valid, internal, import-candidate, imported, rib-install
Received Path ID 0, Local Path ID 0, version 0
Extended community: SoO:192.168.0.1:100 0x060e:0000.0000.0001 RT:10:10 RT:100:100
EVPN ESI: 0100.0000.acce.5500.0100
Source AFI: L2VPN EVPN, Source VRF: default, Source Route Distinguisher: 192.168.0.3:100
Workaround
Need to manually decode it
