[c-nsp] Re: cisco-nsp Digest, Vol 21, Issue 96

[Voll, Scott]

SPAN only works on local switches.  That is why they made RSPAN.  Switch
A has a source you want to track.  Switch B has a Destination you want
it logged to.  The RSPAN Vlan is how you transport the traffic from
Switch A to B or C or D for that matter.  

Scott

-----Original Message-----
From: ovidiu [mailto:ovidiu at ipnet.ro] 
Sent: Sunday, August 29, 2004 5:21 AM
To: cisco-nsp at puck.nether.net; Tim Stevenson
Subject: Re: [c-nsp] Re: cisco-nsp Digest, Vol 21, Issue 96

hi. thank you for the answer. correct me if I am wrong:
RSPAN source session is the session between the source port or source
vlan
and the RSPAN VLAN (this sessions being located on the source switch)
and RSPAN destinatination session is the session between the RSPAN VLAN
and
the destination interface (this session being located on the destination
switch ) ?



----- Original Message ----- 
From: "Tim Stevenson" <tstevens at cisco.com>
To: <cisco-nsp at puck.nether.net>; <cisco-nsp at puck.nether.net>
Sent: Sunday, August 29, 2004 3:11 AM
Subject: [c-nsp] Re: cisco-nsp Digest, Vol 21, Issue 96


> This is an RSPAN source session:
> monitor 1 source vlan 10
> monitor 1 destination remote vlan 100
>
> Where VLAN 100 is your RSPAN VLAN.
>
> This is an RSPAN destination session:
> monitor session 2 source remote vlan 100
> monitor session 2 destination int gig 1/1
>
> This is shown in the show monitor output:
>
> tstevens-6506#sh mon
> Session 1
> ---------
> Type                   : Remote Source Session <<<<<<< HERE
> Source VLANs           :
>      Both               : 10
> Destination RSPAN VLAN : 100
>
> Session 2
> ---------
> Type                   : Remote Destination Session <<<< & HERE
> Source RSPAN VLAN      : 100
> Destination Ports      : Gi1/1
>
> tstevens-6506#
>
> There are limits to each type of session, dependent on the Sup version
and
> also whether running IOS or CatOS, as shown in the docs.
>
> Tim
>
>
>
> At 09:00 AM 8/28/2004, cisco-nsp-request at puck.nether.net declared:
> >Message: 8
> >Date: Sat, 28 Aug 2004 12:29:41 +0300
> >From: "ovidiu neghina" <ovidiu at ipnet.ro>
> >Subject: Re: [c-nsp] question about rspan  sessions
> >To: <cisco-nsp at puck.nether.net>
> >Message-ID: <003a01c48ce1$8c317c00$330c060a at shiko>
> >
> >thank you for the quick answer.
> >i understood what a destination, source and reflector port is.
> >but i am not clear with the terms: "destination session" and "source
> >session" and the limitations for them :
> >
> >RSPAN source sessions have one destination per session with an RSPAN
> >VLAN associated for that session.
> >Each RSPAN destination session has one or more destination interfaces
> >for each RSPAN VLAN that they support.
>
>
>
> Tim Stevenson, tstevens at cisco.com
> Routing & Switching CCIE #5561
> Technical Marketing Engineer, Catalyst 6500
> Cisco Systems, http://www.cisco.com
> IP Phone: 408-526-6759
> ********************************************************
> The contents of this message may be *Cisco Confidential*
> and are intended for the specified recipients only.
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/