Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Catalyst 6500 Series Switches

Catalyst 6500 Series Switch Content Switching Module (CSM) Installation and Configuration Note Software Release 1.2

Downloads

Table Of Contents

Catalyst 6000 Family Content Switching Module Installation and Configuration Note

Contents

Overview

Features

Front Panel Description

Status LED

RJ-45 Connector

Operation Mode

Client-to-CSM-to-Server Traffic Flow

Safety Overview

System Requirements

Memory Requirements

Hardware Supported

Environmental Requirements

Power Requirements

Software Requirements

Required Tools

Installing the Content Switching Module

Preparing to Install the CSM

Installing the CSM

Verifying the Installation

Using the Command-Line Interface

Accessing Online Help

Upgrading to a New Software Release

Upgrading from the Supervisor Engine Bootflash

Upgrading from a PCMCIA Card

Upgrading Over the Network

Configuring the Content Switching Module

Configuring VLANs

Configuring Client-Side VLANs

Configuring Server-Side VLANs

Configuring Server Farms

Configuring Real Servers

Configuring Policies

Configuring Maps

Configuring Sticky Groups

Configuring Virtual Servers

Configuring TCP Parameters

Configuring Dynamic Feedback Protocol

Configuring Redirect Virtual Servers

Configuring Client NAT Pools

Configuring Server NAT

Writing and Restoring Configurations

Configuration Examples

Single Subnet (Bridge) Mode Configuration

Secure (Router) Mode Configuration

Fault-Tolerant Configuration

Configuring HSRP

Configuring Probes for Health Monitoring

Commands Available to all Probe Configurations

HTTP Probe

ICMP Probe

TCP Probe

FTP, SMTP, and Telnet Probe

DNS Probe Submode

Configuring Route Health Injection

Understanding RHI

RHI Overview

Routing to VIP Addresses Without RHI

Routing to VIP Addresses With RHI

Understanding How the CSM Determines VIP Availability

Understanding Propagation of VIP Availability Information

Configuring RHI for Virtual Servers

Regulatory Standards Compliance

Translated Safety Warnings

Safety Information Referral Warning

Wrist Strap Warning

Blank Faceplate Installation Requirement Warning

Qualified Personnel Warning

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone


Catalyst 6000 Family Content Switching Module Installation and Configuration Note

Product Number: WS-X6066-SLB-APC

This publication contains the procedures for installing and configuring the Catalyst 6000 family Content Switching Module (CSM).

This publication does not contain the instructions to install the Catalyst 6000 family switch chassis. For information on installing the switch chassis, refer to the Catalyst 6000 Family Installation Guide.

Note For translations of the warnings in this publication, see the "Translated Safety Warnings" section.

Contents

This publication consists of these sections:

•Overview

•Safety Overview

•System Requirements

•Required Tools

•Installing the Content Switching Module

•Verifying the Installation

•Upgrading to a New Software Release

•Configuring the Content Switching Module

•Writing and Restoring Configurations

•Configuration Examples

•Configuring Probes for Health Monitoring

•Configuring Route Health Injection

•Regulatory Standards Compliance

•Translated Safety Warnings

•Related Documentation

•Obtaining Documentation

•Obtaining Technical Assistance

Overview

The CSM provides high-performance connections between network devices and server farms (groups of real servers) based on Layer 4 through 7 packet information. Clients connect to the CSM by supplying the virtual IP address (VIP) of the virtual server. The CSM is configured to handle VIP address connections. When a client initiates a connection to the virtual server, the CSM chooses a real server (a physical device that is assigned to a server farm) for the connection based on configured load-balancing algorithms and policies.

Representing server farms as virtual servers facilitates scalability and availability. The addition of new servers and the removal or failure of existing servers can occur at any time without affecting the virtual server's availability.

Sticky connections limit traffic to individual servers. These connections are configured so that multiple connections from the same client are stuck to the same real server using source IP addresses, source IP subnets, cookies, secure socket layer (SSL), or redirected using the Hypertext Transfer Protocol (HTTP) requests. Policies manage traffic by defining where to send client requests for information Configuring server load balancing requires that you know the following:

•Network topology you are using in your installation.

•Real server IP addresses.

•The Domain Name Server (DNS) must have an entry for the CSM VIPs (if you want them to be reached through names).

•Each virtual server's IP address.

Note You cannot run Cisco IOS server load balancing software on the same switch as the CSM.

Note The CSM runs on Cisco IOS Release 12.1(6)E or later. If you are using a Supervisor Engine 2, you must use Cisco IOS Release 12.1(8a)E or later. For more information, see the "System Requirements" section.

Caution You can use the Multilayer Switch Feature Card (MSFC), internal to the Catalyst 6000 family switch, to route traffic on either the client side or the server side of the CSM, but not both simultaneously.
Caution The WS-X6066-SLB-APC Content Switching Module is not fabric enabled.

These sections describe the CSM:

•Features

•Front Panel Description

•Operation Mode

•Client-to-CSM-to-Server Traffic Flow

Features

Table 1 describes the features of the CSM.

Table 1 Content Switching Module Features 

Feature
Description

Management

Standard Cisco IOS command-line interface

 

Management interface integrated with host platform

Load-Balancing Algorithms

Weighted round-robin

 

Weighted least connections

 

Connection high/low watermarks

 

Source address-based hashing algorithm

Flow and URL Identification

URL regular expression match

 

Cookie regular expression match

 

SSL1 session ID match

 

Source IP address

 

Standard ACLs

Security

Source IP address and URL expression match and AC entry match

Statistics

Packets through normal and special switching

 

Connections created, established, destroyed, current, and timed out

 

Failed server connections

 

Layer 4 load-balanced decisions and rejected connections

 

Layer 7 load-balanced decisions and rejected connections

 

Layer 4 and Layer 7 rejected connections

 

Checksum failures

 

Redirect and FTP connections

 

MAC frames

Health Monitoring

TCP, HTTP, ICMP, Telnet, FTP

Other Features

SSL session ID, cookie and source IP address-based sticky connections

 

Fragmented IP frames support

 

MTU2 of 9000

 

Load and availability reporting supporting remote monitoring and management

 

High availability preventing service disruptions

 

Redundant modules configured for fault-tolerance support

1 SSL = Secure Socket Layer

2 MTU = Maximum Transmission Unit


Front Panel Description

The CSM front panel features are shown in Figure 1.

Figure 1 Content Switching Module Front Panel

Note The RJ-45 connector is covered by a removable plate.

Status LED

When the CSM powers up, it initializes various hardware components and communicates with the supervisor engine. The Status LED on the CSM shows the dialog with the supervisor engine and the results of the initialization.

Note For more information on the supervisor engine LEDs, refer to the Catalyst 6000 Family Module Installation Guide.

During the normal initialization sequence, the status LED changes from Off to Red, Orange, and then Green. Table 2 describes the status LED operation.

Table 2 Content Switching Module Status LED 

Color
Description

Off

•The module is waiting for the supervisor engine to grant power.

•The module is not online.

•The module is not receiving power, which could be caused by the following:

–Power is not available to the CSM.

–Module temperature is over the limit1 .

Red

•The module is released from reset by the supervisor engine and is booting.

•If the boot code fails to execute, the LED stays red after power up.

Orange

•The module is initializing hardware or communicating with the supervisor engine.

•A fault occurred during the initialization sequence.

•If the module fails to download its Field Programmable Gate Arrays (FPGAs) on power up, it still proceeds with the rest of the initialization sequence and is granted module online status from the supervisor engine, but the LED stays orange.

•If the module is not granted module online status from the supervisor engine, the LED stays orange. This problem could be caused by the supervisor engine detecting a failure in an external loopback test that it issued to the CSM.

Green

•The module is operational; the supervisor engine has granted module online status.

Green to Orange

•The module is disabled through the supervisor engine CLI 2 using the set module disable mod command.

1 Enter the show environment temperature mod command to display the temperature of each of four sensors on the CSM.

2 CLI = command-line interface.


RJ-45 Connector

The RJ-45 connector on the front panel provides a connection point for a management station or test device. The RJ-45 connector is covered by a removable plate. Typically, this connector is used by field engineers to perform testing and to obtain dump information.

Operation Mode

Clients and servers communicate through the CSM using Layer 2 and Layer 3 technology in a specific VLAN configuration. (See Figure 2.) Clients connect to the client side VLAN and servers connect to the server side VLAN. Servers and clients can exist on different subnets. Servers can also be located one or more Layer 3 hops away and connect to the server-side VLAN through routers.

A client sends a request that arrives on one of the module's VIP addresses. The CSM forwards this request to a server that can satisfy the request. The server then forwards the response to the CSM. The CSM forwards the response to the client.

When the client-side and server-side VLANs are on the same subnets, you can configure the CSM in single subnet (bridge) mode. For more information, see the "Single Subnet (Bridge) Mode Configuration" section.

When the client- and server-side VLANs are on different subnets, you can configure the CSM to operate in a secure (router) mode. For more information, see the "Secure (Router) Mode Configuration" section.

You can set up a fault-tolerant configuration in either the secure (router) or single subnet (bridged) mode using redundant CSMs. For more information, see the "Fault-Tolerant Configuration" section. Using multiple VLANs, single subnet (bridge) mode and secure (router) mode can coexist in the same CSM.

Figure 2 Content Switching Module and Servers

Client-to-CSM-to-Server Traffic Flow

This section describes how the traffic flows between the client and server in a CSM environment. (See Figure 3.)

Figure 3 Client-to-Content Switching Module-to-Server Traffic Flow

Note The numbers in Figure 3 refer to the steps in the following procedure.

When you enter a request for information by entering a URL, the traffic flow is as follows:

Step 1 You enter a URL. (For example, in Figure 3 you enter www.fox.com.)

Step 2 The client contacts a DNS server to locate the IP address associated with the URL you entered.

Step 3 The DNS server sends the IP address of the virtual IP (VIP) to the client.

Step 4 The client uses that IP address (CSM VIP) to send the HTTP request to the CSM.

Step 5 The CSM receives the request with the URL, makes a load balancing decision, and selects a server. For example, in Figure 3, the CSM selects a server (X server) from the www.fox.com server pool, replacing its own VIP address with the address of the X server and forwards the traffic to the X server.

Step 6 The CSM performs the Network Address Translation (NAT).

Safety Overview

Safety warnings appear throughout this publication in procedures that, if performed incorrectly, may harm you. A warning symbol precedes each warning statement.

Warning This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. To see translations of the warnings that appear in this publication, refer to the "Translated Safety Warnings" section in this document.

Waarschuwing

Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de hoogte te zijn van standaard maatregelen om ongelukken te voorkomen. Voor vertalingen van de waarschuwingen die in deze publicatie verschijnen, kunt u het gedeelte "Translated Safety Warnings" (Vertalingen van veiligheidsvoorschriften) raadplegen in dit document.

Varoitus

Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien ehkäisykeinoista. Tässä julkaisussa esiintyvien varoitusten käännökset löydät tämän asiakirjan "Translated Safety Warnings" (käännetyt turvallisuutta koskevat varoitukset).

Attention

Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers posés par les circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions d'avertissements figurant dans cette publication, consultez la section « Translated Safety Warnings » (Traduction des avis de sécurité) de ce document.

Warnung

Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren und der Standardpraktiken zur Vermeidung von Unfällen bewußt. Übersetzungen der in dieser Veröffentlichung enthaltenen Warnhinweise finden Sie im Abschnitt "Translated Safety Warnings" (Übersetzung der Warnhinweise) in diesem Dokument.

Avvertenza

Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche standard per la prevenzione di incidenti. La traduzione delle avvertenze riportate in questa pubblicazione si trova nella documento "Translated Safety Warnings" (Traduzione delle avvertenze di sicurezza) nel presente documento.

Advarsel

Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig praksis når det gjelder å unngå ulykker. Hvis du vil se oversettelser av de advarslene som finnes i denne publikasjonen, kan du se i avsnittet "Translated Safety Warnings" [Oversatte sikkerhetsadvarsler] i dette dokumentet.

Aviso

Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar danos físicos. Antes de começar a trabalhar com qualquer equipamento, familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer práticas comuns que possam prevenir possíveis acidentes. Para ver as traduções dos avisos que constam desta publicação, consulte a secção "Translated Safety Warnings" - "Traduções dos Avisos de Segurança" neste documento.

¡Advertencia!

Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considerar los riesgos que entraña la corriente eléctrica y familiarizarse con los procedimientos estándar de prevención de accidentes. Para ver una traducción de las advertencias que aparecen en esta publicación, consultar la sección titulada "Translated Safety Warnings" que aparece en este documento.

Varning!

Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till personskada. Innan du utför arbete på någon utrustning måste du vara medveten om farorna med elkretsar och känna till vanligt förfarande för att förebygga skador. Om du vill se översättningar av de varningar som visas i denna publikation, se avsnittet "Translated Safety Warnings" [Översatta säkerhetsvarningar] i detta dokument.


Warning Before you install, operate, or service the system, read the Site Preparation and Safety Guide. This guide contains important safety information you should know before working with the system.

Warning Only trained and qualified personnel should be allowed to install or replace this equipment.

System Requirements

Before you install the CSM into the Catalyst 6000 family switch, make sure your Catalyst 6000 family switch meets the hardware and software requirements listed in this section.

Caution You cannot run Cisco IOS server load-balancing software on the same switch as the CSM.
Caution You can use the MSFC, internal to the Catalyst 6000 family switch, to route traffic on either the client side or the server side of the CSM, but not both simultaneously.

Memory Requirements

The CSM memory is not configurable.

Hardware Supported

Before you can use the CSM, you must have a Supervisor Engine 1A with an MSFC and a Policy Feature Card (PFC), or a Supervisor Engine 2 with an MSFC, and any module with ports to connect server and client networks. The PFC is required for the VLAN access control list (VACL) capture functionality.

Caution The WS-X6066-SLB-APC Content Switching Module is not fabric enabled.

Product Number
Product Description
Minimum
Software Version
Recommended
Software Version
IOS Release
Content Switching Module
 

WS-X6066-SLB-APC with Supervisor Engine 1A

Content Switching Module

1.1(1)

1.1(1) or higher

12.1(6)E or 12.1(7)E

WS-X6066-SLB-APC with Supervisor Engine 1A

Content Switching Module

1.1(1)

1.2(1) or higher

12.1(8)E

WS-X6066-SLB-APC with Supervisor Engine 2

Content Switching Module

1.2(1)

1.2(1)

12.1(8a)E

Console Cable
 

72-876-01

Console Cable

Not applicable

Not applicable

Not applicable

Accessory Kit
 

800-05097-01

Accessory kit (contains the Console Cable)

Not applicable

Not applicable

Not applicable


Environmental Requirements

The CSM operates in temperatures from 0o to 40o C (32o to 104o F). The module can withstand, without damage, nonoperating temperatures from -40o to 70o C (-40o to 158o F).

The CSM can operate in relative humidity from 10 to 90 percent (noncondensing) and can withstand, without damage, nonoperating relative humidity of 5 to 95 percent (noncondensing).

Power Requirements

You can place the CSM in any slot in the Catalyst 6000 family chassis except for the slots occupied by the supervisor engine and the standby supervisor engine. The CSM operates on power supplied by the chassis.

Note Slot 1 is reserved for the supervisor engine. Slot 2 can contain an additional supervisor engine in case the supervisor engine in slot 1 fails. If a redundant supervisor engine is not required, you can insert the CSM in slots 2 through 6 on the 6-slot chassis, in slots 2 through 9 on a 9-slot chassis, or slots 2 through 13 on the 13-slot chassis.

Software Requirements

Catalyst 6000 family CSM software release 1.1(1) requires Cisco IOS Release 12.1(6)E or 12.1(7)E.

Catalyst 6000 family CSM software release 1.2(1) requires Cisco IOS Release 12.1(8a)E or later only.

CSM Software Release
Software Part Number
Hardware
Cisco IOS Release
Added Features

1.1(1)

SC6k-SLB-APC-1.1

Supervisor Engine 1A with MSFC and PFC

12.1(6)E or
12.1(7)E

Initial Release

1.2(1)

SC6K-1.2-CSM

Supervisor Engine 1A with MSFC and PFC

12.1(8a)E

Supervisor Engine 2 support

1.2(1)

SC6K-1.2-CSM

Supervisor Engine 2 Module with MSFC 2

12.1(8a)E

Supervisor Engine 2 support


Required Tools

This section describes the tools and requirements you need to install the CSM.

Note Before installing the CSM, you must install the Catalyst 6000 family switch chassis and at least one supervisor engine. For information on installing the switch chassis, refer to the Catalyst 6000 Family Installation Guide.

These tools are required to install the CSM into the Catalyst 6000 family switch:

•Flat-blade screwdriver

•Wrist strap or other grounding device

•Antistatic mat or antistatic foam

Caution Whenever you handle the supervisor engine or switching modules, always use a wrist strap or other grounding device to prevent electrostatic discharge (ESD). See the "Installing the Content Switching Module" section for more information.

Installing the Content Switching Module

To install the CSM into the Catalyst 6000 family switch, perform the steps in the following sections:

•Preparing to Install the CSM

•Installing the CSM

•Verifying the Installation

Preparing to Install the CSM

Before installing the CSM, make sure that the following are available:

•Catalyst 6000 family switch chassis

•Servers that are connected to the Catalyst 6000 family switch through a bridged or a routed connection

•Management station that is available through a Telnet or a console connection to perform configuration tasks

Installing the CSM

This section describes how to install the CSM into the Catalyst 6000 family switch.

Note All modules, including the supervisor engine (if you have redundant supervisor engines), support hot swapping. You can add, replace, or remove modules without interrupting the system power or causing other software or interfaces to shut down. For more information about hot-swapping modules, refer to the Catalyst 6000 Family Module Installation Guide.

To install the CSM into the Catalyst 6000 family switch, perform these steps:

Step 1 Make sure you take the necessary precautions to prevent ESD damage.

Warning During this procedure, wear grounding wrist straps to avoid ESD damage to the card. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.

Step 2 Choose a slot for the CSM. See Figure 4 for slot numbers on a Catalyst 6000 family switch.

Note Slot 1 is reserved for the supervisor engine. Slot 2 can contain an additional supervisor engine in case the supervisor engine in slot 1 fails. If a redundant supervisor engine is not required, you can insert the CSM in slots 2 through 9 on a 9-slot chassis, or slots 2 through 6 on the 6-slot chassis, or slots 2 through 13 on the 13-slot chassis.

Figure 4 Slot Numbers on Catalyst 6000 Family Switches

Step 3 Check that there is enough clearance to accommodate any interface equipment that you will connect directly to the supervisor engine or switching-module ports.

Note If possible, place switching modules between empty slots that contain only switching-module filler plates (Cisco part number 800-00292-01).

Warning Blank faceplates (filler panels) serve three important functions: they prevent exposure to hazardous voltages and currents inside the chassis; they contain electromagnetic interference (EMI) that might disrupt other equipment; and they direct the flow of cooling air through the chassis. Do not operate the system unless all cards and faceplates are in place.

Step 4 Loosen the captive installation screws that secure the switching-module filler plate (or an existing switching module) to the desired slot.

Step 5 Remove the switching-module filler plate (or an existing switching module).

Step 6 Hold the handle of the CSM with one hand, and place your other hand under the carrier support. Do not touch the printed circuit boards or connector pins.

Step 7 Place the CSM in the slot. Align the notch on the sides of the switching-module carrier with the groove in the slot. (See Figure 5.)

Figure 5 Installing Modules in the Catalyst 6000 Family Switch

Step 8 Keep the CSM at a 90-degree orientation to the backplane and carefully slide the CSM into the slot until the switching-module faceplate contacts the ejector levers. (See Figure 6.)

Figure 6 Ejector Levers and Captive Installation Screws

Step 9 Using the thumb and forefinger of each hand, simultaneously push in the left and right levers to fully seat the CSM in the backplane connector.

Caution Always use the ejector levers when installing or removing the CSM. A module that is partially seated in the backplane will cause the system to halt and subsequently crash.

Note If you perform a hot swap, the console displays the message "Module n has been inserted." This message does not appear, however, if you are connected to the Catalyst 6000 family switch through a Telnet session.

Step 10 Use a screwdriver to tighten the captive installation screws on the left and right ends of the CSM.

This completes the CSM installation procedure.

Verifying the Installation

When you install the CSM into the Catalyst 6000 family switch, the module goes through a boot sequence that requires no intervention. At the successful conclusion of the boot sequence, the green status LED will illuminate and remain on.

Using the Command-Line Interface

The software interface for the CSM is the Cisco IOS interface. To understand the Cisco IOS command-line interface and Cisco IOS command modes, refer to Chapter 2 in the Catalyst 6000 Family IOS Software Configuration Guide.

Note Because of each prompt's character limit, some prompts may be truncated. For example:
Router(config-slb-vlan-server)# may appear as Router(config-slb-vlan-serve)#

Accessing Online Help

In any command mode, you can get a list of available commands by entering a question mark (?) as follows: 

Router> ?

or 

Router(config)# ip slb ?

Note Online help shows the default configuration values and ranges available to commands.

Upgrading to a New Software Release

This section describes the three methods on how to upgrade the CSM:

•Upgrading from the Supervisor Engine Bootflash

•Upgrading from a PCMCIA Card

•Upgrading Over the Network

Note When upgrading to a new software release, you must upgrade the CSM image before upgrading the Cisco IOS image. Failure to do so will cause the supervisor engine to not recognize the CSM. In this case, you would have to downgrade the Cisco IOS image, upgrade the CSM image, and then upgrade the Cisco IOS image.

During the upgrade, enter all commands on a console connected to the supervisor engine. Enter each configuration command on a separate line. To complete the upgrade, enter the exit command to return to the supervisor engine prompt.

Caution You must enter the exit command to terminate sessions with the CSM being upgraded. If you do not terminate the session and you remove the CSM from the Catalyst 6000 family chassis, you cannot issue configuration commands to the CSM unless you press Ctrl + ^, enter x, and type the disconnect command at the prompt.

Upgrading from the Supervisor Engine Bootflash

Upgrade the CSM from the supervisor engine bootflash as follows:

Note Refer to the Catalyst 6000 Family Supervisor Engine Flash PC Card Installation Note for instructions on loading images into bootflash.

Step 1 Enable the TFTP server to supply the image from bootflash as follows: 

Router>

Router> enable

Router# conf t

Router(config)# tftp-server sup-bootflash:c6slb-apc.revision-num.bin

Router(config)

Step 2 Set up a session between the supervisor engine and the CSM: 

Router# session CSM-slot-number 0

Step 3 Load the image from the supervisor engine to the CSM: 

CSM> upgrade 127.0.0.zz c6slb-apc.revision-num.bin

where

zz = 12 if the supervisor engine is installed in chassis slot 1
zz = 22 if the supervisor engine is installed in chassis slot 2

Note The supervisor engine can only be installed in chassis slot 1 or slot 2.

Step 4 Reboot the CSM by power cycling the CSM or by issuing the following commands on the supervisor engine console. 

Router# config t

Router(config)# power cycle module slot-number

Upgrading from a PCMCIA Card

Upgrade the CSM from a removable Flash (PCMCIA) card inserted in the supervisor engine as follows:

Step 1 Enable the TFTP server to supply the image from the removable Flash card: 

Router>

Router> enable

Router# conf t

Router(config)# tftp-server slotx:c6slb-apc.revision-num.bin

where

x = 0 if the PCMCIA card is installed in supervisor engine PCMCIA slot 0.

Step 2 Set up a session between the supervisor engine and the CSM: 

Router# session CSM-slot-number 0

Step 3 Load the image from the supervisor engine to the CSM: 

CSM> upgrade slot0: c6slb-apc.revision-num.bin

Note The supervisor engine can only be installed in chassis slot 1 or slot 2.

Step 4 Reboot the CSM by power cycling the CSM or by issuing the following commands on the supervisor engine console: 

router# config t

Router (config)# power cycle module slot-number

Upgrading Over the Network

Upgrade the CSM from an external TFTP server as follows:

Step 1 Create a VLAN on the supervisor engine for the TFTP CSM runtime image download.

Note It is possible to use an existing VLAN. However, for reliability in the download, create a VLAN specifically for the TFTP connection.

Step 2 Configure the interface that is connected to your TFTP server.

Step 3 Add the interface to the VLAN.

Step 4 Enter the ip slb vlan command, as explained in the "Configuring VLANs" section, to make the VLAN a client VLAN.

Step 5 Add an IP address to the VLAN for the CSM.

Step 6 Enter the show command as described in "Configuring VLANs" section to verify the configuration.

Step 7 Make a Telnet connection into the CSM with the session CSM-slot-number 0 command.

Step 8 Upgrade the image using the upgrade TFTP-server-IP-address c6slb-apc.rev-number.bin command.

Configuring the Content Switching Module

This section describes how to configure load balancing on the CSM. Before you configure the CSM, the switch must meet these prerequisites:

Caution Enter the ip slb mode csm command before you enter any other CSM configuration commands.

•The Cisco IOS versions for the switch and the module must match.

•Turn off the Cisco IOS-based server load balancing. Enter the ip slb mode and enable the CSM operating mode csm (content switching mode) which disables the rp (router processing mode).

This example shows how to enable the csm mode: 

Router(config)# ip slb mode ?

csm SLB in Application Processor Complex board

rp SLB in IOS system

Router(config)# ip slb mode csm

•You must configure VLANs on the Catalyst 6000 family switch before you configure VLANs for the CSM. VLAN IDs must be the same for the switch and the module. Refer to the Catalyst 6000 Family Software Configuration Guide for details.

This example shows how to configure VLANs: 

Router>

Router> enable

Router# vlan database

Router(vlan)# vlan 130

VLAN 130 added:

Name: VLAN130

Router(vlan)# vlan 150

VLAN 150 added:

Name: VLAN150

Router(vlan)# exit

•You should place physical interfaces that connect to the servers or to the clients in the corresponding VLAN.

This example shows how to configure a physical interface as a Layer 2 interface and assign it to a VLAN: 

Router>

Router> enable

Router# config

Router(config)# interface 3/1

Router(config-if)# switchport

Router(config-if)# switchport access vlan 150

Router(config-if)# no shutdown

Router(vlan)# exit

If the Multilayer Switch Function Card (MSFC) is used on the next hop router on either the client or the server side VLAN, then the corresponding Layer 3 VLAN interface must be configured.

Caution The MSFC cannot be used simultaneously as the router for both the client and the server side. Do not configure the Layer 3 VLAN interface for both the client and the server side.

This example shows how to configure the Layer 3 VLAN interface: 

Router>

Router> enable

Router# config

Router(config)# interface vlan 130

Router(config-if)# ip address 10.10.1.10 255.255.255.0

Router(config-if)# no shutdown

Router(vlan)# exit

Figure 7 shows an overview of the configuration process. Required and optional operations are shown.

Note Configuring policies is not necessary for basic Layer 4 load balancing.

Figure 7 Configuration Overview

Configure the required parameters in the following sections:

•Configuring VLANs

•Configuring Server Farms

•Configuring Real Servers

•Configuring Policies

•Configuring Virtual Servers

After you configure the required load-balancing parameters on the CSM, you may configure the optional parameters in the following sections:

•Configuring TCP Parameters

•Configuring Dynamic Feedback Protocol

•Configuring Redirect Virtual Servers

•Configuring Client NAT Pools

•Configuring Server NAT

To save or restore your configurations or to work with advanced configurations, refer to the following sections:

•Writing and Restoring Configurations

•Configuration Examples

•Configuring Probes for Health Monitoring

•Configuring Route Health Injection

Configuring VLANs

The CSM requires configuration for client-side and server-side VLANs when you install the module in a Catalyst 6500 series switch.

Note You must configure VLANs on the Catalyst 6000 family switch before you configure VLANs for the CSM. VLAN IDs must be the same for the switch and the module.

The CSM dynamically allocates one client gateway to the active router for a total of two client gateways for an HSRP group. You can configure a maximum of three HSRP groups on the client side of the CSM; fewer if other routers exist on the client-side.

You need to create both a client- and server-side VLAN. (See Figure 8.)

Figure 8 Configuring VLANs

See Figure 8 for the following notes:

Note *Any router configured as a client-side gateway or a next hop router for servers more than one hop away must have ICMP redirects disabled. The CSM does not perform a Layer 3 lookup to forward traffic; the CSM cannot act upon ICMP redirects.

Note ** HSRP provides automatic router backup using an active standby router that allows active and standby routers in an HSRP group to exchange messages and respond to topology changes by selecting a new active router dynamically. Because traffic can come from both the virtual and physical MAC addresses of the gateway, the CSM uses two entries per virtual IP gateway configured. You can configure only seven client gateways on the CSM. An HSRP group is assigned one client gateway for the virtual IP address when it is configured. (See the "Configuring HSRP" section.)

Configuring Client-Side VLANs

To configure client-side VLANs, perform this task:

Caution You cannot use VLAN 1 as a client-side or server-side VLAN for the CSM.

 
Command
Purpose

Step 1  

Router(config)# ip slb vlan vlanid client

Configure the client-side VLANs and enter the client VLAN mode1 .

Step 2  

Router(config-slb-vlan-client)# ip 
ip-address netmask

Configure an IP address to the CSM used by probes and ARP requests on this particular VLAN2 .

Step 3  

Router(config-slb-vlan-client)# gateway 
ip-address

Configure the gateway IP address. Enter this command only in the client submode.

1 Enter the exit command to leave a mode or submode. Enter the end command to return to the menu's top level.

2 The no form of this command restores the defaults.

This example shows how to configure the CSM for client-side VLANs: 

Router(config)# ip slb vlan 130 client

Router(config-slb-vlan-client)# ip addr 123.44.50.6 255.255.255.0

Router(config-slb-vlan-client)# gateway 123.44.50.1

Router(config-slb-vlan-client)# exit

Router# show ip slb VLAN

Configuring Server-Side VLANs

To configure server-side VLANs, perform this task:

 
Command
Purpose

Step 1  

Router(config)# ip slb vlan vlanid server

Configure the server-side VLANs and enter the server VLAN mode1 .

Step 2  

Router(config-slb-vlan-server)# route 
ip-address netmask gateway gw-ip-address

Configure a static route to reach the real servers in case they are more than one Layer 3 hop away from the CSM.

Step 3  

Router(config-slb-vlan-server)# alias 
ip-address netmask

Optionally, you can configure multiple IP addresses to the CSM to place the module in a different IP network than real servers without using a router. Use this command only in the server submode.

Step 4  

Router(config-slb-vlan-server)# ip ip-address 
netmask

Configure an IP address for the server VLAN2 .

Step 5  

Router # show ip slb vlan

Display the client-side and server-side VLAN configurations.

1 Enter the exit command to leave a mode or submode. Enter the end command to return to the menu's top level.

2 The no form of this command restores the defaults.

This example shows how to configure the CSM for server-side VLANs: 

Router(config)# ip slb vlan 150 server

Router(config-slb-vlan-server)# ip addr 123.46.50.6 255.255.255.0

Router(config-slb-vlan-server)# route 123.50.0.0 255.255.0.0 gateway 123.44.50.1

Router(config-slb-vlan-server)# alias 123.60.7.6 255.255.255.0

Router(config-slb-vlan-server)# exit

Configuring Server Farms

A server farm or server pool is a collection of servers that contain the same content. You specify the server farm name when you configure the server farm and add servers to it, and when you bind the server farm to a virtual server. Configuring server farms requires naming the server farm, configuring a load-balancing algorithm (predictor) and other attributes of the farm, setting or specifying a set of real servers (see the "Configuring Real Servers" section), and setting or specifying the attributes of the real servers.

When you configure server farms, you must perform the following:

•Create the server farm

•Configure the server farm

•Create real servers

•Configure the real servers

To configure server farms, perform this task:

 
Command
Purpose

Step 1  

Router(config)# ip slb serverfarm 
serverfarm-name

Create and name a server farm and enter the server farm configuration mode1 2 .

Step 2  

Router(config-slb-sfarm)# predictor 
[roundrobin | leastconns | ip-hash netmask]

Configure the load-balancing prediction algorithm2. If not specified, the default is roundrobin.

Step 3  

Router(config-slb-sfarm)# nat client 
client-pool-name

Enable the NAT mode, client2. Refer to the "Configuring Client NAT Pools" section3 .

Step 4  

Router(config-slb-sfarm)# probe probe-name

Associate the server farm to a probe that can be defined by the probe command2, 3.

Step 5  

Router(config-slb-sfarm)# bindid bind-id

Bind a single physical server to multiple server farms and report a different weight for each one2. The bindid is used by DFP3.

Step 6  

Router# show ip slb serverfarm 
serverfarm-name [detail]

Display information about one or all server farms.

1 Enter the exit command to leave a mode or submode. Enter the end command to return to the menu's top level.

2 The no form of this command restores the defaults.

3 This step is optional.

This example shows how to configure a server farm, named p1_nat, using the least-connections (leastconns) algorithm. The least-connections algorithm specifies which real server handles the next new connection for this server farm. 

Router(config)# ip slb serverfarm pl_nat

Router(config-slb-sfarm)# predictor leastconns

Configuring Real Servers

Real servers are physical devices assigned to a server farm. Real servers provide the services that are load balanced. When the server receives a client request, it pulls matching information from a disk and sends it to the CSM for forwarding to the client.

You configure the real server in the real server configuration mode by specifying the server IP address and port when you assign it to a server farm. You enter the real server configuration mode from the serverfarm mode where you are adding the real server.

To configure real servers, perform this task:

 
Command
Purpose

Step 1  

Router(config-slb-sfarm)# real 
ip-address [port]

Identify a real server as a member of the server farm and enter the real server configuration mode. An optional translation port can also be configured1 , 2 .

Step 2  

Router(config-slb-real)# weight 
weighting-value

(Optional) Set the weighting value for the virtual server predictor algorithm to assign the server's workload capacity relative to the other servers in the server farm if the round robin or least connection is selected2.

Step 3  

Router(config-slb-real)# maxconns 
max-conns

(Optional) Set the maximum number of active connections on the real server2. When the specified maximum is reached, no more new connections are sent to that real server until the number of active connections drops below the minimum threshold.

Step 4  

Router(config-slb-real)# minconns 
min-conns

(Optional) Set the minimum connection threshold2.

Step 5  

Router(config-slb-real)# inservice

Enable the real server for use by the CSM2.

Note Repeat Steps 1 through 5 for each real server you are configuring.

Step 6  

Router# show ip slb reals [sfarm 
serverfarm-name] [detail]

(Optional) Display information about configured real servers. The vserver option limits the display to real servers associated with a particular virtual server. The detail option displays detailed real server information.

Step 7  

Router# show ip slb conns [sfarm 
vserver virtserver-name] [client 
ip-address] [detail]

Display active connections to the CSM. The sfarm option limits the display to connections associated with a particular server farm. The client option limits the display to connections for a particular client. The detail option displays detailed connection information.

1 Enter the exit command to leave a mode or submode. Enter the end command to return to the menu's top level.

2 The no form of this command restores the defaults.

This example shows how to create real servers: 

Router(config)# ip slb serverfarm serverfarm

Router(config-slb-sfarm)# real 10.8.0.7

Router(config-slb-real)# inservice

Router(config-slb-sfarm)# real 10.8.0.8

Router(config-slb-real)# inservice

Router(config-slb-sfarm)# real 10.8.0.9

Router(config-slb-real)# inservice

Router(config-slb-sfarm)# real 10.8.0.10

Router(config-slb-real)# inservice

Router(config-slb-real)# end

Router# show ip slb real detail

Router# show ip slb conns detail

Configuring Policies

Policies are access rules that traffic must match when balancing to a server farm. They provide the means for the CSM to balance Layer 7 traffic. Multiple policies can be assigned to one virtual server, creating multiple access rules for that virtual server. When configuring policies, you first specify access rules by URL maps, client-groups, and sticky groups, and then you combine these access rules under a particular policy.

Note You must associate policies with one server farm. A policy that does not have an associated server farm cannot forward traffic. The server farm associated with a policy receives all the requests that match that policy.

When the CSM is able to match policies, it selects the policy that appears first in the policy list. Policies are located in the policy list in the sequence in which they were bound to the virtual server. You can reorder the policies in the list by removing policies and reentering them in the correct order. Enter the no slb-policy policy name and the slb-policy policy name commands in the ip slb vserver submode to remove and enter policies.

Caution When changing the policies associated with a vserver, you must take out and put back the vserver in service to reflect the changes.

To configure load-balancing policies, perform this task: