Guest

Cisco 7000 Series Routers

Channel Interface Processor (CIP2) Install. and Config.

 Feedback

Table Of Contents

Second Generation Channel Interface Processor (CIP-2) Installation and Configuration

Contents

Related Documentation

CIP2 Installation Prerequisites

CIP2 Software, Hardware, and Microcode Prerequisites

CIP2 Microcode Overview

ECA Software, Hardware, and Microcode Prerequisites

Safety Guidelines

Preventing Electrostatic Discharge Damage

Guidelines for Interface Processor Removal and Installation

Tools and Parts Required

What is the Cisco 7000 Series?

What Is the Cisco 7500 Series?

What is the CIP2?

Channel Attachment Overview

CIP2 Overview

CIP2 Description

CIP2 Hardware Installation

Removing a CIP2 or an Interface Processor Filler

Installing a CIP2

Attaching the CIP2 to the Channel

Checking the CIP2 Installation

CIP2 Microcode Guidelines

How Does CIP Microcode Ship?

CIP2 Microcode Upgrade Overview

Configuring Microcode

Using Flash Memory

Running CIP2 Diagnostic Tests

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Second Generation Channel Interface Processor (CIP-2) Installation and Configuration


Product Numbers: CX-CIP2-ECA1(=), CX-CIP2-ECA2(=), CX-CIP2-ECAP1(=), CX-CIP2-PCA1(=), CX-CIP2-PCA2(=), CX-CIP2-U-ECA1(=), CX-CIP2-U-ECA2(=), CX-CIP2-U-ECAP1(=), CX-CIP2-U-PCA1(=), CX-CIP2-U-PCA2(=), CAB-PCA-Y=, CAB-PCA-VA=, CAB-PCA-VB= <Caveat ID>

This document contains instructions for installing (or replacing) the second-generation Channel Interface Processor (CIP2) in the Cisco 7000 series routers and the Cisco 7500 series routers.


Note The following Cisco IOS releases support the CIP2: Release 10.2(13) or later, Release 10.3(13) or later, Release 11.0(10) or later, or Release 11.1(5) or later. For earlier releases, CIP2 is supported with a special microcode image.

This microcode image is available through download from Cisco Connection Online (CCO), on disks shipped with the CIP2 when shipped separately from a system (as a spare), or is already in Flash memory on a preconfigured system. (For instructions on placing CIP2 microcode in Flash memory, see the "CIP2 Microcode Guidelines" section.)

We recommend that you load and use the version of CIP2 microcode that is bundled with your Cisco IOS software. If you choose not to, you must then copy a CIP2 microcode image into Flash memory and use a specified configuration command to instruct the Cisco IOS software to use this microcode image instead of the microcode image bundled with your version of the Cisco IOS software; however, this is unnecessary if you load the bundled, recommended CIP2 microcode version.

(For general information on CIP2 microcode, refer to the "CIP2 Microcode Overview" section. For specific instructions on configuring the Cisco IOS software to use a CIP2 microcode image from Flash memory, refer to the "CIP2 Microcode Upgrade Overview" section.)



Note For additional specific CIP2 software and hardware requirements, refer to the "CIP2 Software, Hardware, and Microcode Prerequisites" section.

Your CIP2 might contain a newer hardware version of the ESCON channel adapter (ECA). For additional specific software, hardware, and microcode requirements for the next-generation ECAs, refer to the "ECA Software, Hardware, and Microcode Prerequisites" section. For information on how to determine if your CIP2 contains a newer version of the ECA, refer to the "Verifying the ECA Hardware Version by Examining the ECA Hardware" section or the "Verifying the ECA Hardware Version Using the show controllers cbus Command" section.

For complete and detailed descriptions of CIP2-related interface and configuration commands, configuration options, and requirements, refer to the appropriate configuration and command reference publications listed in the "Related Documentation" section.


Contents

This document includes the following sections:

Related Documentation

CIP2 Installation Prerequisites

What is the CIP2?

CIP2 Hardware Installation

Checking the CIP2 Installation

CIP2 Microcode Guidelines

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Related Documentation

The Cisco IOS software running your router contains extensive features and functionality. The effective use of many of many of these features is easier if you have more information at hand. For additional information on configuring and maintaining the Cisco 7000 series and Cisco 7500 series routers and CIP2, the following documentation resources are available to you:

Cisco documentation and additional literature are available in a CD-ROM package that ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

Refer to the following Cisco IOS software modular configuration, modular command reference, and support publications, as appropriate for your configuration:

Configuration Fundamentals Configuration Guide

Configuration Fundamentals Command Reference

Security Configuration Guide

Security Command Reference

Wide-Area Networking Configuration Guide

Wide-Area Networking Command Reference

Network Protocols Configuration Guide, Part 1, 2, and 3 (three separate volumes)

Network Protocols Command Reference, Part 1, 2, and 3 (three separate volumes)

Bridging and IBM Networking Configuration Guide

Bridging and IBM Networking Command Reference

Configuration Builder Getting Started Guide

Troubleshooting Internetworking Systems

Debug Command Reference

System Error Messages

Cisco IOS Software Command Summary

Cisco Management Information Base (MIB) User Quick Reference

Refer to the hardware installation and configuration guide that shipped with your Cisco 7000 series or Cisco 7500 series router

To view Cisco documentation or obtain general information about documentation, refer to the Documentation DVD, to the "Cisco.com" section. See the "Obtaining Documentation" section for additional information.

CIP2 Installation Prerequisites

Before you install the CIP2, review the safety and electrostatic discharge (ESD)-prevention guidelines in this section to avoid injuring yourself or damaging the equipment. This section also provides a list of parts and tools you will need to perform the installation, and lists the software and microcode requirements.

Following is the specific information included in this section:

CIP2 Software, Hardware, and Microcode Prerequisites

CIP2 Microcode Overview

ECA Software, Hardware, and Microcode Prerequisites

Safety Guidelines

Preventing Electrostatic Discharge Damage

Guidelines for Interface Processor Removal and Installation

Tools and Parts Required

What is the Cisco 7000 Series?

What Is the Cisco 7500 Series?

CIP2 Software, Hardware, and Microcode Prerequisites

This section provides important prerequisites you should observe regarding CIP2 software, hardware, and microcode.

Following are important software and hardware prerequisites concerning the CIP2:

To operate with the CIP2, the Cisco 7000 series systems require Cisco IOS Release 10.2(13) or later, Release 10.3(13) or later, Release 11.0(10) or later, Release 11.0(10)BT or later, Release 11.1(5) or later, or Release 11.2(1) or later.

To operate with the CIP2, the Cisco 7500 series systems require Cisco IOS Release 10.3(13) or later,Release 11.0(10) or later, Release 11.0(10)BT or later, Release 11.1(5) or later, or Release 11.2(1) or later.

Refer to Table 1 for the specific Cisco IOS image names.

The CIP2 operates with the CxBus in the Cisco 7000 series routers with either of the following processor types:

Route Processor (RP) and Switch Processor (SP) (or Silicon Switch Processor [SSP]) combination

7000 Series Route Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) combination

The CIP2 operates with the CyBus in the Cisco 7500 series routers, which use the Route Switch Processor (RSP).


Caution To prevent system problems in Cisco 7000 series and Cisco 7500 series systems running Cisco IOS images earlier than Cisco IOS Release 11.1(5), CIP2 (second-generation) cards must not be installed in the same chassis system with CIP (first-generation) cards.

Table 1 lists the specific Cisco IOS software release images that are compatible with the CIP2.

Table 1 Cisco IOS Release Image Names

Cisco IOS Release
Image Names

Release 10.21

gs7-k2-mz, gs7-p2-mz

Release 10.3 1

gs7-k2-mz, gs7-p2-mz
rsp-k2-mz, rsp-p2-mz

Release 11.0 1

gs7-k2-mz, gs7-p2-mz, gs7-ak2-mz
rsp-k2-mz, rsp-p2-mz, rsp-ak2-mz

Release 11.0(10)BT

gs7-k2-mz and rsp-k2-mz

Release 11.1 and later

Starting with Release 11.1, all Cisco IOS images that support the CIP also support the CIP2. The images that support the CIP and CIP2 are indicated by the letters j, p, d, and i in the image name.

1 The Cisco IOS Release 10.2, Release 10.3, and Release 11.0 image names that contain a "2" are compatible with the CIP2.



Note Cisco IOS Releases 10.2 and 10.3 do not support the second or third ECA hardware version. These newer hardware versions of the ECA have specific Cisco IOS release requirements. For information on these release requirements, refer to the "ECA Software, Hardware, and Microcode Prerequisites" section. For information on how to determine if your CIP2 contains the second or third version of the ECA, refer to the "Verifying the ECA Hardware Version by Examining the ECA Hardware" section or the "Verifying the ECA Hardware Version Using the show controllers cbus Command" section.


Table 2 specifies the name of the recommended minimum level of CIP2 microcode for a corresponding Cisco IOS release, which should be used if you are using a Cisco IOS release earlier than the Cisco IOS releases listed in the "CIP2 Software, Hardware, and Microcode Prerequisites" section or in the Notes information on page 2.

Table 2 Cisco IOS Releases and CIP2 Microcode Images

Cisco IOS Release
CIP2 Microcode Image1
Minimum CIP2 Microcode Image Required for the Second and Third ECA Hardware Versions

10.2

cipp20-8 or later

Not supported

10.3

cipp20-8 or later

Not supported

11.0

cipp21-8 or later

cipp21-14 or later, or cipp-k-22-152 or later

11.1

cip22-6 or later

cip22-15 or later

11.2

cip22-6 or later

cip22-15 or later

11.3

cip25-2 or later

All releases support all ECA hardware versions

12.0

cip26-4 or later

All releases support all ECA hardware versions

1 In general, CIP2 microcode image names that have the prefix "cipp" are compatible with the CIP2.

2 This image is for Cisco IOS Release 11.0(10)BT or later.


The show version and show hardware commands display the current hardware configuration of the router, including the system software version that is currently loaded and running. The show microcode command lists the bundled microcode (target hardware) version for each processor type. The CIP (and now CIP2) microcode is no longer bundled in Cisco IOS 11.1 and later, so the show microcode command lists the default microcode that should be used with this Cisco IOS version. The show controller cbus command shows the microcode version you are running. (For additional descriptions of configuration commands, refer to the publications listed in the "Related Documentation" section.)

You can determine the current version of software or microcode stored in Flash memory either by removing the processor module and checking the Flash device label or by using the show controller cbus command and checking the EPROM version number in the output. (Refer to the "CIP2 Microcode Guidelines" section, for basic configuration information, and to the appropriate software documentation for complete configuration instructions and examples, listed in the "Related Documentation" section.)

If the displays indicate that the required system software and microcode is not available in your system, refer to the "Cisco.com" section, or contact a service representative for upgrade information.

CIP2 Microcode Overview

Microcode, also known as firmware, is a set of processor-specific software instructions that enables and manages the features and functions of a specific processor type. At system startup or reload, the system loads the microcode for each processor type present in the system.

The CIP2 microcode boot image resides in a Flash memory device on the CIP2 motherboard. The entire CIP2 microcode image is delivered on a Flash memory card, on floppy disks, or is available via download from CCO.

New microcode is released to enable new features, improve performance, or fix bugs in earlier versions. The Cisco 7000 series and Cisco 7500 series routers feature downloadable software and microcode for most upgrades. These features enable you to download new (upgraded) images remotely, store the images in router memory, and load the new images at system startup without having to physically access the router. You can store multiple versions for a specific processor type in Flash memory, and use configuration commands to specify which version the system should load at startup. All interfaces of the same type (for example, all CIP2s) use the same microcode image.


Caution To ensure proper operation of the CIP2, and to preclude system problems, you should use only the CIP2 microcode image that is recommended for the version of Cisco IOS you are running (see Table 2).

By default, the CIP2 microcode is loaded from either onboard Flash memory (if you have a Cisco 7000 or Cisco 7010 with an RP) or the Flash memory card in slot0 for the Cisco 7500 series routers. The default CIP2 microcode version can be found by entering the show microcode command.

The following is a partial-display example of the show microcode command output:

Router# show microcode
Microcode bundled in system
Card    Microcode
Type    Version      device:filename
----    ---------    -------------------

(additional display text omitted from this example)

CIP2    22-15        slot0:cip22-15

(additional display text omitted from this example)

Microcode flash default images

Note For all Cisco IOS releases earlier than Cisco IOS Release 11.1, the filenames of all CIP2 microcode images use the following nomenclature: cippnn-nn, where nn-nn is the specific microcode version. In Cisco IOS Release 11.1 or later, the filenames of all CIP2 (and CIP) microcode images use the nomenclature cipnn-nn.


ECA Software, Hardware, and Microcode Prerequisites

The ECA/CIP2-motherboard assemblies ship as follows:

Combination PCA and ECA—CX-CIP2-ECAP1(=)

One ECA on a dual carrier—CX-CIP2-ECA1(=)

Two ECAs on a dual carrier—CX-CIP2-ECA2(=)

(Add an equal sign (=) to the product number when you order interface processors as spares.)

One of three hardware versions of the ECA will be installed on your CIP2. The three hardware versions of the ECA can be used in all Cisco 7000 series and Cisco 7500 series routers. The three versions of the ECA are also compatible with each other and with the CIP2.

However, the second and third ECA hardware versions have specific restrictions regarding the Cisco IOS software release your host Cisco 7000 series or Cisco 7500 series router is running, and the CIP2 microcode images to use that are compatible with the second and third ECA hardware versions and the Cisco IOS software images they require.

For information on determining the ECA hardware version on your CIP2, refer to the "Verifying the ECA Hardware Version by Examining the ECA Hardware" section or the "Verifying the ECA Hardware Version Using the show controllers cbus Command" section.

The following are the specific Cisco IOS software and CIP2 microcode requirements that we recommend you carefully observe before you use the second or third ECA hardware versions installed on your CIP2 card:

CIP2 Microcode Release cipp21-14 or later, for Cisco 7000 series and Cisco 7500 series routers running Cisco IOS Release 11.0(14) or later

CIP2 Microcode Release cipp-k-22-15 or later, for Cisco 7000 series and Cisco 7500 series routers running Cisco IOS Release 11.0(14)BT or later

CIP2 Microcode Release cip22-15 or later, for Cisco IOS Release 11.1(10) or later, or Release 11.2(5) or later

All CIP2 microcode releases that work with the Cisco IOS Release 11.3 or later are compatible with the second or third ECA hardware version.

The appropriate CIP2 microcode images are bundled with the Cisco IOS software.

Verifying the ECA Hardware Version by Examining the ECA Hardware

This section contains information on how to determine which hardware version of the ECA is installed on your CIP2. Because ECAs ship under identical product numbers, you must refer to the different part numbers (73-xxxx-xx) and component layouts of the three ESCON channel adapter cards, which are shown in Figure 1, Figure 2 , and Figure 3, then make the appropriate comparisons to the CIP2/ECA assembly shipped to you.

The second and third hardware versions of the ECA are identified by part numbers 72-3936-02 or greater ( Figure 1) or 73-2185-02 or greater ( Figure 2). The first ECA hardware version is part number 73-1201-02 or lower ( Figure 3).

If you determine that you have the second or third ECA hardware version ( Figure 1 or Figure 2), you must observe and comply with the preceding ESCON channel adapter software and microcode prerequisites.

If you determine that you have the first ECA hardware version ( Figure 3), no further action is required.

Figure 1 Third ECA Hardware Version Installed on CIP2

Figure 2 Second ECA Hardware Version Installed on CIP2

Figure 3 First ECA Hardware Version Installed on CIP2

Verifying the ECA Hardware Version Using the show controllers cbus Command

This section provides an alternate method for verifying your ECA's hardware version.


Note If you have Cisco IOS software and CIP2 microcode images loaded and running that support the second and third ECA hardware versions (see Table 2 and the "ECA Software, Hardware, and Microcode Prerequisites" section), then you can also verify which ECA hardware version you have installed using the show controllers cbus command.


Refer to the arrow in the following partial-display example of the show controllers cbus command; a second or third ECA hardware version is indicated by hw version 02 or  hw version 03:

Router# show controllers cbus

(additional text omitted from this example)

slot0: CIP2, hw 5.0, sw 206.172, ccb 5800FF20, cmdq 48000080, vps 8192
    software loaded from flash slot0:biff/cip206-172.cbus_kernel_hw5
    Loaded:seg_eca         Rev. 0    Compiled by biff on Mon 10-Feb-97 09:28

    EPROM version 2.1, VPLD version 5.8
—>  ECA0: hw version 02, microcode version C50602D4
    Load metrics:
      Memory    dram 29763656/32M
      CPU       1m  n/a, 5m  n/a, 60m  n/a
      DMA       1m  n/a, 5m  n/a, 60m  n/a
      ECA0      1m  n/a, 5m  n/a, 60m  n/a

If the installed ECA is the first ECA hardware version, then  hw version 01 or  hw version 00 is displayed, as follows:

(additional text omitted from this example)
 
—>  ECA0: hw version 01, microcode version C50602D4

If the installed ECA is the second ECA hardware version, then  hw version 02 is displayed, as follows:

(additional text omitted from this example)
 
—>  ECA0: hw version 02, microcode version C50602D4

If the installed ECA is the third ECA hardware version, then  hw version 03 is displayed, as follows:

(additional text omitted from this example)
 
—>  ECA0: hw version 03, microcode version C50602D4

Note If you determine that you have the second or third hardware version of the ECA (hw version 02 or hw version 03 is displayed), you must observe and comply with the ECA software and microcode prerequisites (refer to Table 2 and the "ECA Software, Hardware, and Microcode Prerequisites" section).

If you determine that you have the first hardware version of the ECA (hw version 00 or hw version 01 is displayed), no further action is required.


If you see either of the following sets of error messages displayed, you must upgrade the Cisco IOS software and CIP2 microcode by observing and complying with the ECA Cisco IOS software and microcode prerequisites (refer to Table 2 and the "ECA Software, Hardware, and Microcode Prerequisites" section).

%CIP2-0-MSG: %ADAPTER-0-DIAGFAIL: Port 0 failed the I/O chip tests diagnostic 
%CIP2-0-MSG: %ADAPTER-0-DIAGDATA: Module Call: 123 Error ID: FF85

%CIP2-0-MSG: %ADAPTER-0-DIAGFAIL: Port 0 failed the Electrical wrap diagnostic
%CIP2-0-MSG: %ADAPTER-0-DIAGDATA: Module Call: 1221 Error ID: FE14

Note Running CIP2 microcode versions earlier than cip21-11 and cip22-12 with the second or third ECA hardware versions will always result in error messages. Running CIP2 microcode versions earlier than cip21-14 and cip22-15 with the second or third ECA hardware versions might result in error messages.


Safety Guidelines

This section lists safety guidelines you should follow when working with any equipment that connects to electrical power or telephone wiring.

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


Electrical Equipment

Follow these basic guidelines when working with any electrical equipment:

Before beginning any procedures requiring access to the chassis interior, locate the emergency power-off switch for the room in which you are working.

Disconnect all power and external cables before moving a chassis.

Do not work alone when potentially hazardous conditions exist.

Never assume that power has been disconnected from a circuit; always check.

Do not perform any action that creates a potential hazard to people or makes equipment unsafe.

Carefully examine your work area for possible hazards such as moist floors, ungrounded power extension cables, and missing safety grounds.

Telephone Wiring

Use the following guidelines when working with any equipment that is connected to telephone wiring or to other network cabling:

Never install telephone wiring during a lightning storm.

Never install telephone jacks in wet locations unless the jack is specifically designed for wet locations.

Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface.

Use caution when installing or modifying telephone lines.

Preventing Electrostatic Discharge Damage

Electrostatic Discharge Damage (ESD), which can occur when electronic cards or components are improperly handled, results in complete or intermittent failures.

Following are guidelines for preventing ESD damage:

Always use an ESD-preventive wrist or ankle strap and ensure that it makes good skin contact.

When you work at the interface processor end of the chassis, connect the equipment end of the strap to a captive installation screw on an installed interface processor, or to any unpainted chassis surface.

When you install a processor module, use the ejector levers to properly seat the bus connectors in the backplane, then tighten both captive installation screws.

Handle processor modules by the carrier handles and carrier edges only; never touch the board or any connector pins.

When you remove a processor module, place it card side up on an antistatic surface or in a static shielding bag. Immediately place the module in a static shielding bag if you need to return it to Cisco.

Avoid contact between electronic equipment and clothing. Antistatic straps only protect the equipment from ESD voltages on the body; ESD voltages on clothing can still cause damage.


Caution For safety, periodically check the resistance value of the antistatic strap. The measurement should be between 1 and 10 megohms.

Guidelines for Interface Processor Removal and Installation

This section describes mechanical functions of system components, emphasizes the importance of following correct procedures to avoid unnecessary board failures, and is for background only; specific procedures follow in the "CIP2 Hardware Installation" section.

You can remove and replace interface processors while the system is operating; you do not need to notify the software or reset the system power. This functionality enables you to add, remove, or replace interface processors with the system online, which provides a method that is seamless to end users on the network, maintains all routing information, and ensures session preservation.

After an interface processor is reinstalled, the system brings on line only interfaces that match the current configuration and were previously configured as up; all others require that you configure them with the configure command.


Caution The system can indicate a hardware failure if you do not follow proper procedures. Remove or insert only one interface processor at a time. Allow at least 15 seconds for the system to complete the preceding tasks before removing or inserting another interface processor. Disrupting the sequence before the system completes its verification can cause the system to interpret hardware failures.

All interface processors have ejector levers that allow you to firmly seat an interface processor in the interface processor slot. The function of the ejector levers is to align and seat the card connectors in the backplane.


Caution Always use the ejector levers to remove or install the CIP2. The ejectors help ensure that backplane connectors on the card are fully seated in, or fully ejected from, the backplane. Failure to use the ejector levers could result in a partial backplane connection, which can hang the system.

The captive installation screws on the ends of the CIP2 faceplate, when tightened, provide EMI shielding and also help ensure proper seating in the backplane. After using the ejector levers to install a CIP2, tighten the captive installation screws to prevent the CIP2 from becoming partially dislodged from the backplane. These screws must be tightened to meet EMI specifications.

Tools and Parts Required

You need the following tools and parts to install or replace a CIP2. If you need additional equipment, contact a customer service representative for ordering information.

Number 2 Phillips or one-quarter-inch flat-blade screwdriver for the captive installation screws on the CIP2. (Although most interface processors use slotted screws, some interface processor carriers use Phillips screws.)

A new CIP2 shipped as one of the product numbers listed in the "CIP2 Model Numbers" section.

The appropriate cables for your CIP2 type: bus and tag for a PCA (with terminal blocks or 78-pin connectors) and/or ESCON fiber with duplex connectors for an ECA.

ESD-preventive wrist strap or other device for preventing ESD damage.

Interface processor filler (MAS7K-BLANK) if you are removing a CIP2 and not installing a new CIP2 or other interface processor in the empty slot.

What is the Cisco 7000 Series?

This section provides an overview of the Cisco 7000 series routers. The Cisco 7000 series consists of the Cisco 7000 and Cisco 7010 routers. The CIP2 operates in the Cisco 7000 series routers.

For specific software and hardware requirements for the Cisco 7000 series systems, refer to the "CIP2 Software, Hardware, and Microcode Prerequisites" section.

In the Cisco 7000, slot 5 is reserved for the RSP7000 (RSP 7000 slot shown in Figure 4), which contains the system processor and performs packet switching functions; slot 6 is reserved for the RSP7000CI (RSP 7000CI slot shown in Figure 4), which contains all of the environmental monitoring functions for the Cisco 7000. The Cisco 7000 can also be used with the Route Processor (RP) and Switch Processor (SP) or SSP combination.

The remaining five slots (slots 0 through 4) are for interface processors, including the CIP2.

Figure 4 Cisco 7000 with RSP7000 and RSP7000CI Installed Interface Processor

Figure 5 shows the interface processor end of the Cisco 7000, which provides access to the seven processor slots and the removable power supplies. When facing the interface processor end of the chassis, the SP (or SSP) and RP slots are on the far right. The five interface processor slots are numbered 0 to 4 from left to right and are reserved for interface processors, including the CIP2.

Figure 5 Cisco 7000 with RP and SP (or SSP) Installed Interface Processor

In the Cisco 7010, slot 3 is reserved for the RSP7000 (RSP 7000 slot shown in Figure 6), which contains the system processor and performs packet switching functions; slot 4 is reserved for the RSP7000CI (RSP 7000CI slot shown in Figure 6), which contains all of the environmental monitoring functions for the Cisco 7010. The remaining three slots (slots 0 through 2) are for interface processors, including the CIP2.

Figure 6 Cisco 7010 with RSP7000 and RSP7000CI Installed Interface Processor

Figure 7 shows the interface processor end of the Cisco 7010, which provides access to the five processor slots. When facing the interface processor end of the chassis, the RP and SP (or SSP) slots are at the top. The three interface processor slots are numbered from the bottom up beginning with slot 0 (the bottom slot) through 2 (the center slot) and are reserved for interface processors, including the CIP2.

Figure 7 Cisco 7010 with RP and SP (or SSP) Installed (Interface Processor

What Is the Cisco 7500 Series?

This section provides an overview of the Cisco 7500 series routers. The Cisco 7500 series consists of the Cisco 7505, Cisco 7507, and Cisco 7513 routers. The CIP2 operates in the Cisco 7500 series routers.

For specific software and hardware requirements for the Cisco 7500 series systems, refer to the "CIP2 Software, Hardware, and Microcode Prerequisites" section.

Network interfaces reside on modular interface processors, including the CIP2, which are inserted into interface processor slots and provide a direct connection between external networks and the high-speed CyBus in the Cisco 7500 series. Figure 8, Figure 9, and Figure 10 show the rear of the Cisco 7500 series routers: the five-slot Cisco 7505, the seven-slot Cisco 7507, and the thirteen-slot Cisco 7513, respectively.

In the Cisco 7505 ( Figure 8), slot 4 is reserved for the Route Switch Processor (RSP1 or RSP4), which contains the system processor and performs packet switching functions. Slots 0 through 3 are for interface processors, including the CIP2.

Figure 8 Cisco 7505 Interface Processor

Figure 9 shows the rear of the Cisco 7507 router. In the Cisco 7507, up to two slots (2 and 3) are reserved for the Route Switch Processor (RSP2 and RSP4), which contains the system processor and performs packet switching functions. Slots 0 and 1 and 4 through 6 are for interface processors, including the CIP2.

Figure 9 Cisco 7507 Interface Processor End

Figure 10 shows the rear of the Cisco 7513. Two slots (6 and 7) are reserved for the second generation Route Switch Processor (RSP2 and/or RSP4), which contains the system processor and performs packet switching functions. Slots 0 through 5 and 8 through 12 are for interface processors, including the CIP2.

Figure 10 Cisco 7513 Interface Processor

What is the CIP2?

This section discusses channel attachment and the CIP2, its LED functions, and its memory and cable requirements.

The following information is included:

Channel Attachment Overview

CIP2 Overview

CIP2 Description

CIP2 Model Numbers

CIP2 DRAM Configurations

CIP2 LED Indicators and Sequences

ESCON and Bus and Tag Specifications

ESCON Cable

Bus and Tag Cables

Channel Attachment Overview

A mainframe channel (referred to as a channel) is an intelligent processor that manages the protocol on the communications media and controls the data transfer to and from the main central processing unit (CPU) storage. Devices called input/output processors (IOPs) communicate between the host CPU and the channel. One IOP controls multiple channels, and there is no relationship between the number of CPUs and the number of IOPs.

The channel relieves the mainframe CPU of direct communication with input/output (I/O) devices, which saves processing cycles and allows data processing and communications tasks to run concurrently. Channels use one or more channel paths as the links between mainframes and I/O devices. I/O devices are connected directly to control units, which provide the logical capabilities required to operate and control the I/O devices.

CIP2 Overview

The CIP2 provides up to two channel interfaces for Cisco 7000 series and Cisco 7500 series routers; in some situations, this can eliminate the need for a separate front-end processor (FEP). The CIP2 contains combinations of a bus and tag (also called an original equipment manufacturer's interface [OEMI] and a parallel I/O interface) adapter and an Enterprise Systems Connection (ESCON) adapter. The bus and tag adapter is called the Parallel Channel Adapter (PCA), and the ESCON adapter is called the ESCON Channel Adapter (ECA). (For important information on the ECA hardware versions refer to the "ECA Software, Hardware, and Microcode Prerequisites" section.) The PCA and ECA connect directly to the CIP2, and all combinations of the two adapters are available.


Note The ECAs and PCAs must be upgraded or replaced (in the field) by a Cisco-certified maintenance provider only. The CIP2 supports online insertion and removal, which allows you to install or remove a CIP2 while the system is operating, without shutting down system power.



Caution To prevent system problems in Cisco 7000 series and Cisco 7500 series systems running Cisco IOS images earlier than Cisco IOS Release 11.1(5), CIP2 (second-generation) cards must not be installed in the same chassis system with CIP (first-generation) cards.

CIP2 Description

The CIP2 ( Figure 11) consists of a motherboard that is mounted on a metal carrier and one or two ECA and/or PCA interfaces. (The CIP2's front-panel label reads Channel Interface Processor 2.) The ECA and PCA interfaces attach to the motherboard by means of a multipin connector located at the rear edge of the adapter. The ECA and PCA provide the channel attachment interfaces to connect your CIP2 to your channel.

The CIP2 has two DRAM SIMMs and comes configured with 32 MB of DRAM as the minimum standard (default) memory configuration. The CIP2 also has a Flash memory device for storing the CIP2 microcode boot image.

Figure 11 CIP 2


Note The ECA and PCA adapters can be upgraded or replaced (in the field) by a Cisco-certified maintenance provider only.



Caution To prevent damage, and to prevent insertion problems caused by misalignment of the adapters and motherboard, do not attempt to remove the adapters or motherboard from the carrier.

CIP2 Model Numbers

There are three CIP2 carrier types, which offer the following five interface adapter combinations:

One PCA on a PCA/ECA carrier—CX-CIP2-PCA1

Combination PCA and ECA—CX-CIP2-ECAP1

One ECA on a dual carrier—CX-CIP2-ECA1

Two ECAs on a dual carrier—CX-CIP2-ECA2

Two PCAs on a dual carrier—CX-CIP2-PCA2

Add an equal sign (=) to the product number when you order interface processors as spares. For example, the product number for the one PCA on a PCA/ECA carrier if ordered as a spare is CX-CIP2-PCA1(=).

The ECA has a female, duplex connector, and the PCA has a female, DB-78 connector. Figure 12 shows the ECA and PCA interface combinations that are available.

Figure 12 CIP2 Interface Channel Adapter Combinations


Caution The second and third ECA hardware versions have specific software, hardware, and microcode requirements that must be observed to ensure proper system operation. To determine if you have the first ECA or the second ECA on your CIP2, refer to the "ECA Software, Hardware, and Microcode Prerequisites" section.

CIP2 DRAM Configurations

Each CIP2 model is available in the following configurations of dynamic random-access memory (DRAM) single in-line memory modules (SIMMs):

32-MB DRAM—MEM-CIP-32M

32-MB DRAM—MEM-CIP-32M(=)

64-MB DRAM—MEM-CIP-64M(=)

128-MB DRAM—MEM-CIP-128M(=)


Note MEM-CIP-32M is the default memory configuration that ships on the CIP2. MEM-CIP-32M= is a spare memory option, which is intended for CIP2 cards ordered without DRAM.

All CIP2 DRAM upgrade products ship with the configuration note Upgrading DRAM on the CIP2 (Document Number 78-3915-xx, where xx is the latest version of the document). This configuration note is also available on the Documentation CD-ROM.

CIP2 DRAM can be upgraded in the field by Cisco-certified service personnel only.


CIP2 LED Indicators and Sequences

Following are the functions of the CIP2 LEDs ( Figure 13):

Enabled—Indicates that the CIP2 has been enabled for operation by the system.

Present—Indicates that the ECA or PCA adapter has been detected by the CIP2.

Loaded—Indicates that the ECA or PCA adapter firmware has been completely loaded.

Signal—For the ECA, this LED indicates that the Sync signal has been detected. For the PCA, this LED indicates that the Operational Out signal has been detected. Note that even though a system reset and selective reset both cause the operational out signal to drop, the signal LED will still be on during those sequences.

Online—For the ECA, this LED indicates that an establish-logical-path request has been received from the channel. For the PCA, this LED indicates that the PCA is ready to establish connection to the host channel.

Figure 13 CIP2 LED Indicators

The following are the sequences for the CIP2 LED indicators. The enabled LED is not part of the following sequences. On cold boots, the following LED sequences apply:

 
Present
Loaded
Signal
Online

Port 1

On

On

Off

Off

Port 0

Off

Off

Off

Off


 
Present
Loaded
Signal
Online

Port 1

On

On

On

On

Port 0

On

On

Off

Off


 
Present
Loaded
Signal
Online

Port 1

On

On

On

On

Port 0

On

On

On

On


The following LED sequence indicates that the CIP2 is waiting for commands from the RP (or RSP).

 
Present
Loaded
Signal
Online

Port 1

Off

Off

Off

Off

Port 0

Off

Off

Off

Off


On warm boots, the LEDs flash briefly. On downloads, the following three LED sequences apply; the first indicates that the system is downloading volatile programmable logic device (VPLD) code.

 
Present
Loaded
Signal
Online

Port 1

On

On

On

On

Port 0

On

On

On

Off


The following sequence indicates that the CIP2 is downloading microcode:

 
Present
Loaded
Signal
Online

Port 1

Off

Off

Off

Off

Port 0

On

On

On

On


The following sequence indicates that the CIP2 is starting to execute the microcode:

 
Present
Loaded
Signal
Online

Port 1

Off

Off

Off

Off

Port 0

Off

Off

Off

Off


ESCON and Bus and Tag Specifications

Table 3 lists the specifications for the ESCON and bus and tag interfaces.

Table 3 ESCON and Bus and Tag Interfaces 

Characteristic
ESCON
Bus and Tag

Supported processor I/O architectures

ESA/390

System/370
370/Xa
ESA/390

Bit transmission

Serial

Parallel

Maximum distance (for LED with ESCON)

1.9 miles (3.1 km) point-to-point
5.7 miles (9.2 km) with two ESCON Directors

400 ft (122 m)1

Channel data rate

Up to 17 MBps2

Up to 4.5 MBps

Signaling rate3

200 Mbps4

4.5 MBps

Cable types

Fiber-optic (62.5/125 micron multimode)

Copper bus and tag

Addition of devices to running systems

Dynamic5

Static

Number of addressable devices per channel

256 x 16 x 16 x 2536

256

Connectable control units per channel

Up to 59 (through a 9032 ESCON Director)

Up to 8

Connectable channels per adapter

Up to 59 (through a 9032 ESCON Director)
Varies by control unit

1

1 The IBM 3044 C/D (host side/remote side) copper-to-fiber repeater can be used to extend this distance up to 1.2 miles (2 km).

2 MBps = megabytes per second.

3 For bus and tag, the signaling rate matches the channel data rate. For example, if you use a 3.0 MBps channel, the signaling rate is 3.0 MBps. The ESCON interface signals at a constant rate; the bus and tag interface signals at the data rate.

4 Mbps = megabits per second.

5 The CIP2 ESCON requires dynamic = NO with HCD.

6 Where 256 represents available unit addresses, 16 represents the number of partitions (LPARs), 16 represents the number of control unit images, and 253 represents the number of ESCON director paths. It is unlikely a system would have the resources to support the total number of available addresses.


ESCON Cable

The ECA interface uses 62.5/125 micrometer, multimode, fiber-optic cable with male duplex connectors at each end ( Figure 14). ESCON cables are not available from Cisco. Refer to the ESCON specifications in Table 3, and contact your cable supplier or the vendor of your host CPU to order the correct ESCON cable.

Figure 14 ESCON Interface Duplex Connector for the ECA

Bus and Tag Cables

Following are descriptions and illustrations of the bus and tag cables.

Y Cable

The bus and tag cable with three 78-pin connectors ( Figure 15) has a DB-78 male (PCA) connector on the CIP2 end, a DB-78 female connector on the next-control-unit end, and a DB-78 male connector on the from-host end.

Figure 15 PCA Bus and Tag Cable (Y Cable)

The bus and tag model number is CAB-PCA-Y (referred to as the Y cable). The male connector might be labeled IN and is typically black, but can also be a dark gray. The female connector might be labeled OUT and is typically light gray. The female OUT cable is nearest to the select/bypass switch, which is shown in Figure 16. (The IBM part number is 89F8392; however, this number is subject to change.)


Caution The Y cable must connect directly to the PCA. Do not connect any other cables directly to the PCA.


Note Note that the select/bypass switch is marked S (for select mode) and B (for bypass mode). The switch is located on the rear of the PCA connector ( Figure 16). The select/bypass switch is required to separate the cable from the PCA without "opening" the select-out loop.



Caution To prevent halting the system or negatively affecting the mainframe operating system, verify that the select/bypass switch is in bypass mode before you remove the PCA connector from the CIP2.

Figure 16 Select/Bypass Switch on the Rear of the PCA Connector (CAB-PCA-Y Bypass Shown

In select mode the PCA is operational, and the select-out signal is passed in a loop to all control lines on the channel. All control units have a relay that shorts the incoming select-out signal to the outgoing select-out signal when power is not applied to the control unit. When power is applied, the relay is opened, and the signal is passed to the PCA.

Without the select/bypass switch in bypass mode, the channel would need to be taken offline before servicing or replacing a CIP2. If the selected address does not match, the select-out signal is passed to the next control unit. If the select-out signal gets all the way back to the channel, the control unit being addressed is not present.


Note In bypass mode, the incoming select-out signal is shorted to the outgoing select-out signal, bypassing the PCA and allowing other devices on the channel to function properly.



Caution Make sure you provide adequate strain relief for the heavy bus and tag cables that attach to the PCA, to prevent damaging the PCA connector on the CIP2 by unintentionally disconnecting the Y cable from the PCA connector.

VA and VB Cables

The two bus and tag cables with connector blocks have a DB-78 (male or female) connector on the CIP2 end and 48-pin type-A connector blocks on the bus and tag ends ( Figure 17). VA and VB cables are 56 inches (1.42 meters) in length.

For the bus and tag cable that attaches between the host and the PCA, the model number is CAB-PCA-VA, and it is referred to as the VA cable. The female 78-pin connector might be labeled IN and is typically light gray. The cable labeled P2 is bus, and the cable labeled P3 is tag. Looking into the end of the female 78-pin connector (on the VA cable), with the wide part of the connector D-shell on top, the P2 (bus) cable is on the right, and the P3 (tag) cable is on the left. The plastic on the ends of the bus and tag connectors might be black or dark gray.

The IBM part number is 12G8058; however, this number is subject to change. The VA cable ships with a terminator; the Cisco model number CAB-PCA-VA includes this terminator. The terminator and VA cable together have the IBM part number 12G7988; however, this number is subject to change.

For the bus and tag cable that attaches between the next control unit and the PCA, the model number is CAB-PCA-VB, and it is referred to as the VB cable. The male 78-pin connector might be labeled OUT and is typically black or dark gray. The cable labeled P2 is bus, and the cable labeled P3 is tag. Looking into the end of the male 78-pin connector (on the VB cable), with the wide part of the connector D-shell on top, the P2 (bus) cable is on the left, and the P3 (tag) cable is on the right. The plastic on the ends of the bus and tag connectors might be light gray (as opposed to the black or dark gray plastic on the VA cable). The IBM part number is 12G7933; however, this number is subject to change.


Caution To prevent potential system problems, do not connect the VB cable directly to the PCA. You must connect the Y cable to the PCA, then connect the VB cable to the Y cables as appropriate.

Figure 17 PCA Bus and Tag, VA and VB Cables

The Y cable always attaches to the PCA. The VA cable attaches between the male end of the Y cable and the host. The VB cable attaches between the female end of the Y cable and the next (or new) control unit. Do not connect the VB cable directly to the PCA. If the PCA is the last control unit, channel termination is required at the end of the Y cable that points away from the host ( Figure 15). For attachment instructions refer to the "Attaching the CIP2 to the Channel" section.


Caution To prevent damaging the PCA connector on the CIP2 by unintentionally disconnecting the Y cable from the PCA connector, provide adequate strain relief for the heavy bus and tag cables that attach to the PCA.

CIP2 Hardware Installation

The following sections describe the procedures for installing or replacing the CIP2:

Removing a CIP2 or an Interface Processor Filler

Installing a CIP2

Attaching the CIP2 to the Channel


Caution To avoid unnecessary errors, read the "Guidelines for Interface Processor Removal and Installation" section before removing or replacing a CIP2.

Before installing a newCIP2, ensure that your system meets the minimum software and microcode requirements described in the "CIP2 Software, Hardware, and Microcode Prerequisites" section and "CIP2 Microcode Overview" section.

While you can remove and install a CIP2 without turning off system power, we do recommend that you administratively shut down CIP2 interface before insertion and removal. In any case, you must follow the insertion instructions carefully; for example, failure to use the ejector levers or insert the CIP2 properly can cause system error messages indicating a card failure.

Each unused interface processor slot contains an interface processor filler (which is an interface processor carrier without an interface card) to keep dust out of the chassis and to maintain proper airflow through the interface processor compartment.

If you install a new CIP2, select an empty interface processor slot and remove the interface processor filler. If you replace a CIP2, you can retain the existing interface configuration by removing the existing interface processor and installing the new one in the same slot; however, the new CIP2 must have the same channel adapter configuration as the CIP2 you replaced.

Proceed to the "Removing a CIP2 or an Interface Processor Filler" section for instructions on making an interface processor slot available for the new CIP2, then to the "Installing a CIP2" section for the installation instructions. After the new CIP2 is secure, follow the procedures in the "Checking the CIP2 Installation" section to verify that it is installed and functioning properly.

Removing a CIP2 or an Interface Processor Filler

You do not need to shut down the interface or the system power when you remove a CIP2; however, to prevent a possible interface control check on the mainframe, consult with your system administrator to take appropriate precautions. If you are installing a new CIP2, select an available slot and remove the interface processor filler. If you are replacing a CIP2, first remove the existing CIP2 and immediately place it component side up on an antistatic surface, then insert the new CIP2 in the same slot to retain the previous configuration for the new channel interface.

Figure 18 shows proper handling of an interface processor for installation in the Cisco 7010 or Cisco 7505 models. The processor slots are oriented horizontally in the Cisco 7010 and Cisco 7505, and vertically in the Cisco 7000, Cisco 7507, and Cisco 7513. When installing interface processors in these latter chassis, handle the interface processor in the same manner, but rotated 90 degrees clockwise.

Figure 18 Handling Interface Processors During Installation

Figure 19 shows the functions of the ejector levers in the correct orientation for the horizontal processor slots in a Cisco 7010 and Cisco 7505 chassis. In a Cisco 7000, Cisco 7507, and Cisco 7513 chassis, the function of the ejector levers is the same, but the orientation is rotated 90 degrees clockwise for the vertical processor slots.

Figure 19 Function of the Ejector Levers

The function of the ejector levers is to align and seat the card connectors in the backplane. Failure to use the ejector levers and insert the interface processor properly can disrupt the order in which the pins make contact with the backplane.

Following are examples of incorrect insertion practices and their results:

Using the handle to force the interface processor all the way into the slot can pop the ejector levers out of their springs. If you then try to use the ejector levers to seat the interface processor, the first layer of pins (which are already mated to the backplane) can disconnect and then remate with the backplane, which the system interprets as a card failure.

Using the handle to force or slam the interface processor all the way into the slot can also damage the pins on the card connectors if they are not aligned properly with the backplane.

When using the handle (rather than the ejector levers) to seat the interface processor in the backplane, you may need to pull the interface processor back out and push it in again to align it properly. Even if the connector pins are not damaged, the pins mating with and disconnecting from the backplane will cause the system to interpret a card failure. Using the ejector levers ensures that the card connector mates with the backplane in one continuous movement.

Using only the handle to seat or remove an interface processor, or failing to push the ejector levers flat against the CIP2 faceplate, can leave some (not all) of the connector pins mated to the backplane, a state that will halt the system.

Using the ejector levers and making sure that they are pushed fully into position ensures that all three layers of pins are mated with (or free from) the backplane.

It is also important to use the ejector levers when you remove an interface processor to ensure that the card connector pins disconnect from the backplane in the logical sequence expected by the system. Any processor module that is only partially connected to the backplane can halt the bus.

In the following procedures, two channel-related terms are used: vary offline refers to disabling an interface; vary online refers to enabling an interface. For instructions on how to vary the host channel or addresses online or offline, refer to the documentation for your mainframe operating system.

Refer to Figure 19 while performing the following steps to remove a CIP2 or interface processor filler. If you are removing an interface processor filler, proceed to Step 5. If you are replacing an existing CIP2, begin at Step 1.

Follow these steps to remove a CIP2 or an interface processor filler:


Step 1 Vary offline the addresses assigned to the PCA or ECA. For instructions on how to vary offline, refer to the documentation for your mainframe operating system.

Step 2 Use the shutdown interface command to shut down the appropriate interfaces.

Step 3 On the PCA connector, place the select/bypass switch in bypass mode.

Step 4 Disconnect the interface cables from the CIP2 interface ports.

Step 5 Use a screwdriver to loosen both the captive installation screws on the CIP2 or interface processor filler ( Figure 19a).

Step 6 Place your thumbs on the ends of each of the ejector levers and simultaneously pull them both outward, away from the interface port (in the opposite direction from that shown in Figure 19c) to release the carrier from the slot. If you are removing a CIP2, this also releases the CIP2 bus connector from the backplane.

Step 7 Grasp the handle with one hand and pull the CIP2 or interface processor filler straight out of the slot, keeping your other hand under the carrier to guide it ( Figure 18). Keep the carrier parallel to the backplane. Avoid touching the card or any connector pins.

Step 8 Place the removed CIP2 on an antistatic mat or foam pad, or place it in an antistatic bag if you need to return it to Cisco. If you removed an interface processor filler, store the filler in case you need it later to fill an empty slot.

Step 9 If the interface processor slot is to remain empty, install an interface processor filler to keep dust out of the chassis and to maintain proper airflow through the interface processor compartment.

Proceed to the next section to install a new CIP2.


Installing a CIP2

The CIP2 slides into any available interface processor slot and connects directly to the backplane of the Cisco 7000 series or Cisco 7500 series router. The backplane slots are keyed so that the CIP2 can be installed only in an interface processor slot. (Refer to Figure 4, Figure 6, Figure 8, Figure 9, or Figure 10, depending on your chassis type.) Figure 19 shows the functional details of inserting an interface processor and using the ejector levers. Figure 18 shows proper handling of an interface processor during installation.


Caution Remove or insert only one interface processor at a time. Allow at least 15 seconds for the system to complete the preceding tasks before removing or inserting another interface processor. Disrupting the sequence before the system has completed its verification can cause the system to assume that there has been a hardware failure.

Follow these steps to install a CIP2:


Step 1 Ensure that a console terminal is connected to the RP (or RSP) console port and that the console power switch is turned ON.

Step 2 Choose an available interface processor slot for the CIP2 and ensure that the interface cables are of sufficient length to connect the CIP2 to the channel.

Step 3 Hold the CIP2 handle with one hand, and place your other hand under the carrier to support the CIP2 ( Figure 18), and guide it into the slot. Avoid touching the card or any connector pins.

Step 4 Place the back of the CIP2 in the slot and align the notches along the edge of the carrier with the grooves in the slot ( Figure 19a).

Step 5 Keeping the carrier parallel to the backplane, carefully slide the CIP2 into the slot until the back of the faceplate makes contact with the ejector levers, then stop ( Figure 19b).


Caution Always use the ejector levers when installing or removing interface processor modules. A module that is partially seated in the backplane will cause the system to halt and subsequently crash, and shoving or slamming the interface processor into the slot can damage the backplane and connector pins.

Step 6 Using the thumb and forefinger of each hand to pinch each ejector lever, simultaneously push both ejector levers inward (toward the interface ports) until they snap into place and are parallel to the faceplate ( Figure 19c).

Step 7 Use a screwdriver to tighten the two captive screws on the interface processor faceplate, before installing additional interface processors. This prevents the interface processor from becoming partially dislodged from the backplane and ensures proper EMI shielding. (These screws must be tightened to meet EMI specifications.)

Proceed to the next section to attach the bus and tag or ESCON cables between the CIP2 interface ports and your channel.


Attaching the CIP2 to the Channel

The CIP2 can be connected to the channel using the bus and tag cables (for the PCA) or using a fiber-optic ESCON cable with duplex connectors (for the ECA). Bus and tag and ESCON connections each have their own special requirements.

The following sections discuss bus and tag and ESCON connections:

Attaching the Bus and Tag Cables

Attaching the ESCON Cable

Attaching the Bus and Tag Cables

The PCA is connected using the bus and tag cable with 78-pin connectors (the Y cable) and the bus and tag cables with 48-pin, type A connector blocks (the VA and VB cables). In general, a Y cable attaches to the PCA on the CIP2, and the VA and VB cables attach to the remaining ends of the Y cable.

Attaching the PCA to the Host Channel

Attach the PCA to the host as follows:


Caution To reduce the potential for problems, you should have an authorized service representative or other qualified service person perform the following procedure. To prevent hardware problems with your host processor, all the channel connections must be tight. A loose connection can cause the host processor or its channel to halt. All connections must be screwed together.


Step 1 Vary offline the host channel to which the PCA will be attached.

For instructions on how to vary the host channel offline, refer to the documentation for your mainframe operating system.


Caution Ensure the select/bypass switch is in the bypass position; otherwise, the mainframe operating system can be negatively affected.

Step 2 Attach the PCA connector of the Y cable to the PCA ( Figure 20).

Figure 20 Connecting or Removing the Y Cable

Step 3 Attach the female (light-gray) end of the Y cable ( Figure 20a) to the male (dark gray or black) end of the VB cable (that goes to the next control unit).

If the PCA is the last control unit on the channel, attach a terminator to the female end of the Y cable ( Figure 20b). Do not attach a VB cable.


Note If the PCA is the last control unit, channel termination is absolutely required to loop signals back to the host.



Caution To prevent potential system problems, do not connect the VB cable directly to the PCA. You must connect the Y cable to the PCA, then connect the VB cable to the Y cables as appropriate.

Figure 21 Connecting the VB Cable Between the Y Cable and the Next Control Unit

Step 4 If required, extend the length of the Y cable connections (between the VA and VB cables) with a straight-through cable ( Figure 22) that is available from IBM. This cable is not available from Cisco.

Figure 22 Straight-Through Cable

Step 5 Attach the male (dark gray or black) end of the Y cable to the female (light gray) end of the VA cable that comes from the host ( Figure 22).

Figure 23 Connecting the VA Cable Between the Y Cable and the Host

Step 6 Leave the select/bypass switch ( Figure 16) in bypass mode until the PCA connector is attached to the PCA.

Step 7 Connect the Y cable to the PCA.

Step 8 Place the select/bypass switch in select mode.

Step 9 If the CIP2 replaces another interface processor or occupies a previously empty interface processor slot, configure the interface(s) on the CIP2; otherwise, interface configuration is not required.

Step 10 Vary online the host channel. For instructions on how to vary the host channel online, refer to the documentation for your mainframe operating system.

Figure 24 C


Caution To prevent damaging the PCA connector on the CIP2, by unintentionally disconnecting the Y cable from the PCA connector, make sure you provide adequate strain relief for the heavy bus and tag cables that attach to the PCA.


Detaching the Y Cable from the PCA

To properly detach a Y cable from the PCA, use the following procedure.


Caution To reduce the potential for problems, you should have an authorized service representative or other qualified service person perform the following procedure. To prevent hardware problems with your host processor, all the channel connections must be tight. A loose connection can cause the host processor or its channel to halt. Every cable must be tightly seated in its mating connector.


Step 1 Have the system operator vary offline all addresses assigned to the PCA. For instructions on how to vary addresses offline, refer to the documentation for your mainframe operating system.

Step 2 Place the select/bypass switch on the PCA connector in bypass mode ( Figure 16). To allow the propagation of channel signals to downstream control units while the PCA cable is disconnected, leave this switch in bypass mode.


Caution If the select/bypass switch is in select mode when the PCA connector is removed, other devices on the channel and the mainframe operating system might not operate properly.

Step 3 Remove the PCA cable connector (on the Y cable) from the PCA ( Figure 20).

Step 4 When you are finished with the task that required you to detach the PCA from the host channel, reattach the PCA connector (on the Y cable) to the PCA.

Step 5 Place the select/bypass switch on the PCA connector in select mode ( Figure 16).

Step 6 Vary online all addresses assigned to the PCA. For instructions on how to vary addresses online, refer to the documentation for your mainframe operating system.


Caution To prevent damaging the PCA connector on the CIP2 by unintentionally disconnecting the Y cable from the PCA connector, provide adequate strain relief for the heavy bus and tag cables that attach to the PCA.


Attaching the ESCON Cable

Following is the procedure for attaching the ESCON cable between the ECA and the host channel.


Caution To reduce the potential for problems, you should have an authorized service representative or other qualified service person perform the following procedure. To prevent hardware problems with your host processor, all the channel connections must be tight. A loose connection can cause the host processor or its channel to halt. Every cable must be tightly seated in its mating connector.


Step 1 Make certain the ECA interface is shut down (using the shutdown interface command) to prevent excessive error messages from being sent to the router log output. It is recommended, but not necessary, to vary offline the host channel to which the ECA will be attached. For instructions on how to vary the host channel offline, refer to the documentation for your mainframe operating system.

Step 2 Attach an ESCON cable between the ECA and the host channel ( Figure 25). Make certain the ESCON cable plug "clicks" into place in the receptacle on the ECA. If not, the connection will be incomplete and connection problems could result. It is best to visually inspect the connection after you make it, rather than relying on an audible cue in a noisy lab environment.

Figure 25 Connecting an ESCON Cable to the ECA

Step 3 Vary online the host channel. For instructions on how to vary the host channel online, refer to the documentation for your mainframe operating system.

This completes the procedure for attaching an ESCON cable.


Checking the CIP2 Installation

After you install the CIP2 and cables, verify the installation by observing the LED states and the console display. When the system has reinitialized all inserted interfaces, the enabled LED on the newly inserted CIP2 should go on. The console screen will also display a message as the system discovers each interface during its reinitialization. If you need to verify the operation of the interfaces, refer to the "Running CIP2 Diagnostic Tests" section.

When you remove and replace interface processors, the system provides status messages on the console screen. These messages are for information only. The following sample display shows the events logged by the system as a CIP2 is removed from slot 1; the system makes as down the CIP2 that was removed. If the appropriate cables are connected and the no shutdown command is entered after the CIP2 is reinserted, the system marks the interface(s) as up again.

The sample display follows:

Router#
%OIR-6-REMCARD: Card removed from slot 1, interfaces disabled

Router#
%OIR-6-INSCARD: Card inserted in slot 1, interfaces administratively shut down

When a new CIP2 is inserted or when a CIP2 is moved to a new slot, the system recognizes the new interface, but leaves it in an administratively shutdown state until you configure it and change the state to up with the no shutdown command.

The following sample display shows the events logged by the system as a new single-PCA CIP2 is inserted in slot 3:

 Router#
 %OIR-6-INSCARD: Card inserted in slot 3, interfaces administratively shut down 

Verify that the CIP2 is installed correctly, as follows:


Step 1 While the system reinitializes each interface, observe the messages on the console display and verify that the system discovers the CIP2, as follows:

If you installed a new CIP2 that occupies a slot not previously occupied by a similarly configured CIP2, the system should recognize the new interface(s), but leave the interface(s) configured as administratively shut down.

If you replaced a CIP2 with a new CIP2, the system should recognize the interface(s) and place the interface(s) in the same state (up or down) that existed before you removed the first CIP2.

If the systems displays an error message, or fails to recognize the CIP2, verify that the currently running system software and microcode meet the minimum requirements for CIP2 operation. (See the "CIP2 Software, Hardware, and Microcode Prerequisites" section and "CIP2 Microcode Overview" section.) To do this, use the show microcode command, the show controllers cbus command, or the dir slot0 command. If the Cisco IOS software release and microcode versions are correct, reboot the router.

Step 2 Check the enabled LED. (Refer to the state descriptions in the "CIP2 LED Indicators and Sequences" section and Figure 26.) If no LEDs remain on, the CIP2 has not been successfully configured by the system and will not function, or the CIP2 is not inserted properly.

Step 3 When the reinitialization is complete, verify that the enabled LED on the CIP2 goes on and remains on ( Figure 26).

Figure 26 CIP2 LED Indicators

If the enabled LED does go on, the installation check is complete.

If the enabled LED on the CIP2 fails to go on, the CIP2 card connector might not be fully seated in the backplane or the correct version of CIP2 microcode was not available for download. To check the CIP2 card's connections, proceed to Step 4. To check the microcode, use the show microcode command, the show controllers cbus command, or the dir slot0 command.

Step 4 Proceed as follows:

Loosen the captive installation screws, then firmly push the ejector levers inward (toward the interface port) until both are parallel to the CIP2 faceplate.

Tighten the captive installation screws.

After the system reinitializes the interfaces, the enabled LED on the CIP2 should go on.

If it does go on, the installation check is complete. If it does not go on, proceed to Step 5.

Step 5 If the enabled LED still fails to go on, remove the CIP2 and try installing it in another available interface processor slot.

If the enabled LED goes on when the CIP2 is installed in the new slot, there could be a failed backplane port in the original interface processor slot.

If the enabled LED still fails to go on, but other LEDs on the CIP2 are on and indicate activity, the enabled LED on the CIP2 has probably failed. Proceed to Step 7 to resume the installation check.

If the enabled LED still does not go on, do not proceed with the installation. Contact a service representative to report the faulty equipment and obtain further instructions. (Instructions for obtaining technical assistance are provided at the end of this document.)

Step 6 If the present LED fails to go on, the connection between the ECA or PCA and the motherboard might be faulty; however, do not attempt to disassemble the CIP2 in order to check this connection. Instead, contact a service representative.

Step 7 If the interface is new, refer to the publications listed in the "Related Documentation" section to configure the new interface. (This configuration does not have to be done immediately, but an interface will not be available until you configure it.)

If this installation was to replace a CIP2, use the show interfaces or show controllers cxbus EXEC commands to verify the status of the interface. (For complete descriptions of the show commands, refer to the publications listed in the "Related Documentation" section.)

If an error message is displayed on the console terminal, refer to the System Error Messages publication for error message definitions. If you experience other problems that you are unable to solve, contact a service representative for assistance.

This completes the CIP2 hardware installation.



Note For complete CIP2 configuration information, refer to the appropriate software configuration guide and command reference listed in the "Related Documentation" section.


CIP2 Microcode Guidelines

The following sections discuss CIP2 microcode configuration requirements:

How Does CIP Microcode Ship?

CIP2 Microcode Upgrade Overview

Configuring Microcode

(For additional information about specific microcode requirements, refer to the " "ECA Software, Hardware, and Microcode Prerequisites" section.)

How Does CIP Microcode Ship?

For the Cisco 7000 series and Cisco 7500 series routers, CIP2 microcode is available on floppy disks, Flash memory cards (which also include the Cisco IOS release compatible with the microcode version), and via Cisco Connection Online (CCO).

As of Cisco IOS Release 11.1, the CIP2 microcode is shipped or available on the following media:

Via electronic download from CCO using File Transfer Protocol (FTP) for all Cisco 7000 family routers

On a separate set of floppy disks shipped with Cisco IOS Release 11.1 disks for all Cisco 7000 series and Cisco 7500 series routers

On floppy disks shipped with Cisco IOS Release 11.1 ROMs (RP-based Cisco 7000 series routers only)

Preinstalled on a Flash memory card with Cisco IOS Release 11.1 (available as an upgrade for RP-based Cisco 7000 series routers only)


Note CIP2-compatible microcode images are bundled with all other Cisco IOS releases that support CIP2, including Cisco IOS Release 10.2(13) or later, Release 10.3(13) or later, Release 11.0(10) or later, or Release 11.0(10)BT or later.


CIP2 Microcode Upgrade Overview

Following is an overview of what you need to do to upgrade unbundled CIP2 microcode (that shipped on floppy disks and Flash memory cards) for the Cisco 7000 series and Cisco 7500 series routers.


Caution To prevent system problems in the following procedure, a CIP2-compatible, bootloader-capable Cisco IOS image must be booted before the CIP2 microcode image is copied to Flash memory.

Upgrading from Floppy Disks

For CIP2 microcode images that shipped on floppy disks or were obtained from CCO, do the following:


Step 1 Upload the CIP2 microcode image (and the Cisco IOS image if not on ROMs) on floppy disks or from CCO to a TFTP server.

Step 2 Remove any configuration commands that specify a CIP2 microcode image from the running configuration.

Step 3 Save your running configuration to a TFTP server or Flash memory.


Note If you have a Cisco 7000 series router and plan to install new software ROMs with Cisco IOS Release 11.1 or later, skip Steps 4 and 5 and turn off power to your router.

Install the new ROMs, then proceed to Step 6.


Step 4 Download the Cisco IOS image to Flash memory.

Step 5 Configure the router to boot from the Flash memory where the Cisco IOS image resides.

Step 6 Boot the Cisco IOS image.


Note The router must already be running a CIP2-compatible Cisco IOS image before performing a copy of the CIP2 microcode image to Flash memory in the following step, because the CIP2 microcode image must be "exploded" from the single image file on the TFTP server to multiple files in Flash memory. This capability is available in Cisco IOS Release 11.1 or later.


Step 7 Download the CIP2 microcode image to the Flash memory card in slot 0.

Step 8 Restore the running configuration with the configuration you saved to the TFTP server in Step 3.

Step 9 Reconfigure the router, as required, to use the CIP2 microcode image stored in the Flash memory card in slot 0.

Step 10 Perform a microcode reload.

Upgrading from a Flash Memory Card

For CIP2 microcode that shipped on Flash memory cards, do the following:


Step 1 Insert the Flash memory card into a Flash memory card slot 0.

Step 2 Configure the router to boot from the Flash memory card in slot 0.


Note For the specific procedures associated with the steps in this overview, refer to the companion publication Upgrading Software and Microcode in Cisco 7000 Series and Cisco 7500 Series Routers (Document Number 78-1144-xx), which includes the information and procedures necessary to upgrade your CIP2 microcode.

The Upgrading Software and Microcode in Cisco 7000 Series and Cisco 7500 Series Routers publication includes information on upgrading software and microcode images, transferring files to and from Trivial File Transfer Protocol (TFTP) servers, copying files between nonvolatile random-access memory (NVRAM) and Flash memory, and between TFTP servers and Flash memory; the publication also includes basic instructions for booting your system.


Configuring Microcode

This section describes how to modify the startup configuration to load different microcode images at startup, or to change existing configuration instructions and reenable the system default.

At system startup or reload, the system loads a microcode image for each processor type. All processors of the same type use the same microcode image; only one image for each type can load at startup. The CIP2 Flash memory provides a CIP2 microcode boot image. The entire CIP2 microcode image is located in a Flash memory card, on a floppy disk, or is available from CCO or from a TFTP server.

Whenever you upgrade software or microcode by downloading new images into Flash memory, you must configure the system to load the new image at startup. Otherwise, the system will continue to load the default image from the system, or attempt to load the previous image (if any) if it is still specified in the configuration file.


Note If you are running anything other than the default CIP2 microcode with your Cisco IOS image and you want to upgrade to a later version of Cisco IOS, and want to use the default CIP2 microcode that comes with that later version, you have to remove the microcode cip flash statement from the system configuration file, otherwise the Cisco IOS will try to load that old version of the CIP2 microcode.


To instruct the system to boot a CIP2 microcode image other than the default at startup, use the microcode cip flash [bootflash | slot0 | slot1 ]:filename configuration command to add the instructions to the configuration file.


Note If you are currently running a previous Cisco IOS release, refer to the appropriate configuration and command reference publications for specific commands that apply to this procedure depending on your Cisco IOS release. All Cisco IOS release documentation is available on the Cisco Connection Documentation, Enterprise Series CD-ROM.


If you plan to load a microcode image from an individual file or a bundled system image stored in Flash memory, enter the show flash slot0: EXEC command to display the contents and verify the exact name of the file (cip1234 is used in this example):

Router> show flash slot0:

(additional displayed text omitted)

-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1   .. FFFFFFFF A831B720 3828CC  16   3549260  Feb 24 1996 20:28:56 rsp-k-mz.111-5
2   .. FFFFFFFF 83A6447F 8B8D18  16   761932   Apr 17 1996 15:15:59 cip1234

(additional displayed text omitted)

5419388 bytes available (15158916 bytes used)

Follow these steps to configure the microcode for a CIP2 on a router configured with Cisco IOS Release 11.1(5) or later.


Step 1 Enter the privileged EXEC mode command interpreter, as follows:

Router> enable
Password:
Router#

Note For complete information on the command interpreter and software functions, refer to the publications listed in the "Related Documentation" section.


Step 2 If you need to copy a new CIP2 microcode image into your system's Flash memory, refer to the "Using Flash Memory" section, then proceed to Step 3.

Step 3 In privileged command mode, enter router configuration mode and specify that the console terminal will be the source of the configuration subcommands, as follows:

Router# configure terminal 

To load the microcode from an individual microcode image that is stored as a file in Flash memory, enter the microcode command, the processor type, the specific memory location of the CIP2 microcode image, and the exact argument for filename (cip1234 is used in this example):

Router(config)# microcode cip flash slot0:cip1234

The no microcode command cancels any existing instructions to load an image from Flash memory:

Router(config)# no microcode cip flash slot0:cip1234

Step 4 To save the configuration file, press Ctrl-Z, then copy the new configuration to nonvolatile random-access memory (NVRAM) as follows:

Router# copy running-config startup-config

The microcode reload command must be invoked whenever you modify the system default to load a microcode image, using the microcode cip flash command.

If you see either of the following sets of error messages displayed, you must upgrade the Cisco IOS software and CIP2 microcode by observing and complying with the ESCON channel adapter Cisco IOS software and microcode prerequisites; refer to Table 2 and the "ECA Software, Hardware, and Microcode Prerequisites" section.

%CIP2-0-MSG: %ADAPTER-0-DIAGFAIL: Port 0 failed the I/O chip tests diagnostic 
%CIP2-0-MSG: %ADAPTER-0-DIAGDATA: Module Call: 123 Error ID: FF85

%CIP2-0-MSG: %ADAPTER-0-DIAGFAIL: Port 0 failed the Electrical wrap diagnostic
%CIP2-0-MSG: %ADAPTER-0-DIAGDATA: Module Call: 1221 Error ID: FE14

Note Running CIP2 microcode versions earlier than cip21-11 and cip22-12 with the second or third ECA hardware version will always result in error messages. Running CIP2 microcode versions earlier than cip21-14 and cip22-15 with the second or third ECA hardware version might result in error messages.


Step 5 To verify that the correct microcode is loaded according to the new instructions, enter the show controller cbus EXEC command. The resulting display indicates the currently loaded and running microcode version for each interface processor.

Step 6 To verify the contents of the configuration file, enter the show running-config and show startup-config EXEC commands. You can also verify that the correct system image is configured to load at system restart or reload.

This completes the procedure for configuring microcode. For complete descriptions of the show commands, refer to the publications listed in the "Related Documentation" section.


Using Flash Memory

The following sections discuss various Flash-memory functionality that you might need for microcode configuration:

Copying to Flash Memory on an RSP or RSP7000

Additional Flash Memory Commands

Recovering from Locked Blocks

Copying to Flash Memory on an RSP or RSP7000

Copying a new image to Flash memory might be required whenever a new microcode image becomes available. Use the command copy tftp:filename [ bootflash | slot0 | slot1 ]:filename for the copy procedure where tftp:filename is the source of the file and [ bootflash | slot0 | slot1 ]:filename is the destination in onboard Flash memory or on either of the Flash memory cards. An example of the copy tftp:filename command for Cisco IOS Release 11.1 follows:

Router# copy tftp:cip1234 slot0:cip1234
2283972 bytes available on device flash, proceed? [confirm]
Address or name of remote host [biff.cisco.com]? 
Accessing file "cip1234" on biff.cisco.com ...FOUND
Loading mhoerler/cip1234 from 1.1.1.22 (via Ethernet0/0): !Verifying via checksum...

Flash verification successful.  Length = 1, checksum = 0xFFFF

--- expanding multi-segment file --- 
flash:cip1234_kernel_hw4 size = 238626
!!!!!!!!!!!!!!!!!!!!!!!!!Verifying via checksum... vvvvvvvvvvvvvv

Flash verification successful.  Length = 238626, checksum = 0x0000

--- expanding multi-segment file --- 
flash:cip1234_seg_802 size = 198600
!!!!!!!!!!!!!!!!!!!!!!!!!Verifying via checksum... vvvvvvvvvvvv

Flash verification successful.  Length = 198600, checksum = 0x9237

--- expanding multi-segment file --- 
flash:cip1234_seg_csna size = 102392
!!!!!!!!!!!!!!!!!!!!Verifying via checksum... vvvvvv

Flash verification successful.  Length = 102392, checksum = 0x771E

--- expanding multi-segment file --- 
flash:cip1234_seg_eca size = 461408
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Verifying via checksum... vvvvvvvvvvvvvvvvvvvvvvvvvvvv

Flash verification successful.  Length = 461408, checksum = 0xB791

--- expanding multi-segment file --- 
flash:cip1234_seg_offload size = 52608
!!!!!!!!!!Verifying via checksum... vvv

Flash verification successful.  Length = 52608, checksum = 0x0FBC

--- expanding multi-segment file --- 
flash:cip1234_seg_pca size = 69360
!!!!!!!!!!!!!!Verifying via checksum... vvvv

Flash verification successful.  Length = 69360, checksum = 0x737F

--- expanding multi-segment file --- 
flash:cip1234_seg_tcpip size = 175320
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Verifying via checksum... vvvvvvvvvv

Flash verification successful.  Length = 175320, checksum = 0xD416

Note In the preceding example, the exclamation points (!!!) appear as the file is downloaded, and the "v" characters signify calculation of the checksum, which is a verification that the file has been correctly downloaded to the Flash memory card.


Additional Flash Memory Commands

Following are additional commands related to the Flash memory in the single in-line memory module (SIMM) on the RSP1, RSP2 and RSP7000 (called bootflash) and in PCMCIA Flash memory cards. (The following example assumes you are currently accessing the Flash memory card in PCMCIA slot 0.) You can determine which PCMCIA slot you are accessing using the pwd command as follows:

Router# pwd
slot0

You can move between Flash memory media using the cd [ bootflash | slot0 | slot1 ] command as follows:

Router# cd slot0
slot0
Router# cd slot1
Router# pwd
slot1

You can list the directory of any Flash memory media using the dir [ bootflash | slot0 | slot1 ] command as follows:

Router# dir
-#- -length- -----date/time------ name
1   4601977  May 19 1994 09:42:19 myfile1
6   679      May 19 1994 05:43:56 todays-config
7   1        May 19 1994 09:54:53 fun1

You can delete a file from any Flash memory media using the delete command as follows:

Router# delete slot0:fun1
Router# dir
-#- -length- -----date/time------ name
1   4601977  May 19 1994 09:42:19 myfile1
6   679      May 19 1994 05:43:56 todays-config

To verify that the delete command was successful, use the dir/all/long command.


Note Files that are deleted are simply marked as deleted, but still occupy space in Flash memory. To remove them, use the squeeze command.


The squeeze command permanently removes files, which are marked as deleted, and pushes all other undeleted files together to eliminate spaces between them.

Following is the syntax of the squeeze command:

Router# squeeze slot0:
All deleted files will be removed, proceed? [confirm]
Squeeze operation may take a while, proceed? [confirm]
ebESZ

To prevent loss of data due to sudden power loss, the "squeezed" data is temporarily saved to another location of Flash memory, which is specially used by the system.

In the preceding command display output, the character "e" means this special location has been erased (which must be performed before any write operation). The character "b" means that the data that is about to be written to this special location has been temporarily copied. The character "E" signifies that the sector which was temporarily occupied by the data has been erased. The character "S" signifies that the data was written to its permanent location in Flash memory.

The squeeze command operation keeps a log of which of these functions has been performed so upon sudden power failure, it can come back to the right place and continue with the process. The character "Z" means this log was erased after the successful squeeze command operation.

Recovering from Locked Blocks

A locked block of Flash memory occurs when power is lost or a Flash memory card is unplugged during a write or erase operation. When a block of Flash memory is locked, it cannot be written to or erased, and the operation will consistently fail at a particular block location. The only way to recover from locked blocks is by reformatting the Flash memory card with the format command.


Caution Formatting a Flash memory card to recover from locked blocks will cause existing data to be lost.

Running CIP2 Diagnostic Tests

There are six PCA and ECA diagnostic test routines, as follows:

Processor test 1

Processor test 2

I/O device tests

Serial link controller (SLC) device tests

Internal electrical wrap

External optical wrap (ECA only) or external electrical wrap (PCA only)

The external wrap routine runs in two modes: optical and electrical.


Note All diagnostic tests are run every time the adapter is started. They cannot be run independently. The wrap tests require special wrap plugs for the PCA and ECA; contact a service representative to obtain the appropriate wrap plugs.


The interface has to pass the first five tests. The sixth test (which is the same as the fifth, but with a different mode for the optical wrap plug for the ECA, instead of electrically wrapping the interface) will fail if no wrap plug is installed or if the interface is connected to the channel. This type of failure will not affect the channel.

If a wrap plug is inserted, following is how the wrap diagnostics will be repeated:

Until a failure occurs

Until the wrap plug is removed (which may be reported as a failure depending on when you pull the wrap plug)

Until you enable the second adapter (as in a dual channel CIP2)

If you suspect that an adapter might be the cause of a problem you are seeing, you can run a single pass of the diagnostic tests on an installed PCA or ECA interface by entering configuration mode and specifying that the console terminal will be the source of the configuration subcommands, as follows:

Router# configure terminal

Next, specify the slot/port number (interface processor slot number/port number) of the interface for which you want the diagnostic tests to run by entering the interface channel command followed by the slot/port of the interface.

The example that follows is for a CIP2 interface in interface processor slot 1:

Router(config)# interface channel 1/0

To run the diagnostic tests once, enter the shutdown command and then the no shutdown command, as follows:

Router(config)# shutdown
Router(config)# no shutdown
Ctrl-Z
Router#

The no shutdown command causes the diagnostic tests to run on the PCA or ECA interface you selected. If no failures occur, you can rule out that adapter as the source of your problem.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only —  security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies —  psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

http://www.cisco.com/go/guide

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

Printed in the USA on recycled paper containing 10% postconsumer waste.