You are on page 1of 15

Lab: CONFIGURING EXPANDED SWITCHED NETWORKS: VLANs and VTP Lab Summary

Lab Summary

vLab Title Skills

Level Of Difficulty Course Lab Length Certification Desired Learner Outcome Desired Network Outcome Dependencies Author Vendor

336317 CONFIGURING EXPANDED SWITCHED NETWORKS: VLANs and VTP By completing the lab, you will be able to: Configure a VTP domain. Change the VTP mode set on the switch. Verify your VTP settings with show commands. Configure 802.1Q encapsulation to be used on trunk ports. Enable trunking between switches. Configure a default gateway for the switch to use. Create VLANs. Assign ports to become members of a VLAN. Configure portfast on an interface. Configure a default route. Verify your work with ping and show commands. Basic ICND2 60 minutes CCNA You will gain the skills required for the practical portion of the CCNA certification and will be able to configure and troubleshoot small Cisco networks. Working through these labs, you will gain hands-on experience and practice in implementing and operating a simple Cisco network that includes real switches, routers, and remote access technologies. Trey McMahon

Network Type Technology References

Cisco SPV2 Cisco Cisco Systems, Interconnecting Cisco Network Devices 2, Cisco Systems, Inc., Cisco authorized courseware for CCNA certification. James Boney, Cisco IOS In a Nutshell, O'Reilly, A Desktop Quick Reference for IOS on IP Networks

Lab Scenario
Scenario
Quick Start Instructions Assignment Story Conditions Notes Diagram Quick Start Instructions Once a lab has finished initializing, click on the Sample Solution link if one is available. For performance based labs, Sample Solution will not be available. IT IS IMPORTANT TO WAIT UNTIL AFTER INITIALIZATION BEFORE GOING TO THE SAMPLE SOLUTION. The reason is that during initialization, you are assigned custom IP addresses that are dynamically added to your lab instructions. This makes the lab easier to follow than the traditional method of trying to look up pod-specific information in tables. After initialization, the Sample Solution will have the correct information for your gear. To console into the routers and switches mentioned in the lab steps, click on the network diagram shown on the main page.

1. In Performance Mode.255. When the devices are ready. ping the core router at 10. 11) On Sw1. 2) On Sw1. For your first attempt. you can start the lab again. To console into routers and switches. 3) On Sw1. click on Sample Solution link if you are launching it in non performance mode . 18) On R1. 7) Set port 11 on Sw1 to trunk mode. The Suggested Approach steps are provided to test your mastery when taking a vLab for the second time. 6) Set the trunk encapsulation type on port 11 to 802.5 to be the default gateway on Sw1. IT IS IMPORTANT TO WAIT UNTIL AFTER INITIALIZATION BEFORE GOING TO SAMPLE SOLUTION.1.50.5 address. configure portfast on port 2. go to the Device Controls link and click on Reload.255. When the devices are ready.Once you have completed a lab. After initialization. create VLAN 11. Reason is that during initialization. 19) From R1. you can start the lab again. Shut down ports 1 and 12. Assignment Gain skills required for practical portion of CCNA certification by completing tasks outlined below. Once you have completed the lab. There is no need for lab report for Cisco vLabs. Once lab finishes initializing. 5) Verify the VTP configuration using a show command. 4) On Sw1. 10) Configure 10. the interface that connects to CoreSwA. verify that the correct VLAN has been added.2. click on network diagram shown on main page. 9) To verify trunk connectivity.1. set the VTP mode to transparent. set the VTP domain name to ICND. to VLAN 11.1.1. enable inter-VLAN communications by configuring a default route that points to the core router’s 10. 12) Using the show vlan command from the EXEC mode. assign port 2. 20) You have finished this lab. if you have additional time and wish to take it again. . 8) Verify the trunk configuration. enable port 11. if you have additional time and wish to take it again. Device configuration will be captured automatically by vLab platform once you either quit the lab or lab timer counts down to zero.1Q. verify that inter-VLAN routing is taking place by pinging Sw1: 10. which is connected to R1. Change the address and subnet mask on f0/0 to 10. 16) Console to R1. ping the core router’s 10.1. This is sent to email address you entered prior to starting the lab and will be used for assessment.1. 15) Enter the proper show command for verifying that port 2 is now in the correct VLAN.5 from Sw1.1.1.50. go to Device Controls link and click on Reload.1 255. you are assigned custom IP addresses that are dynamically added to your lab instructions. CONFIGURING EXPANDED SWITCHED NETWORKS: VLANs and VTP 1) Console into Sw1.5 address. 13) On Sw1. follow the steps listed under Sample Solution.50. 14) On Sw1. Sample Solution will have correct information for your gear. 17) From R1. This makes the lab easier to follow than the traditional method of trying to look up pod-specific information in tables.0.

baseline configurations are found here for reference Device Controls: place a check next to each device. Nothing is simulated.Story N/A Conditions The devices in blue on the diagram are the routers and switches that you have control over. title. . clicking clearline will allow you to reconnect without losing your configurations Diagram Suggested Approach Suggested Approach The Suggested Approach steps are provided to test your mastery when taking a vLab for the second time. You've got a number of tools available on the left bar of the main page to aid you in your lab. explanations of the WHY behind your configurations are given when needed. Here are brief notes on each. the interface that connects to CoreSwA. you can also print this out from home to use as a study guide for the CCNA certification Check Results: since the labs already have built-in verification steps. but not HOW to do it. try Suggested Approach link for a challenge. follow the steps listed under Sample Solution. enable port 11. CONFIGURING EXPANDED SWITCHED NETWORKS: VLANs and VTP 1) Console into Sw1. Shut down ports 1 and 12. if you become disconnected. clicking Reload will make the gear ready to take a lab again or to take a new lab. 2) On Sw1. The devices in green are core devices with fixed configurations which play the role of the service provider. For your first attempt. Notes After taking a vLab for first time using Sample Solution in non performance mode. book references Suggested Approach: contains WHAT to do. use this if you have already completed the lab once and wish to test your mastery in a second attempt Sample Solution: start here when taking the lab for the first time. All of the devices that you access through vLab are real Cisco routers and switches. Summary: lab length.

17) From R1. 8) Verify the trunk configuration. ping the core router’s 10.1.1. configure portfast on port 2.1.50. 5) Verify the VTP configuration using a show command. Shut down ports 1 and 12. The commands for both types are listed here. type both.255.2. 6) Set the trunk encapsulation type on port 11 to 802. If you are unsure as to which has been assigned for this lab.3) On Sw1.5 to be the default gateway on Sw1.50. Sample Solution Sample Solution Task Index Task 1 CONFIGURING EXPANDED SWITCHED NETWORKS: VLANs and VTP Task 1 CONFIGURING EXPANDED SWITCHED NETWORKS: VLANs and VTP Step 1 : Console into Sw1. 12) Using the show vlan command from the EXEC mode. 9) To verify trunk connectivity.5 address. 13) On Sw1. 18) On R1. create VLAN 11.50. 7) Set port 11 on Sw1 to trunk mode. set the VTP mode to transparent. Change the address and subnet mask on f0/0 to 10. 14) On Sw1. 4) On Sw1. You'll see errors for the ones that don't exist. 19) From R1. 11) On Sw1. 16) Console to R1.0. assign port 2.1Q.1 255. 15) Enter the proper show command for verifying that port 2 is now in the correct VLAN. to VLAN 11.1. but it won't affect your lab because the switch will simply ignore those lines. ping the core router at 10. 20) You have finished this lab. verify that inter-VLAN routing is taking place by pinging Sw1: 10.1. which is connected to R1. sw1> enable .1.1. enable inter-VLAN communications by configuring a default route that points to the core router’s 10.5 address. set the VTP domain name to ICND. Action: The vLab system has assigned you switches with either FastEthernet or GigabitEthernet ports.1.5 from Sw1. 10) Configure 10.255.1. verify that the correct VLAN has been added.

set the VTP mode to transparent. Port 12 connects to CoreSwB. It may be included in the baseline configuration for this lab. Explanation: In this lab. through port 11. If you are unsure as to which has been assigned for this lab. but it won't affect your lab because the switch will simply ignore those lines. The commands for both types are listed here. Step 4 : On Sw1. port 11 connects Sw1 to CoreSwA. This is fine. you will only be using one path. Step 2 : On Sw1. Step 3 : On Sw1. enable port 11. type both. the interface that connects to CoreSwA. Port 1 connects to CoreSwC. to connect to the core. enter interface g0/1 and interface g0/12 instead. Action: sw1(config-if)# interface f0/11 sw1(config-if)# no shut sw1(config-if)# interface g0/11 sw1(config-if)# no shut sw1(config-if)# Result: The vLab system has assigned you switches with either FastEthernet or GigabitEthernet ports. Explanation: Press ENTER after the device finishes reloading from the previous step to view the sw1> prompt. Action: sw1(config)# vtp mode transparent sw1(config)# . Action: sw1(config-if)# exit sw1(config)# vtp domain ICND sw1(config)# Result: You may see a message that the ICND domain already exists. If the interface f0/1 and interface f0/12 commands give you an error. You'll see errors for the ones that don't exist.sw1# config t sw1(config)# interface f0/1 sw1(config-if)# shut sw1(config)# interface f0/12 sw1(config-if)# shut sw1(config-if)# sw1(config)# interface g0/1 sw1(config-if)# shut sw1(config)# interface g0/12 sw1(config-if)# shut sw1(config-if)# Result: You may find that your switch has upgraded gigabit interfaces. set the VTP domain name to ICND.

type both. On any given trunk link.Result: Explanation: In transparent mode. If you are unsure as to which has been assigned for this lab. The commands for both types are listed here. The commands for both types are listed here. both sides must match. Step 6 : Set the trunk encapsulation type on port 11 to 802. Explanation: Interfaces on switches can be access ports. your entire group could lose all connectivity if someone from another department were to delete the Engineering VLAN. type both. An example of an access port would be a connection to a PC.1Q. which carry traffic from multiple VLANs. if you were in charge of the Engineering department and created an Engineering VLAN. However. Action: sw1# config t sw1(config)# interface f0/11 sw1(config-if)# switchport trunk encapsulation dot1q sw1(config-if)# interface g0/11 sw1(config-if)# switchport trunk encapsulation dot1q Result: The vLab system has assigned you switches with either FastEthernet or GigabitEthernet ports. meaning they belong to one and only one VLAN. If you are unsure as to which has been assigned for this lab. but it won't affect your lab because the switch will simply ignore those lines. but it won't affect your lab because the switch will simply ignore those lines. VLANs created or deleted on other switches will not affect the transparent mode switch. You'll see errors for the ones that don't exist. some switches only have the ability to use one or the other. or they can be trunk ports. You'll see errors for the ones that don't exist. Step 5 : Verify the VTP configuration using a show command. Step 7 : Set port 11 on Sw1 to trunk mode. Action: sw1(config)# exit sw1# show vtp status sw1# Result: Explanation: You should see that the VTP mode is set to Transparent and that the domain name is ICND. as you see here. is a . Changing to transparent mode prevents this. An example of a trunk port. Action: sw1(config-if)# int f0/11 sw1(config-if)# switchport mode trunk sw1(config-if)# int g0/11 sw1(config-if)# switchport mode trunk Result: The vLab system has assigned you switches with either FastEthernet or GigabitEthernet ports. Explanation: Many Cisco switches can be configured to use either ISL or 802.1Q trunks. For instance.

you should see that the Operational mode is trunk.1.5 from Sw1. Explanation: If the pings do not go through at first. Wait 60 seconds and try again. but it won't affect your lab because the switch will simply ignore those lines. Step 11 : On Sw1. Step 8 : Verify the trunk configuration.5 is the core router.1. The commands for both types are listed here.1. You'll see errors for the ones that don't exist. Step 9 : To verify trunk connectivity.1.connection from one switch to another switch.1. Action: sw1# ping 10.1.5 sw1(config)# Result: 10. Step 10 : Configure 10.5 sw1# Result: Your pings should be successful.1.1Q).1. ping the core router at 10. Explanation: About 4 lines down. Action: sw1# config t sw1(config)# ip default-gateway 10.5 to be the default gateway on Sw1.1. you should also see that the encapsulation is set to dot1q (IEEE 802. Below that line. create VLAN 11. Action: . Action: sw1(config-if)# end sw1# show interface f0/11 switchport sw1# show interface g0/11 switchport Result: The vLab system has assigned you switches with either FastEthernet or GigabitEthernet ports. type both.1. it may be due to the trunk being established and for convergence to take place. verify that the correct VLAN has been added. Action: sw1(config)# vlan 11 sw1(config-vlan)# Result: Step 12 : Using the show vlan command from the EXEC mode. If you are unsure as to which has been assigned for this lab.

Step 15 : Enter the proper show command for verifying that port 2 is now in the correct VLAN. This is because you haven’t yet assigned any ports to VLAN 11. which is missing. However.sw1(config-vlan)# end sw1# show vlan sw1# Result: Explanation: Notice that to the right of VLAN 1. Step 14 : On Sw1. The reason port 11 is not included is because you configured it as a trunk. an interface on a switch must transition from blocking into forwarding (30-50 seconds) when it first connects. an access port in VLAN 1. In this step. This is the preferred behavior when the port connects to another switch because there is a chance that it will create a bridging loop and cause problems. The commands for both types are listed here. Explanation: Normally. configure portfast on port 2. Step 13 : On Sw1. type both. essentially disables Spanning Tree for a particular port. Portfast. you are fine since the connection is to R1 and is not a trunk. assign port 2. but it won't affect your lab because the switch will simply ignore those lines. If you are unsure as to which has been assigned for this lab. which is connected to R1. This command changes the access port to instead belong to VLAN 11. Action: sw1(config-if)# end . You'll see errors for the ones that don't exist. when connecting to a PC or a router. Explanation: The interface is. to VLAN 11. Action: sw1(config-if)# int f0/2 sw1(config-if)# spanning-tree portfast sw1(config-if)# int g0/2 sw1(config-if)# spanning-tree portfast Result: You will see a warning stating that portfast should only be enabled on ports connected to a single host and will only work if the port is not trunking. Action: sw1# config t sw1(config)# interface f0/2 sw1(config-if)# switchport access vlan 11 sw1(config-if)# interface g0/2 sw1(config-if)# switchport access vlan 11 Result: The vLab system has assigned you switches with either FastEthernet or GigabitEthernet ports. Also notice that to the right of VLAN 11. by default. you see no ports listed. this waiting for convergence is unnecessary. you see all of the ports listed as members except for port 11.

1.50.2.50. ping the core router’s 10. Anytime you see a device blinking.1.1 255.5 r1(config)# Result: Explanation: The default route instructs R1 to send packets to 10. you will see that port 2 is now a member. Therefore. Action: r1# config t r1(config)# ip route 0.5 if all else fails.5 r1# Result: Your pings should be successful. Explanation: A VLAN is a subnet. if you were to attempt to ping Sw1.1.255.1. 10.0 subnet. Now.0.1. Step 19 : From R1. However. The core router has interfaces in both VLAN 1 (10.1. send it to the core router. cisco is the user mode password and sanfran is the enable mode password.0 subnet. The reason is that they are now in different subnets and inter-VLAN routing has not yet been configured.1 255. if a packet is destined for a route not explicitly found in the routing table.1.255. they must be on different subnets. Step 16 : Console to R1.5 address. Action: . Step 18 : On R1.0.50.1.sw1# sw1# show vlan brief Result: Looking to the right of VLAN 11.50.1.1. which acts just like the default route you just configured. VLAN 1 is the 10.0.1.255. In other words. on the 10. Sw1 has a default gateway pointing to the core router as well.1. If you have different VLANs.255.0.5) and VLAN 11 (10.50.0. At this point. Step 17 : From R1.1.50. 10.1. it knows how to get to both subnets. R1 should be able to ping it because they are in the same subnet.0.50.50.1.1. the router is in VLAN 11 so the IP address had to be changed. it is a reminder to console into a new device.1.50. Action: r1> enable r1# config t r1(config)# interface f0/0 r1(config-if)# ip address 10. The rest of the interfaces are still in VLAN 1. Action: r1(config-if)# end r1# ping 10.1. it would fail.5 address. the core router can now route packets between the two VLANs.5).1.0 subnet and VLAN 11 is the 10.2. verify that inter-VLAN routing is taking place by pinging Sw1: 10. Change the address and subnet mask on f0/0 to 10.0 0. Explanation: One of the interfaces on the core router is in the same VLAN as R1.1. the router was in VLAN 1.50. enable inter-VLAN communications by configuring a default route that points to the core router’s 10. Before you placed the Sw1 interface connecting to R1 in VLAN 11.0 r1(config-if)# Result: If you are prompted for passwords.0 10.

hostname r1 ! no ip domain lookup ! interface FastEthernet0/0 description CONNECTION TO SW1 ip address 10. Step 20 : You have finished the lab. you first need to reset the devices back to the baseline configurations that were present at the beginning of the lab.1 255.1 255. Action: You can take this lab again if time permits. and clicking the Reload button. The routers and switches begin the lab with baseline configurations in place.r1(config)# end r1# ping 10. This provides the same steps. you can begin the lab.1.1 255. The configurations for each device are listed below for reference.0 ! interface FastEthernet0/1 shutdown ! interface Serial1/0 shutdown ! interface Serial1/1 description CONNECTION TO R2 ip address 10.0 ! interface Serial1/2 description CONNECTION TO FRAME SWITCH ip address 172.255. Instead of using the Sample Solution link which walks you through each step. This can be done by clicking on the Device Controls link on the left bar. but without the walkthrough.1.41.0 encapsulation frame-relay frame-relay map ip 172. you can use the Suggested Approach link. Result: To take the lab a second time. This process takes several minutes.255.1.1.255.255. selecting all devices.2 r1# Result: Your pings should be successful.255.0.255. Check Results Check Results This vLab was designed with verification commands and detailed explanations already built in to give you a deeper understanding of the technologies.5 41 broadcast no frame-relay inverse-arp .1. Once the devices are all marked green. You can also test your mastery of the material when you take the lab for the second time.1.41.1.

2 255.41.2 255.255.0 encapsulation frame-relay frame-relay map ip 172.! interface Serial1/3 shutdown ! line con 0 exec-timeout 30 0 logging synchronous line aux 0 line vty 0 4 logging synchronous login ! end hostname r2 ! no ip domain lookup ! interface FastEthernet0/0 shutdown ! interface FastEthernet0/1 shutdown ! interface Serial1/0 description CONNECTION TO R1 ip address 10.255.0 clock rate 64000 ! interface Serial1/1 shutdown ! interface Serial1/2 description CONNECTION TO FRAME SWITCH ip address 172.1.255.1.1.255.41.5 94 broadcast no frame-relay inverse-arp ! interface Serial1/3 shutdown ! line con 0 exec-timeout 30 0 logging synchronous line aux 0 line vty 0 4 logging synchronous login ! end .0.

hostname sw1 ! spanning-tree mode pvst spanning-tree extend system-id ! interface FastEthernet0/1 description CONNECTION TO CORESWC switchport mode dynamic desirable shutdown ! interface FastEthernet0/2 description CONNECTION TO R1 switchport mode access ! interface FastEthernet0/3 switchport mode dynamic desirable ! interface FastEthernet0/4 switchport mode dynamic desirable ! interface FastEthernet0/5 switchport mode dynamic desirable ! interface FastEthernet0/6 switchport mode dynamic desirable ! interface FastEthernet0/7 switchport mode dynamic desirable ! interface FastEthernet0/8 switchport mode dynamic desirable ! interface FastEthernet0/9 switchport mode dynamic desirable ! interface FastEthernet0/10 switchport mode dynamic desirable ! interface FastEthernet0/11 description CONNECTION TO CORESWA switchport mode dynamic desirable shutdown ! interface FastEthernet0/12 description CONNECTION TO CORESWB switchport mode dynamic desirable shutdown ! interface FastEthernet0/13 switchport mode dynamic desirable ! interface FastEthernet0/14 switchport mode dynamic desirable ! interface FastEthernet0/15 switchport mode dynamic desirable ! interface FastEthernet0/16 switchport mode dynamic desirable ! interface FastEthernet0/17 .

0 ! ip default-gateway 10.1.1.1.2 255.255.1 ! line con 0 exec-timeout 30 0 logging synchronous line vty 0 4 login line vty 5 15 login ! end hostname CoreSwC ! no ip domain-lookup vtp domain ICND vtp mode transparent ! spanning-tree mode rapid-pvst spanning-tree extend system-id spanning-tree vlan 1 priority 28672 ! vlan 11 ! interface FastEthernet0/1 .1.switchport mode dynamic desirable ! interface FastEthernet0/18 switchport mode dynamic desirable ! interface FastEthernet0/19 switchport mode dynamic desirable ! interface FastEthernet0/20 switchport mode dynamic desirable ! interface FastEthernet0/21 switchport mode dynamic desirable ! interface FastEthernet0/22 switchport mode dynamic desirable ! interface FastEthernet0/23 switchport mode dynamic desirable ! interface FastEthernet0/24 switchport mode dynamic desirable ! interface GigabitEthernet0/1 switchport mode dynamic desirable ! interface GigabitEthernet0/2 switchport mode dynamic desirable ! interface Vlan1 ip address 10.255.

description CONNECTION TO SW1 switchport trunk encapsulation dot1q switchport mode trunk switchport nonegotiate ! interface FastEthernet0/2 switchport mode dynamic desirable ! interface FastEthernet0/3 switchport mode dynamic desirable ! interface FastEthernet0/4 switchport mode dynamic desirable ! interface FastEthernet0/5 switchport mode dynamic desirable ! interface FastEthernet0/6 switchport mode dynamic desirable ! interface FastEthernet0/7 switchport mode dynamic desirable ! interface FastEthernet0/8 switchport mode dynamic desirable ! interface FastEthernet0/9 switchport mode dynamic desirable ! interface FastEthernet0/10 switchport mode dynamic desirable ! interface FastEthernet0/11 switchport mode dynamic desirable ! interface FastEthernet0/12 description CONNECTION TO CORESWB switchport trunk encapsulation dot1q switchport mode trunk switchport nonegotiate ! interface FastEthernet0/13 switchport mode dynamic desirable ! interface FastEthernet0/14 switchport mode dynamic desirable ! interface FastEthernet0/15 switchport mode dynamic desirable ! interface FastEthernet0/16 switchport mode dynamic desirable ! interface FastEthernet0/17 switchport mode dynamic desirable ! interface FastEthernet0/18 switchport mode dynamic desirable ! interface FastEthernet0/19 switchport mode dynamic desirable .

255.255.! interface FastEthernet0/20 switchport mode dynamic desirable ! interface FastEthernet0/21 switchport mode dynamic desirable ! interface FastEthernet0/22 switchport mode dynamic desirable ! interface FastEthernet0/23 switchport mode dynamic desirable ! interface FastEthernet0/24 switchport mode dynamic desirable ! interface GigabitEthernet0/1 switchport mode dynamic desirable ! interface GigabitEthernet0/2 switchport mode dynamic desirable ! interface Vlan1 ip address 10.1.1.8 255.1.1 ! line con 0 exec-timeout 30 0 logging synchronous line vty 0 4 login line vty 5 15 login ! end .0 ! ip default-gateway 10.1.