VLANCCNA 200-301

New Switch with Higher VTP Revision Wiping VLAN Database

Presenting Symptom

After connecting a new switch to the network, all switches in the VTP domain lose their VLAN configurations, and end-user connectivity is disrupted.

Network Context

The network is a small enterprise campus with a mix of Cisco Catalyst 2960 and 3650 switches running IOS 15.x. VTP is configured in transparent mode on most switches, but one switch was recently added from a lab environment where it had a higher VTP revision number. The new switch was connected to the network without first resetting its VTP configuration.

Diagnostic Steps

1

Check VTP status on the affected switches

show vtp status
VTP Version                      : 2
Configuration Revision          : 10
Maximum VLANs supported locally : 255
Number of existing VLANs        : 5
VTP Operating Mode              : Server
VTP Domain Name                 : CCNA_LAB
VTP Pruning Mode                : Disabled
VTP V2 Mode                     : Enabled
VTP Traps Generation            : Disabled
MD5 digest                      : 0x12 0x34 ...

Look at the Configuration Revision number. If it is unexpectedly high (e.g., 10) compared to other switches, this indicates the switch has a higher revision and will propagate its VLAN database. Also check VTP Operating Mode; if it is Server or Client, it can overwrite other switches.

2

Compare VTP revision numbers across switches

show vtp status | include Configuration Revision
Configuration Revision          : 10
Configuration Revision          : 3
Configuration Revision          : 3

If one switch has a significantly higher revision number (e.g., 10) than others (e.g., 3), that switch will overwrite the VLAN database of lower-revision switches when it connects. This confirms the root cause.

3

Check VLAN database on affected switches

show vlan brief
VLAN Name                             Status    Ports
---- -------------------------------- --------- -------------------------------
1    default                          active    Fa0/1, Fa0/2, Gi0/1
10   VLAN0010                          active    
20   VLAN0020                          active    
1002 fddi-default                     act/unsup 
1003 token-ring-default               act/unsup 
1004 fddinet-default                  act/unsup 
1005 trnet-default                    act/unsup

If the VLAN list is missing expected VLANs (e.g., VLAN 100, 200), the new switch's higher revision has wiped them. This confirms the problem.

4

Check VTP domain name on the new switch

show vtp status | include Domain Name
VTP Domain Name                 : CCNA_LAB

Ensure the domain name matches the rest of the network. If it does, the switch will propagate its VLAN database. If it doesn't, VTP updates are ignored.

Root Cause

The newly added switch had a higher VTP configuration revision number than the existing switches in the same VTP domain. When connected, it propagated its VLAN database (which may have been empty or had different VLANs), overwriting the VLAN configurations on all other switches in the domain.

Resolution

1. Change the VTP mode to transparent on all switches to stop VTP propagation: configure terminal, vtp mode transparent. 2. Recreate the missing VLANs on the affected switches: vlan <vlan-id>, name <vlan-name>. 3. Reset the VTP revision number on the problematic switch by changing the domain name temporarily: vtp domain TEMP, then change back to the original domain: vtp domain CCNA_LAB. This resets the revision to 0. 4. Optionally, set VTP mode to transparent on all switches to prevent future issues.

Verification

Run 'show vtp status' on all switches to confirm the revision numbers are low (e.g., 0 or 1) and consistent. Run 'show vlan brief' to verify all required VLANs are present. Test end-to-end connectivity between devices in different VLANs.

Prevention

1. Always reset the VTP revision number on a switch before adding it to a production network by changing the VTP domain to a dummy name and back, or by setting VTP mode to transparent. 2. Use VTP transparent mode in production networks to avoid accidental VLAN overwrites. 3. Implement VTP version 3 if needed, which provides better protection against revision number conflicts.

CCNA Exam Relevance

On the CCNA 200-301 exam, this scenario appears in troubleshooting questions where a new switch causes VLAN loss. The exam tests understanding of VTP revision numbers and the impact of connecting a switch with a higher revision. Candidates must know that VTP servers and clients propagate VLAN information based on revision number, and that transparent mode does not propagate.

Exam Tips

1.

Memorize that VTP revision number is the key factor: the switch with the highest revision number overwrites others in the same domain.

2.

Remember that changing VTP domain name resets the revision number to 0.

3.

Know that VTP transparent mode does not participate in VTP updates, so it is safe for production.

Commands Used in This Scenario

Test Your CCNA Knowledge

Practice with scenario-based questions to prepare for the CCNA 200-301 exam.

Practice CCNA Questions