From: Swaroop Potdar (swarooppotdar@hotmail.com)
Date: Sun Nov 14 2004 - 02:20:19 GMT-3
Hey Tim,
Thanks for your time and reply...
Wonder of wonders is a detailed explanation is available in the BCMSN course
ware of CCNP.
Sometimes we wander so far away that we forget to search simple and
available things.!!
Thanks,
Swaroop.
>From: "ccie2be" <ccie2be@nyc.rr.com>
>Reply-To: "ccie2be" <ccie2be@nyc.rr.com>
>To: "Swaroop Potdar" <swarooppotdar@hotmail.com>, <ccielab@groupstudy.com>
>Subject: Re: Spanning Remotely.
>Date: Sat, 13 Nov 2004 11:40:55 -0500
>
>Swaroop,
>
>I think I can help you out with this one and I feel good that I can pay you
>back a little for all the help you've given me.
>
>The key thing to remember with remote spanning is this requires a vlan
>dedicated to the remote span traffic. Now, unless you've prohibited the
>vlan
>for remote span from the trunks and vtp is running on all the switches, it
>shouldn't matter that the source switch is multiple hops away from the
>destination switch since vtp will propagate the rspan vlan to all switches.
>
>Once you've created the rspan vlan, then just follow the directions in the
>CG
>for configuring the source switch and destination switch.
>
>This is from the 3550 CR,
>Usage Guidelines
>When a VLAN is converted from a normal VLAN to an RSPAN VLAN (or the
>reverse),
>the VLAN is first deleted and is then recreated with the new configuration.
>If
>VTP is enabled, the RSPAN feature is propagated by VLAN Trunking Protocol
>(VTP) for VLAN-IDs that are lower than 1024.
>
>Before you configure the RSPAN remote-span feature, use the vlan (global
>configuration) command to create the VLAN.
>
>Examples
>This example shows how to configure an RSPAN VLAN.
>
>Switch(config)# vlan 901
>Switch(config-vlan)# remote-spanLet me know if you have any other questions
>on
>this.HTH, Tim
>
>----- Original Message -----
>From: "Swaroop Potdar" <swarooppotdar@hotmail.com>
>To: <ccielab@groupstudy.com>
>Sent: Saturday, November 13, 2004 8:19 AM
>Subject: Spanning Remotely.
>
>
> > Hi All,
> >
> >
> > If I have say around 10 switches.
> >
> > And all are trunked to each other and all the vlans are allowed on the
> > trunks.
> >
> > Lets assume there are vlans 2,3,4,5,6
> >
> > So if I want to monitor the port 10 on switch 1 of vlan 2 as the source
> >
> > and my analyzer is on switch 7 on vlan 5 on port 12
> >
> > In this case what would the configuration be.
> >
> > And where the configuration would be applied.
> >
> > -------------
> >
> > Or is it so that we give the same session numbers on both these switches
>but
> > configure the source parameters on the switch 1 and destination
>parameters
> > on the switch 7 and the sessions negotiate automatically to send and
>receive
> > data at as per teh configuration....???
> >
> > This is purely academic...as its quite a odd question.
> >
> > Your inputs would be helpful as i havent found much doumentation on this
> > topic..
> >
> > Thanks,
> > Swaroop.
> >
> > Regards,
> > Swaroop.
> > ------------------------------------------------------------------
> > Life Is Short & Sweet.
> > Live It To The Fullest.
> > ------------------------------------------------------------------
> >
> > _________________________________________________________________
> > NRIs! Easy to send, easy to receive!
> > http://creative.mediaturf.net/creatives/citibankrca/rca_msntagofline.htm
>Ask
> > us how!
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
>
>_______________________________________________________________________
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html
Regards,
Swaroop.
------------------------------------------------------------------
Life Is Short & Sweet.
Live It To The Fullest.
------------------------------------------------------------------
This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:43 GMT-3