02-01-2010 07:54 AM - edited 03-06-2019 09:31 AM
I made my 9 switch stack the VTP ser
ver yesterday. Today I get VTP message that says:
Feb 1 10:35:49: %SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: MD5 digest checksum mismatch on receipt of equal revision summary on trunk: St9 (KBCSTACK01-9). I am getting this for devices in the stack. In addition I made another switch (a non-stacked switch) a VTP server as well. The revision and exisiting vlans match on both devices.
Show vtp status says:
VTP Version : running VTP2
Configuration Revision : 31
Maximum VLANs supported locally : 1005
Number of existing VLANs : 24
VTP Operating Mode : Server
VTP Domain Name : jergens
VTP Pruning Mode : Enabled
VTP V2 Mode : Enabled
VTP Traps Generation : Enabled
MD5 digest : 0x17 0x26 0x91 0x2F 0x80 0x81 0x01 0x51
*** MD5 digest checksum mismatch on trunk: St1 ***
*** MD5 digest checksum mismatch on trunk: St2 ***
*** MD5 digest checksum mismatch on trunk: St3 ***
*** MD5 digest checksum mismatch on trunk: St4 ***
*** MD5 digest checksum mismatch on trunk: St5 ***
*** MD5 digest checksum mismatch on trunk: St6 ***
*** MD5 digest checksum mismatch on trunk: St7 ***
*** MD5 digest checksum mismatch on trunk: St8 ***
*** MD5 digest checksum mismatch on trunk: St9 ***
Configuration last modified by 10.49.1.62 at 1-31-10 12:31:26
Local updater ID is 10.49.1.62 on interface Vl1 (lowest numbered VLAN interface
06-05-2013 07:03 AM
eagle1981
Does the vlan creation still resolve the problem in this IOS version?
06-05-2013 07:21 AM
It does.
Create new vlan on vtp server and md5 hashes become identical and VTP sync.
03-02-2018 02:16 PM
waw, thank you very much for this
10-02-2018 08:27 PM
09-24-2012 11:02 AM
Excellent. I had the same problem. resolved by adding another VLAN to VTP server switch. U r a champion.
06-08-2013 04:49 AM
Make a new vlan in the server so the server switch sync with all the other client switches, ofcourse your vtp version and domain+passwords should also match among all switches and bingo it will work without showing you any mismatch errors.
06-18-2013 11:18 PM
Thanks jhon,
I've also faced this issue this morning ,and simply i have just created Vlan 4 and issue resolved.
:-)
07-23-2014 07:30 AM
I was able resolve this error by briefly setting the VTP mode on the switch to server, then changing it back to transparent. This was on a C2960 in a stack running 15.0(2)SE2 code.
04-10-2018 01:42 AM - edited 04-10-2018 01:52 AM
Though this is an old thread....I dont think this is a bug. I believe the reason for this may be due to two servers with the same revision number but different vlan databases (hence wrong hash). Most ppl have solved this by adding a new VLAN on one server; this will increase the revision for that switch and push its config to all other switches but you have to be careful about losing missing VLAN information on the other server. A better solution is to figure out the miss-matched VLANs and add those on the other server so that while increasing the revision number you also maintain all the VLANs
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide