Packet Tracer CCNA Prep: Inter-VLAN Routing
In this practice lab, we are going to investigate inter-VLAN routing using Packet Tracer. I am assuming every reader of this article has fundamental knowledge about VLAN otherwise you can check my previous article on Inter-VLAN here.
As we know, VLANs subdivided LAN into different groups and Inter-VLAN routing is required to communicate with each other. In the below topology, we will first create VLAN and then apply the router-on-a-stick method for inter-VLAN communication.
From the topology above, you can see we created VLAN 10 and VLAN 20. In order to apply the router-on–a-stick method for Inter-VLAN communication, we will have to create sub-interfaces on fast-Ethernet interface of the router c. Remember we will only create as many sub-interfaces for as many VLANs we are using in our topology. In this case we are using two VLANs, so we will create two sub-interfaces for both VLANs. After that we will apply encapsulation on those sub-interfaces.
Tasks to Perform:
1. You need to configure the specified VLANs for Switch ACS
2. Perform router-on-a-stick method for inter-VLAN communication so Hosts H1.1, H1.2 and H2.1, H2.2 can successfully ping each other.
Note: You need to configure only Switch ACS & router C to complete the task
The following subnets are available to implement this solution:
Hosts H1.1, H1.2, H2.1, H2.2 are configured with the correct IP address and default gateway. Switch ACS uses Cisco as the enable password.
At this point, we have completed the steps to enable inter-VLAN communication. But what if we have 100s of VLAN in a network? We have to create hundreds of sub-interfaces, which is not a feasible solution. The issue can be resolved by creating SVI (Switched Virtual Interface) and for that we need an L3 switch as you read in my previous article on inter-VLAN communication.
Tasks to perform inter-VLAN routing using SVI are:
You need to configure the illustrated VLANs and SVI on SwitchX so that Hosts H1.1, H1.2, H2.1, H2.2 can successfully ping the server S1. To complete this task, you need to configure VLAN port assignments or create trunk links. Don’t try to use static or default routing. All routes must be learned via EIGRP 10 routing protocol.
Note: You do not have access to router C. Router C is correctly configured.
Hosts H1.1, H1.2, H2.1, and H2.2 are configured with the correct IP address and default gateway.
SwitchX uses Cisco as the enable password.
Routing must only be enabled for the specific subnets shown in the diagram. This lab is complete when you can demonstrate IP connectivity between each of the user VLANs and the external server network, and between the switch management VLAN and the server network.
Note: I have enclosed a solution file for verification or to use as a reference to clear your doubts.
In this Practice CCNA Lab you can use Packet Tracer (Ver 5.3 & above) to troubleshoot a simulated network that was designed and configured to support two VLANs and a separate server network. Inter-VLAN routing is provided by an external router in a router-on-a-stick configuration as well as SVI configuration. However, the network is not working as designed and complaints from your users do not provide much insight into the source of the problems. You must first define what is not working as expected, and then analyze the existing configurations to determine and correct the source of the problems.
Latest posts by Afazuddin Ahamed (see all)
- CCNA Prep: Introduction to WAN - November 27, 2013
- CCNA Prep: Route Summarization—A Need for a Routing Table - October 28, 2013
- Packet Tracer CCNA Prep: Inter-VLAN Routing - October 7, 2013