I noticed sometimes when I setup a new switch at my desk with a production config including IP info, VTP Domain and client info and then save my config. When I get to the install site and boot the switch sometimes it saved my VTP config info and sometimes it reverts back to server mode?? VTP domain is correct though. I have been booting the switch on console to verify the VTP domain and mode before connecting to my production network. I don't see this every time and I haven't pinpointed the reason. I suspect it has something to do with the way I paste my base config to the switch. Usually I just xmodem the config over since I am mostly replacing an older switch or a RMA switch. Then make my small changes. Anyone know why the VTP mode switches back to Server after I set it to client?
-
Saving VTP Status
-
This may come down to where VTP mode is saved:
-
If a switch is set to VTP Server mode, the VTP configurations are saved to NVRAM.
-
If a switch is set to VTP Client mode, the VTP configurations are not saved to NVRAM in version 1 and 2 but only in version 3.
So if you're changing the VTP mode to client and saving your VTP configurations it could be that it's not writing to the NVRAM and therefore not saving it for reboots. It's also possible the switches are experiencing NVRAM issues preventing the VTP info save.
Another issue may be the max number of vlans supported the switch you're configuring. Sometime with too many vlans than what that switch can support, it may do something similar to what you're describing, usually switching from client to transparent.
-
-
Thank you Ronnie for the quick reply! I will check into the version number on the next one I change out.
