Configuring Ip Unicast Layer 3 Switching On Supervisor Engine 2; Understanding How Layer 3 Switching Works; Understanding Hardware Layer 3 Switching On Pfc2 And Dfcs; Understanding Layer 3-Switched Packet Rewrite - Cisco 6500 Series Software Configuration Manual
Hide thumbs
Also See for 6500 Series:
- Configuration manual (392 pages) ,
- Configuration note (212 pages) ,
- Installation manual (194 pages)
Table of Contents
Advertisement
Understanding How Layer 3 Switching Works
Understanding Hardware Layer 3 Switching on PFC2 and DFCs
Hardware Layer 3 switching allows the PFC2 and DFCs, instead of the MSFC2, to forward IP unicast
traffic between subnets. Hardware Layer 3 switching provides wire-speed forwarding on the PFC2 and
DFCs, instead of in software on the MSFC2. Hardware Layer 3 switching requires minimal support from
the MSFC2. The MSFC2 routes any traffic that cannot be hardware Layer 3 switched.
Hardware Layer 3 switching supports the routing protocols configured on the MSFC2. Hardware
Layer 3 switching does not replace the routing protocols configured on the MSFC2.
Hardware Layer 3 switching, which runs equally on the PFC2 and DFCs to provide IP unicast Layer 3
switching locally on each module, consists of the following functions:
•
•
•
Hardware Layer 3 switching on the PFC2 supports modules that do not have a DFC. The MSFC2
forwards traffic that cannot be Layer 3 switched.
Traffic is hardware Layer 3 switched after being processed by access lists and quality of service (QoS).
Hardware Layer 3 switching makes a forwarding decision locally on the ingress-port module for each
packet and sends the rewrite information for each packet to the egress port, where the rewrite occurs
when the packet is transmitted from the Catalyst 6500 series switch.
Hardware Layer 3 switching generates flow statistics for Layer 3-switched traffic
flow statistics can be used for NetFlow Data Export (NDE). (See
Understanding Layer 3-Switched Packet Rewrite
When a packet is Layer 3 switched from a source in one subnet to a destination in another subnet, the
Catalyst 6500 series switch performs a packet rewrite at the egress port based on information learned
from the MSFC2 so that the packets appear to have been routed by the MSFC2.
Packet rewrite alters five fields:
•
•
•
•
•
Packets are rewritten with the encapsulation appropriate for the next-hop subnet.
Note
If Source A and Destination B are in different subnets and Source A sends a packet to the MSFC2 to be
routed to Destination B, the switch recognizes that the packet was sent to the Layer 2 (MAC) address of
the MSFC2.
To perform Layer 3 switching, the switch rewrites the Layer 2 frame header, changing the Layer 2
destination address to the Layer 2 address of Destination B and the Layer 2 source address to the Layer 2
address of the MSFC2. The Layer 3 addresses remain the same.
In IP unicast and IP multicast traffic, the switch decrements the Layer 3 TTL value by 1 and recomputes
the Layer 3 packet checksum. The switch recomputes the Layer 2 frame checksum and forwards (or, for
multicast packets, replicates as necessary) the rewritten packet to Destination B's subnet.
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide—Release 12.1 E
17-2
Hardware access control list (ACL) switching—For policy-based routing (PBR)
Hardware NetFlow switching—For TCP intercept, reflexive ACL forwarding decisions, Web Cache
Communication Protocol (WCCP), and server load balancing (SLB)
Hardware Cisco Express Forwarding (CEF) switching—For all other IP unicast traffic
Layer 2 (MAC) destination address
Layer 2 (MAC) source address
Layer 3 IP Time to Live (TTL)
Layer 3 checksum
Layer 2 (MAC) checksum (also called the frame checksum or FCS)
Chapter 17
Configuring IP Unicast Layer 3 Switching on Supervisor Engine 2
Chapter 33, "Configuring
Hardware Layer 3
.
NDE".)
78-14099-04
Advertisement
Table of Contents
Troubleshooting
