Here is the situation:
One switch is configured as the VTp server witn interface VLAN 1 shutdown.
Other Vlans are configured on that switch, and one of the created Vlan is the new management Vlan (let's say vlan200).
Trunking is enable on the Gig interfaces (by the way this is a 3550 with 12.1 and I am not sure which one is the Native vlan on the trunk).
A VTP domain name has been configured and no vtp password
the vlans were not created using the vlan database config mode
Here is the problem:
When another switch is added to the network, the switch does not bring up its vlan interface (the one configured for vlan200, since vlan1 is admin down).
Here is what was done in chronological order to fix the issue but I need to understand why it worked. . . I have an idea but I want to be sure:
1. new switch comes online . . .
2. configured the VTP mode to client
3. configured the VTP domain name (no password set)
4. create an interface for Vlan 200 with an ip address that does not conflict with other any ip addresses on the vlan, and do a "no shut"
5. configured the Gig port for 802.1q encapsulation and trunking mode (the gig interface shows that it is up/up)
6. do a show vtp stat to ensure that the switch is learning the vlan . . . to no avail
7. checked the interface vlan 200 and it show down/down
8. delete the originally created vlan 200 interface
9. move the switch to vtp server mode
10. re-create the interface vlan 200 . . . which now shows up/up
11. check the vtp stats to make sure the switch has learned about the other vlans . . . which it has.
12. move the switch back to client mode
I am thinking this is due to vlan 1 (or native vlan) being disabled and 802.1q not passing VTP information. I have not had a chance yet to check if both ends of the trunk had Vlan 1 or 200 set as the native Vlan or if there was a mismatch, but so far that is my best guess. The only problem with this is that if there was a mismatch, shouldn't the trunk be in a down status as opposed to up/up?
What do you guys think?
Thanks for the help