[c-nsp] Vlans and catalyst 2950
nick.nauwelaerts at thomson.com
nick.nauwelaerts at thomson.com
Wed Feb 9 04:54:31 EST 2005
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net
> [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Alban Dani
> Sent: Wednesday, February 09, 2005 02:58 AM
> To: mrz at intelenet.net
> Cc: cisco-nsp at puck.nether.net
> Subject: [c-nsp] Vlans and catalyst 2950
>
>
> Hello Matthew,
>
> I also am having a very wierd issue with vlans and 2950-s.
>
> We are running pst+.
> We have a 6509 in the core and everytime we try to get a new vlan
> passed through a chain of switches( all connected via dot1q trunks)
> that has a 2950 in it, it does not work. The only workaround we found
> so far is to go to a port on the given 2950 , set the port on the
> requried vlan and connect a machine to it and through some traffic.
> That makes the 2950 aware of that vlan.
>
> If this was not enough, if the vlan in question does not see traffic
> for a couple of days the 2950 totally forgets about it.
>
> I am wondering if you ever found a solution to your problem and if so
> what was it?
>
> I have upgraded to the latest IOS but it did not help.
We also have a 6500 at the core and some 2950Gs in the wiring closet.
I've haven't run into any issues with VLAn propagation yet. Have you
checked that your 6500's VTP settings are set to server and the 2950's
are set to client? I've seen issues if you mix transparent ones in
between a client/server setup.
12.1(22)EA2 on the 2950s, 12.2(18)SXD3 native IOS on the 6500, but it
worked with previous versions just as well.
// nick
More information about the cisco-nsp
mailing list