10Aug/11Off
VTP – Very Trying Protocol (Vlan Trunking Protocol)
The last couple of weeks I have been designing and working on a rather large switched project. Overall the topology isn't complex, it just spans a large area. The length is about 3 kilometres.
The project uses 2960S/G and 3560x model switches with SFP SM Fibre between each with redundancy in between each switch. Once spanning tree was sorted with setting priorities as required by the brief I started to implement VTP.
Working over two days I was copying the config of VTP across from a base config. I have found a few little caveats.
- VTP configs aren't displayed in Show Run. When you are making a base template for a common group of switches you must ensure you either input the information or manually add it to each switch.
- VTP Password. Make sure you have the same password across the entire domain! Enough said.
I found in hindsight it is best to configure VTP if you decide on using it before you create VLANs. Designate what switches you want to be the servers and where you want client and transparent switches. This way you won't have to deal with any issues pertaining to revision numbers or human input!
I did lose my VLAN database once due to not paying attention and placing the wrong switch as a server. Shoop! There goes some VLANs!
No wonder there are though out there who love/hate it. It's that kind of protocol!
And as always, wr mem.
Who is this guy?
About Me- Network Engineer, blogger and CCIE wannabe. I am a guest blogger on PacketPushers, my own content here at blog.ciscoinferno.net and on Twitter @pandom_
Twitterfeed
- Labbed - Rootguard (with answer key) blog.ciscoinferno.net/lab-rootguard Try your hand at stabilizing your L2 topology today. 1 day ago
- RT @fetep: Four 9s is 4.32 minutes of downtime per (30 day) month. You will not reach four 9s if it takes 10 minutes to escalate an outage. 2 days ago
- Looking at Mi-Token 2FA and now looking at you @networkjanitor , @cooperlees 2 days ago