1

Inter-VLAN routing



: 4452675 4456830
2
Topics
Routing network traffic between VLANs
Configuring a router for routing between
VLANs
Troubleshoot inter-VLAN connectivity issues
3
LAN Design
Basic Switch
Concepts
VLANs
VTP
STP
Inter-VLAN
routing
Wireless
4
Inter VLAN routing
Switch keeps
VLANs
separate.
Router can
route between
VLANs
(subnets).
5
Traditional inter-VLAN routing
The router has one physical port for each
VLAN.
Each port has an IP address on its own
VLAN.
Routing is the same as routing between any
subnets.
6
Traditional inter-VLAN routing
PC1 has a
packet for
192.168.2.19
different
subnet
ARP request to
find MAC address
of default gateway
Send packet to
F0/0 of router

Router looks up
192.168.2.0 network
port F0/1
Router sends out
packet through F0/1 to
switchport F0/2
Switchport F0/2 is
on VLAN30 and
forwards to PC3.
7
Traditional inter-VLAN routing
Trunks
between
switches.
No trunk to
router.
No tags on
frames to
router.
8
Traditional Vs Router-on-stick (1)
Port Limits
Physical interfaces are configured to have one
interface per VLAN on the network.
On networks with many VLANs, using a single router to
perform inter-VLAN routing is not possible.
Instead, you could use multiple routers to perform inter-
VLAN routing for all VLANs if avoiding the use of
subinterfaces is a priority.

Subinterfaces allow a router to scale to
accommodate more VLANs than the physical
interfaces permit..
9
Traditional Vs Router-on-stick (2)
Performance

Because there is no contention for bandwidth on separate physical
interfaces, physical interfaces have better performance when
compared to using subinterfaces.
Traffic from each connected VLAN has access to the full bandwidth
of the physical router interface connected to that VLAN for inter-
VLAN routing.

When subinterfaces are used for inter-VLAN routing, the traffic
being routed competes for bandwidth on the single physical
interface.
On a busy network, this could cause a bottleneck for
communication.
10
Traditional Vs Router-on-stick (3)
Access Ports and Trunk Ports

Connecting physical interfaces for inter-VLAN
routing requires that the switch ports be configured
as access ports.
Subinterfaces require the switch port to be
configured as a trunk port so that it can accept
VLAN tagged traffic on the trunk link.
11
Traditional Vs Router-on-stick (4)
Cost

Financially, it is more cost-effective to use subinterfaces over
separate physical interfaces.
Routers that have many physical interfaces cost more than
routers with a single interface.
Additionally, if you have a router with many physical interfaces,
each interface is connected to a separate switch port, consuming
extra switch ports on the network.
Switch ports are an expensive resource on high performance
switches.
12
Traditional Vs Router-on-stick (5)
Complexity

Using subinterfaces for inter-VLAN routing results in a less complex
physical configuration than using separate physical interfaces,
because there are fewer physical network cables interconnecting the
router to the switch.
On the other hand, using subinterfaces with a trunk port results in a
more complex software configuration, which can be difficult to
troubleshoot.
If one VLAN is having trouble routing to other VLANs, you need to
check to see if the switch port is configured to be a trunk and verify
that the VLAN is not being filtered on any of the trunk links before it
reaches the router interface.
You also need to check that the router subinterface is configured to
use the correct VLAN ID and IP address for the subnet associated
with that VLAN.
13
Traditional Vs Router-on-stick (6)
14
Trunk to the router
You soon run out of router ports.
What about making a trunk link to the router?
A trunk link can be used with several VLANs
on the same physical port.
But each VLAN needs a different IP address.
So use subinterfaces, each with its own IP
address.
15
Router on a stick
R1 F0/0 has
subinterfaces,
one for each
VLAN.
Each has its
own IP
address.
VLAN tags on
trunk.
17
Subinterfaces
Subinterfaces take the interface name
followed by a dot and a number.
It is normal to use the VLAN number. If this
ties in with the IP address, even better.
E.g. interface f0/0.10
The subinterfaces each have an IP address.
The physical interface has no IP address
The physical interfaces needs no shutdown
18
Configuring subinterfaces
R1(config)#interface f0/0.10
R1(config-subif)#encapsulation dot1q 10
R1(config-subif)#ip address 172.17.10.1
255.255.255.0
(add any other subinterfaces)
R1(config-subif)#interface f0/0
R1(config-if)#no shutdown
19
Routing table
Subinterfaces are shown

172.17.0.0/24 is subnetted, 2 subnets
C 172.17.10.0 is directly connected,
FastEthernet0/0.10
C 172.17.30.0 is directly connected,
FastEthernet0/0.30

20
Subinterface considerations
Routers have a limited number of interfaces,
so subinterfaces help where there are many
VLANs.
Subinterfaces share the bandwidth on a
physical interface so can cause bottlenecks.
Cheaper to use subinterfaces.
Simpler physical layout but more complex
configuration with subinterfaces.
21
Configuring Traditional Inter VLAN routing
22
Configure router-on-a-stick inter VLAN routing
23
Configure router-on-a-stick inter VLAN routing
24
Configure router-on-a-stick inter VLAN routing
25
Multilayer switch
A multilayer switch can
route between VLANs.
27
Troubleshooting
Check physical connections
Check switchport VLAN assigment
Check trunking on switches
Check IP addressing and subnetting scheme
in relation to VLANs
Check router subinterface configuration
28
Troubleshooting inter VLAN
routing switch issues (1)
Incorrect VLAN
29
Troubleshooting inter VLAN
routing switch issues (2)
Not configure as a trunk
30
Troubleshooting inter VLAN
routing switch issues (3)
No Redundant link
31
Troubleshooting inter VLAN
routing router issues
Incorrect VLAN on a stick
32
Troubleshooting inter VLAN
routing IP addressing issues (1)
Incorrect IP
Addressing
33
Troubleshooting inter VLAN
routing IP addressing issues (2)
Incorrect
subnet mask
34
The End