From: mdye@bevillcntr.org
Date: Wed Oct 09 2002 - 14:48:03 GMT-3
That should be exactly the problem. You can check this with the show vtp
status command.
You get and output like:
3350-FOR-CCIEs#show vtp status
VTP Version : 2
Configuration Revision : 1
Maximum VLANs supported locally : 1005
Number of existing VLANs : 6
VTP Operating Mode : Server
.... (output omitted)
In general, always configure your switches that are to be VTP servers
ON-LINE and those that are to be VTP clients OFF-LINE.
That should avoid that issue. The other thing you can do that may work is
to make a change to the VTP database on the server. (Something that does
not make any difference and even change it back) That should up the
revision number and force the client to accept the new revision.
The only other thing I have seen that problem with is wrong VTP Domain.
Keep in mind VTP domain names tend to be case sensitive.
Let me know what it turns out to be.
At 12:38 PM 10/9/02 -0400, Tim Fletcher wrote:
>I've had similar problems which I solved by changing the client to
>transparent mode, then back to client mode. Make sure you exit vlan
>database config mode between each change so they get saved. I think the
>problem is that the vlan database revisions get out of sync.
>
>-Tim
>
>On Wed, 9 Oct 2002, chenyan wrote:
>
>> hi,guys
>>
>> one 3550 connecting two 2950, all the vtp and vlan information are
configured, and the 3550 and one 2950 work fine that all the vlans created
on the 3550 are transfered to the 2950, but the other 2950 does not get the
vlan information, why? the connection between the 3550 and the 2950 are
trunked aith dot1q encapulation.
>>
>> Thanks
This archive was generated by hypermail 2.1.4 : Tue Nov 05 2002 - 08:35:43 GMT-3