Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
On one bridge-domain, one AC interface bounce cause another sub-interface AC out-lif MVID and profile value get cleared. on this output below, mvid for hun0/0/2/0.10 get cleared after other AC interface ten0/0/0/19 bounce. interface TenGigE0/0/0/19 l2transport ! interface HundredGigE0/0/2/0.10 l2transport encapsulation dot1q 10 <<<<<<<<<<<<<< it should be tagged with vlan 10 rewrite ingress tag pop 1 symmetric l2vpn bridge group VLAN10 bridge-domain 10 ! interface TenGigE0/0/0/19 ! interface HundredGigE0/0/2/0.10 ! routed interface BVI10 ! ! RP/0/RP0/CPU0:F340.13.16-NCS-55A2-6#show ether-ea interface hun0/0/2/0.10 loc 0/0/cpu0 | in lif Tue Jul 28 18:41:16.179 UTC extlif details : pm_info->intf_info.lif : 0x80200a pm_info->intf_info.lif : 0x80200a ifinfo->lif : 0x80200a <<<<<<<<<<<<< ifinfo->local_outlif : 0x400e RP/0/RP0/CPU0:F340.13.16-NCS-55A2-6#sh controllers fia diag 0 "diag pp lif id=0x200a gl=1 type=out" loc 0/0/cpu0 Tue Jul 28 17:19:49.925 UTC Node ID: 0/0/CPU0 Global Out_LIF:0x0000200a -> Local Out_LIF:0x0000400e -> Type:(null) Bank:1 Offset:7 Out-AC: ^Medit_info:Outer Tag [edit_info_0]: ^Mvid: 0 <— this should be 10, however it get cleared incorrectly ^Mpcp: 0 ^Mdei: 0 ^MInner Tag [edit_info_1]: ^Mvid: 0 ^Mpcp: 0 ^Mdei: 0 ^Mnof_tags: 2 ^Medit_profile: 0 <— this should have been set to push 1 profile which is 3, however it get cleared incorrectly. ^Mpcp_profile: 0 ^Mlif_profile: 0 ^Moam_lif_set: 0 ^Mprotection_info:protection_pointer: 2 ^Mprotection_pass_value: 0 ^MNext_eep: 0xffffffff
This problem happen when condition 1 and condition 2 are matched. 1. the bouncing AC interface PP port id is the same as the impacted AC interface physical port "port_class_id" ( it is also called vlan_domain), please see the output below 2. the bouncing AC is main port, the impacted AC encapsulation is sub-interface with tagging. interface HundredGigE0/0/2/0.10 l2transport encapsulation dot1q 10 rewrite ingress tag pop 1 symmetric interface TenGigE0/0/0/19 l2transport ! l2vpn bridge group VLAN10 bridge-domain 10 ! interface TenGigE0/0/0/19 <<<<<<<<< bouncing interface ! interface HundredGigE0/0/2/0.10 <<<<<<<<<< impacted interface ! RP/0/RP0/CPU0:F340.13.16-NCS-55A2-6#show im database interface hun0/0/2/0 brief Tue Jul 28 18:37:41.181 UTC View: OWN - Owner, L3P - Local 3rd Party, G3P - Global 3rd Party, LDP - Local Data Plane GDP - Global Data Plane, RED - Redundancy, UL - UL Node 0/0/CPU0 (0x0) Handle | Name | State | MTU |#P|#C| Views | ----------|----------------------|----------|-----|--|--|-------------------| 0x00000048 Hu0/0/2/0 up 1514 3 4 GDP|LDP|L3P|OWN <<<<<<<< hun0/0/2/0 handle is 0x48 RP/0/RP0/CPU0:F340.13.16-NCS-55A2-6#attach loc 0/0/cpu0 [snip] [xr-vm_node0_0_CPU0:~]$export PS1='#' # /pkg/bin/dpa_l2port_show_client -D | grep -a -B2 -A80 'dpa_intf_t intf => 0x00000048' <<<<< 0x48 is hun0/0/2/0 handle above. l2port element 0 (hdl:0x308c806028): ofa_npu_mask_t npu_mask => 1 dpa_intf_t intf => 0x00000048 dpa_intf_t bundle_ifh => (not set) [snip] sys_port_arr.tmport.refhdl => 0x308ca992d0 npu0:uint16_t lagport_class_id => (not set) npu0:uint16_t port_class_id => 41 <<<<<<<<<<<<<< port_class_id is 41 RP/0/RP0/CPU0:F340.13.16-NCS-55A2-6#show controllers npu voq-usage interface all instance all loc 0/0/cpu0 Tue Jul 28 18:36:25.738 UTC ------------------------------------------------------------------- Node ID: 0/0/CPU0 Intf Intf NPU NPU PP Sys VOQ Flow VOQ Port name handle # core Port Port base base port speed (hex) type ---------------------------------------------------------------------- Hu0/0/2/0 48 0 0 9 9 1344 5544 local 100G Hu0/0/2/1 68 0 1 13 13 1352 5536 local 100G Hu0/0/2/2 88 0 0 17 17 1360 5552 local 100G Te0/0/0/5 c8 0 0 25 25 1192 5456 local 10G Te0/0/0/6 d0 0 0 26 26 1168 5432 local 10G Gi0/0/0/7 d8 0 0 27 27 1160 5424 local 1G Te0/0/0/4 e0 0 0 28 28 1184 5448 local 10G Te0/0/0/9 e8 0 1 29 29 1144 5456 local 10G Te0/0/0/8 f0 0 1 30 30 1152 5464 local 10G Te0/0/0/11 f8 0 1 31 31 1128 5440 local 10G Te0/0/0/10 100 0 1 32 32 1136 5448 local 10G Te0/0/0/1 108 0 0 33 33 1176 5440 local 10G Gi0/0/0/2 110 0 0 34 34 1200 5464 local 1G Gi0/0/0/3 118 0 0 35 35 1208 5472 local 1G Te0/0/0/0 120 0 0 36 36 1024 5384 local 10G Te0/0/0/15 128 0 1 37 37 1096 5408 local 10G Te0/0/0/14 130 0 1 38 38 1104 5416 local 10G Te0/0/0/13 138 0 1 39 39 1112 5424 local 10G Te0/0/0/12 140 0 1 40 40 1120 5432 local 10G Te0/0/0/19 148 0 0 41 41 1064 5392 local 10G <<<<<<<<<< ten 0/0/0/19 pp port id is 41. Te0/0/0/18 150 0 0 42 42 1072 5400 local 10G Te0/0/0/17 158 0 0 43 43 1080 5408 local 10G [snip]] RP/0/RP0/CPU0:F340.13.16-NCS-55A2-6#
the bridge-domain configuration should prevent the condition above.
In order to recover this problem, we can re-apply "rewrite ingress tag pop 1 symmetric" under impacted sub-interface AC interface HundredGigE0/0/2/0.10 l2transport no rewrite ingress tag pop 1 symmetric commit interface HundredGigE0/0/2/0.10 l2transport rewrite ingress tag pop 1 symmetric commit