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.

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

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

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

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

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

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

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

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

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

255.2 255.! 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.2 255.1.255.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.0 clock rate 64000 ! interface Serial1/1 shutdown ! interface Serial1/2 description CONNECTION TO FRAME SWITCH ip address 172.41.1.0.1.0 encapsulation frame-relay frame-relay map ip 172.255.255.

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.1.255.1.1.255.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.0 ! ip default-gateway 10.2 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 .

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 .

0 ! ip default-gateway 10.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.8 255.1.1.1 ! line con 0 exec-timeout 30 0 logging synchronous line vty 0 4 login line vty 5 15 login ! end .1.255.1.