Could Destination Port Be VLAN in Port Mirroring on NCS5500

[lzhang9]

Could Destination Port Be VLAN in Port Mirroring on NCS5500? I saw failure messages as follows.

Monitor-session xxxx

Destination interface HundredGigE0/0/0/15.200

Session has not been set up in the hardware

================================================

Source Interface      Dir   Status

--------------------- ----  ----------------------------------------------------

Hu0/0/0/17.200        Both  Traffic may be replicated to the wrong destination

[balaji.bandi]

what IOS XR code running on device, can you able to post the relevant configuration and show monitor-session status detail

HundredGigE0/0/0/15.200  and Hu0/0/0/17.200  - i see both sub-interface are 200 (is this tag both same VLAN ?)

check some reference  guide :

https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/interfaces/78x/b-interfaces-hardware-component-cg-ncs5500-78x/configuring-traffic-mirroring.html

[lzhang9]

Thanks.

The version is "Cisco IOS XR Software, Version 7.7.2".

I am currently using VLAN tag 200 for both sub-interfaces for testing purposes. It would be more effective to use different VLAN tags for each sub-interface.

Here is the details of monitor-session from the router.

RP/0/RP0/CPU0:xxxx#show monitor-session status detail 
Monitor-session xxxx
  Destination interface HundredGigE0/0/0/15.200
  Session has not been set up in the hardware
  Source Interfaces
  -----------------
  HundredGigE0/0/0/17.200
    Direction:    Both
    Port level:   False
    ACL match:    Disabled
    IPv4 ACL:     Disabled
    IPv6 ACL:     Disabled
    Portion:      Full packet
    Interval:     Mirror all packets
    Mirror drops: Disabled
    Status:       Traffic may be replicated to the wrong destination.

More details on the sub interfaces used in the port mirroring. 

RP/0/RP0/CPU0:xxx-sw#show interfaces HundredGigE 0/0/0/15.200
Wed May 29 13:24:38.914 UTC
HundredGigE0/0/0/15.200 is up, line protocol is up 
  Interface state transitions: 1
  Hardware is VLAN sub-interface(s), address is 94ae.f0dc.a83c
  Layer 2 Transport Mode
  MTU 9220 bytes, BW 100000000 Kbit (Max: 100000000 Kbit)
     reliability Unknown, txload Unknown, rxload Unknown
  Encapsulation 802.1Q Virtual LAN,
    Outer Match: Dot1Q VLAN 200
    Ethertype Any, MAC Match src any, dest any
  loopback not set,
  Last link flapped 07:42:17
  Last input never, output never
  Last clearing of "show interface" counters never
     0 packets input, 0 bytes
     0 input drops, 0 queue drops, 0 input errors
     0 packets output, 0 bytes
     0 output drops, 0 queue drops, 0 output errors

RP/0/RP0/CPU0:xxx-sw#show interfaces HundredGigE 0/0/0/17.200
Wed May 29 13:27:02.001 UTC
HundredGigE0/0/0/17.200 is up, line protocol is up 
  Interface state transitions: 1
  Hardware is VLAN sub-interface(s), address is 94ae.f0dc.a844
  Layer 2 Transport Mode
  MTU 9220 bytes, BW 100000000 Kbit (Max: 100000000 Kbit)
     reliability Unknown, txload Unknown, rxload Unknown
  Encapsulation 802.1Q Virtual LAN,
    Outer Match: Dot1Q VLAN 200
    Ethertype Any, MAC Match src any, dest any
  loopback not set,
  Last link flapped 07:44:40
  Last input never, output never
  Last clearing of "show interface" counters never
     0 packets input, 0 bytes
     0 input drops, 0 queue drops, 0 input errors
     0 packets output, 0 bytes
     0 output drops, 0 queue drops, 0 output errors

[Giuseppe Larosa]

Hello @lzhang9 ,

try to use the physical interface as destination interface as reported in the examples in config guide provided by BB

Hope to help

Giuseppe

[lzhang9]

Thank you @Giuseppe.P93 

It works if the destination port is physical interface. However, in my situation, using the VLAN tag is intentional.

BB mentions the version of 7.8.x while my version is 7.7.2. Is the VLAN destination port a new feature introduced since 7.8.1?

Release 7.8.1

SPAN filtering of outgoing traffic on Layer 2 interfaces for Cisco NC57 line cards was introduced.

[lzhang9]

Update:

I tried the same configuration on the NCS5700 routers and it works fine. So it looks like some constraint of NCS5500 hardware/software.