cc/td/doc/product/l3sw/8540/rel_12_0/wx5_11a
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Overview of Layer 3 Switching and Software Features

Overview of Layer 3 Switching and Software Features

This chapter provides a definition of Layer 3 switching, giving an overview and focusing on software features. It shows how the switch router fits into the network, and lists the type of interfaces used in Layer 3 switching. Also included is a list of Layer 3 switching software features with brief descriptions of selected features. This chapter includes the following sections:

Defining Layer 3 Switching

Layer 3 switching refers to a class of high-performance routers optimized for the campus LAN or intranet, providing both wirespeed Ethernet routing and switching services.

A Layer 3 switch router performs the following three major functions:

Compared to other routers, Layer 3 switch routers process more packets faster by using application-specific integrated circuit (ASIC) hardware instead of microprocessor-based engines. Layer 3 switch routers also improve network performance with two software functions--route processing and intelligent network services.

Switch Routers with Layer 3 Switching Software

You can use Layer 3 switching software features in both campus switch routers (CSR) and multiservice switch routers (MSR). You can also combine Layer 3 (packet switching) and ATM (cell switching) in the same Catalyst 8540 MSR chassis at the same time.

The following switch routers use Layer 3 switching software features:

CSR Switch Routers MSR Switch Routers

Catalyst 8540 CSR

Catalyst 8510 CSR

Catalyst 8540 CSR


Note Throughout this document, the generic term Layer 3 switching software is used to describe software features used in any of the switch routers listed above.

Network Configuration Examples

Figure 1-1 shows how the Catalyst 8500 CSR can be used as a campus backbone.


Figure 1-1: Typical Network Configuration for the Catalyst 8500 CSR

The Catalyst 8540 MSR combines Layer 3 (packet) and ATM (cell) switching on a single platform for campus and WAN networks. Figure 1-2 shows an example of a Catalyst 8540 MSR used as a campus backbone.


Figure 1-2: Typical Network Configuration for the Catalyst 8540 MSR

Layer 3 Switching Interface Types

Table 1-1 lists the interfaces supported in Layer 3 switching.


Table 1-1: Interfaces Supported in Layer 3 Switching
Interface Types Platform Ports Per Slot Max. Density

10/100 Mbps Fast Ethernet--UTP

Catalyst 8540 CSR

Catalyst 8540 MSR

16

128

10/100 Mbps Fast Ethernet--UTP

Catalyst 8510 CSR

8

32

100 Mbps Fast Ethernet--multimode fiber

Catalyst 8540 CSR

Catalyst 8540 MSR

16

128

100 Mbps Fast Ethernet--multimode fiber

Catalyst 8510 CSR

8

32

1 Gbps Gigabit Ethernet uplink

Catalyst 8540 CSR

Catalyst 8540 MSR

2

16

1 Gbps Gigabit Ethernet uplink

Catalyst 8540 CSR

Catalyst 8540 MSR

8

64

1 Gbps Gigabit Ethernet uplink

Catalyst 8510 CSR

1

4

Layer 3 Switching Software Features

This section lists Layer 3 switching software features.

Layer 1 Features
Layer 2 Bridging Features
Virtual LAN (VLAN) Features
Layer 3 Routing, Switching, and Forwarding
Supported Routing Protocols
Fast EtherChannel (FEC) Features
Gigabit EtherChannel (GEC) Features
Access Control List (ACL)
Additional Protocols and Features

About Key Features

This section briefly describes key features supported in Layer 3 switching software.

Spanning Tree Protocol

Spanning-Tree Protocol (STP) is a bridge protocol that enables a learning bridge to dynamically work around loops in a network topology by creating a spanning tree. Bridges exchange BPDU messages with other bridges to detect loops, and then remove the loops by shutting down selected bridge interfaces.

STP is a standardized technique for maintaining a network of multiple bridges or switches. When the topology changes, STP transparently reconfigures bridges and switches to avoid the creation of loops by placing ports in a forwarding or blocking state. Each VLAN is treated as a separate bridge and a separate instance of STP is applied to each.

STP parameters are set for each VLAN. For each spanning-tree instance, you configure a set of global options with a set of port parameters. The port parameter list contains only ports that are members of a given VLAN. A maximum of 64 spanning-tree instances are supported, one for each VLAN.

To configure STP, see the IOS Command Reference publication.

Integrated Routing and Bridging

Integrated routing and bridging (IRB) allows you to route a given protocol between routed interfaces and various bridge groups or between bridge groups within a single router. Multiple ports in the switch router can reside in one bridge group with one IP address and be routed to other switch router interfaces with different IP addresses.

Specifically, local or unroutable traffic is bridged among the bridged interfaces in the same bridge group, while routable traffic is routed to other routed interfaces or bridge groups.

Layer 3 switching software supports IRB for IP and IPX only.

Here are some examples of when to use IRB:

For example, when you are migrating a bridged network to a routed network, or when the remote site does not have routing capabilities, you can use the switch router to interconnect the bridged and routed networks.

To configure IRB, see the "Configuring IRB" section.

Virtual LANs

A virtual LAN (VLAN) facilitates the configuration of switches and routers according to logical rather than physical topologies. Using VLANs, a network administrator can combine any collection of LAN segments within an internetwork into an autonomous user group, which appears as a single LAN. VLANs logically segment the network into different broadcast domains so that packets are switched only between ports within the VLAN. Typically, a VLAN corresponds to a particular subnet, although not necessarily.

Layer 3 switching software supports up to 255 VLANs per system. Because routing will take place, each VLAN is assumed to terminate at the switch router. Since this might not necessarily be the case, integrated routing and bridging (IRB) is also supported. To configure IRB, see the "About Integrated Routing and Bridging" section.

To configure VLANs, you define a subinterface at the interface, define a bridge group, and map a VLAN to the subinterface.

To configure VLANs, see the "About Virtual LANs" section.

Inter-Switch Link and 802.1Q Encapsulation

Layer 3 switching software supports Inter-Switch Link and 802.1Q VLAN encapsulation over all media, including Ethernet, Fast Ethernet, Gigabit Ethernet, Fast EtherChannel, and GigaChannel. This allows the switch router to be installed in environments in which ISL is the primary VLAN tagging scheme, or in networks with 802.1Q high-speed routing. The Layer 3 switch router can also route between ISL and 802.1Q stations.

The switch router identifies frames from end stations as belonging to a particular VLAN. VLAN encapsulation is accomplished with the Cisco ISL trunking protocol.

ISL and 802.1Q encapsulation use packet tagging to multiplex VLANs across a single physical link, while maintaining strict adherence to the individual VLAN domains.

The frame is a standard Ethernet, encapsulated and tagged with a VLAN ID. Because it is a standard frame, repeater hubs and transparent bridges forward it as they would any other frame. Any 10/100 Mbps Ethernet link can support these encapsulation methods. The link can run at either half duplex or full duplex.


Note The four adjacent ports (such as 0 through 3, or 4 through 7) on a 10/100 interface must all use the same VLAN encapsulation, i.e., either 802.1Q and native, or ISL and native.

To configure encapsulation over EtherChannel, see the "About Encapsulation Over EtherChannel" section.

Gigabit EtherChannel

Gigabit EtherChannel (GEC) allows grouping of multiple Gigabit Ethernet ports into a single multigigabit logical EtherChannel link. GEC establishes a high-bandwidth connection between two Catalyst switch devices. Thus, the members of the bundle can be on different interface modules, providing flexibility and fault tolerance.

You can bundle up to four gigabit Ethernet connections as one logical link, which can provide up to 8-Gb aggregate capacity on up to 64-Gb EtherChannel logical links. If a failure of any one link is detected, the packets are switched on the remaining active links in the EtherChannel.

No dependencies are placed on which ports to configure in the channel. The ports can exist on the same or on different interface modules in the chassis.

Gigabit EtherChannel uses a source-destination IP address load-balancing scheme for up to four ports in a channel group. Each channel group has its own IP address.When a packet is queued to exit out of the port channel interface, the last two bits of the IP source and destination address determine which interface in the channel the packet takes.

As with all EtherChannel technologies, the traffic load is shared across all links within the bundled ports; convergence occurs within one second of a Gigabit EtherChannel failure.


Note IP/IPX filtering at Layer 3 with the ACL daughter card is not supported for GEC.

To configure the EtherChannel, see "EtherChannel Configurations."

Fast EtherChannel

Fast EtherChannel (FEC) establishes a high-bandwidth connection between two Layer 3 switch devices. You can use up to four Fast Ethernet connections as one Layer 3 forwarding path, which can provide up to 800 Mbps full duplex aggregate capacity. If link detection determines a failure of any one link, the packets are switched on the remaining active links in the FEC.

No dependencies are placed on which ports to configure in the channel. The ports can exist on the same or on different interface modules in the chassis.

Fast EtherChannel uses a source-destination IP address load-balancing scheme for up to four ports in a channel group. Each channel group has its own IP address.When a packet is queued to exit out of the port channel interface, the last two bits of the IP source and destination address determine which interface in the channel the packet takes.


Note IP/IPX filtering at Layer 3 with the ACL daughter card is not supported for FEC.

To configure the EtherChannel, see "EtherChannel Configurations."

Distributed Hardware Forwarding

Layer 3 switching software employs a distributed architecture in which the control path and data path are relatively independent. The control path code, such as routing protocols, runs on the route processor, whereas most of the data packets are forwarded by the Ethernet interface module and the switching fabric.

Each interface module includes a microcoded processor that handles all packet forwarding. The following are the main functions of the control layer between the routing protocol and the firmware datapath microcode.

QoS-Based Forwarding

Quality of service (QoS) includes technologies such as Resource Reservation Protocol (RSVP) and weighted fair queuing (WFQ), which help control bandwidth, network delay, jitter, and packet loss in networks that become congested. In the switch router, QoS-based forwarding sorts traffic into a small number of classes and marks the packets accordingly. The QoS identifier provides specific treatment to traffic in different classes, so that different quality of service is provided to each class.

Frame and packet scheduling and discarding policies are determined by the class to which the frames and packets belong. For example, the overall service given to frames and packets in the premium class will be better than that given to the standard class; the premium class is expected to experience lower loss rate or delay.

The switch router has QoS-based forwarding for IP traffic only. The implementation of QoS forwarding is based on local administrative policy and IP precedence. The mapping between the IP precedence field and the QoS field determines the delay priority of the packet.

For a summary of QoS features and related commands, see "Quality of Service Feature Summary."

Network Class Redundancy

Layer 3 switching features hot-swappable Ethernet interface modules. The redundancy of Cisco IOS software provides key network features, such as Hot Standby Router Protocol (HSRP), routing protocol convergence with Routing Information Protocol (RIP), Open Shortest Path First (OSPF), Enhanced Interior Gateway Routing Protocol (EIGRP), Fast EtherChannel, and load sharing across equal cost Layer 3 paths and spanning trees (for Layer 2 based networks).

Remote Monitoring

Layer 3 switching software support the first four remote monitoring (RMON) groups.

RMON is a network management protocol for gathering network information and monitoring traffic data within remote LAN segments from a central location. RMON allows you to monitor all nodes and their interaction on a LAN segment. RMON, used in conjunction with the SNMP agent in the router, allows you to view both the traffic that flows through the router and segment traffic not necessarily destined for the router. Layer 3 switching software combines RMON alarms and events with existing MIBs so you can choose where monitoring will occur.

To configure RMON, see "Router and Network Monitoring Commands" in the Cisco IOS Configuation Fundamentals Command Reference publication.

Port-Based Snooping

Port-based snooping augments the RMON events and alarms. Port-based snooping, or mirroring, lets you transparently mirror traffic from an individual source port or multiple source ports to a destination port. Typically, the destination port has a network analyzer or RMON probe attached.

In addition to having multiple source ports active, multiple snooping sessions can operate simultaneously. You can specify whether the source ports are mirrored for transmit, receive, or both. Up to ten ports may be monitored, but the combined bandwidth of the source ports must not exceed the bandwidth of the destination port.

To configure port-based snooping, refer to the "About Port Snooping" section.

Access Control Lists

Access control lists (ACLs) provide a tool for network control and security, giving you the ability to filter packet flow into or out of router interfaces. They are sometimes called filters. You can use ACLs to limit network traffic and restrict network use by certain users or devices. ACLs can be configured for all routed network protocols (IP, Appletalk, Novell IPX) to filter packets for the protocol as they pass through a router. You create access lists for each protocol you wish to filter, per router interface. For some protocols, you create one access list to filter inbound traffic, and one access list to filter outbound traffic.

When creating access lists, you define criteria to apply to each packet processed by the router; the router decides whether to forward or block the packet based on whether or not the packet matches the criteria in your list. Packets that do not match any criteria in your list will be automatically blocked by the implicit "deny all traffic" criteria statement at the end of every access list.

For more information about ACLs, see Access Control Lists: Overview and Guidelines in the Cisco IOS Security Configuration Guide.

The specific instructions for creating access lists and applying them to interfaces vary from protocol to protocol. Configuration of Layer 3 switching access lists is identical to the configuration methods currently employed on all Cisco routers.

To find complete command information for access lists, see the Network Protocol Command Reference publication in the Cisco IOS documentation.

Standard MAC address filtering is supported at Layer 2. IP/IPX filtering is supported at Layer 3 through the use of an ACL daughter card. For a list of supported ACLs, see the "Access Control List (ACL)" section.


Note IP/IPX filtering at Layer 3 with the ACL daughter card is not supported for GEC, FEC, BVI, or the eight-port Gigabit Ethernet interface. The ACL daughter card does not support dynamic and reflexive ACLs, IPX extended ACLs, or ACL logging. UDP flooding is disabled on routers with an ACL daughter card.

Load Balancing

A router that employs load balancing can distribute traffic over all its network ports that are the same distance from the destination address. Load balancing increases the utilization of network segments, thus increasing effective network bandwidth.

Layer 3 switching software uses source + destination-based load balancing, an enhanced version of the Cisco IOS software per-destination load balancing. Essentially, this method takes certain bits from the source and destination IP addresses and maps them into a path.

Using this method has the following two benefits:

Layer 3 switching software supports load balancing for two equal-cost paths and uses the destination and source address pair to perform load balancing. Per-packet load balancing is not supported.

Cisco IOS Routing Protocols

Layer 3 switching software provides a comprehensive suite of routing protocols based on Cisco IOS software. The following are supported routing protocols by networking protocol.

IP Networks IPX Networks AppleTalk Networks

RIP

RIP-2

OSPF

IGRP

EIGRP

IPX RIP

EIGRP

RTMP

EIGRP

AURP

Many of the Cisco IOS routing protocol features, such as route redistribution and load balancing over equal cost paths (for OSPF and EIGRP) are supported. Configuration of these routing protocols is identical to the configuration methods currently employed on all Cisco routers.

To configure network and routing protocols, see "Networking Protocol Configurations."

Cisco Discovery Protocol

Cisco Discovery Protocol (CDP) is a device-discovery protocol that is both media and protocol independent. CDP is available on all Cisco products, including routers, switches, bridges, and access servers. Using CDP, a device can advertise its existence to other devices and receive information about other devices on the same LAN. CDP enables Cisco products to exchange information with each other regarding their MAC addresses, IP addresses, and outgoing interfaces. CDP runs over the data link layer only, thereby allowing two systems that support different network-layer protocols to learn about each other.

Each device configured for CDP sends periodic messages to a multicast address. Each device advertises at least one address at which it can receive Simple Network Management Protocol (SNMP) messages.

Hot Standby Router Protocol

The Hot Standby Router Protocol (HSRP) provides high network availability by routing IP traffic from hosts on Ethernet networks without relying on the availability of any single router. This feature is particularly useful for hosts that do not support a router discovery protocol (such as the Intermediate System-to-Intermediate System Interdomain Routing Protocol) and do not have the functionality to switch to a new router when their selected router reloads or loses power.

Devices that are running the HSRP detect a failure by sending and receiving multicast User Datagram Protocol (UDP) "hello" packets. When HSRP detects that the designated active router has failed, the selected backup router assumes control of the HSRP group's MAC and IP addresses. (You can also select a new standby router at that time.)

The chosen MAC address and IP addresses are unique and do not conflict with any others on the same network segment. The MAC address is selected from a pool of Cisco MAC addresses. Configure the last byte of the MAC address by configuring the HSRP group number. You also configure the unique virtual IP address. The IP address must be specified on a single router within the same group. When the HSRP is running, it selects an active router and instructs its device layer to listen on an additional (dummy) MAC address.

Layer 3 switching software supports HSRP over 10/100 Ethernet, Gigabit Ethernet, FEC, GEC, and BVI (Bridge-Group Virtual Interface).

Cisco Express Forwarding

Layer 3 switching software features Cisco Express Forwarding (CEF). CEF is advanced Layer 3 IP switching technology. CEF optimizes network performance and scalability for networks with large and dynamic traffic patterns, such as the Internet, on networks characterized by intensive Web-based applications, or interactive sessions. Although you can use CEF in any part of a network, it is designed for high-performance, highly resilient Layer 3 IP backbone switching.

CEF manages route distribution and forwarding by distributing routing information from the route processor (RP) to the individual Ethernet interface modules. This technology, used within the Internet, provides scalability in large campus core networks. CEF provides Layer 3 forwarding based on a topology map of the entire network, resulting in high-speed routing table lookups and forwarding.

One of the key benefits of CEF in the Layer 3 switching is its routing convergence. Since the forwarding information base (FIB) is distributed to all interface modules, whenever a route goes away or is added, the FIB updates that information and provides it to the interface modules. Thus, RP interrupts are minimized. The interface modules receive the new topology very quickly and reconverge around a failed link based on the routing protocol being used.

Caution Cisco strongly recommends that you do not issue any CEF configuration commands. The CEF default settings should not be altered, and doing so may adversely affect the performance of your system.

UDP Turbo Flooding

Layer 3 switching supports User Datagram Protocol (UDP) turbo flooding using wirespeed switching technology. In IP internetworks, most broadcasts are UDP broadcasts. A directed broadcast is sent to a specific network or a series of networks. A flooded broadcast is sent to every network.

The UDP turbo flooding feature uses the spanning tree algorithm to forward broadcasts in a controlled manner. When a switch router is configured for UDP broadcast flooding, Ethernet broadcasts are flooded out to all of the Fast Ethernet and Gigabit Ethernet interfaces in a configured bridge group.

Bridging is enabled on each router interface for the sole purpose of building the spanning tree. The spanning tree prevents loops by stopping a broadcast from being forwarded out an interface on which the broadcast was received. The spanning tree also prevents packet duplication by placing certain interfaces in the blocked state (so that no packets are forwarded) and other interfaces in the forwarding state (so that packets that need to be forwarded are forwarded).

To enable UDP turbo flooding, the switch router must be running software that supports transparent bridging, and bridging must be configured on each interface that is to participate in the flooding. If bridging is not configured for an interface, the interface receives broadcasts, but the switch router does not forward those broadcasts and does not use that interface as a destination for sending broadcasts received on a different interface.


Note UDP turbo flooding is disabled on routers with an ACL daughter card.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Aug 2 15:25:55 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.