Professional Documents
Culture Documents
Chapter 3 Case Study
Objectives:
Intro:
Ajax Enterprise wants to optimize their network and asked you to lead the project.
The Scenario:
Ajax increased the number of computers on their network and because of that, they decided to ensure
their network will support it with no impact on the performance. Ajax also has no plans to buy new devices
now; they want to use the gear they already have. After a study on Ajax network devices, you decide to
implement the topology shown below.
The topology uses 3 different VLANs to separate traffic: VLAN10, VLAN20 and VLAN30. The router R1
will route between them.
Topology:
The switch Ajax already has is a layer 2 switch. Since each VLAN will have a different IP subnet, this
switch will not be able to route layer 3 packets between the VLANs created in it. In order to route layer 3
packets, a layer 3 network device must be used.
Ajax also has a Cisco 1841 router loaded with an IOS version which supports 802.1q trunk protocol and
you decided to use it to route layer 3 packets between VLANs.
The idea is to configure R1’s fastethernet0/0 to speak 802.1q trunk protocol. This will create an 802.1q
trunk link between SW1 and R1 through which traffic from all VLANs will flow. In order to separate VLAN
traffic into R1, sub-interfaces must be created in R1. Once each VLAN has its own sub-interface, R1 will
see each VLAN as a regular interface, place its network into its routing table as a direct connected route
and will be able to route between them as usual.
When a user device needs to communicate to other user device within the same VLAN, the switch will
forward the frames with no R1’s help. When devices under different VLANs must communicate (VLAN 10
sending packets to VLAN 30, for example) the switch will use the trunk link to send the frame to R1. R1
will receive the packets via its sub-interface fastEthernet0/0.10 (sub-interface which represents VLAN 10)
and, after check its routing table, will realize that to reach the destination address, it must forward the
packet via sub-interface fastEthernet0/0.30. Even though fastEthernet0/0.10 and fastEthernet0/0.30 are
part of the same physical interface (fastEthernet0/0), from R1’s routing stand point, fa0/0.10 and fa0/0.30
are regular interfaces. This solution is called Router-on-a-stick.
Note: Router-on-a-stick is only possible if the router supports 802.1q trunk protocol.
You decide to begin the configuration by SW1. You connect the console cable to SW1 console port and
create all 3 VLANs: VLAN10, VLAN20 and VLAN30. Once the VLANs are created, you assign the switch
ports to the correct VLAN. Since port 24 will be the port connected to R1, it must be configured as an
802.1q link. The VLAN mapping to be used in SW1 is shown below:
VLAN ID Port
10 1, 2, 3, 4, 5
20 6, 7, 8, 9, 10
30 11,12,13,14,15
Trunk Link 24
Question 1:
Step 2 – Configuring R1
You connected your laptop to R1 to configure it. As stated before, interface fastEthernet0/0 must be
configured as a trunk link and the cable connected to SW1’s fa0/24 port. Also, 3 sub-interfaces must be
created in R1 to separate VLAN traffic. You also define the sub-interfaces encapsulation as 802.1q.
Note: the number at the end of the encapsulation command represents the VLAN ID and must match the
VLAN ID configured in the switch.
Step 3 – Wrapping up
Once SW1 and R1 are configured to perform router-on-a-stick, you check the user PCs and devices to
ensure they all have proper IP configuration (IP address, default gateway, subnet mask, etc) of the VLAN
it belongs. All user devices must use R1’s sub-interface representing its VLAN as default gateway.
After everything is set, you issue a few pings within the same VLAN and between different VLANs and
watch all of them flow successfully.