Guest

Cisco Services Modules

Installation Note, Cisco ACE Application Control Engine (ACE30) Module (Software Version A4(1.0) and Later, Software Version A5(1.0) and Later)

  • Viewing Options

  • PDF (1.6 MB)
  • Feedback
Installation Note, Cisco ACE Application Control Engine ACE30 Module

Table Of Contents

Installation Note, Cisco ACE Application Control Engine ACE30 Module

Contents

Safety Overview

ACE30 Overview

Front Panel Description

Status LED

Shutdown Button

USB Port

RJ-45 Console Connector

Chassis, Supervisor Engine, and IOS Requirements for the ACE30

Virtual Switching System Support

NEBS Level 3 Compliance

System and Environmental Requirements

Supported Hardware and Software

Power Requirements

Memory Requirements

Environmental Requirements

Before You Install or Remove a Module

Installing a Module

Removing a Module

Migrating Redundant ACE10 or ACE20 Modules to ACE30 Modules

Prerequisites

Before You Begin

Addressing Probe Port Inheritance

Understanding the ACE30 Licenses

Downloading and Installing the Supervisor Engine Image

Disabling Preemption in the Active ACE

Manually Backing Up Your Configuration Files and Dependent Files

Using the Backup Utility to Back Up Your Configuration Files and Dependent Files

Removing the ACE10 or ACE20 from the Chassis

Installing the ACE30 in the Chassis

Configuring a Management VLAN Interface for IP Connectivity

Installing the ACE30 License

Copying the Backup Archive to Disk0

Disassociating the Supervisor Engine VLANs from the ACE

Checking the Uptime of the ACE30 Module

Restoring the Backup Archive Files and Powering Down the Standby

Reassociating the Supervisor Engine VLANs and Powering up the ACE

Checking the FT States of the Peers

Forcing a Switchover

Migrating the Former Active ACE10 or ACE20 to an ACE30

Reenabling Preemption on the Active ACE30

Migrating a Single ACE10 or ACE20 Module to an ACE30 Module

Downgrading an ACE30 in a Redundant Configuration

Disabling Preemption in the Active ACE

Removing the ACE30 from the Chassis

Installing the Original ACE10 or ACE20 and Logging In

Checking the FT States of the Peers

Forcing a Switchover

Downgrading the Former Active ACE30 to an ACE10 or ACE20

Reenabling Preemption on the Active ACE10 or ACE20

Downgrading a Single ACE30 Module

Accessing the ACE Command-Line Interface

Related Documentation

Translated Safety Warnings

Obtaining Documentation, Obtaining Support, and Security Guidelines


Installation Note, Cisco ACE Application Control Engine ACE30 Module


Released: October 2010

Revised: September 2012

Product Numbers: ACE30-MOD-K9

This document describes how to install the Cisco ACE Application Control Engine (ACE30) module. The ACE30 module supports operation with software versions:

A4(1.0) or later

A5(1.0) or later

You can install an ACE30 module in the following chassis:

Any Catalyst 6500E series switch or a Catalyst 6513 non-E chassis with IOS software version 12.2(33)SXI4 or later. See the "Before You Install or Remove a Module" section for information about the various chassis and slot use.

Any Cisco 7600 or 7600S series router with IOS software release 15.0(1)S. See the "Before You Install or Remove a Module" section for information about the various chassis and slot use.


Note Be sure to upgrade the IOS software in your chassis as described above before you install an ACE30.



Note ACE10-6500-K9, ACE20-MOD-K9 and ACE30-MOD-K9 modules can occupy the same chassis with a maximum of four modules in one chassis. However, you cannot use an ACE10 or an ACE20 with an ACE30 for redundancy.


Contents

This document contains the following sections:

Safety Overview

ACE30 Overview

Front Panel Description

Chassis, Supervisor Engine, and IOS Requirements for the ACE30

Virtual Switching System Support

NEBS Level 3 Compliance

System and Environmental Requirements

Before You Install or Remove a Module

Installing a Module

Removing a Module

Migrating Redundant ACE10 or ACE20 Modules to ACE30 Modules

Migrating a Single ACE10 or ACE20 Module to an ACE30 Module

Downgrading an ACE30 in a Redundant Configuration

Downgrading a Single ACE30 Module

Accessing the ACE Command-Line Interface

Related Documentation

Translated Safety Warnings

Obtaining Documentation, Obtaining Support, and Security Guidelines

Safety Overview


Warning

IMPORTANT SAFETY INSTRUCTIONS

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. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device. Statement 1071

SAVE THESE INSTRUCTIONS

Waarschuwing

BELANGRIJKE VEILIGHEIDSINSTRUCTIES

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 de standaard praktijken om ongelukken te voorkomen. Gebruik het nummer van de verklaring onderaan de waarschuwing als u een vertaling van de waarschuwing die bij het apparaat wordt geleverd, wilt raadplegen.

BEWAAR DEZE INSTRUCTIES

Varoitus

TÄRKEITÄ TURVALLISUUSOHJEITA

Tämä varoitusmerkki merkitsee vaaraa. Tilanne voi aiheuttaa ruumiillisia vammoja. Ennen kuin käsittelet laitteistoa, huomioi sähköpiirien käsittelemiseen liittyvät riskit ja tutustu onnettomuuksien yleisiin ehkäisytapoihin. Turvallisuusvaroitusten käännökset löytyvät laitteen mukana toimitettujen käännettyjen turvallisuusvaroitusten joukosta varoitusten lopussa näkyvien lausuntonumeroiden avulla.

SÄILYTÄ NÄMÄ OHJEET

Attention

IMPORTANTES INFORMATIONS DE SÉCURITÉ

Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation pouvant entraîner des blessures ou des dommages corporels. Avant de travailler sur un équipement, soyez conscient des dangers liés aux circuits électriques et familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents. Pour prendre connaissance des traductions des avertissements figurant dans les consignes de sécurité traduites qui accompagnent cet appareil, référez-vous au numéro de l'instruction situé à la fin de chaque avertissement.

CONSERVEZ CES INFORMATIONS

Warnung

WICHTIGE SICHERHEITSHINWEISE

Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu Verletzungen führen kann. Machen Sie sich vor der Arbeit mit Geräten mit den Gefahren elektrischer Schaltungen und den üblichen Verfahren zur Vorbeugung vor Unfällen vertraut. Suchen Sie mit der am Ende jeder Warnung angegebenen Anweisungsnummer nach der jeweiligen Übersetzung in den übersetzten Sicherheitshinweisen, die zusammen mit diesem Gerät ausgeliefert wurden.

BEWAHREN SIE DIESE HINWEISE GUT AUF.

Avvertenza

IMPORTANTI ISTRUZIONI SULLA SICUREZZA

Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare infortuni alle persone. Prima di intervenire su qualsiasi apparecchiatura, occorre essere al corrente dei pericoli relativi ai circuiti elettrici e conoscere le procedure standard per la prevenzione di incidenti. Utilizzare il numero di istruzione presente alla fine di ciascuna avvertenza per individuare le traduzioni delle avvertenze riportate in questo documento.

CONSERVARE QUESTE ISTRUZIONI

Advarsel

VIKTIGE SIKKERHETSINSTRUKSJONER

Dette advarselssymbolet betyr fare. Du er i en situasjon som kan føre til skade på person. Før du begynner å arbeide med noe av utstyret, må du være oppmerksom på farene forbundet med elektriske kretser, og kjenne til standardprosedyrer for å forhindre ulykker. Bruk nummeret i slutten av hver advarsel for å finne oversettelsen i de oversatte sikkerhetsadvarslene som fulgte med denne enheten.

TA VARE PÅ DISSE INSTRUKSJONENE

Aviso

INSTRUÇÕES IMPORTANTES DE SEGURANÇA

Este símbolo de aviso significa perigo. Você está em uma situação que poderá ser causadora de lesões corporais. Antes de iniciar a utilização de qualquer equipamento, tenha conhecimento dos perigos envolvidos no manuseio de circuitos elétricos e familiarize-se com as práticas habituais de prevenção de acidentes. Utilize o número da instrução fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham este dispositivo.

GUARDE ESTAS INSTRUÇÕES

¡Advertencia!

INSTRUCCIONES IMPORTANTES DE SEGURIDAD

Este símbolo de aviso indica peligro. Existe riesgo para su integridad física. Antes de manipular cualquier equipo, considere los riesgos de la corriente eléctrica y familiarícese con los procedimientos estándar de prevención de accidentes. Al final de cada advertencia encontrará el número que le ayudará a encontrar el texto traducido en el apartado de traducciones que acompaña a este dispositivo.

GUARDE ESTAS INSTRUCCIONES

Varning!

VIKTIGA SÄKERHETSANVISNINGAR

Denna varningssignal 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 vanliga förfaranden för att förebygga olyckor. Använd det nummer som finns i slutet av varje varning för att hitta dess översättning i de översatta säkerhetsvarningar som medföljer denna anordning.

SPARA DESSA ANVISNINGAR

Aviso

INSTRUÇÕES IMPORTANTES DE SEGURANÇA

Este símbolo de aviso significa perigo. Você se encontra em uma situação em que há risco de lesões corporais. Antes de trabalhar com qualquer equipamento, esteja ciente dos riscos que envolvem os circuitos elétricos e familiarize-se com as práticas padrão de prevenção de acidentes. Use o número da declaração fornecido ao final de cada aviso para localizar sua tradução nos avisos de segurança traduzidos que acompanham o dispositivo.

GUARDE ESTAS INSTRUÇÕES

Advarsel

VIGTIGE SIKKERHEDSANVISNINGER

Dette advarselssymbol betyder fare. Du befinder dig i en situation med risiko for legemesbeskadigelse. Før du begynder arbejde på udstyr, skal du være opmærksom på de involverede risici, der er ved elektriske kredsløb, og du skal sætte dig ind i standardprocedurer til undgåelse af ulykker. Brug erklæringsnummeret efter hver advarsel for at finde oversættelsen i de oversatte advarsler, der fulgte med denne enhed.

GEM DISSE ANVISNINGER

 



ACE30 Overview

The ACE30 module consists of a base board and two daughter cards. The base board provides back plane connectivity, packet distribution, and the control plane. Each daughter card contains two network processors (NPs) that are responsible for compression and improved Layer 4 through Layer 7 data plane processing. The four NPs are similar to the one used in the ACE appliance. Other features include a 4 GB compact flash and increased control plane memory.

Front Panel Description

Figure 1 illustrates the front panel of the ACE30.

Figure 1 ACE30-MOD-K9 Front Panel

This section contains the following topics that describe the individual components on the front panel:

Status LED

Shutdown Button

USB Port

RJ-45 Console Connector

Status LED

When you power up the ACE module, it initializes various hardware components and communicates with the supervisor engine. The Status LED indicates the supervisor engine operations and the initialization results. During the normal initialization sequence, the status LED changes from off to red, orange, and green.


Note For information on the supervisor engine LEDs, see the Catalyst 6500 Series Switch Module Installation Guide or the Cisco 7600 Series Router Module Installation Guide.


Table 1 describes the Status LED operation.

Table 1 Status LED Description 

LED Color
Description

Off

Indicates one of the following conditions:

The module is waiting for the supervisor engine to provide power.

The module is offline.

The module is not receiving power, which may be caused by one of the following:

Power is not available to the module.

Module temperature is over the limit1 .

Red

Indicates one of the following conditions:

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

The boot code failed to run.

Orange

Indicates one of the following conditions:

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

A fault occurred during the initialization sequence.

The module failed to download its Field Programmable Gate Arrays (FPGAs) at startup. The module continues with the remainder of the initialization sequence and provides the module online status from the supervisor engine.

The module has not received the module online status from the supervisor engine. This problem may be caused by the supervisor engine detecting a failure in an external loopback test that it issued to the module.

Green

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

Green to Orange

The module is disabled through the supervisor engine command-line interface (CLI) using the no power enable module command.

1 Enter the show environment temperature mod command at the Catalyst 6500 series switch or Cisco 7600 series router CLI to display the temperature of each of the four sensors on the module.


Shutdown Button


Caution Do not remove the ACE module from the Catalyst 6500 series switch or the Cisco 7600 series router until the module has shut down completely and the Status LED is orange. To avoid damaging the ACE module, you must correctly shut down the module before you remove it from the chassis or before you disconnect the power. You may damage the ACE module if you remove it from the switch before it completely shuts down.

The Shutdown button manually shuts down the ACE module. To properly shut down the ACE module to prevent data loss, enter the no power enable module command in Configure mode at the switch or router CLI.

If the ACE module fails to respond to this command, shut down the module by using a small pointed object (such as a paper clip) to access the Shutdown button on the front panel of the ACE module. The shutdown procedure may take several minutes. The Status LED turns off when the module shuts down.

USB Port

The USB port has been removed from the ACE30 because it is not used.

RJ-45 Console Connector

The RJ-45 Console port is used to initially configure the ACE module. The initial ACE module configuration must be made through a direct connection to the Console port. After the initial configurations, you can make an Secure Shell (SSH) or Telnet connection to the module to further configure it.

The Console port uses an 8-pin RJ-45 connector to connect the ACE module to a terminal. Two RJ-45 console cables are included as part of the ACE module accessory kit.

The settings for the Console port are 9600 baud, 8 data bits, 1 stop bit, no parity. The Console port settings are fixed and cannot be changed.

Chassis, Supervisor Engine, and IOS Requirements for the ACE30

Table 2 and Table 3 summarize the chassis, supervisor engine models, and IOS version support for the ACE30 in the Catalyst 6500 series switch and the Cisco 7600 series router, respectively.

Table 2 Chassis, Supervisor Engine, and Cisco IOS Support for the ACE 30 in a Catalyst 6500 Series Switch with a Multilayer Switch Feature Card (MSFC3 or Later)

Catalyst 6500 Series Switch Chassis
Supervisor Engine Model
Minimum Required Cisco IOS Version

6503-E

6504-E

6506-E

6509-E1

6509-V-E

6513

6513-E2

VS-S2T-10G 3

VS-S2T-10G-XL

15.0(1)SY (or later)

WS-SUP720-3B

WS-SUP720-3BXL

VS-S720-10G-3C(=)

VS-S720-10G-3CXL(=)

12.2(33)SXI4 or later releases

1 The Catalyst 6509-E chassis supports up to six ACE 30 modules with Supervisor Engine 2T (VS-S2T-10G or VS-S2T-10G-XL), and running Cisco IOS software version 15.0(1)SY1 (or later) with ACE module software version A5(1.2) or later.

2 The Catalyst 6513-E chassis supports up to nine ACE 30 modules with Supervisor Engine 2T (VS-S2T-10G or VS-S2T-10G-XL), and running Cisco IOS software version 15.0(1)SY1 (or later) with ACE module software version A5(1.2) or later.

3 The minimum required ACE30 module software version for Supervisor Engine 2T support is A5(1.1) or later. This software version supports both supervisor engine models: VS-S2T-10G and VS-S2T-10G-XL.


Table 3 Supervisor Engine, Route Switch Processor (RSP), and IOS Support for the ACE30 in a Cisco 7600 Series Router with an MSFC3 or Later

Cisco 7600 Series Router Chassis
Supervisor Engine or RSP
Minimum Required IOS Version

7603

WS-SUP720-3B

WS-SUP720-3BXL

RSP720-3C-GE(=)

RSP720-3CXL-GE(=)

RSP720-3C-10GE

RSP720-3CXL-10GE

15.0(1)S (or later)

7604

7609

7613

7603-S

7604-S

7606-S

7609-S



Note If you are running a Catalyst 6500 series switch with a non-E chassis, you must upgrade to an E-chassis, unless it is a Catalyst 6513 switch.


An ACE30 occupies one slot in the supported Catalyst 6500 series switch or Cisco 7600 series router chassis and a single chassis supports a maximum of four ACE30 modules. ACE10-6500-K9, ACE20-MOD-K9, and ACE30-MOD-K9 modules can occupy the same chassis, but you cannot use an ACE10 or an ACE20 with an ACE30 for redundancy.


Note The ACE30 requires that you install in the chassis any module that has ports to connect to the server and the client networks.


For more information about the Catalyst 6500 series switch, see the Catalyst 6500 Series Switch Installation Guide.

For more information about the Cisco 7600 series router, see the Cisco 7600 Series Router Installation Guide.

For more information about the required Cisco IOS releases, see the Release Notes for Cisco IOS Release 12.2(33)SXH and Later Releases and the Cross-Platform Release Notes for Cisco IOS Release 15.0S.

Virtual Switching System Support

The ACE30 running ACE software versions A4(1.0) or later and A5(1.0) or later, and installed in a Catalyst 6500E series switch or the Catalyst 6513 non-E chassis running IOS software version 12.2(33)SXI4 or later support the Virtual Switching System (VSS). VSS is a system virtualization technology that allows the pooling of multiple Catalyst 6500 switches into a single virtual switch for increased operational efficiency by simplifying the network. Inter-chassis Supervisor switchover (SSO) boosts non-stop communication. For more information about VSS, see the Cisco IOS Version 12.2(33)SXI4 Configuration Guide.

NEBS Level 3 Compliance

Table 4 lists the NEBS Level 3 compliance and environmental requirements for the ACE30.

Table 4 NEBS Compliance and Environmental Requirements

Specification
Description
Comments

NEBS Criteria Levels

SR-3580 NEBS level 3 (GR-63-CORE, issue 3, GR-1089-CORE, issue 5)

 

Verizon NEBS Compliance

Telecommunications Carrier Group (TCG) Checklist

 

Qwest NEBS Requirements

Telecommunications Carrier Group (TCG) Checklist

 

ATT NEBS Requirements

ATT TP76200 level 3, TP7645 and TCG Checklist

 

System and Environmental Requirements

The following sections describe the system and environmental requirements for the ACE module:

Supported Hardware and Software

Power Requirements

Memory Requirements

Environmental Requirements

Supported Hardware and Software

Table 5 lists the minimum ACE module Application Control Software (ACSW) release, supported hardware, and the minimum Cisco IOS software version.

Table 5 Supported Hardware and Software 

Product Description
Product ID (PID) or Part Number
Minimum Application Control Software (ACSW) Release
Minimum Cisco IOS Release
Catalyst 6500 Series Switch
Cisco 7600 Series Router

ACE module

ACE30-MOD-K9

A4(1.0) or later

A5(1.0) or later

Cisco IOS Release
12.2(33)SXI4 (or later)

Cisco IOS Release
15.0(1)S or later

Console cable

72-876-01

Not applicable

Not applicable

Not applicable

Accessory kit (contains two console cables)

800-05097-01

Not applicable

Not applicable

Not applicable


Power Requirements

An ACE module operates on power supplied by the Catalyst 6500 series switch or the Cisco 7600 series router. An ACE30 consumes 440 W (1502 BTU/hr) because of the additional power requirements of the attached daughter cards (each daughter card requires 110 W or 375.5 BTU/hr). To ensure that you have sufficient power available for the ACE30 in your chassis, enter the following command at the supervisor engine CLI:

SUP-C# show power available
system power available =  496.86 Watts (11.83 Amps @ 42V)

Memory Requirements

The ACE module memory is not configurable.

Environmental Requirements

Table 6 lists the environmental requirements for the ACE module.

Table 6 ACE module Environmental Requirements

Item
Specification

Temperature, ambient operating

0o to 40oC (32o to 104oF)

Temperature, ambient nonoperating

-40o to 70oC (-40o to 158oF)

Humidity (RH), ambient (noncondensing) operating

10% to 85%

Nonoperating relative humidity (noncondensing)

5% to 95%


Before You Install or Remove a Module

Before you install an ACE module in the Catalyst 6500 series switch or Cisco 7600 series router, ensure that the following items are available:

Management station available through a Telnet or a console connection to perform the configuration tasks

Phillips-head screwdriver

Wrist strap or other grounding device

Antistatic mat or antistatic foam

When you handle a module, always use a wrist strap or other grounding device to prevent electrostatic discharge (ESD).


Caution During this procedure, wear grounding wrist straps to avoid ESD damage to the modules.


Caution Do not directly touch the backplane with your hand or any metal tool or you may shock yourself.

All Catalyst 6500 series switches and Cisco 7600 series routers support hot swapping, allowing you to install, remove, and replace modules without turning off chassis power. For more information on removing the modules from a switch, see the "Removing a Module" section.

When the software detects that a module has been installed or removed, it automatically runs diagnostic and discovery routines, acknowledges the presence or absence of the module, and resumes switch operation.

The Catalyst 6503-E switch, Cisco 7603 router, or Cisco 7603-S router chassis has three horizontal slots. The Catalyst 6504-E switch, Cisco 7604 router, or Cisco 7604-S router chassis has four horizontal slots. In these chassis, the slots can be used as follows:

Slot 1, the top-most slot, is reserved for the supervisor engine.

Slot 2 can be used for a redundant supervisor engine.

If a redundant supervisor engine is not required, the following slots are available for modules:

Slots 2 and 3 on the 3-slot chassis

Slots 2 through 4 on the 4-slot chassis

Empty slots require filler panels to maintain consistent airflow through the chassis.

The Catalyst 6509-V-E switch, the Cisco 7609 router, or the Cisco 7609-S router chassis has nine vertical slots, which are numbered 1 to 9 from right to left. Install vertical modules with the component side facing to the right. In these chassis, the slots can be used as follows:

Slot 5 is reserved for the supervisor engine.

Slot 6 can be used for a redundant supervisor engine.

If a redundant supervisor engine is not required, the following slots are available for modules:

Slots 1 through 4 and slot 6 on the 6-slot chassis

Slots 1 through 4 and slots 6 through 9 on the 9-slot chassis

Empty slots require filler panels to maintain consistent airflow through the switch chassis.

The Catalyst 6513 switch or Cisco 7613 router chassis has 13 horizontal slots. In these chassis, the slots can be used as follows:

Slot 7 is reserved for the supervisor engine.

Slot 8 can be used for a redundant supervisor engine.

If a redundant supervisor engine is not required, slots 1 through 6 and slots 8 through 13 are available for modules.

Empty slots require filler panels to maintain consistent airflow through the chassis.

Installing a Module

This section describes how to install an ACE module in a Catalyst 6500 series switch or a Cisco 7600 series router. If you are migrating your ACE10 or ACE20 to an ACE30, see the "Migrating Redundant ACE10 or ACE20 Modules to ACE30 Modules" section.


Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.

Caution To prevent ESD damage, handle modules by the carrier edges only.


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

To install a module in the chassis, perform these steps:


Step 1 Choose an appropriate slot for the module.

Step 2 Verify that there is enough clearance to accommodate any interface equipment that you will connect directly to the module ports. If possible, place the modules between the empty slots that contain only the module filler panels.

Step 3 Verify that the captive installation screws are tightened on all modules installed in the chassis. This action ensures that the EMI gaskets on all modules are fully compressed to maximize the opening space for the replacement module.


Note If the captive installation screws are loose, the EMI gaskets on the installed modules push adjacent modules toward the open slot, reducing the opening size and making it difficult to install the replacement module.


Step 4 Remove the filler panel by removing the two Phillips pan-head screws from the filler panel.

Step 5 Open both ejector levers fully on the module (see Figure 2).

Figure 2 Positioning the Module in a Horizontal Slot Chassis

Step 6 Depending on the orientation of the slots in the chassis (horizontal or vertical), perform one of the following sets of substeps:

Horizontal slots

a. Position the module in the slot. Ensure that you align the sides of the module carrier with the slot guides on each side of the slot (see Figure 2).

b. Carefully slide the module into the slot until the EMI gasket along the top edge of the module makes contact with the module in the slot above it and both ejector levers have closed to approximately
45 degrees with respect to the module faceplate (see Figure 3).

Figure 3 Clearing the EMI Gasket in a Horizontal Slot Chassis

c. Using the thumb and forefinger of each hand, grasp the two ejector levers and press down to create a small (0.040 inch [1 mm]) gap between the EMI gasket and the module above it (see Figure 3).


Caution Do not press down too firmly on the levers because you may bend or damage them.

d. While pressing down on the left and right ejector levers, simultaneously close them to fully seat the module in the backplane connector. The ejector levers are fully closed when they are flush with the module faceplate (see Figure 4).

Figure 4 Ejector Levers Fully Closed in a Horizontal Slot Chassis


Note Failure to fully seat the module in the backplane connector may result in error messages.


e. Tighten the two captive installation screws on the module. Make sure that the ejector levers are fully closed before tightening the captive installation screws.

When you install an ACE module into a chassis, it runs a startup sequence that requires no intervention. At the successful conclusion of the startup sequence, the green Status LED lights and remains on. If the Status LED is not green or is off, see Table 1 to determine the module status.

Vertical slots

a. Position the module in the slot (see Figure 5). Make sure that you align the sides of the module carrier with the slot guides on the top and bottom of the slot.

Figure 5 Positioning the Module in a Vertical Slot Chassis

b. Carefully slide the module into the slot until the EMI gasket along the right edge of the module makes contact with the module in the slot adjacent to it. Close both ejector levers to approximately 45 degrees with respect to the module faceplate (see Figure 5).

c. Using the thumb and forefinger of each hand, grasp the two ejector levers and exert a slight pressure to the left, deflecting the module approximately 0.040 inches (1 mm) to create a small gap between the module EMI gasket and the module adjacent to it (see Figure 6).

Figure 6 Clearing the EMI Gasket in a Vertical Slot Chassis


Caution Do not exert excessive pressure on the ejector levers because you may bend or damage them.

d. While pressing on the ejector levers, simultaneously close them to fully seat the module in the backplane connector. The ejector levers are fully closed when they are flush with the module faceplate (see Figure 7).

Figure 7 Ejector Levers Fully Closed in a Vertical Slot Chassis

e. Tighten the two captive installation screws on the module. Make sure that the ejector levers are fully closed before tightening the captive installation screws.


When you install an ACE module into the chassis, it runs a startup sequence that requires no intervention. At the successful conclusion of the startup sequence, the green Status LED lights and remains on. If the Status LED is not green or is off, see Table 1 to determine the module status.

Removing a Module

This section describes how to remove an existing module from a chassis slot.


Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.

Caution During this procedure, wear grounding wrist straps to avoid ESD damage to the module.


Caution Do not directly touch the backplane with your hand or any metal tool or you may shock yourself.

To remove a module from the chassis, perform these steps:


Step 1 Before you remove the module from the chassis, enter the no power enable module command in configuration mode at the switch or router CLI to properly shut down the module to prevent data loss.

Step 2 Verify that the captive installation screws on all of the modules in the chassis are tight.

This step assures that the space that is created by the removed module is maintained.


Note If the captive installation screws are loose, the electromagnetic interference (EMI) gaskets on the installed modules push the modules toward the open slot, reducing the opening size and making it difficult to reinstall the module.


Step 3 Loosen the two captive installation screws on the standby module. See Figure 8.

Figure 8 Loosening the Captive Installation Screws on the ACE

Step 4 Depending on the orientation of the slots in the chassis (horizontal or vertical), perform one of the following sets of substeps:

Removing the ACE from a Horizontal Slot

Removing the ACE from a Vertical Slot

Removing the ACE from a Horizontal Slot

a. Place your thumbs on the left and right ejector levers, and simultaneously rotate the levers outward to unseat the module from the backplane connector.

b. Grasp the front edge of the module with one hand, and slide the module part of the way out of the slot. Place your other hand under the module to support its weight. Do not touch the module circuitry. See Figure 9.

Removing the ACE from a Vertical Slot

a. Place your thumbs on the ejector levers that are located at the top and bottom of the module, and simultaneously rotate the levers outward to unseat the module from the backplane connector.

b. Grasp the edges of the module, and slide the module straight out of the slot. Do not touch the module circuitry.

Figure 9 Removing the Module from a Horizontal Slot Chassis

Step 5 Place the module on an antistatic mat or antistatic foam, or immediately reinstall it in another slot.

Step 6 If the slot from which you removed the module is to remain empty, install a filler panel to keep dust out of the chassis and to maintain proper airflow through the chassis.



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.

Migrating Redundant ACE10 or ACE20 Modules to ACE30 Modules

This section describes the procedures you use to migrate from an ACE10 or ACE20 module to an ACE30 module to support Application Control Software (ACSW) software versions A4(1.0) or later and A5(1.0) or later. If you are upgrading from ACE software version A2(3.0) or later, be sure that you have backed up your configuration files, SSL files, license files, scripted probes, and checkpoint files.

If you are replacing an ACE module that is managed by the Cisco Application Networking Manager, there are steps that you must perform when replacing the ACE that are in addition to the steps described in this document. Use the ACE module replacement procedure described in the User Guide for the Cisco Application Networking Manager 4.1 (see the "Replacing an ACE Managed by ANM" section in Chapter 4, Importing and Managing Devices) along with the information provided in this document.

If you are migrating from a software version earlier than A2(3.0), we recommend that you first upgrade to software version A2(3.0) or later so that you can take advantage of the backup and restore features. For details, see the "Before You Begin" and the "Manually Backing Up Your Configuration Files and Dependent Files" sections.


Note Be sure to read this section in its entirety before you begin the migration process. Perform each procedure in the following sections in the order presented.


This section consists of the following subsections:

Prerequisites

Before You Begin

Addressing Probe Port Inheritance

Understanding the ACE30 Licenses

Downloading and Installing the Supervisor Engine Image

Disabling Preemption in the Active ACE

Manually Backing Up Your Configuration Files and Dependent Files

Using the Backup Utility to Back Up Your Configuration Files and Dependent Files

Removing the ACE10 or ACE20 from the Chassis

Installing the ACE30 in the Chassis

Configuring a Management VLAN Interface for IP Connectivity

Installing the ACE30 License

Copying the Backup Archive to Disk0

Disassociating the Supervisor Engine VLANs from the ACE

Checking the Uptime of the ACE30 Module

Restoring the Backup Archive Files and Powering Down the Standby

Reassociating the Supervisor Engine VLANs and Powering up the ACE

Checking the FT States of the Peers

Forcing a Switchover

Migrating the Former Active ACE10 or ACE20 to an ACE30

Reenabling Preemption on the Active ACE30

Prerequisites

Before you remove an ACE module from the chassis, ensure that the following conditions have been met:

A flat surface with an antistatic mat or antistatic foam is available.

You are wearing a grounded anti-electrostatic discharge (ESD) wrist strap.

#2 Phillips-head screwdriver is available.

Before You Begin

Before you perform the procedures in this upgrade and installation note, please read each procedure in its entirety, paying close attention to any notes or cautions.

Ensure that the following conditions exist:

When migrating from an ACE20 module to an ACE30 module that is running the A4(x.x) software release, ensure that you have a minimum of 150 MBytes of HighFree memory available on the ACE20 module before you migrate the same configuration to the ACE30 module. If the available memory is less than the recommended minimum of 150 MBytes, we recommend that you migrate to the A5(x.x) software release. Use the show system kmem command to confirm the available free memory on the ACE.

The redundancy states of the FT group in the active ACE and the standby ACE are ACTIVE and STANDBY_HOT, respectively. Enter the show ft group status command in Exec mode on the active ACE to check the redundancy state.

To take advantage of backing up and restoring your configuration files, scripted probes, and dependent files, ensure that both ACEs in a redundant configuration are running software version A2(3.0) or later. To verify your current software version, enter the show version command in Exec mode. If you are running a software version earlier than A2(3.0), we recommend that you upgrade your ACE software to version A2(3.0).


Note Software version A2(3.0) or later is required to support the backup and restore of configuration files, SSL certificate and key files, license files, scripted probes, and checkpoint files. If you are not concerned about using the backup and restore utilities, you can manually back up and restore these files and upgrade to software version A4(1.0) or later from software version A2(1.6a) or later. A1(x) software releases are not supported as an upgrade path to A4(1.0) or later. If you are running one of these releases, we recommend that you upgrade to A2(2.4) before you upgrade to A4(1.0) or later.


With software version A4(1.0) and later, the underscore (_) character is not supported in the hostname for the ACE (through the hostname command). If your ACE hostname includes the underscore (_) character, be sure to remove it prior to backing up and restoring your configuration files.

Note that snmp-bulk-request and snmp-server bulk-request max-oid have been deprecated and are not available in software version A4(1.0) and later. Please remove these command from your configuration prior to backing up and restoring your configuration files.

If you are upgrading to a version of ACE software earlier than A4(2.2) or A5(1.2), and your configuration includes contexts with exportable and non-exportable SSL files on the ACE10 or ACE20 module, during the restore process the SSL configuration commands related to the missing SSL files will not migrate, causing a restore error and termination of the restore process. This behavior occurs because the non-exportable SSL files do not exist in the backup. In this case, you will have to manually restore each context one at a time.

All configured HTTPS probes take their resource limits from the Admin context. If you use the limit-resource rate ssl-connections command to define a zero minimum limit for SSL connections in the Admin context, the HTTPS probes will fail on all contexts. To avoid this failure when migrating to the ACE 30 module, ensure that you have set a non- zero minimum limit for SSL connections.

The restore software may display errors during the restoration process because of minor software version differences among a few CLI commands, but you can ignore these restore errors. If necessary, resolve any major errors by adjusting your configuration. Table 7 provides a summary of ACE CLI commands that can result in a restore error during the restoration process.

Table 7 Summary of ACE Commands That Can Result in a Restore Error When Migrating to an ACE30 Module 

ACE Command
ACE Behavior in Software Releases Prior to A4(1.0)
ACE Behavior in Software Releases Starting With A4(1.0)

arp inspection validate
(interface configuration mode

arp inspection validate src-mac

arp inspection validate src-mac [flood | no-flood]
(The flood | no flood options were added. There is no change in functionality other than the additional options)

match-any
(class map configuration mode)

You can include only one match any command within a class map, and you are allowed to combine the match any command with other types of match commands in a class map.

You can include only one match any command within a class map, and you cannot combine the match any command with other types of match commands in a class map because the match criteria will be ignored.

match access-list
(class map configuration mode)

You can include only one match access-list command within a class map, and you are allowed to combine the match access-list command with other types of match commands in a class map.

You can include only one match access-list command within a class map, and you cannot combine the match access-list command with other types of match commands in a class map because the match criteria will be ignored.

persistence-rebalance
(parameter map HTTP configuration mode)

Disabled
(no persistence-rebalance)

Enabled
(persistence-rebalance)

probe interval
(probe configuration mode)

120(default)

15 (default)

passdetect interval
(probe configuration mode)

300 (default)

60 (default)

open timeout
(probe configuration mode)

10 (default)

1 (default)


Addressing Probe Port Inheritance

Starting with software version A4(1.0), this ACE module release introduced probe port inheritance. If you choose not to specify a port number for a probe, the ACE can dynamically inherit the port number specified from the real server specified in a server farm or from the VIP specified in a Layer 3 and Layer 4 class map. This flexibility provides you with an ease of configuration. In this case, all you need is a single probe configuration, which will be sufficient to probe a real server on multiple ports or on all VIP ports. The same probe inherits all of the real server's ports or all of the VIP ports and creates probe instances for each port.

For background details on the port probe inheritance feature, see the following ACE module documents:

For software version A4(x.x):

http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA4_2_0/configuration/slb/guide/probe.html#wpmkr1196914

For software version A5(x.x):

http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA5_1_0/configuration/slb/guide/probe.html#wpmkr1196914

With the introduction of port inheritance, you may encounter issues when migrating from an ACE20 module to an ACE30 module during the following conditions:

There are no port numbers configured on a probe (for example, only one probe monitors a GET result on default port 80).

There are no port numbers configured under real servers.

Your configuration does not include the fail-on-all command.

Your ACE20 module to an ACE30 module upgrade happens with a single VIP class map that contains multiple ports.

As an example, a single class map has VIPs with multiple ports, where one port is 80 and the other port is 443. There are no port numbers configured on a probe, and there is only one probe checking a GET result on default port 80.

When you upgrade to the ACE30 module, it will use the new probe port inheritance function and the new port 443 being probed fails. This failure results in the server farm failing, and it will not be ready for a "hot" failover.

To address this upgrade issue, perform one of workarounds outlined below before you migrate from an ACE10 or ACE20 module to an ACE30 module to support software version A4(1.0) or later.

Workaround 1

1. Before you begin the migration process, remove the probe from the server farm on the ACE20 module.

2. After migration, configure the probe port as described in the Cisco Application Control Engine Module Server Load-Balancing Guide.

3. Reapply the probe on the server farm.

Workaround 2

1. Before you begin the migration process, configure the server farm with the fail-on-all command to configure a real server to remain in the OPERATIONAL state unless all probes associated with it fail (see the Cisco Application Control Engine Module Server Load-Balancing Guide).

2. After migration, configure the probe port as described in the Cisco Application Control Engine Module Server Load-Balancing Guide.

3. Remove the fail-on-all command from the ACE30 module configuration.

Understanding the ACE30 Licenses

The software version A4(1.0) or later feature licensing consists of license bundles that are different from the way that licensing was done in past ACE releases. The license bundles consist of four levels as shown in Table 8.

Table 8 ACE30 License Bundles 

License Bundle
Product ID (PID)
License File
Description

Base (default)

ACE30-BASE-04-K9

None required

4 Gbps bandwidth
1 Gbps compression
1,000 TPS SSL
5 Virtual Contexts

Base to 4 Gbps Upgrade

4 Gbps Bundle

ACE30-MOD-UPG1=

ACE30-MOD-04-K9

ACE30-MOD-UPG1

ACE30-MOD-04-K9

4 Gbps bandwidth
6 Gbps compression
30,000 TPS SSL
250 Virtual Contexts

4 Gbps to 8 Gbps Upgrade

8 Gbps Bundle

ACE30-MOD-UPG2=

ACE30-MOD-08-K9

ACE30-MOD-UPG2

ACE30-MOD-08-K9

8 Gbps bandwidth
6 Gbps compression
30,000 TPS SSL
250 virtual contexts

8 Gbps to 16 Gbps Upgrade

16 Gbps Bundle

ACE30-MOD-UPG3=

ACE30-MOD-16-K9

ACE30-MOD-UPG3

ACE30-MOD-16-K9

16 Gbps bandwidth
6 Gbps compression
30,000 TPS SSL
250 virtual contexts


To display your current license levels, enter the show license status command in Exec mode. Then, use Table 9 to determine the minimum required ACE30 license that will accommodate your current licensed features.

Table 9 Minimum ACE30 Licenses Required for ACE10 or ACE20 Licensed Features

Current ACE10 or ACE20 Licensed Features
Minimum ACE30 License
Bandwidth
Virtual Contexts
SSL TPS

4 Gbps

5

1,000

ACE30-BASE-04-K9

4 Gbps

More than 5

1,000

ACE30-MOD-04-K9

4 Gbps

5

5,000 or more

ACE30-MOD-04-K9

8 Gbps

Any number

Any number

ACE30-MOD-08-K9

16 Gbps

Any number

Any number

ACE30-MOD-16-K9


If you ordered your licenses at the time that you ordered your ACE30 module, check to ensure that the licenses are present on disk0: by entering the dir disk0: command at the CLI in Exec mode. If they are not present on disk0: or not installed, verify your license requirements and installation status before proceeding further. For complete details about ACE licenses, see the Cisco Application Control Engine Module Administration Guide.

Downloading and Installing the Supervisor Engine Image

You must upgrade your supervisor engine IOS software image to one of the releases that support the ACE30. For the Catalyst 6500E series switches, it is Cisco IOS software release 12.2(33)SXI4 or later. For the Cisco 7600 series router, it is Cisco IOS release 15.0(1)S or later. For instructions, see the Cisco Catalyst 6500 Series Switch or the Cisco 7600 Series router installation and configuration guide.

Continue with the "Disabling Preemption in the Active ACE" section.

Disabling Preemption in the Active ACE

To maintain the ACE in a known stable state in a redundant configuration, you must disable preemption for all FT groups in the active ACE. To identify the active ACE in an FT group, enter the show ft group status command. To disable preemption in the active ACE, perform the following steps:


Step 1 Enter configuration mode.

ACE/Admin# config
ACE/Admin(config)# 
 
   

Step 2 Disable preemption for all FT groups by entering the following commands.

ACE/Admin(config)# ft group 1
ACE/Admin(config-ft-group)# no preempt
ACE/Admin(config-ft-group)# exit
ACE/Admin(config)# 
 
   

Repeat this step for each FT group in your active ACE. You need to perform this step only for the first ACE in a redundant pair.

Step 3 Save the running-configuration files in all contexts by entering the following command.

ACE/Admin# write mem all
 
   

If you are upgrading to software version A4(1.0) or later from version A2(3.0) or later, skip to the "Using the Backup Utility to Back Up Your Configuration Files and Dependent Files" section.

If you are upgrading to software version A4(1.0) or later from a release prior to A2(3.0), continue with the "Manually Backing Up Your Configuration Files and Dependent Files" section below.

Manually Backing Up Your Configuration Files and Dependent Files

Software version A2(3.0) or later is required to support the back up and restore of configuration files, SSL certificate and key files, license files, and checkpoint files. If you are upgrading to software version A4(1.0) or later from software version A2(1.x) or later but earlier than A2(3.0), you can archive these files to an FTP, SFTP, or TFTP server by using the following commands:

copy running-config and copy startup-config commands to copy configuration files to a remote server (for details, see the Cisco Application Control Engine Module Administration Guide)

crypto export command to export SSL certificates and keys to a remote server (for details, see the Cisco Application Control Engine Module SSL Configuration Guide)

copy checkpoint command to copy checkpoint files to a remote server (for details, see the Cisco Application Control Engine Module Administration Guide)

copy probe: command to copy scripted probes to a remote server (for details, see the Cisco Application Control Engine Module Administration Guide)

After the upgrade is complete, copy these archived files back to the ACE.

Continue with the "Removing the ACE10 or ACE20 from the Chassis" section.

Using the Backup Utility to Back Up Your Configuration Files and Dependent Files

If you are upgrading from software version A2(3.0) or later, back up the following files in all contexts in both ACEs in a redundant configuration to an FTP, SFTP, or TFTP server:

Startup configuration file

SSL certificate files

SSL key files

License files

Scripted probes

Checkpoint files

To back up the ACE configuration files and dependent files and copy them to an external server, perform the following steps:


Step 1 Enter the following command in Exec mode on each ACE:

ACE/Admin# backup all
 
   

Step 2 To check the status of the backup operation, enter the following command:

ACE/Admin# show backup status
 
   
Backup Archive: ACE2_08_April_2010_11_11_04_PM.tgz
Type          : Full
Start-time    : Thu Apr  8 23:11:04 2010
Finished-time : Thu Apr  8 23:11:06 2010
Status        : SUCCESS
Current vc    : C2
Completed     : 4/4
 
   

Step 3 Copy the backup archive file to an FTP, SFTP, or TFTP server for later use. To save the backup archive file to an FTP or an SFTP server, use the copy backup-all ftp: or the copy backup-all sftp: command. If you have access only to a TFTP server, use the copy disk0: tftp command instead. For example, to copy the backup archive to an FTP server, enter the following command:

ACE/Admin# copy backup-all ftp:
Enter Address for the ftp server[]? 172.25.91.127
Enter the destination filename[]? [ACE2_08_April_2010_11_11_04_PM.tgz]
Enter username[]? root
Enter the file transfer mode[bin/ascii]: [bin]
Enable Passive mode[Yes/No]: [Yes]
Password: 12345678
Passive mode on.
Hash mark printing on (1024 bytes/hash mark).
###
ACE/Admin#

Step 4 Record the backup archive filename for future reference. In this example, the backup filename is ACE2_08_April_2010_11_11_04_PM.tgz.


Continue with the "Removing the ACE10 or ACE20 from the Chassis" section.

Removing the ACE10 or ACE20 from the Chassis


Caution Ensure that you have archived all important ACE files on an external device (for example, an FTP server) before you remove your ACE10 or ACE20 from the chassis. This includes, but is not limited to, non-exportable SSL certificates and keys. Use the copy ftp: command to copy these files to a remote server. After the upgrade is complete, copy these files back to the ACE.

To ensure uninterrupted traffic of non-proxied flows during the upgrade, remove and replace the standby module first in a redundant configuration. To remove your ACE10 or ACE20 from the chassis, perform Steps 1 to 5 in the "Removing a Module" section, then continue with the "Installing the ACE30 in the Chassis" section.


Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.

Caution During this procedure, wear grounding wrist straps to avoid ESD damage to the module.


Caution Do not directly touch the backplane with your hand or any metal tool or you may shock yourself.

Continue with the "Installing the ACE30 in the Chassis" section.

Installing the ACE30 in the Chassis

You can install your new ACE30 module in the same slot that was occupied by the ACE10 or ACE20 that you removed or in another suitable slot in the chassis. Before you install the ACE30, ensure that there is sufficient chassis power to support the module. The ACE30 requires 440 W. For more details, see the "Power Requirements" section.

To check the chassis power enter the following command from the supervisor engine:

c6k# show power available
system power available = 1635.48 Watts (38.94 Amps @ 42V)
 
   

To install the ACE30 in the chassis, perform Steps 1 through 6 in the "Installing a Module" section.


Warning Invisible laser radiation may be emitted from disconnected fibers or connectors. Do not stare into beams or view directly with optical instruments.

Caution To prevent ESD damage, handle modules by the carrier edges only. During this procedure, wear grounding wrist straps to avoid ESD damage to the module. Do not directly touch the backplane with your hand or any metal tool, or you could shock yourself.

The ACE30 boots up with the image that was preinstalled in the module.

Continue with the "Configuring a Management VLAN Interface for IP Connectivity" section.

Configuring a Management VLAN Interface for IP Connectivity

Before you can copy the software image from the remote server to the new ACE30, you must configure a management policy for IP connectivity. To configure a simple, full-access management policy, perform the following steps:


Step 1 Session in to the ACE30 from the supervisor engine or connect to the ACE30 through the console port and log in. For example, to session in to the ACE30:

c6k# session slot 5 proc 0
The default escape character is Ctrl-^, then x.
You can also type 'exit' at the remote prompt to end the session
Trying 127.0.0.110 ... Open
 
   
ACE login: admin
Password: xxxxx
Last login: Thu Sep  9 18:22:21 2010 from 127.0.0.81 on pts/0
Cisco Application Control Software (ACSW)
TAC support: http://www.cisco.com/tac
Copyright (c) 1985-2010 by Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
User 'www' is disabled.Please change the password to enable the user.
ACE/Admin#
 
   

Step 2 Enter configuration mode.

ACE/Admin# config
Enter configuration commands, one per line. End with CNTL/Z
ACE/Admin(config)#
 
   

Step 3 Configure a management VLAN interface as follows:

ACE/Admin(config)# interface vlan 50
ACE/Admin(config-if)# ip address 172.16.1.100 255.255.0.0
ACE/Admin(config-if)# Ctrl-z
ACE/Admin#
 
   

Continue with the "Installing the ACE30 License" section.

Installing the ACE30 License

Your new ACE30 comes with the feature license that you purchased and it has been preloaded in the disk0: directory of the ACE. Before you can restore the backup archive, you must install the new ACE30 license. To install the license, perform the following steps:


Step 1 Install the ACE30.lic license file.

switch/Admin# license install disk0:ace30.lic
Installing license... done
 
   

Step 2 Verify that the license is installed.

ACE/Admin# show license status
 
   
Licensed Feature                            Count
------------------------------------        -----
SSL transactions per second                 30000
Virtualized contexts                        250
Module bandwidth in Gbps                    16.0
Compression Performance in Gbps             6
 
   

Continue with the "Copying the Backup Archive to Disk0" section.

Copying the Backup Archive to Disk0

Copy the backup archive or the individually copied files from the external server to disk0: of the ACE30. These are the files that you archived using the backup all command in the "Using the Backup Utility to Back Up Your Configuration Files and Dependent Files" section or that you copied manually in the "Manually Backing Up Your Configuration Files and Dependent Files" section.

For example, copy the backup file for the original standby ACE from the external server where you stored the backup archive to the ACE30 disk0: as follows:

ACE/Admin# copy ftp://172.25.91.127/switch_08_April_2010_11_11_04_PM.tgz disk0:
Enter the destination filename[]? [ACE2_08_April_2010_11_11_04_PM.tgz]
Enter username[]? root
Enter the file transfer mode[bin/ascii]: [bin]
Enable Passive mode[Yes/No]: [Yes]
Password: 12345678
Passive mode on.
Hash mark printing on (1024 bytes/hash mark).
###
ACE/Admin#
 
   

Continue with the "Disassociating the Supervisor Engine VLANs from the ACE" section.

Disassociating the Supervisor Engine VLANs from the ACE

Before you copy and restore the backup archive to the ACE30, you must disassociate the supervisor engine VLANs from the ACE. To disassociate the supervisor engine VLANs from the ACE, perform the following steps:


Step 1 If you are not already logged in to the supervisor engine in the chassis, log in now.

# telnet 192.168.12.15
Trying 192.168.12.15...
Connected to 192.168.12.15 (192.168.12.15).
Escape character is '^]'.
 
   
 
   
User Access Verification
 
   
Username: admin
Password: xxxxxxxx
c6k#
 
   

Step 2 Enter configuration mode.

c6k#config t
Enter configuration commands, one per line.  End with CNTL/Z.
c6k(config)#
 
   

Step 3 Disassociate the supervisor VLANs from the ACE30. For example, enter the following command for an ACE30 in chassis slot 5 and specify the correct VLAN group numbers or ranges for the ACE:

c6k(config)#no svclc module 5 vlan-group 10-20,100,200
 
   

Continue with the "Restoring the Backup Archive Files and Powering Down the Standby" section.

Checking the Uptime of the ACE30 Module

Before you restore the backup archive, be sure that the uptime of the ACE30 is less than the uptime of the active ACE. To check the uptime of the ACEs, enter the following command on each:

ACE/Admin# show system uptime
System start time:          Thu Sep  9 04:44:24 2010
System uptime:              0 days, 18 hours, 56 minutes, 15 seconds
Kernel uptime:              0 days, 19 hours, 0 minutes, 15 seconds
 
   

If the ACE30 uptime is greater than that of the active ACE, remove power from the ACE30, remove the ACE30 from the backplane of the chassis, and then reinsert it in the chassis.

Restoring the Backup Archive Files and Powering Down the Standby

If you backed up your startup configuration files and dependent files as described in the "Using the Backup Utility to Back Up Your Configuration Files and Dependent Files" section, you must restore the archived files using the restore utility.


Caution Before you restore your ACE10 or ACE20 backup archive files to the ACE30, ensure that you have the correct ACE30 license installed to accommodate the bandwidth, number of virtual contexts, and SSL TPS that are required by the configuration files in the backup archive. See the "Understanding the ACE30 Licenses" and the "Installing the ACE30 License" sections. Failure to install the correct license before restoring the backup archive may result in missing contexts or lower than expected bandwidth, compression performance, or SSL TPS. If you are upgrading to an ACE30, your ACE30 license was preinstalled by Cisco Systems based on your current licenses. To check your installed ACE30 license, enter the show license status command. For information about the minimum required ACE30 license for your current ACE10 or ACE20 license levels, see Table 9. If you need to install or upgrade an ACE30 license, see the "Managing ACE Software Licenses" chapter in the Cisco Application Control Engine Module Administration Guide.

To download and restore the backup archive on the standby ACE, perform the following steps:


Step 1 Log in to the new ACE30

switch login: admin
Password: xxxxxxxxx
Cisco Application Control Software (ACSW)
TAC support: http://www.cisco.com/tac
Copyright (c) 2002-2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
ACE/Admin#
 
   

Step 2 If you have not already done so, you must install the new ACE30 license now. See the "Installing the ACE30 License" section.

Step 3 Restore the backup archive and exclude the old ACE10 or ACE20 licenses by entering the following command:

ACE/Admin# restore all disk0:switch_08_April_2010_11_11_04_PM.tgz exclude licenses
 
   

The restore software may display errors during the restoration process because of minor software version differences among a few CLI commands, but you can ignore these errors. If necessary, resolve any major errors by adjusting your configuration. See Table 7 for a summary of ACE commands that can result in a restore error during the restoration process.

 
   

Step 4 Check the status of the restoration by entering the following command:

ACE/Admin# show restore status
Backup Archive: switch_08_April_2010_11_11_04_PM.tgz
Type          : Full
Start-time    : Fri Apr  9 00:12:21 2010
Finished-time : Fri Apr  9 00:12:38 2010
Status        : SUCCESS
Current vc    : C2
Completed     : 4/4

Step 5 Verify the current BOOT environment variable and configuration register setting that occurred as part of the restoration by entering the show bootvar command in Exec mode. For example, enter:

ACE/Admin# show bootvar
BOOT variable = "disk0:c6ace-t1k9-mz.A2_3_5.bin"
Configuration register is 0x1
 
   

Step 6 Remove the existing image from the boot variable on the ACE by entering the no boot system image:ACE_image command in configuration mode. For example, to remove the A2(3.5) image, enter the following command:

ACE/Admin# configure
Enter configuration commands, one per line. End with CNTL/Z.
ACE/Admin(config)# no boot system image:disk0:c6ace-t1k9-mz.A2_3_5.bin 
 
   

Step 7 Set the BOOT environment variable to specify the A4(1.0) or later image from the boot variable on the ACE by entering the boot system image:ACE_image command in configuration mode. For example, to select the A4(1.0) image, enter the following command:

ACE/Admin(config)# boot system image:c6ace-t1k9-mz.A4_1_0.bin
ACE/Admin(config)# exit
ACE/Admin#
 
   

Step 8 To verify the BOOT environment variable setting, enter the following command

ACE/Admin# show bootvar
BOOT variable = "disk0:c6ace-t1k9-mzg.A4_1_0.bin
Configuration register is 0x1
 
   

Step 9 Save the configurations of all contexts in the ACE by entering the following command:

ACE/Admin# write mem all
 
   

Step 10 From configuration mode on the supervisor engine, remove power from the standby ACE. For example, enter the following command:

c6k(config)#no power enable module 5
 
   

Continue with the "Reassociating the Supervisor Engine VLANs and Powering up the ACE" section.

Reassociating the Supervisor Engine VLANs and Powering up the ACE

Now that you have successfully restored the backup archive to the ACE30 and powered it down, reassociate the supervisor engine VLANs with the ACE. To reassociate the supervisor engine VLANs with the ACE, perform the following steps:


Step 1 You should still be logged in to the supervisor engine in the chassis. If not, log in now.

# telnet 192.168.12.15
Trying 192.168.12.15...
Connected to 192.168.12.15 (192.168.12.15).
Escape character is '^]'.
 
   
 
   
User Access Verification
 
   
Username: admin
Password: xxxxxxxx
c6k#
 
   

Step 2 Enter configuration mode.

c6k#config t
Enter configuration commands, one per line.  End with CNTL/Z.
c6k(config)#
 
   

Step 3 Reassociate the appropriate supervisor VLAN groups with the ACE30. For example, enter the following command for an ACE30 in chassis slot 5 and specify the correct VLAN group numbers or ranges for the ACE:

c6k(config)#svclc module 5 vlan-group 10-20,100,200
 
   

Step 4 Power up the standby module by entering the following command:

c6k(config)#power enable module 5

Continue with the "Checking the FT States of the Peers" section.

Checking the FT States of the Peers

After the restoration completes successfully and you have reassociated the supervisor engine VLANs with the ACE30, the ACE30 is ready to take over as the standby ACE. Before you force a switchover in the next section, check the FT states of the two peers. To check the states of the peers, enter the following command in all contexts:

ACE/Admin# show ft peer detail
 
   

All contexts should now be in the FSM_PEER_STATE_COMPATIBLE state.


Note If you have an ACE10 or ACE20 license with more than 5 virtual contexts, you may also observe the LICENSE_INCOMPATIBLE state in the License Compatibility field. This is expected and normal because of the differences in licensing between the ACE10 or ACE20 and the ACE30.


To check the redundancy states of the active and standby, enter the following command:

ACE/Admin# show ft group status
 
   

The active ACE should be in the ACTIVE state and the standby should be in the STANDBY_WARM state.

When you upgrade from one major release of ACE software to another major release (for example, from A2(3.0) to A4(1.0)) in a redundant configuration, bulk synchronization and dynamic incremental synchronization are automatically disabled while there is a software mismatch (split mode) between the two ACEs. We recommend that you do not make any configuration changes during this time and that you do not keep the ACEs in this state for an extended period of time. However, if you must make configuration changes while the ACEs are in split mode, ensure that you manually synchronize to the standby ACE any configuration changes that you make on the active ACE. After you complete the software upgrade of both ACEs, a bulk sync occurs automatically and dynamic incremental sync will be enabled again. For details about config sync, see the Cisco Application Control Engine Module Administration Guide.


Note If you observe other states, see the Troubleshooting Redundancy page of the Application Control Engine (ACE) Troubleshooting Wiki. If you cannot solve your problem using the wiki, call the Cisco Technical Assistance Center (TAC) as described in the Contacting TAC section in the wiki.


Continue with the "Forcing a Switchover" section.

Forcing a Switchover

Before you can upgrade the active ACE10 or ACE20 module to an ACE30 in a redundant configuration, you must force a switchover of all FT groups from the active ACE to the standby ACE to ensure that there is no interruption of your non-proxied network traffic. To check the FT states of the peers and force a switchover, perform the following steps:


Step 1 Force a switchover of all configured FT groups by entering the following command on the active ACE:

ACE/Admin# ft switchover all
This command will cause card to switchover (yes/no)?  [no] yes
 
   

The standby ACE that you upgraded to an ACE30 becomes the new active ACE and the former active ACE10 or ACE20 is now the standby.

Step 2 Verify that the redundancy states of the active ACE and the standby ACE are now ACTIVE and STANDBY_WARM, respectively by entering the following command on the new active ACE.

ACE/Admin# show ft group status
 
   

Continue with the "Migrating the Former Active ACE10 or ACE20 to an ACE30" section.

Migrating the Former Active ACE10 or ACE20 to an ACE30

To migrate the former active ACE10 or ACE20 to an ACE30, repeat the procedures in the following sections in the order presented:

Removing the ACE10 or ACE20 from the Chassis

Installing the ACE30 in the Chassis

Configuring a Management VLAN Interface for IP Connectivity

Installing the ACE30 License

Copying the Backup Archive to Disk0

Disassociating the Supervisor Engine VLANs from the ACE

Restoring the Backup Archive Files and Powering Down the Standby

Reassociating the Supervisor Engine VLANs and Powering up the ACE

Check the FT states of the peers by entering the show ft peer detail and the show ft group status commands in Exec mode. The peer states should now be FSM_PEER_STATE_COMPATIBLE, and the FT group states should be ACTIVE and STANDBY_HOT, respectively.

Continue with the optional "Reenabling Preemption on the Active ACE30" section. If you do not wish to reenable preemption, the ACE30 migration process is now complete.

Reenabling Preemption on the Active ACE30

This section is optional and it is completely dependent on the needs of your network. If preempt was enabled before the migration, you may want to reenable it now. To reenable preemption on the active ACE30, perform the following steps:


Step 1 Log in to the active ACE30.

Step 2 Enter configuration mode.

ACE/Admin# config
ACE/Admin(config)#
 
   

Step 3 Reenable preemption for each FT group in the active ACE as follows:

ACE/Admin(config)# ft group 1
ACE/Admin(config-ft-group)# preempt
ACE/Admin(config-ft-group)#exit
ACE/Admin(config)# 
 
   

Reenabling preempt will likely cause a switchover if the peer has a higher priority.


This procedure concludes your ACE30 migration in a redundant configuration.

Migrating a Single ACE10 or ACE20 Module to an ACE30 Module

To migrate a single ACE10 or ACE20 module to an ACE30 module, read and perform the procedures in the following sections in the order presented:

Prerequisites

Before You Begin

Addressing Probe Port Inheritance

Understanding the ACE30 Licenses

Downloading and Installing the Supervisor Engine Image

Manually Backing Up Your Configuration Files and Dependent Files

Using the Backup Utility to Back Up Your Configuration Files and Dependent Files

Removing the ACE10 or ACE20 from the Chassis

Installing the ACE30 in the Chassis

Configuring a Management VLAN Interface for IP Connectivity

Installing the ACE30 License

Copying the Backup Archive to Disk0

Restoring the Backup Archive Files and Powering Down the Standby - In this section, do not perform Step 6.

Downgrading an ACE30 in a Redundant Configuration

If you need to downgrade the ACE from software version A4(1.0) or later to version A2(3.x) or A2(1.6a) or later, use the procedure that follows. Note that this procedure requires that you remove both ACE30s and reinstall the original ACE10s or ACE20s in their original slots. Before you attempt this downgrade process, please read this section in its entirety.

In a redundant configuration, dynamic incremental sync is a form of config sync that copies configuration changes that you make on the active ACE to the standby ACE when the two ACEs are running the same version of software and when both ACEs are up. When you downgrade from one major release of ACE software to another major release (for example, from A4(1.0) to A2(3.0), bulk sync, dynamic incremental sync, and connection replication are automatically disabled while the active ACE is running software version A4(1.0) and the standby ACE is running software version A2(3.0). See Table 10.

Table 10 Feature Matrix for Redundancy when the Active and the Standby ACEs Are Running Different Major Software Versions

Active
Standby
Bulk Sync
Dynamic
Incremental Sync
Connection Replication
Comments

A2(3.0)

A4(1.0)

Yes

Yes

Yes

A4(1.0)

A2(3.0)

No

No

No

Functionality not supported due to architectural differences between the ACE20 and the ACE30 hardware


We recommend that you do not make any configuration changes during this time and that you do not keep the ACEs in this split-mode state for an extended period of time. After you complete the downgrade of both ACEs, a bulk sync occurs automatically to replicate the entire configuration of the new active ACE to the new standby ACE. At this time, dynamic incremental sync and connection replication will be enabled again. For details about config sync, see Chapter 6, "Configuring Redundant ACEs" in the Cisco Application Control Engine Module Administration Guide.

This section contains the following topics:

Disabling Preemption in the Active ACE

Removing the ACE30 from the Chassis

Installing the Original ACE10 or ACE20 and Logging In

Checking the FT States of the Peers

Forcing a Switchover

Downgrading the Former Active ACE30 to an ACE10 or ACE20

Reenabling Preemption on the Active ACE10 or ACE20

Disabling Preemption in the Active ACE

To maintain the ACE in a known stable state in a redundant configuration, you must disable preemption for all FT groups in the active ACE. To identify the active ACE in an FT group, enter the show ft group status command. To disable preemption in the active ACE, perform the following steps:


Step 1 Enter configuration mode.

ACE/Admin# config
ACE/Admin(config)# 
 
   

Step 2 Disable preemption for all FT groups by entering the following commands.

ACE/Admin(config)# ft group 1
ACE/Admin(config-ft-group)# no preempt
ACE/Admin(config-ft-group)# exit
ACE/Admin(config)# 
 
   

Repeat this step for each FT group in your active ACE. You need to perform this step only for the first ACE in a redundant pair.

Step 3 Save the running-configuration files in all contexts by entering the following command.

ACE/Admin# write mem all
 
   

Continue with the "Removing the ACE30 from the Chassis" section.

Removing the ACE30 from the Chassis

Remove the standby ACE30 from the chassis. For details about how to remove a module from a chassis, see the "Removing a Module" section. Label the ACE30 with the chassis number, slot number and redundancy state for future reference. For example: "Chassis 1, slot 5, original standby."

Continue with the "Installing the Original ACE10 or ACE20 and Logging In" section.

Installing the Original ACE10 or ACE20 and Logging In

Insert the original standby ACE10 or ACE20 in the slot from which you just removed the ACE30. For details about installing a module in a chassis, see the "Installing a Module" section. The module automatically boots up.

After the ACE10 or ACE20 module boots up, log in as follows:

ACE login: admin
Password: xxxxxxxx
Last login: Tue Oct 26 22:44:36 2010 from 172.23.244.110 on pts/0
Cisco Application Control Software (ACSW)
TAC support: http://www.cisco.com/tac
Copyright (c) 1985-2010 by Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
User 'www' is disabled.Please change the password to enable the user.

ACE/Admin#

Continue with the "Checking the FT States of the Peers" section.

Checking the FT States of the Peers

The original ACE10 or ACE20 is now ready to take over as the standby ACE. Before you force a switchover in the next section, check the FT states of the two peers. To check the states of the peers, enter the following command in all contexts:

ACE/Admin# show ft peer detail
 
   

All contexts should now be in the FSM_PEER_STATE_COMPATIBLE state.


Note If you have an ACE10 or ACE20 license with more than 5 virtual contexts, you may also observe the LICENSE_INCOMPATIBLE state in the License Compatibility field. This is expected and normal because of the differences in licensing between the ACE10 or ACE20 and the ACE30.


To check the redundancy states of the active and standby, enter the following command:

ACE/Admin# show ft group status
 
   

The active ACE should be in the ACTIVE state and the standby should be in the STANDBY_WARM state.

When you downgrade from one major release of ACE software to another major release (for example, from A4(1.0) to A2(3.0)) in a redundant configuration, bulk synchronization and dynamic incremental synchronization are automatically disabled while the active ACE is running A4(1.0) and the standby ACE is running the earlier version. We recommend that you do not make any configuration changes during this time and that you do not keep the ACEs in this state for an extended period of time. After you complete the downgrade of both ACEs, a bulk sync occurs automatically and dynamic incremental sync will be enabled again. For details about config sync, see the Cisco Application Control Engine Module Administration Guide.


Note If you observe other states, see the Troubleshooting Redundancy page of the Application Control Engine (ACE) Troubleshooting Wiki. If you cannot solve your problem using the wiki, call the Cisco Technical Assistance Center (TAC) as described in the Contacting TAC section in the wiki.


Continue with the "Forcing a Switchover" section.

Forcing a Switchover

Before you can downgrade the active ACE30 to an ACE10 or ACE20 in a redundant configuration, you must force a switchover of all FT groups from the active ACE to the standby ACE. To force a switchover and check the FT states of the peers, perform the following steps:


Step 1 Force a switchover of all configured FT groups by entering the following command on the active ACE:

ACE/Admin# ft switchover all
This command will cause card to switchover (yes/no)?  [no] yes
 
   

The standby ACE30 that you downgraded to an ACE10 or ACE20 becomes the new active ACE and the former active ACE30 is now the standby.

Step 2 Verify that the redundancy states of the active ACE and the standby ACE are now ACTIVE and STANDBY_WARM, respectively by entering the following command on the new active ACE.

ACE/Admin# show ft group status
 
   

Continue with the "Downgrading the Former Active ACE30 to an ACE10 or ACE20" section.

Downgrading the Former Active ACE30 to an ACE10 or ACE20

To downgrade the former active ACE30 to an ACE10 or ACE20, repeat the procedures in the following sections in the order presented:

Removing the ACE30 from the Chassis

Installing the Original ACE10 or ACE20 and Logging In

Check the FT states of the peers by entering the show ft peer detail and the show ft group status commands in Exec mode on the active ACE. The peer states should now be FSM_PEER_STATE_COMPATIBLE, and the FT group states should be ACTIVE and STANDBY_HOT, respectively.

Continue with the optional "Reenabling Preemption on the Active ACE10 or ACE20" section. If you do not wish to reenable preemption, the downgrade process is now complete.

Reenabling Preemption on the Active ACE10 or ACE20

This section is optional and it is completely dependent on the needs of your network. If preemption was enabled before the migration, you may want to reenable it now. To reenable preemption on the active ACE30, perform the following steps:


Step 1 Log in to the active ACE10 or ACE20.

Step 2 Enter configuration mode.

ACE/Admin# config
ACE/Admin(config)#
 
   

Step 3 Reenable preemption for each FT group in the active ACE as follows:

ACE/Admin(config)# ft group 1
ACE/Admin(config-ft-group)# preempt
ACE/Admin(config-ft-group)#exit
ACE/Admin(config)# 
 
   

Reenabling preempt will likely cause a switchover if the peer has a higher priority.


This procedure concludes the downgrade of the ACE module from A4(1.0) or later to A2(3.x) or A2(1.6a) or later in a redundant configuration.

Downgrading a Single ACE30 Module

To downgrade a single ACE30 module, read and perform the procedures in the following sections in the order presented:

Removing the ACE30 from the Chassis

Installing the Original ACE10 or ACE20 and Logging In

Accessing the ACE Command-Line Interface

The software interface for the ACE module is the command-line interface (CLI). You access the ACE module CLI by performing one of these tasks:

Establishing a direct serial connection between your terminal and the ACE by making a serial connection to the console port on the front of the ACE.

Establishing a remote connection using the SSH or Telnet protocols from a PC.

Unless your Catalyst 6500 series switch or Cisco 7600 series router is located in a fully trusted environment, we recommend that you configure the ACE module using SSH encryption.

See the Cisco Application Control Engine Module Administration Guide for details about accessing the ACE module, performing initial set up, and establishing remote access.

Related Documentation

For information about caveats for the ACE module, see the Release Note for the Cisco Application Control Engine Module.

For information about the configuration of the ACE module, refer to the following documents:

Cisco Application Control Engine Module Getting Started Guide

Cisco Application Control Engine Module Administration Guide

Cisco Application Control Engine Module Virtualization Configuration Guide

Cisco Application Control Engine Module Routing and Bridging Configuration Guide

Cisco Application Control Engine Module Server Load-Balancing Configuration Guide

Cisco Application Control Engine Module Security Configuration Guide

Cisco Application Control Engine Module SSL Configuration Guide

Cisco Application Control Engine Module System Message Guide

Cisco Application Control Engine Module Command Reference

Cisco CSM-to-ACE Conversion Tool User Guide

Cisco CSS-to-ACE Conversion Tool User Guide

Cisco Application Control Engine (ACE) Troubleshooting Guide (wiki)

Cisco Application Control Engine (ACE) Configuration Examples (wiki)

To understand the Cisco IOS command-line interface and Cisco IOS command modes, see the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide or the Cisco 7600 Series Router Cisco IOS Software Configuration Guide.

Translated Safety Warnings


Warning

Invisible laser radiation present. Statement 1016

Waarschuwing

Onzichtbare laserstraling aanwezig.

Varoitus

Näkymättömiä lasersäteitä.

Attention

Rayonnement laser actif mais invisible.

Warnung

Unsichtbare Laserstrahlung.

Avvertenza

Radiazione laser invisibile.

Advarsel

Usynlig laserstråling.

Aviso

Radiação laser invisível presente.

¡Advertencia!

Existe radiación láser invisible.

Varning!

Nu pågående osynlig laserstrålning.

 




Warning

Blank faceplates and cover 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, faceplates, front covers, and rear covers are in place. Statement 1029

Waarschuwing

Lege vlakplaten en afdekpanelen vervullen drie belangrijke functies: ze voorkomen blootstelling aan gevaarlijke voltages en stroom binnenin het frame, ze bevatten elektromagnetische storing (EMI) hetgeen andere apparaten kan verstoren en ze leiden de stroom van koellucht door het frame. Het systeem niet bedienen tenzij alle kaarten, vlakplaten en afdekkingen aan de voor- en achterkant zich op hun plaats bevinden.

Varoitus

Tyhjillä tasolaikoilla ja suojapaneeleilla on kolme tärkeää käyttötarkoitusta: Ne suojaavat asennuspohjan sisäisille vaarallisille jännitteille ja sähkövirralle altistumiselta; ne pitävät sisällään elektromagneettisen häiriön (EMI), joka voi häiritä muita laitteita; ja ne suuntaavat tuuletusilman asennuspohjan läpi. Järjestelmää ei saa käyttää, elleivät kaikki tasolaikat, etukannet ja takakannet ole kunnolla paikoillaan.

Attention

Ne jamais faire fonctionner le système sans que l'intégralité des cartes, des plaques métalliques et des panneaux avant et arrière ne soient fixés à leur emplacement. Ceux-ci remplissent trois fonctions essentielles : ils évitent tout risque de contact avec des tensions et des courants dangereux à l'intérieur du châssis, ils évitent toute diffusion d'interférences électromagnétiques qui pourraient perturber le fonctionnement des autres équipements, et ils canalisent le flux d'air de refroidissement dans le châssis.

Warnung

Blanke Faceplates und Abdeckungen haben drei wichtigen Funktionen: (1) Sie schützen vor gefährlichen Spannungen und Strom innerhalb des Chassis; (2) sie halten elektromagnetische Interferenzen (EMI) zurück, die andere Geräte stören könnten; (3) sie lenken den kühlenden Luftstrom durch das Chassis. Das System darf nur betrieben werden, wenn alle Karten, Faceplates, Voder- und Rückabdeckungen an Ort und Stelle sind.

Avvertenza

Le piattaforme bianche e i panelli di protezione hanno tre funzioni importanti: Evitano l'esposizione a voltaggi e correnti elettriche pericolose nello chassis, trattengono le interferenze elettromagnetiche (EMI) che potrebbero scombussolare altri apparati e dirigono il flusso di aria per il raffreddamento attraverso lo chassis. Non mettete in funzione il sistema se le schede, le piattaforme, i panelli frontali e posteriori non sono in posizione.

Advarsel

Blanke ytterplater og deksler sørger for tre viktige funksjoner: de forhindrer utsettelse for farlig spenning og strøm inni kabinettet; de inneholder elektromagnetisk forstyrrelse (EMI) som kan avbryte annet utstyr, og de dirigerer luftavkjølingsstrømmen gjennom kabinettet. Betjen ikke systemet med mindre alle kort, ytterplater, frontdeksler og bakdeksler sitter på plass.

Aviso

As faces furadas e os painéis de protecção desempenham três importantes funções: previnem contra uma exposição perigosa a voltagens e correntes existentes no interior do chassis; previnem contra interferência electromagnética (EMI) que poderá danificar outro equipamento; e canalizam o fluxo do ar de refrigeração através do chassis. Não deverá operar o sistema sem que todas as placas, faces, protecções anteriores e posteriores estejam nos seus lugares.

¡Advertencia!

Las placas frontales y los paneles de relleno cumplen tres funciones importantes: evitan la exposición a niveles peligrosos de voltaje y corriente dentro del chasis; reducen la interferencia electromagnética (EMI) que podría perturbar la operación de otros equipos y dirigen el flujo de aire de enfriamiento a través del chasis. No haga funcionar el sistema a menos que todas las tarjetas, placas frontales, cubiertas frontales y cubiertas traseras estén en su lugar.

Varning!

Tomma framplattor och skyddspaneler har tre viktiga funktioner: de förhindrar att personer utsätts för farlig spänning och ström som finns inuti chassit; de innehåller elektromagnetisk interferens (EMI) som kan störa annan utrustning; och de styr riktningen på kylluftsflödet genom chassit. Använd inte systemet om inte alla kort, framplattor, fram- och bakskydd är på plats.

 



Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html