From: Stefan Grey (examplebrain@hotmail.com)
Date: Mon Oct 17 2005 - 10:30:14 GMT-3
Thanks Tim,
your answer really helps but still not identified why this problem uppears
and how to solve this definitely. I think this problem is ver very usual,
that's why anybody should face to it. Maybe somebody else also has something
to tell about it??? please...
And also what this command "state active" really does. How does it influence
on this problem??
(The summary of the promblem is: when we reboot the server VTP switch all
vlans which are not dierctly connected to the switch disappear and those
which are connected loose their names like "VlanA" and have only default
like vlan0001
, even after copy run start command).
Thanks.
>From: "Tim" <ccie2be@nyc.rr.com>
>Reply-To: "Tim" <ccie2be@nyc.rr.com>
>To: "'Stefan Grey'" <examplebrain@hotmail.com>, <ccielab@groupstudy.com>
>Subject: RE: Switch Vlan database.
>Date: Mon, 17 Oct 2005 07:45:07 -0400
>
>Stefan,
>
>I've run into similar situations where vlans I've created don't show up
>where I expect them to on vtp clients.
>
>I'm not 100% sure what the reason is. Maybe I was too impatient and if I
>had just waited a little longer it would show up or something else was
>going
>on - I couldn't always figure it out. Maybe, it was because I forgot to
>save my config after creating the vlans - I don't know.
>
>But, I have found one command that sometimes helps:
>
>State active. This command forces the vlan to show up in the show vlan
>brief output even if no port is assigned to that vlan on that switch.
>
>Re: root for a given vlan; This is based on STP and is totally independent
>of VTP (where vlan is create). So, just use the spantree command to make a
>given switch the root for a given vlan. Check the doc's for the command
>syntax.
>
>HTH, Tim
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>Stefan Grey
>Sent: Monday, October 17, 2005 4:21 AM
>To: ccielab@groupstudy.com
>Subject: Switch Vlan database.
>
>Hello gruop,
>
>I have got such a question. When for example I have 2 directly connected
>switches and one is in server mode second in client mode. I configure the
>vlan database on the fist one...
>
>say:
>vlanA
>vlanB
>vlanC
>vlanD
>
>the first switch has just VlanA access port. SW2 has only vlanC and vlanD
>accessport.
>and we want SW1 to become the root for VLAN B.
>
>1. When this is configured evertything is just fine. But after rebooting.
>Switch one has only vlanA in its database.. hence nothing for SW2 and not
>VlanB. I can't unerstand this since prunning is not enabled. What could it
>be?? The vlan database is stored in vlan.dat file as far as I understand
>and
>
>should be the same after rebooting what should it be??
>
>2. If in the task is not explicitely told should we set extra access port
>for VlanB. To make it a root port.
>
>and general question. I heared some advises to reboot all the devices to
>check that everything is fine during the lab. Is this also recommended for
>switches??
>
>Thanks,
>
>_________________________________________________________________
>Browse smarter with tabs - get the all-new MSN Toolbar!
>http://toolbar.msn.ie
>
>_______________________________________________________________________
>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
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:51 GMT-3