In VTP world, VTP server is VLAN in the network communications management concentration points. Every time you create a new VLAN in VTP server, the VLAN is automatically propagated to the switches in the same VTP domain. Think of as a single autonomous system or individual collection shares the same VTP domain for VLAN switching. For example you have a large network of campus construction in the University. Design of three-layer model of the building will have a core of access and distribution. In this design, the distribution switch a VTP server. In most cases, the VTP server chassis switches or switch stack to provide redundancy to access converter.
Create a VLAN on the distribution switches will allow all exchangers access other access switches in the same VLAN as the different floors of the building, so you do not have 3 different switches, distribution and access to the two examples given in the create the VLAN on switch.
VTPv2 is available in large commercial network in the campus core VTPv2 is capable of transmitting up to 1005 VLAN, but once you hit the ceiling in VTP VLAN will need to migrate to the VTP version 3 to allow for the 4095 VLAN propagation.
There are currently three VTP version; this is a fairly new version of VTP version 3 offers more than one or two major advantages.
VTP version 1 was originally released this technology is configured as a VTP Server enables you to Exchange, VTP client, VTP transparent switch (4-11 discussion in a lab) and VTP mode off, completely disable VTP on CatOS switches.
VTP version 2 is not a lot different from v1 VTPv2 including support for token ring VLAN and VTP pruning. If these features are not needed in the network you don't need to start with a version upgrade to version two.
VTP version 3 on the other hand there has been a significant advantage over its predecessors, both to the most advantageous feature of modern network are VTP v3 supports the entire IEEE VLAN range 1-4095, also private VLAN information dissemination capacity. VTP v3 also gives a better administrative control by allowing you to configure the VTP domain which devices can update other devices the VLAN topology view. You can now select the VTP is opened on a per trunk basis to open or close the VTP and VTP server is now the primary and backup servers.
Step back now, ask yourself if someone else inserted and later databases with the same VTP domain and VLAN information entirely different network switches what's going to happen. The answer is very simple, you have a network of VLAN into the barrel as you change on all the switches, and pulled them out, new additions, and so on. When switches and ports to the VLAN is deleted it is at the time the specific VLAN, port access shut down. All in all, if this happens on your watch and its your fault you better update your resume.
But don't worry, there is hope!! The same VTP password, you can help prevent harmful VTP Server switch in the network. By using the VTP password matches the switch is a VTP server only if the password of the client.
VTP domain can be a unique location, but there is a domain name, is special, VTP domain: Null, this domain name is basically without a domain name, its blank and null object that represents the domain name. When it is changed, however you cannot change it back to Null.
In this lab, you will familiarize yourself with the following command;
Lab Instruction:
Step 1. Configure SW1 and SW2 and SW3 is configured as a VTP server as a VTP client. Settings for Cisco on all three switches in the VTP domain name.
Configuring VTP and VTP domains by using VTP mode ModeType VTP domain and the domain name is shown below; set the VTP domain, please keep in mind that before this must be set the VTP mode, if you set the VTP domain on a client-side exchanger. If you need to change you must set its transparent VTP domain and then change the name, and/or password and then switch back to the VTP mode client.
SW1 con0 is now available
Press RETURN to get started.
SW1>enable
SW1#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
SW1(config)#vtp mode server
Device mode already VTP SERVER.
SW1(config)#vtp domain CISCO
Changing VTP domain name from NULL to CISCO
SW1(config)#
SW2 con0 is now available
Press RETURN to get started.
SW2>enable
SW2#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
SW2(config)#vtp domain CISCO
Domain name already set to CISCO.
SW2(config)#vtp mode client
Setting device to VTP CLIENT mode.
SW2(config)#
SW3 con0 is now available
Press RETURN to get started.
SW3>enable
SW3#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
SW3(config)#vtp domain CISCO
Domain name already set to CISCO.
SW3(config)#vtp mode client
Setting device to VTP CLIENT mode.
SW3(config)#
Step 2. Develop configured on the VTP servers by using the name of VLAN 10, and verify that it is correctly propagated to SW2 and SW3.
To accomplish this goal, you need to create a VLAN in VTP server, in this case is the SW1. Create VLAN as you would on any other VLAN, Cisco Catalyst series switches shown below;
SW1(config)#vlan 10
SW1(config-vlan)#name Development
SW1(config-vlan)#end
SW1#
0 comments:
Post a Comment