From: Moses Polalysa (mpurple7@yahoo.com)
Date: Mon Mar 24 2008 - 23:55:21 ART
Hi Joseph,
How is about if the boot port originally already member of difference VLAN? Should we change the VLAN membership?
I think it can make the original VLAN in disorder and the port span can't communicate with the origin VLAN. CMIIW.
Thank you.
Regards,
Moses
----- Original Message ----
From: Joseph Brunner <joe@affirmedsystems.com>
To: Moses Polalysa <mpurple7@yahoo.com>; ccielab@groupstudy.com
Sent: Tuesday, March 25, 2008 10:46:28 AM
Subject: RE: Remote SPAN
Hey Moses,
On the Remote span source switch think of it as you are dumping packets onto
The RSPAN VLAN, where they will be TRUNKED to the switch where the packets
will be put back onto a MONITORING DESTINATION PORT
So your configuration is correct.
One caveat;
Make sure vlan 100 is forwarding according to the "show interface trunk"
Command. If the vlan is not allowed on trunk ports in the direction of SW2,
That RSPAN traffic aint going no where.
-Joe
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Moses Polalysa
Sent: Monday, March 24, 2008 9:15 PM
To: ccielab@groupstudy.com
Subject: Remote SPAN
Hi expert,
I just wondering if we need to add the source & destination interface to the
remote-span VLAN? Or we just configure monitor session? Please see the
config.
SW1:
!
vlan 100
remote-span
!
monitor session 1 source interface Fa0/20
monitor session 1 destination remote vlan 100
!
int fa0/20
sw ac vlan 100 -> ???
SW2:
!
vlan 100
remote-span
!
monitor session 1 source remote vlan 100
monitor session 1 destination interface Fa0/24
!
int fa0/24
sw ac vlan 100 -> ???
Sorry for this easy question. Thanks in advance.
Regards,
Moses
This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:54 ART