NETW-204 Introduction to Routing Week 3 - Configure and verify interVLAN routing using a router on a stick + Introduction + Configuring interVLAN routing with a router on a stick + Summary Introduction The Configure and verify interVLAN routing using a router on a stick module provides you with the instructions and Cisco hardware to develop your hands on skills in configuring interVLAN routing using a router as the router (aka a router on a stick). This module includes the following exercise: 1) Configuring interVLAN routing with a router on a stick Lab Diagram During your session you will have access to the following lab configuration. Depending on the exercises you may or may not use all of the devices, but they are shown here in the layout to get an overall understanding of the topology of the lab.aieieo ewan wRiwAN ee CemTook Sener rm seca 124 Connecting to your lab In this module you will be working on the following equipment to carry out the steps defined in each exercise. « NYEDGE1 + NYCORE1 * NYACCESS1 « PLABCSCOo1 Each exercise will detail which terminal you are required to work on to carry out the steps. During the boot up process an activity indicator will be displayed in the device name tab: + Black - Powered Off * Blue - Working on your request * Green - Ready to accessIf the remote terminal is not displayed automatically in the main window (or popup) click the Connect icon located in the tools bar to start your session. Copyright Notice ‘This document and its content is copyright of Practice-IT - © Practice-IT 2015. All rights reserved. Any redistribution or reproduction of part or all of the contents in any form is prohibited other than the following: 1) You may print or download to a local hard disk extracts for your personal and non- commercial use only. 2) You may copy the content to individual third parties for their personal use, but only if you acknowledge the website as the source of the material. You may not, except with our express written permission, distribute or commercially exploit the content. Nor may you transmit it or store it in any other website or other form of electronic retrieval system. Exercise 1 - Configuring interVLAN routing with a router on a stick In this exercise you will configure a router to route between VLANs enabling IP communication between them. Use your study material or your favourite search engine to find information on the following topic: * Configuring InterVLAN Routing and ISL/802.1Q Trunking on a Catalyst 2900XL/3500XL/2950 Switch Using an External Router Lab Diagram This diagram shows an enlarged version of the lab diagram in the introduction with the additional VLAN information that will be used in this exercise.Single physical link, trunked with multiple VLANs (16,17,18) NYEDGE1 NYCORE1 Configuration tasks There are a few tasks that need to be achieved to get this to work and tested. Here is the configuration task list that needs to be completed. Some of these are already pre- configured so we can focus on the key areas: Create a number of VLANs so we can test the technology (COMPLETED) Create trunk links between NYACCESS1 and NYCORE1 so we can use PLABCSCO01 as a test device (COMPLETED) Configure an IP address on NYACCESS1 so we can use this as a test device, but in a different VLAN (COMPLETED) Create a trunk link between NYCORE1 and NYEDGE1as this router will be our router on a stick Configure the correct subnets on NYEDGE1 to reflect each VLAN Test Creating the trunk interface As you will have learnt in your course, configuring a router on a stick requires the router to be connected to a trunk interface on a switch. You may have previously created trunksin the lab if you have followed this course in sequence and configuring a trunk between a router and a switch is no different (at least on the switch end of the link). Our first configuration task is therefore to create this trunk link. Step 1 Click on NYCORE1 and configure FastEthernet 1/0/1 as a trunk adding the relevant VLANs. This switch interface is where NYEDGE1 GigabitEthernet 0/0 is connected to. The VLANs that have been pre-created are Id’s 16, 17 and 18, the subnet mapping are as follows: * VLAN 16 = 192.168.16.0/24 * VLAN 17 = 192.168.17.0/24 « VLAN 18 = 192.168.18.0/24 Create a trunk link using 802.1q encapsulation type, allowing only the above VLAN id’s on the link: NYCORE1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. NYCORE1(config)#interface fastEthernet 1/0/1 NYCORE1(config-if)#switchport trunk encapsulation dotiq NYCORE1(config-if)#switchport trunk allowed vlan none NYCORE1(config-if)#switchport trunk allowed vlan add 16,17,18 NYCORE1(config-if)#switchport mode trunk Step 2 Now we have our trunk configured, we need to create the router end of the configuration. To create a trunk interface on a router, you need to create sub interfaces, each subinterface in this example relates to a VLAN. To create a sub-interface on a router, the format is: interface x/y.sub For example: FastEthernet 0/0.10 This would create sub-interface 10. It’s important to note, 10 is not the VLAN id, it is simply an interface identifier. To assign the VLAN there is an additional command to tell the router what the sub- interface VLAN id is, this comes in the form of: encapsulation dotiq x Replacing x with the VLAN id, for example: encapsulation dotiq 16 Before we put this together, one thing I would stress is that to keep things easy to read and troubleshoot, I recommend where possible to map the sub-interface identifier with the VLAN id. For example, I would recommend the following: GigabitEtherneto/o.16 = VLAN 16 GigabitEtherneto/o.17 = VLAN 17 GigabitEtherneto/o.18 = VLAN 18 Doing this in a production environment shows that you have thought about your configuration and will aide troubleshooting. Our configuration is therefore as follows:NYEDGE1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. NYEDGE1(config)#interface gigabitethernet @/0.16 NYEDGE1(config-subif)#encapsulation dot1q 16 NYEDGE1(config-subif)#ip address 192.168.16.1 255.255.255.0 NYEDGE1(config-subif)#interface gigabitethernet 0/0.17 NYEDGE1(config-subif)#encapsulation dot1q 17 NYEDGE1(config-subif)#ip address 192.168.17.1 255.255.255.@ NYEDGE1(config-subif)#interface gigabitethernet @/0.18 NYEDGE1(config-subif)#encapsulation dot1q 18 NYEDGE1(config-subif)#ip address 192.168.18.1 255.255.255.@ NYEDGE1(config-subif)#interface gigabitethernet 0/0 NYEDGE1(config-if)#no shutdown Finally we bring up the main interface using the no shutdown command. Step 3 Confirm your router configuration using the show ip interface brief command: NYEDGE1#show ip interface brief Interface IP-Address OK? Method Status Protocol Embedded-Service-Engine@/@ unassigned YES unset administratively down down GigabitEthernet@/@ unassigned YES unset up up GigabitEthernet@/@.16 192.168.16.1 YES manual up up GigabitEthernet@/0.17 192.168.17.1 YES manual upup GigabitEthernet@/@.18 192.168.18.1 YES manual up up GigabitEthernet@/1 unassigned YES unset administratively down down GigabitEthernet@/2 unassigned YES unset administratively down down Serial@/0/e unassigned YES unset administratively down down Serial@/e/1 unassigned YES unset administratively down down Step 4 Now we have our router interface and switch configured, confirm the trunk is up between the two using the show interfaces trunk command on NYCORE, we are looking for the interface that is connected to NYEDGE1 which is Fasi/o/1: NYCORE1#show interfaces trunk Port Mode Encapsulation Status Native vlan Fal/0/1 on 802.1q trunking 1 Fal1/0/22 auto n-802.1q trunking 1 Port Vlans allowed on trunk Fa1/0/1 16-18 Fal1/0/22 1-4094 Port Vlans allowed and active in management domain Fa1/0/1 16-18 Fa1/0/22 1,16-18 Port Vlans in spanning tree forwarding state and not pruned Fa1/0/1 16-18Fa1/0/22 1,16-18 As we can see in the output, Fa1/o/1 is trunking. Step 5 If at this point the configuration is successful, you should be able to ping NYACCESS1 which is on VLAN 17 at 192.168.17.10 NYEDGE1#ping 192.168.17.10 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.17.10, timeout is 2 seconds: Success rate is 10@ percent (5/5), round-trip min/avg/max = 1/2/4 ms You should also be able to ping PLABCSCOo1 at 192.168.16.10: NYEDGE1#ping 192.168.16.10 Type escape sequence to abort. Sending 5, 10@-byte ICMP Echos to 192.168.16.10, timeout is 2 seconds: Success rate is 10@ percent (5/5), round-trip min/avg/max = 1/1/4 ms If you can ping both devices you have successfully created a router on a stick!Step 6 The final test is to see if NYACCESS1 and PLABCSCOo1 can communicate between each other. On NYACCESS1, ping PLABCSCO01 at 192.168.16.10: NYACCESS1#ping 192.168.16.10 Type escape sequence to abort. Sending 5, 10@-byte ICMP Echos to 192.168.16.10, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/9 ms This final test proves that the router is in fact routing between the two VLANs/subnets. NYACCESS1 and has a default gateway of 192.168.17.1 (our router NYEDGE1) and PLABCSC001 has a default gateway of 192.168.16.1, also NYEDGE1. Summary In this module you achieved the following activities: + You configured a trunk link between NYCORE1 and NYEDGE1 * You configured sub-interfaces on NYEDGE1 to map the VLANs to a router interface + You tested your configuration and proved that you could use the router NYEDGE1 to route between the VLANs using a single interface