Configuring RSPAN between core and client access switch

Morne Vermeulen · ‎10-06-2015

Hi All,

I have an issue with configuring RSPAN. Can't seem to see what the problem is.

Core: 3750-E Distribution switch.

Client Access: 2960-48P

Both running VLAN 300 with IPs on 192.168.240.x/24 range. The two switches can see each other on VLAN 300. So there isn't anything wrong with the VLAN or trunk configs.

My packet sniffer is sitting on Fa0/13 on the client access switch, with an IP in the vlan 300 range.

CORE Config:

VLAN 300

remote-span

int vlan 300

ip address 192.168.240.1 255.255.255.0

monitor session 1 source vlan 300

monitor session 1 destination remote vlan 300

Client Access Config:

VLAN 300

name RSPAN_MONITORING

int vlan 300

ip address 192.168.240.2 255.255.255.0

monitor session 1 source vlan 300

monitor session 1 destination interface FastEthernet 0/13

As soon as I apply this config to the Client access switch, the interface Fa0/13 goes to protocol state = down. As soon as I remote the config, it returns to protocol state = up and I can ping the packet sniffer on the 240.3 IP.

Please help on this.

Thanks!

Morne

Mark Malone · ‎10-06-2015

hey try monitor session 1 source remote vlan 300

Morne Vermeulen · ‎10-06-2015

Hi Mark,

Unfortunately the client switch doesn't allow this command.

CLIENT_SW1(config)#monitor session 1 source remote vlan 300
^
% Invalid input detected at '^' marker.

CLIENT_SW1(config)#

Mark Malone · ‎10-06-2015

Hi ok but that's what your missing to make the rspan connection and the vlan needs to be the same throughout the L2 domain that the rspan takes place on as well , does the switch your trying to implement this on not support span at all ?

what you have created on client side is just standard span without the remote syntax but if it does not take the monitor command switch may not support any type of span , what type of switch is it

Take a look at this may help

http://cauew.blogspot.ie/2008/07/remote-switched-port-analyzer-rspan.html