...
Traffic routed out by N9K/N3K (EoR) device via L3 physical interface uses internally vlan 4095 tag which is preserved in SPAN copy of this traffic. When SPAN copy is received by NDB device (N3000/N3500) it is being dropped as NDB device does not recognize vlan 4095.
Traffic with vlan tag 4095 received by NDB device is dropped.
This configuration is applicable to N3172 and variants: N3K-3# bcm-shell module 1 "stg show" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Views the VLAN and STP instances configured on ASIC N3K-3# bcm-shell module 1 "vlan create 4095" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Creates VLAN in ASIC N3K-3# N3K-3# bcm-shell module 1 "vlan add 4095 PortBitMap=xe48 UntagBitMap=xe48" >>>>>> Assigns VLAN to interface - similar to adding VLANs to trunk N3K-3# bcm-shell module 1 "vlan add 4095 PortBitMap=xe31 UntagBitMap=xe31" >>>>>> Assigns VLAN to interface - similar to adding VLANs to trunk N3K-3# N3K-3# bcm-shell module 1 "stg show" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Verify which STG (Spanning Tree Group) was VLAN 4095 assigned N3K-3# bcm-shell module 1 "stg stp 1 xe31 forward" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Places interface in forwarding state for STG 1 - STG may vary N3K-3# bcm-shell module 1 "stg stp 1 xe48 forward" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Places interface in forwarding state for STG 1 - STG may vary N3K-3# bcm-shell module 1 "stg show" >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Verify forwarding state *** - To verify the BCM port mapping, use following command: N3K-3# show interface hardware-mappings | in ^Name|--|1/32 >>>>>>>>>>>>>>>>>>>>>> Change interface as needed ------------------------------------------------------------------ Name Ifindex Smod Unit HPort HName FPort NPort VPort SrcId ------------------------------------------------------------------ Eth1/32 1a003e00 1 0 32 xe31 255 124 -1 0 ------------------------------------------------------------------ Name Ifindex Smod Unit HPort HName FPort NPort VPort SrcId ------------------------------------------------------------------
This is an expected behavior on EoR architecture as it is a hardware limitation, workaround can be used instead.