Configuring IP Unicast Routing
Configuring IP Unicast Routing
Configuring IP Unicast Routing
CH A P T E R 38
Configuring IP Unicast Routing
This chapter describes how to configure IP Version 4 (IPv4) static IP unicast routing on the Catalyst
2960-S and 2960 switch. Static routing is supported only on switched virtual interfaces (SVIs) and not
on physical interfaces. The switch does not support routing protocols.
Unless otherwise noted, the term switch refers to a standalone switch and a switch stack. A switch stack
operates and appears as a single router to the rest of the routers in the network.
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS IP
Command Reference, Volume 1 of 3: Addressing and Services, Release 12.2
This chapter consists of these sections:
• Understanding IP Routing, page 38-1
• Steps for Configuring Routing, page 38-3
• Enabling IP Unicast Routing, page 38-4
• Configuring Static Unicast Routes, page 38-5
• Monitoring and Maintaining the IP Network, page 38-5
Note When configuring routing parameters on the switch and to allocate system resources to maximize the
number of unicast routes allowed, use the sdm prefer lanbase-routing global configuration command
to set the Switch Database Management (sdm) feature to the routing template. For more information on
the SDM templates, see Chapter 10, “Configuring SDM Templates” or see the sdm prefer command in
the command reference for this release.
Understanding IP Routing
In some network environments, VLANs are associated with individual networks or subnetworks. In an
IP network, each subnetwork is mapped to an individual VLAN. Configuring VLANs helps control the
size of the broadcast domain and keeps local traffic local. However, network devices in different VLANs
cannot communicate with one another without a Layer 3 device to route traffic between the VLAN,
referred to as inter-VLAN routing. You configure one or more routers to route traffic to the appropriate
destination VLAN.
Figure 38-1 shows a basic routing topology. Switch A is in VLAN 10, and Switch B is in VLAN 20. The
router has an interface in each VLAN.
When Host A in VLAN 10 needs to communicate with Host B in VLAN 10, it sends a packet addressed
to that host. Switch A forwards the packet directly to Host B, without sending it to the router.
When Host A sends a packet to Host C in VLAN 20, Switch A forwards the packet to the router, which
receives the traffic on the VLAN 10 interface. The router checks the routing table, finds the correct
outgoing interface, and forwards the packet on the VLAN 20 interface to Switch B. Switch B receives
the packet and forwards it to Host C.
Types of Routing
Routers and Layer 3 switches can route packets in three different ways:
• By using default routing to send traffic with a destination unknown to the router to a default outlet
or destination.
• By using static routes to forward packets from predetermined ports through a single path into and
out of a network.
• By dynamically calculating routes by using a routing protocol.
The switch supports static routes; it does not support routing protocols.
A switch stack appears to the network as a single switch, regardless of which switch in the stack is
connected to a peer. For additional information about switch stack operation, see Chapter 5, “Managing
Switch Stacks.”
The stack master performs these functions:
• The MAC address of the stack master is used as the router MAC address for the whole stack, and all
outside devices use this address to send IP packets to the stack.
• All IP packets that require software forwarding or processing go through the CPU of the stack
master.
Note If you configure the persistent MAC address feature on the stack and the stack master
changes, the stack MAC address does not change for the configured time period. If the
previous stack master rejoins the stack as a member switch during that time period, the stack
MAC address remains the MAC address of the previous stack master. See the “Enabling
Persistent MAC Address” section on page 5-18.
Note The switch supports 16 user-configured static routes in addition to any directly connected routes and
default routes for the management interface. switch can have an IP address assigned to each SVI. The
number of routed ports and SVIs that you can configure is not limited by software. However, the
interrelationship between this number and the number and volume of features being implemented might
have an impact on CPU utilization because of hardware limitations. Before enabling routing, enter the
sdm prefer lanbase-routing global configuration command and reload the switch.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable IP routing.
Step 3 end Return to privileged EXEC mode.
Step 4 show running-config Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface vlan vlan_id Enter interface configuration mode, and specify the Layer 3
VLAN to configure.
Step 3 ip address ip-address subnet-mask Configure the IP address and IP subnet mask.
Command Purpose
Step 4 end Return to privileged EXEC mode.
Step 5 show interfaces [interface-id] Verify your entries.
show ip interface [interface-id]
show running-config interface [interface-id]
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip route prefix mask {address | interface} [distance] Establish a static route.
Step 3 end Return to privileged EXEC mode.
Step 4 show ip route Display the current state of the routing table to verify
the configuration.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ip route prefix mask {address | interface} global configuration command to remove a static
route. The switch retains static routes until you remove them.
When an interface goes down, all static routes through that interface are removed from the IP routing
table. When the software can no longer find a valid next hop for the address specified as the forwarding
router's address in a static route, the static route is also removed from the IP routing table.
Command Purpose
show ip route [address [mask] [longer-prefixes]] | Display the current state of the routing table.
show ip route summary Display the current state of the routing table in summary form.
show platform ip unicast Display platform-dependent IP unicast information.
show platform ip unicast {adjacency | cef-idb | counts | dhcp | failed {adjacency | arp [A.B.C.D]
| route} | loadbalance | mpaths | proxy | route | standby | statistics | table | trace} [ | {begin
| exclude | include} expression]
Note Though visible in the command-line help strings, the proxy and table keywords are not supported.
Usage Guidelines You should use this command only when you are working directly with a technical support representative
while troubleshooting a problem. Do not use this command unless a technical support representative asks
you to do so.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output
do not appear, but the lines that contain Output appear.
Note: other enabled commands are IOS PI and we do not include in our docs.