InterVLAN Routing

with Catalyst IOS

 Chapter Overview
 Communicating Between VLANs
 VLAN capable switch

 Router: External or Internal

 Router to VLAN connection

 Configuring/Verifying InterVLAN Routing

 Switch virtual interface
 Routed port
 External router and an internal route processor
 Router-on-a-stick

 Troubleshooting InterVLAN Routing

 Overview

VLANs control broadcast domain size and keep local traffic local.
 Key components of InterVLAN Routing
 Requirements for InterVLAN
Routing InterVLAN Routing Using a Route Processor

Layer 3 Switch

 VLAN capable switch

Internal

 Router: External or Route Processor

integrated within a switch

VLAN 10

VLAN 20
VLAN 30
 Router to VLAN connection
InterVLAN Routing Using a single link
InterVLAN Routing Using one link per VLAN
VLAN 20
VLAN 10

VLAN 30

VLAN 10 VLAN 20 VLAN 30

 Comparison of Layer 2 and Layer 3
Operations in the Core
Switched Core Routed Core

Optimal path selected by

routing protocol
STP
Blocked
 InterVLAN Routing
Performance and Scalability Issues

 Regardless of routing technique,access

and distribution layer switched
elements must be aligned with routing
functionality at the distribution layer.
 The distribution layer switch must be
the root of the spanning tree for each
VLAN.
Role of the Native VLAN (1)
 Trunked switches tags frames with
the appropriate VLAN number.
Untagged frames considered
members of the Native VLAN.
 Both ends of a switch-to-switch link
must have consistent native VLANs.
 If not the same, independent broadcast
domains between the VLANs no longer
exist.
 Role of the Native VLAN (2)
 Routers performing interVLAN routing using a trunk expect
tagged frames.
 Problems arise when the native VLAN is also carried by
the trunk.

 VLAN 1 is often configured with an IP address which is also

the default native VLAN on trunks.

 Solution: Insure native VLAN not trunked.

 Assign native VLAN to a dummy VLAN not used for
routing or
 Make the native VLAN ineligible for trunking and
configure router to expect untagged frames.
Trunking
 The 3550 switch supports two types of trunking
encapsulation
 802.1Q

 ISL

 The 2950 switch supports only 802.1Q trunking

Route Switch Processors
 Highest performing interVLAN routing option.

 Router card plugged into a modular switch or built into

a switch.

 Advantages and benefits:

 Router CPU power matched to switch capacity.

 Direct switch backplane access for more bandwidth.

 Easy Multi-Layer switching implementation.

 Ease of configuration and management.

 External Routers
InterVLAN Routing using a single link

 Router-on-a-Stick, Lollipop
Routing, One Armed Bandit
 Trunk Link Advantages: VLAN 10
192.168.1.0
 Saves router and switch VLAN 20
192.168.2.0
ports…saves money and
reduces complexity. Trunk
 Scales to larger number of VLAN 30
192.168.3.0
VLANs than one-link-per-VLAN
design.
Physical interface
 Trunk Link Disadvantages: FastEthernet 0/0
 Additional router overhead
Logical interface
 Older IOS versions support FastEthernet 0/0.10
ip address 192.168.1.1
limited sets of features on Logical interface
trunked interfaces and may FastEthernet 0/0.20
ip address 192.168.2.1
only support ISL trunking Logical interface

encapsulation. FastEthernet 0/0.30

ip address 192.168.3.1
 Cisco Layer 3 Feature Cards
Catalyst 6000 Family Multilayer
Router-on-a-stick most Switch Feature Card (MSFC2)
appropriate when other
options not available.
Route switch processors
generally adequate unless
a high proportion of traffic
crosses VLAN boundaries
or a large number of
gigabit or greater
interfaces are present.
Switch Fabric Module
adds switching capacity.
 Configuring InterVLAN Routing (1)
 First task to turn on switch routing functionality.
 Switch(config)# ip routing

 Switch virtual interface (most common).

 Switch#interface vlan 40

 Switch(config-if)# ip address 10.0.40.1

255.255.255.0
 Routed port (turns an Ethernet switch into an Ethernet
Router by turning off a switch port functionality).
 Switch(config)# interface fa 0/1

 Switch(config-if)# no switchport

 Switch(config-if)# ip address 10.0.1.1 255.255.255.0

 The switch port can now be used as a physical router

port for connection to an external device such as a

router.
 Configuring InterVLAN Routing (2)
 RSP(config)#ip routing
Connecting an external router to a  RSP(config)# interface fa 0/1
route switch processor  RSP(config-if)# no switchport
 RSP(config)-if# ip address
10.0.1.1 255.255.255.0
WAN  Ext(config)# interface fa0/0
Routed port  Ext(config-if)# ip address
10.0.1.2 255.255.255.0

S 0/0
Fa 0/1 Fa 0/0 Ext Router InterVLAN routing most likely achieved through a
virtual interface. As an example, VLAN 10 and VLAN
Si 20 configured on the multi-layer switch.

RSP(config)# interface vlan 10

RSP(config-if)# ip address 10.0.10.1 255.255.255.0
RSP(config)# interface vlan 20
RSP(config-if)# ip address 10.0.20.1 255.255.255.0
Don’t forget to enable a routing protocol on both the RSP and
External router.
Configuring InterVLAN Routing (3)
Router-on-a-stick configuration example

VLAN 10
192.168.1.0 VLAN 20
192.168.2.0

Trunk
VLAN 30
192.168.3.0

Physical interface
FastEthernet 0/0

Logical interface
FastEthernet 0/0.10
ip address 192.168.1.1

Logical interface
FastEthernet 0/0.20
ip address 192.168.2.1

Logical interface
FastEthernet 0/0.30
ip address 192.168.3.1
Verifying InterVLAN Routing
Configurations
 Switch# show ip route
 Switch# show ip interface
brief
Verifying interVLAN routing
 Switch# show ip interface
fastethernet module/port
 Can show if the port is

Routed port
WAN configured for routing
 Switch# show ip interface
S 0/0 fastethernet module/port
Fa 0/1 Fa 0/0 Ext Router
switchport
Si
 Either switchport information
10.0.10.0 / 24 10.0.20.0 / 24
VLAN 10 VLAN 20
will be displayed or
“Switchport: Disabled” will
indicate the port is likely
configured for routing.
 Troubleshooting InterVLAN
Routing (1)
 The same commands for verifying interVLAN routing can be
used to troubleshoot interVLAN routing.
 Check that routing is enabled.

 Check that Layer 2 VLANs and Layer 3 IP addressing are

correct and check if routing is configured for an individual
switch interface or for an entire VLAN.
 Switch# show ip interfaces brief

 Switch# show interfaces status

 Check that switch IP address is in the correct VLAN and the

gateway is set.
 Check Layer 2 problems with a ping within each VLAN and
verify connectivity with the router interface for every VLAN.
 Check Layer 3 configurations. Be sure the appropriate gateway
is set on hosts and switch management interfaces.
 Troubleshooting InterVLAN Routing (2)
 Check configurations of routing protocols.
 Switch#show ip route

 Switch#show running-config

 Check native VLAN issues.

 Do not trunk a VLAN that is also the trunk’s
native VLAN.
 Switch#show interfaces fastethernet 0/1
switchport
 Summary

 Communicating Between VLANs Requires:

 VLAN capable switch

 Router: External or Internal

 Router to VLAN connection

 The role of the native VLAN is important.

 Performance and scalability need to be considered when

planning and implementing interVLAN designs.
Presentation_ID © 2001, Cisco Systems, Inc. All rights reserved. 20