This happens whether the switch is a VTP client or a VTP server. A VTP
client can erase VLAN information on a VTP server. A typical indication that this has
happened is when many of the ports in your network go into an inactive state but continue
to be assigned to a nonexistent VLAN.
To prevent this problem from occurring, always ensure that the con?¬?guration revision
number of all switches that you insert into the VTP domain is lower than the con?¬?guration
revision number of the switches that are already in the VTP domain. You can accomplish
this by changing the VTP mode to transparent and then back to server or client. You can
also accomplish it by changing the VTP domain name and then changing it back.
All Ports Inactive After Power Cycle
Switch ports move to the inactive state when they are members of VLANs that do not exist
in the VLAN database. A common issue is all the ports moving to this inactive state after a
power cycle. Generally, you see this issue when the switch is con?¬?gured as a VTP client
with the uplink trunk port on a VLAN other than VLAN1. Because the switch is in VTP
client mode, when the switch resets, it loses its VLAN database and causes the uplink port
and any other ports that were not members of VLAN1 to become inactive.
Pages:
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151