Using Local SPAN instead of RSPAN destination session

[soichi.iizuka]

For some reason, I would like to config RSPAN destination session with multiple vlans.

But RSPAN destination session "monitor session 1 source remote vlan ~" is for only one vlan.

I configed local SPAN "monitor session 1 source vlan ~" for RSPAN vlans, and it seemed working.

What is the difference between following 2 config ?

# monitor session 1 source vlan 100

# monitor session 1 source remote vlan 100

(vlan 100 is "remote-span"ed in both cases)

[JohnTylerPearce]

The first one is monitoring vlan 100 traffic, the second one is monitoring the clan specified as rspan.


Sent from Cisco Technical Support Android App

[soichi.iizuka]

To make my question clearer, here is sample config.

Switch3 is connected to monitor device which need to capture traffic on Switch1 and Switch2.

On Switch3, I tried Local SPAN to mirror vlan900 and vlan901 to one physical port.

It seemed working because monitor device was recieving both traffic on Switch1 and Switch2.

So my question is...

If Local SPAN can be used instead of RSPAN dest session, why is there RSPAN dest session?

As RSPAN dest session can mirror only one vlan, does Local SPAN have upper compatibility?

Switch1:

vlan 900

remote-span

monitor session 1 source int f0/1 - 20

monirot session 1 destination remote vlan 900

Switch2:

vlan 901

remote-span

monitor session 1 source int f0/1 - 20

monirot session 1 destination remote vlan 901

Switch3:

vlan 900

remote-span

vlan 901

remote-span

monitor session 1 source vlan 900 - 901

monitor session 1 destination int f0/1