The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
Please vote in the Forum Structure Poll. Polling will close at 2PM EST on January 21, 2025.
Cisco nerds report: Implementing VTP
Locust76
Registered User regular
Registered User regular
Hello Cisco nerds!
I'm the new network admin (working on getting my CCENT/CCNA) at my company and the network here is mostly Cisco (a few old HP switches here and there, but the rest consists of about 35 Cisco switches). Up until now, we've run in VTP Transparent mode. Our network is expanding, however, and I'd like to see VTP implemented across all our Cisco switches.
Now... I understand how dangerous a bad VTP configuration can be, so I've done some reading up about it and I've even run simulations in Packet Tracer to see how a VTP Transparent network would react to the introduction of VTP, and so far things look good.
Basically, what I've done so far in the simulations is taken the Layer 3 switch at the backbone (which contains most of the VLAN configurations) and set it up on the VTP domain and set it as VTP Server. Then, I systematically switched the edge switches over to VTP Client mode (in the same domain) and checked out what happened.
Initially: nothing. The VLAN configs remained (regardless of whether or not the edge switches contained VLANs I wanted) until I added a VLAN on the server switch. Then, like magic, all switches were synchronized with the Server switch, which is, y'know, a good thing.
Does it really work like that in a real-world scenario? Even with the thought of doing the configurations on the weekend (when almost nobody's there and I have tons of time to fix any mistakes) makes my buttchecks clench up. I also just realized that we have 2 other stacks of L3 switches forming mini "cores" along the edge of the network. Would it be best to split them into their own VTP domain, or include them as clients in the grand scheme of things?
Are there any special things I need to be mindful of when planning/doing this thing in RL?
I'm the new network admin (working on getting my CCENT/CCNA) at my company and the network here is mostly Cisco (a few old HP switches here and there, but the rest consists of about 35 Cisco switches). Up until now, we've run in VTP Transparent mode. Our network is expanding, however, and I'd like to see VTP implemented across all our Cisco switches.
Now... I understand how dangerous a bad VTP configuration can be, so I've done some reading up about it and I've even run simulations in Packet Tracer to see how a VTP Transparent network would react to the introduction of VTP, and so far things look good.
Basically, what I've done so far in the simulations is taken the Layer 3 switch at the backbone (which contains most of the VLAN configurations) and set it up on the VTP domain and set it as VTP Server. Then, I systematically switched the edge switches over to VTP Client mode (in the same domain) and checked out what happened.
Initially: nothing. The VLAN configs remained (regardless of whether or not the edge switches contained VLANs I wanted) until I added a VLAN on the server switch. Then, like magic, all switches were synchronized with the Server switch, which is, y'know, a good thing.
Does it really work like that in a real-world scenario? Even with the thought of doing the configurations on the weekend (when almost nobody's there and I have tons of time to fix any mistakes) makes my buttchecks clench up. I also just realized that we have 2 other stacks of L3 switches forming mini "cores" along the edge of the network. Would it be best to split them into their own VTP domain, or include them as clients in the grand scheme of things?
Are there any special things I need to be mindful of when planning/doing this thing in RL?
Locust76 on
0