CISCO-UATF

Objectives: Describe the VTP concept and configuration Introduction: Ajax Enterprise acquired more switches and wants to connect them to their network. They called you to accomplish the task. The Scenario: Ajax increased the number of computers on their network and decided to optimize it. After a study of Ajax network (designed by you in the past), you decided to implement the topology shown below. The topology uses 3 different VLANs to separate traffic: VLAN10, VLAN20 and VLAN30. The router R1 will route between them. A VTP domain will be created to manage the VLANs. Topology:

CCNAIII

Step 1 Creating a VTP domain Ajax bought 3 more layer 2 switches and wants to connect other areas of the company. Because all 4 switches connected to Ajax network will have ports assigned to the same VLANs, you decide to create a VTP domain to help VLAN management within Ajax network. SW1 will be the VTP server and SW2, SW3 and SW4 will be the VTP clients. Before connecting the new switches to the network, you turn them on, perform some basic configuration and configure them as VTP clients. The commands are listed below: Note: Even the output below show configuration being made under vlan database configuration mode, depending on the IOS version running on the switch, the VTP configuration must be done directly inside configuration mode.
SW1# vlan database SW1(vlan)# vtp server SW1(vlan)# vtp domain AJAX SW2# vlan database SW2(vlan)# vtp client

CISCO-UATF
SW2(vlan)# vtp domain AJAX SW3# vlan database SW3(vlan)# vtp client SW3(vlan)# vtp domain AJAX SW3# vlan database SW3(vlan)# vtp client SW3(vlan)# vtp domain AJAX

CCNAIII

Question 1: Why is it necessary to configure the switches as VTP clients before connecting them to the network?

Question 2: The VTP name AJAX was configured with capital letters in all 3 switches. Is this necessary?

Once the switches are configured, you connect the cables. VTP domains require a trunk link between the switches. You configure all trunk links between SW1-SW2, SW1-SW3 and SW1-SW4 as shown on the topology above. The commands are shown below:
SW1(config)# SW1(config)# SW1(config)# SW1(config)# SW1(config)# SW1(config)# SW1(config)# SW1(config)# SW1(config)# int fa 0/20 switchport mode trunk no shut int fa 0/21 switchport mode trunk no shut int fa 0/22 switchport mode trunk no shut

Even though Cisco switches establish trunk links by default, you connect to SW2, SW3 and SW4 to ensure their links are set to trunking mode:
SW2(config)# SW2(config)# SW2(config)# SW3(config)# SW3(config)# SW3(config)# SW4(config)# SW4(config)# SW4(config)# int fa 0/24 switchport mode trunk no shut int fa 0/24 switchport mode trunk no shut int fa 0/24 switchport mode trunk no shut

Once all trunk links are up and running, you issue a show vlan command in SW2, SW3 and SW4 and notice all VLANs created in SW1 were learnt by the new switches via VTP Domain:
SW2#sh vlan VLAN Name Status Ports ---- ----------------------- ------- -------------------------------------1 default active 10 VLAN10 active Fa0/1, Fa0/2, Fa0/3, Fa0/4, Fa0/5 20 VLAN20 active Fa0/6, Fa0/7, Fa0/8, Fa0/9, Fa0/10 30 VLAN30 active Fa0/11, Fa0/12, Fa0/13, Fa0/14, Fa0/15 1002 fddi-default active 1003 token-ring-default active 1004 fddinet-default active 1005 trnet-default active

CISCO-UATF CCNA Exploration: LAN Switching and Wireless Chapter 4 Case Study
2009 Cisco Learning Institute
VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2 ---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ -----1 enet 100001 1500 - - - - - 0 0 10 enet 100010 1500 - - - - - 0 0 20 enet 100020 1500 - - - - - 0 0 30 enet 100024 1500 - - - - - 0 0 1002 fddi 101002 1500 - 0 - - - 0 0 1003 tr 101003 1500 - 0 - - srb 0 0 1004 fdnet 101004 1500 - - - ieee - 0 0 1005 trnet 101005 1500 - - - ibm - 0 0

CCNAIII

Once the new switches have learnt the VLANs, it is time to assign ports to the VLANs and you decide to keep the same VLAN map used in SW1. The association table VLAN x Port is shown below: VLAN ID Port 10 1, 2, 3, 4, 5 20 6, 7, 8, 9, 10 30 11,12,13,14,15 Trunk Link 24 The commands are listed for future reference: SW2# SW2# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SW2(config)# interface range fastethernet 0/1 - 5 SW2(config-if)# switchport mode access SW2(config-if)# switchport access vlan 10 SW2(config-if)# no shut SW2(config)# interface range fastethernet 0/6 - 10 SW2(config-if)# switchport mode access SW2(config-if)# switchport access vlan 20 SW2(config-if)# no shut SW2(config)# interface range fastethernet 0/11 - 15 SW2(config-if)# switchport mode access SW2(config-if)# switchport access vlan 30 SW2(config-if)# end SW3(config)# interface range fastethernet 0/1 - 5 SW3(config-if)# switchport mode access SW3(config-if)# switchport access vlan 10 SW3(config-if)# no shut SW3(config)# interface range fastethernet 0/6 - 10 SW3(config-if)# switchport mode access SW3(config-if)# switchport access vlan 20 SW3(config-if)# no shut

CCNA Exploration: LAN Switching and Wireless Chapter 4 Case Study

2009 Cisco Learning Institute SW3(config)# interface range fastethernet 0/11 - 15 SW3(config-if)# switchport mode access SW3(config-if)# switchport access vlan 30 SW3(config-if)# end SW4(config)# interface range fastethernet 0/1 - 5 SW4(config-if)# switchport mode access SW4(config-if)# switchport access vlan 10 SW4(config-if)# no shut SW4(config)# interface range fastethernet 0/6 - 10

CISCO-UATF
SW4(config-if)# switchport mode access SW4(config-if)# switchport access vlan 20 SW4(config-if)# no shut SW4(config)# interface range fastethernet 0/11 - 15 SW4(config-if)# switchport mode access SW4(config-if)# switchport access vlan 30 SW4(config-if)# end Step 3 Wrapping up After everything is set, you issue a few pings and watch all of them flow successfully. Pings issued within the same VLAN flow through the trunk links as necessary. Pings issued to different VLANs are routed by R1. For more info about configuring R1 as router-on-a-stick, refer to Exploration 3 Chapter 3 Case Study.

CCNAIII