Implementing Inter-VLAN Routing

Describing Routing Between VLANs

Inter-VLAN Routing with External Router

• Single trunk link carries traffic for multiple VLANs to and

from router.
Inter-VLAN Routing
External Router Configuration Commands

Configure on subinterface
• encapsulation dot1Q (or isl) 10
• ip address 10.10.1.1 255.255.255.0
Verify
• show vlan 10
• show ip route
Inter-VLAN Routing on External Router:
802.1Q Trunk Link
Inter-VLAN Routing on External Router:
ISL Trunk Link
Verifying Inter-VLAN Routing

The ping command tests connectivity to remote hosts.

Verifying the Inter-VLAN Routing
Configuration

Router#show vlan

• Displays the current IP configuration per VLAN

Router#show ip route

• Displays IP route table information

Router#show ip interface brief

• Displays IP address on interfaces and current state of interface

Explaining Multilayer Switching
Layer 2 Switch Forwarding Process
Logical Packet Flow for a
Multilayer Switch
 IP Unicast Frame and Packet Rewrite

Incoming IP Unicast Packet

Rewritten IP Unicast Packet

CAM Table

• Requires an exact
match on all bits
• Matching is a binary
operation: 0 or 1
• Provides very high-
speed lookups
TCAM Table

• Matches only significant

values
• Matches based on three
values: 0, 1, or X (either)
• Masks used to wildcard some
content fields
Summary

• A router on a stick can be used to route between VLANs

using either ISL or 802.1Q as the trunking protocol.
• A router on a stick requires subinterfaces, one for
each VLAN.
• Verify inter-VLAN routing by generating IP packets between
two subnets.
• Multilayer switches can forward traffic at both Layer 2 and
Layer 3.
• Multilayer switches rewrite the Layer 2 and Layer 3 header
using tables held in hardware.
Implementing Inter-VLAN Routing

Enabling Routing Between VLANs on a

Multilayer Switch
Layer 3 SVI
SVI on a Multilayer Switch

Configure
• ip routing
• interface vlan 10
– ip address 10.1.1.1 255.255.255.0
• router eigrp 50
– network 10.0.0.0
Verify
• show ip route
Configuring Inter-VLAN Routing
Through an SVI

Step 1 : Configure IP routing.

Switch(config)#ip routing

Step 2 : Create an SVI interface.

Switch(config)#interface vlan vlan-id

Step 3 : Assign an IP address to the SVI.

Switch(config-if)#ip address ip-address mask

Step 4 : Configure the IP routing protocol if needed.

Switch(config)#router ip_routing_protocol <options>

Routed Ports on a Multilayer Switch (Cont.)
Routed Ports on a Multilayer Switch

• Physical switch port with Layer 3 capability

• Not associated with a VLAN
• Requires removal of Layer 2 port functionality

Configure
• ip routing
• interface fa0/1
– no switchport
– ip address 10.3.3.1 255.255.255.0
• router eigrp 50
– network 10.0.0.0
Configuring a Routed Port

Step 1 : Configure IP routing.

Switch(config)#ip routing

Step 2 : Create a routed port.

Switch(config-if)#no switchport

Step 3 : Assign an IP address to the routed port.

Switch(config-if)#ip address ip-address mask

Step 4 : Configure the IP routing protocol if needed.

Switch(config)#router ip_routing_protocol <options>

Summary

• SVI is a VLAN of switch ports represented by one interface to

the routing system.
• Specific commands are used to configure and verify routing
on multilayer switch interfaces.
• The interface vlan command creates the SVI.
• A routed port has Layer 3 attributes.
• A routed port requires the removal of Layer 2 port
functionality with the no switchport command.
• To receive dynamic updates, a routing protocol is required.
Implementing Inter-VLAN Routing

Deploying CEF-Based Multilayer Switching

Layer 3 Switch Processing

In Layer 3 switches, the

control path and data path
are relatively independent.
• The control path code,
such as routing
protocols, runs on the
route processor.
• Data packets are
forwarded by the
switching fabric.
Layer 3 Switch Processing (Cont.)

Layer 3 switching can occur at two different locations

on the switch.
• Centralized switching: Switching decisions are made on the
route processor by a central forwarding table.
• Distributed switching: Switching decisions can be made on a
port or line-card level.
Layer 3 switching takes place using one of these two
methods:
• Route caching: A Layer 3 route cache is built in hardware as
the switch sees traffic flow into the switch.
• Topology-based switching: Information from the routing
table is used to populate the route cache, regardless
of traffic.
CEF-Based Multilayer Switches

• CEF caches routing information in the FIB table

and Layer 2 next-hop addresses in the adjacency
table.
Multilayer Switch Packet Forwarding Process

• Some IP packets cannot be

processed in hardware.
• If an IP packet cannot be
processed in hardware, it is
processed by the Layer 3
engine.
CEF-Based MLS Lookups

1. Layer 3 packets initiate TCAM lookup.

2. The longest match returns adjacency with rewrite information.
3. The packet is rewritten per adjacency information and forwarded.
ARP Throttling
CEF-Based MLS Operation
Configuring and Verifying CEF

Configuring CEF
• ip cef (enabled by default)
• ip route-cache cef (only on VLAN interface)
Verifying CEF
• show ip cef fa 0/1 detail
• show adjacency fa 0/1 detail
 Enabling CEF

The commands required to enable CEF are platform

dependent:
• On the Cisco Catalyst 4000 switch
Switch(config-if)#ip cef

• On the Cisco Catalyst 3550 switch

Switch(config-if)#ip route-cache cef
 Verifying CEF

Switch#show ip cef [type mod/port | vlan_interface] [detail]

Switch# show ip cef vlan 11 detail

IP CEF with switching (Table Version 11), flags=0x0

10 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 0
13 leaves, 12 nodes, 14248 bytes, 14 inserts, 1 invalidations
0 load sharing elements, 0 bytes, 0 references
universal per-destination load sharing algorithm, id 4B936A24
2(0) CEF resets, 0 revisions of existing leaves
Resolution Timer: Exponential (currently 1s, peak 1s)
0 in-place/0 aborted modifications
refcounts: 1061 leaf, 1052 node

Table epoch: 0 (13 entries at this epoch)

172.16.11.0/24, version 6, epoch 0, attached, connected

0 packets, 0 bytes
via Vlan11, 0 dependencies
valid glean adjacency
Common CEF Problems

• Is ideal switching method (CEF, DCEF) in use?

• Are CEF tables complete and accurate?
 Verify Layer 3 Switching

Switch#show interface {{type mod/port} | {port-channel

number}} | begin L3

Switch#show interface fastethernet 3/3 | begin L3

L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 12 pkt, 778 bytes mcast
L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
4046399 packets input, 349370039 bytes, 0 no buffer
Received 3795255 broadcasts, 2 runts, 0 giants, 0 throttles
.....
Switch#
 Displaying Hardware Layer 3 Switching
Statistics

Switch#show interfaces {{type mod/port} | {port-channel

number}} include switched

Switch#show interfaces gigabitethernet 9/5 | include switched

L2 Switched: ucast: 8199 pkt, 1362060 bytes - mcast: 6980 pkt, 371952 bytes
L3 in Switched: ucast: 3045 pkt, 742761 bytes - mcast: 0 pkt, 0 bytes mcast
L3 out Switched: ucast: 2975 pkt, 693411 bytes - mcast: 0 pkt, 0 bytes
 Adjacency Information

Switch#show adjacency [{{type mod/port} |

{port-channel number}} | detail | internal | summary]

Switch#show adjacency gigabitethernet 9/5 detail

Protocol Interface Address
IP GigabitEthernet9/5 172.20.53.206(11)
504 packets, 6110 bytes
00605C865B82
000164F83FA50800
ARP 03:49:31
 Debugging CEF Operations

Switch#debug ip cef {drops | access-list | receive |

events | prefix-ipc | table}

• Displays debug information for CEF

Switch#debug ip cef {ipc | interface-ipc}

• Displays debug information related to IPC in CEF

Switch#ping ip

• Performs an extended ping

How to Troubleshoot CEF
Summary

• Layer 3 switching is high-performance packet switching

in hardware.
• MLS functionality can be implemented through CEF.
• CEF uses tables in hardware to forward packets.
• Specific commands are used to enable and verify
CEF operations.
• Commands to enable CEF are platform dependent.
• CEF problems can be matched to specific solutions.
• Specific commands are used to troubleshoot and solve
CEF problems.
• Ordered steps assist in troubleshooting CEF-based
problems.
Module Summary

• An external router can be configured to route packets

between the VLANs on a Layer 2 switch.
• Multilayer switches allow routing and the configuration of
interfaces to pass packets between VLANs.
• CEF-based multilayer switching facilitates packet switching
in hardware.