4 switches connected as #1 - #4 - #2 - #3
VTPv3, no password, #1, #2, #3 VTPv3 switches in server mode, #4 in client mode
#3 is already primary, adding password making the VTP domain partitioned (#3 gets isolated), increment rev number to 4 on #3
promote #2 to primary, increment rev number to 4 with different changes on #2
#1, #4 accepts rev 4 from #2
configure the correct password on #2, now domain partitioned as #1/#4 vs #2/#3. #2 loses primary (Is this because of the password change?) and accepts rev 4 from #3 (prior to this both #3 and #4 had rev 4 but the vlan database was different)
remove password on #2, now #2 reverts to its previous rev 4 originally created by itself (picked up from #2?) Why #2 already with a rev 4 database revert to another rev 4 database?
In this scenario things are going seriously wrong (same rev different digest) and there was no clear warning on what was happening.
