Vtp revision not updating joey lauren adams dating
You can't manually force updates because VTP configs are pushed based on the highest current VLAN database revision number.Normally, after every change to your VTP config the configuration revision number should be incremented.Processor board ID FAA0503L0P5, with hardware revision 0x01Last reset from warm-reset Processor is running Enterprise Edition Software Cluster command switch capable Cluster member switch capable8 Gigabit Ethernet/IEEE 802.3 interface(s)32K bytes of flash-simulated non-volatile configuration memory.Base ethernet MAC Address: : DD:29:7D:80Motherboard assembly number: 73-3985-07Power supply part number: 34-0940-01Motherboard serial number: FAA050309QLPower supply serial number: APQ04500145Model revision number: A0Motherboard revision number: B0Model number: WS-C3508G-XL-ENSystem serial number: FAA0503L0P5Configuration register is 0x F Below is the trunk port info from both switches.The only way to force update this is by actually doing a VTP database change.If you have a unique situation where your client switch has a higher version # than the server, you either have to increase the version on the server (through multiple changes in the DB), or reset the client's version count by switching the VTP to another value, and then back to match the existing server, which will click the client's version to 0, making it request the newest DB from the server.If a VLAN is not known to a switch, that switch cannot transfer traffic across any of its ports for that VLAN.
The 3550 trunk is using dot1q and is tagged with non-routing Vlan A.
The 3550 is set to client The 6513 is set to server Some, but not all of the Vlans show up on the 3550.3550 sho vtp status info: VTP Version : 2Configuration Revision : 8Maximum VLANs supported locally : 1005Number of existing VLANs : 27VTP Operating Mode : Client VTP Domain Name : XXXVTP Pruning Mode : Disabled VTP V2 Mode : Disabled VTP Traps Generation : Enabled MD5 digest : XXXXXXX Configuration last modified by 10.70.0.5 at ^@^@:^@^@:^@^@ - actual characters, not changed6513 vtp stat info: Version : running VTP1 (VTP3 capable)Domain Name : XXX Password : not configured Notifications: disabled Updater ID: X. Assuming the domain name is the same, and since no password is set, it would at least be one thing to look at.
The other thing to look at is to make sure the database revision number isn't set higher than the server's rev number, since it will just assume it has a more up to date db, and won't change anything.
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.