""Larry Letterman""  wrote in message
news:200210170727.HAA24444@;groupstudy.com...
> I personally changed out a secondary sup card, when I was new in the lan
> team..
> the redundant sup came up with with the trunk port 2/1 config'd for native
> vlan
> 1. this caused the vtp management to issue a vlan mismatch...which then
> started
> a stp recalc, which caused utilization on the gateway to go up trying to
> process the
> bpdu storm, which prevented the network from working correctly...


CL: let he who has never brought a network to its knees cast the first stone
:->


>
> leaving everything in native 1 prevents this....
>
>
> Larry Letterman
> Network Engineer
> Cisco Systems Inc.
>
>
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED] [mailto:nobody@;groupstudy.com]On Behalf Of
> > Erick B.
> > Sent: Wednesday, October 16, 2002 11:53 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Native VLAN 1 [7:55743]
> >
> >
> > Comments inline...
> >
> > --- The Long and Winding Road
> >  wrote:
> > > ""Larry Letterman""  wrote in message
> > > news:200210170505.FAA27055@;groupstudy.com...
> > > > Pris,
> > > >
> > > > In our 6509's we used to make the native vlan and
> > > the data vlan
> > > > the same and it was something other than 1...if a
> > > blade fails and
> > > > we put in a new one , it defaults to vlan 1 for
> > > all ports. If the
> > > > blade has trunk ports in it, they get set to
> > > native vlan 1. The other
> > > > end is set for something else, this resulted in
> > > vlan mismatch in the vtp
> > > > domain, and in a lot of instances we suffered stp
> > > recalcs that took
> > > > buildings down for periods of time...we
> > > subsequently have returned to
> > > > making native vlan 1 on all trunks and have not
> > > had any issues since..
> > > >
> >
> > I want to clarify a few items so we fully understand
> > this behavior so next time I need to hot-swap I am
> > prepared to make config changes as well.
> >
> > I thought the running config in RAM (and NVRAM) stayed
> > the same when swapping *same model* blades in the same
> > slot. If this isn't the case, then is some of the
> > config the same and some is defaulted?
> >
> > Can you point us to a cisco doc explaining this
> > behavior?
> >
> > Thank you very much!
> >
> >
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Faith Hill - Exclusive Performances, Videos & More
> > http://faith.yahoo.com




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=55809&t=55743
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to