Cisco vtp not updating
I’m answering the question about when using VTP in your network, which versions are risky – that’s risky is terms of how do you prevent VTP updates from ‘crossing’ a switch by explaining how each version works.There are three versions of VTP – Version 1, 2 and 3.
The problem I'm having is that the new tagged port for Vlan B isn't picking up a dhcp address.It has the ip helper defined and is working from other switches that are trunked with a different native vlan than Vlan A. Well IRS helped me determine that it's actually a VTP problem.The 3550 doesn't seem to be getting updates from the 6513. XFeature Mode Revision-------------- -------------- -----------VLAN Server 32Pruning : disabled VLANs prune eligible: 2-1000 The first thing I notice is that you are running two different versions, but I'm not certain that's the issue.The 6513 has vlan A and B defined and Vlan B has a helper address as it works on other routers that use a different Vlan for management (don't ask).Because ethernet port 47 is tagged as vlan B, shouldn't it route once it gets to the 6513 even though the trunk connecting the 3550 to the 6513 is natively tagged non-routed vlan A? non-routed, but I'll assume you mean one is allowed/defined, and the other isn't. So long as it's tagged on f0/47 (which you say it is), and so long as B is a member of the trunk (on both ends), it should go to (and through) the 6513 as you describe..the final caveat that the routing and any associated ACLs are properly defined. The trunk is a dot1q and has a native vlan of Vlan A, the isolated network.Hi it's my first time that im trying to configure a switch so im not so good right now with it Im trying to add a switch cisco catalyst 3560G to my network I read this page set the switch as a VTP Client.
I entered the mode (client), the domain and password. If i use the command "show vtp status" on the new switch this is what i get VTP Version : 2 Configuration Revision : 3 Maximum VLANs supported locally : 1005 Number of existing VLANs : 7 VTP Operating Mode : Client VTP Domain Name : [email protected] VTP Pruning Mode : Enabled VTP V2 Mode : Disabled VTP Traps Generation : Disabled MD5 digest : 0x B1 0x96 0x D1 0x22 0x84 0x44 0x76 0x6B Configuration last modified by 192.1 at 3-1-93 If i do the command on my switch that is the server, this is what i get VTP Version : running VTP1 (VTP2 capable) Configuration Revision : 59 Maximum VLANs supported locally : 1005 Number of existing VLANs : 23 VTP Operating Mode : Server VTP Domain Name : [email protected] VTP Pruning Mode : Enabled VTP V2 Mode : Disabled VTP Traps Generation : Disabled MD5 digest : 0x C7 0x60 0x7B 0x B2 0x D7 0x41 0x69 0x E8 Configuration last modified by 192.168.10.1 at 12-6-07 Local updater ID is 192.168.10.1 on interface Vl10 (lowest numbered VLAN interface found) Is there something else i need to do ?
If VTP is not updating the VLANs correctly, check to make sure the MD5 digest on all VTP domain switches is the same.
The MD5 digest is calculated using the revision number, domain name, and password to make sure the information in the VTP update can be trusted.
CCNP SWITCH Trunk Links VLAN Trunking Protocol (VTP) is a Cisco proprietary feature.
VTP is a Layer 2 messaging protocol that maintains VLAN configuration consistency by managing the addition, deletion, and renaming of VLANs on a network-wide basis.
The only way to force update this is by actually doing a VTP database change.