We will be undergoing scheduled maintenance on May 20th, 2013 at 02:00 GMT.
Implementing Cisco IP Switched Networks (642-813 SWITCH) Tutorials
Basic Switch Configuration / LAB VTP Configuration
Subtitles of the Movie (Implementing Cisco IP Switched Networks (642-813 SWITCH) / Basic Switch Configuration / LAB VTP Configuration)
So in this section of the lab we are going to set up VTP. Now we've got our VLANs configured, we'll do Show VLAN just to get them up on the screen and, and review a little bit. Got our three VLANs, each with a port in them but no VTP is going out. Now I'm going to go in and set a VTP Domain Name and when I do that, a lot of stuff's going to happen really quickly. Namely that, because all of the switches have a null VTP Domain Name, when I set it on this server, it's going to synchronize out to all of the other switches on the network. And the main reason for this, is if I go back in here and do Show VTP Status again, my configuration revision is higher than anybody else on the network and I've gone and verified that myself. But if this were lower then, once I push this out, then any switches that had a configuration revision of higher than 16 would just overwrite the changes that I've done. Now how I verified that is, it's kind of a trick and, and it's not really a trick, it's working by design. If we do a Dir Flash on this guy, you'll see this file right here named VLAN.dat. Now that's where all the VLAN information is kept, that's also where all of the VTP Configuration information is kept. So if you have a switch that happens to be in a different VTP Domain and you need to bring into this VTP Domain, the best way to do that is to actually go in and delete VLAN.dat, just doing the Del Flash VLAN.dat and I'm not going to do it because I don't want to undo all of my changes. You delete the VLAN.dat, you reboot the switch, then it comes up with no VLANs, no VTP information, no nothing, it's just brain dead out of the box except for any Layer 3 information you've configured in it obviously. At which point it's a lot easier to join that switch to your VTP Domain. So let's go ahead and set this up on Core 2. So we'll do Config T and we'll type VTP and hit Question Mark. We see that we don't have very many Configuration Commands here because VTP's pretty simple at, at it's core. We're going to Set VTP Domain and we're going to say VTC Lab. Once we do that, changing the VTP Domain Name from null to VTC Lab we get a Trap Information here in the console and once we do that, let's go look at the Core Switch over here. So now if we do Show VTP Status, you'll see that it has absorbed this VTC Lab Domain Name. It still thinks it's a server but it's configuration revision is 16. If we do Show VLAN since we've not enabled pruning, it's pushed this out to the Core 1 Switch as well the Access 2 Switch, it's over here as VTC Lab and Access 1, Show VTP Stat over here and it's VTC Lab. And you see that the configuration is last modified by 10.10.1.101 which if we look back over here is Core 2, so it's actually being updated from the switch that expect it to be updated with. Now you'll notice that we're all running VTP 1 so since we have multiple servers on the network, we're going to go back to the one that's our Server Switch. Since it currently has the highest configuration revision and we'll do Config T and we'll do VTP Version 2. Once we do that, it's pushed out just as quickly and if we go back over to this guy, we see that it's now running VTP 2 whereas before it was running VTP 1, it was capable of VTP 2. The last thing we would do in a production network is go into all of these Access Switches and the Core Switch, go into Config T, do VTP Mode and we'll set the mode to Client. Setting device to VTP Client Mode, at this point, we can no longer make any VLAN changes on this Access Switch. If we go into Config and remember the command we issued up on the core, VLAN 70 for example, it tells us VTP Configuration is not allowed when this device is in Client Mode. Again working as designed and if we now go out and do Show VTP Stat, we now see that we are in Client Operating Mode. Now I won't bore you with doing that on all of the switches but it's the same song and dance you'd go through on Access 2 and Core 1 and I'll, I'll do that when I'm not actually recording. Now this is how you configure VTP information on most modern IOS's. Now if you put this GNS3 and you attempt to get a 3640 router and put a Switch Module in it and do VTP and VLAN Configuration, you'll have to actually use a different method of configuring VLANs and VTP. Now I happen to have a 2900XL which is an old brain dead switch that I keep around just for situations like this and you'll notice that on this switch, I have to actually manually go into the VLAN Database by entering the VLAN Database Command at the EXEC Mode. Once we are in VLAN Database, this is where we actually perform the VTP administrative functions, we can set it to VTP Client, set the name of the Administrative Domain et cetera, et cetera. The commands are pretty much the same although they do require a little more planning because you don't do like VTP Mode Client, you just do VTP Client or VTP Transparent. So you can't just rip a config out of a newer switch and put it into this guy, because it will just barf all over you, it will not work out like you planned. And that concludes our lab about VLAN set up and VTP Configuration.
Tutorial Information
| Course: | Implementing Cisco IP Switched Networks (642-813 SWITCH) |
| Author: | Greg Dickinson |
| SKU: | 34304 |
| ISBN: | 978-1-61866-041-1 |
| Release Date: | 2012-04-20 |
| Duration: | 8.5 hrs / 102 lessons |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
