Catalyst 4500 Series Software Configuration Guide, 8.3 GLX and 8.4GLX
Configuring Switch Acceleration

Table Of Contents

Configuring Switch Acceleration

Understanding How Switch Acceleration Works

Configuring Switch Acceleration on the Switch

Enabling Switch Acceleration

Displaying Switch-Acceleration Information

Backplane Channel Module


Configuring Switch Acceleration


This chapter describes how to configure switch acceleration on the Catalyst enterprise LAN switches.

This chapter consists of these sections:

Understanding How Switch Acceleration Works

Configuring Switch Acceleration on the Switch

Backplane Channel Module


Note For complete syntax and usage information for the commands that are used in this chapter, refer to the Catalyst 4500 Series, Catalyst 2948G, Catalyst 2948G-GE-TX, and Catalyst 2980G Switches Command Reference.


Understanding How Switch Acceleration Works

The switch acceleration feature provides the following supervisor engine performance benefits:

Increased bandwidth between switch engines

Full-mesh connectivity between switch engines

Reduced internal traffic congestion

Switch acceleration, which is supported on Catalyst 4006 switches with Supervisor Engine II and on the Catalyst 4000 family Backplane Channel Module, reduces internal traffic congestion by creating a full-mesh connection between the switch engines (SEs).

Supervisor Engine II has three switch engines that switch traffic to and from the modules and the uplink ports as follows:


Note This publication refers to Switch Engine 1 as SE1, Switch Engine 2 as SE2, and Switch Engine 3 as SE3.


SE1 handles traffic for Gigabit Ethernet uplink port 1/1 and traffic between modules that are installed in the chassis.

SE3 handles traffic for Gigabit Ethernet uplink port 1/2 and traffic between modules that are installed in the chassis.

SE2 switches internal traffic and forwards traffic that is bound for the uplink ports to the correct SE for that port.

By default, there is no direct internal connection between SE1 and SE3. Traffic coming in on SE1 that is destined for SE3, or vice versa, must go through SE2, which could potentially create congestion. To avoid congestion, you can disable the uplink ports and create a direct internal link between SE1 and SE3.

Switch acceleration is supported in different configuration modes. Supervisor Engine II supports a mesh configuration with no uplink connections. With the Backplane Channel Module installed, two additional modes are supported.

Figure 36-1 shows the possible configurations.

Figure 36-1 Switch Acceleration Configuration Modes

Option A—No switch acceleration is configured (default).

Option B—Fully meshed interconnections exist between SEs; there are no Gigabit Ethernet uplink port connections.

This mode requires that you enable switch acceleration on the supervisor engine.

Option C—Fully meshed interconnections exist between SEs; there is dual-link load-balancing between SE1 and SE2 and between SE2 and SE3; there are Gigabit Ethernet uplink port connections.

This mode requires that the Backplane Channel Module is installed and that switch acceleration is not configured on the supervisor engine.

Option D—Fully meshed interconnections and multilink load balancing exist between all SEs; there are no Gigabit Ethernet uplink port connections.

This mode requires that the Backplane Channel Module is installed and that switch acceleration is configured on the supervisor engine.

Configuring Switch Acceleration on the Switch

By default, switch acceleration is disabled on the Supervisor Engine II. Before you enable switch acceleration, you must disable the two front-panel Gigabit Ethernet uplink ports on Supervisor Engine II.

Enabling Switch Acceleration

To enable switch acceleration, perform this task in privileged mode:

 
Task
Command

Step 1 

Disable front-panel Gigabit Ethernet ports.

set port disable mod_num/port_num

Step 2 

Enable switch acceleration.

set switchacceleration {enable | disable} mod-num

This example shows how to enable switch acceleration on the switch:

Console> (enable) set port disable 1/1-2
Port(s) 1/1-2 disabled.
Console> (enable) set switchacceleration enable 1
Enabling or Disabling switch acceleration may impact performance for 1-2 seconds.
Do you want to continue (y/n) [n]? y
Switch Acceleration on module 1 enabled.
Console> (enable)

This example shows how to disable switch acceleration on the switch:

Console> (enable) set switchacceleration disable 1
Enabling or Disabling switch acceleration may impact performance for 1-2 seconds.
Do you want to continue (y/n) [n]? y
Switch Acceleration on module 1 disabled.
Console> (enable)

Displaying Switch-Acceleration Information

To display the switch-acceleration status, perform this task in privileged mode:

Task
Command

Display the switch-acceleration status.

show switchacceleration mod_num


This example shows how to display the switch-acceleration status:

Console> show switchacceleration 1
Module 1 has switch acceleration enabled.
Console> 

Backplane Channel Module

The Backplane Channel Module provides multilink load balancing between the switch engines. The Backplane Channel Module also allows you to retain the Gigabit Ethernet uplinks on the supervisor engine.

The Backplane Channel Module provides the following in the default configuration mode:

Full-mesh connection between all three switch engines

Multilink load balancing between SE1 and SE2 and between SE2 and SE3

Supervisor engine Gigabit Ethernet uplink connections

As an alternative, you can configure switch acceleration on the supervisor engine to get dual-link load balancing between all three SEs.


Note If you want to keep the uplink connections, do not enable switch acceleration on the supervisor engine.


You can insert or remove a Backplane Channel Module at any time. When you remove the Backplane Channel Module, traffic might be interrupted for a short time. For minimal disruption, disable the Backplane Channel Module, and then remove it.

You do not need to configure the Backplane Channel Module because it is enabled by default.