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.

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

the interface that connects to CoreSwA. 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. 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. Summary: lab length. All of the devices that you access through vLab are real Cisco routers and switches. but not HOW to do it. baseline configurations are found here for reference Device Controls: place a check next to each device. follow the steps listed under Sample Solution. Notes After taking a vLab for first time using Sample Solution in non performance mode. explanations of the WHY behind your configurations are given when needed. For your first attempt. You've got a number of tools available on the left bar of the main page to aid you in your lab. title. book references Suggested Approach: contains WHAT to do. Shut down ports 1 and 12. clicking Reload will make the gear ready to take a lab again or to take a new lab. enable port 11. 2) On Sw1. CONFIGURING EXPANDED SWITCHED NETWORKS: VLANs and VTP 1) Console into Sw1. try Suggested Approach link for a challenge. . if you become disconnected. Here are brief notes on each.Story N/A Conditions The devices in blue on the diagram are the routers and switches that you have control over. The devices in green are core devices with fixed configurations which play the role of the service provider. Nothing is simulated. 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.

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

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

your entire group could lose all connectivity if someone from another department were to delete the Engineering VLAN. If you are unsure as to which has been assigned for this lab. The commands for both types are listed here. Explanation: Interfaces on switches can be access ports. is a . Changing to transparent mode prevents this. Step 6 : Set the trunk encapsulation type on port 11 to 802. 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. VLANs created or deleted on other switches will not affect the transparent mode switch. An example of a trunk port. type both. You'll see errors for the ones that don't exist. but it won't affect your lab because the switch will simply ignore those lines. which carry traffic from multiple VLANs. You'll see errors for the ones that don't exist. both sides must match. or they can be trunk ports.Result: Explanation: In transparent mode. meaning they belong to one and only one VLAN.1Q. An example of an access port would be a connection to a PC. 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. if you were in charge of the Engineering department and created an Engineering VLAN. Explanation: Many Cisco switches can be configured to use either ISL or 802. If you are unsure as to which has been assigned for this lab. 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. as you see here. The commands for both types are listed here. On any given trunk link.1Q trunks. some switches only have the ability to use one or the other. For instance. but it won't affect your lab because the switch will simply ignore those lines. type both. However. Step 5 : Verify the VTP configuration using a show command.

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

This is because you haven’t yet assigned any ports to VLAN 11. Explanation: Normally. Step 13 : On Sw1. Step 14 : On Sw1. You'll see errors for the ones that don't exist. assign port 2. you see all of the ports listed as members except for port 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.sw1(config-vlan)# end sw1# show vlan sw1# Result: Explanation: Notice that to the right of VLAN 1. but it won't affect your lab because the switch will simply ignore those lines. Explanation: The interface is. this waiting for convergence is unnecessary. 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. to VLAN 11. configure portfast on port 2. Portfast. If you are unsure as to which has been assigned for this lab. an interface on a switch must transition from blocking into forwarding (30-50 seconds) when it first connects. Step 15 : Enter the proper show command for verifying that port 2 is now in the correct VLAN. 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. you are fine since the connection is to R1 and is not a trunk. type both. The reason port 11 is not included is because you configured it as a trunk. Action: sw1(config-if)# end . you see no ports listed. which is missing. In this step. However. an access port in VLAN 1. The commands for both types are listed here. when connecting to a PC or a router. This command changes the access port to instead belong to VLAN 11. by default. which is connected to R1. Also notice that to the right of VLAN 11. essentially disables Spanning Tree for a particular port.

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

Action: You can take this lab again if time permits. you can begin the lab.0 encapsulation frame-relay frame-relay map ip 172.5 41 broadcast no frame-relay inverse-arp .41.255.1.0 ! interface Serial1/2 description CONNECTION TO FRAME SWITCH ip address 172. The configurations for each device are listed below for reference.255.1.255.0 ! interface FastEthernet0/1 shutdown ! interface Serial1/0 shutdown ! interface Serial1/1 description CONNECTION TO R2 ip address 10.1.41. you can use the Suggested Approach link.255. You can also test your mastery of the material when you take the lab for the second time.1 255.1.1. 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.2 r1# Result: Your pings should be successful. hostname r1 ! no ip domain lookup ! interface FastEthernet0/0 description CONNECTION TO SW1 ip address 10. Instead of using the Sample Solution link which walks you through each step.255.255.1 255. Result: To take the lab a second time.0. This process takes several minutes. This provides the same steps. you first need to reset the devices back to the baseline configurations that were present at the beginning of the lab. This can be done by clicking on the Device Controls link on the left bar.1 255. and clicking the Reload button.r1(config)# end r1# ping 10. Step 20 : You have finished the lab. The routers and switches begin the lab with baseline configurations in place. Once the devices are all marked green.1. selecting all devices. but without the walkthrough.1.

41.0 clock rate 64000 ! interface Serial1/1 shutdown ! interface Serial1/2 description CONNECTION TO FRAME SWITCH ip address 172.2 255.255.2 255.255.0 encapsulation frame-relay frame-relay map ip 172.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 .41.255.255.0.1.! 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.1.1.

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 .

1.255.1.1.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 .255.0 ! ip default-gateway 10.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.2 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.1.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.1 ! line con 0 exec-timeout 30 0 logging synchronous line vty 0 4 login line vty 5 15 login ! end .1.0 ! ip default-gateway 10.8 255.