Channel Interface Processor

This chapter provides information about the second-generation Channel Interface Processor (CIP2). (See Figure 3-1.)

The CIP2 provides up to two channel-attachment interfaces for Cisco 7000 series and Cisco 7500 series routers. The interfaces are mounted on separate boards called channel adapters, and attach to the motherboard by means of a multipin connector located at the rear edge of the channel adapter. The CIP2 has two DRAM SIMMs (U1 and U2) 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.

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. Input/output I/O devices are connected directly to control units, which provide the logical capabilities required to operate and control the I/O devices.

CIP2 Hardware and Software Prerequisites

This section provides information about hardware and software requirements for the CIP2, which follows:

• 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.

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.

• 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 systems, which use the Route Switch Processor (RSP).

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

To display the current hardware configuration of the router, including the system software version that is currently loaded and running, use the show version or show hardware commands. The show microcode command lists the bundled microcode (target hardware) version for each processor type. The CIP2 microcode is no longer bundled in Cisco IOS Release 11.1 and later, so the show microcode command lists the default CIP2 microcode image that should be used. The show controller cbus command shows the microcode version you are running.

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 section "CIP2 Microcode," on page 3-33, for basic microcode configuration information.)

If the displays indicate that the required system software and microcode is not available in your system, refer to the section "Cisco Connection Online," in the chapter "Using Interface Processors," and contact a service representative for upgrade information.

ESCON Channel Adapter Hardware, Software, and Microcode Prerequisites

The second-generation ESCON channel adapter is the latest Enterprise Systems Connection Channel Adapter (ECA) available from Cisco Systems. Both ECA models can be used in all Cisco 7000 series and Cisco 7500 series routers, and both ECAs are compatible with each other, and with the CIP2.

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 CIP2s as spares.)

Following are the specific Cisco IOS software and CIP2 microcode requirements that we recommend you carefully observe before you use the latest ECA 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

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

Verifying ECA Models by Examining ECA Hardware

Verify which type of ECA you have on your CIP2; it should be one of the following:

• The latest ECA model (see Figure 3-2)

• The earlier ECA model (see Figure 3-3)

Verifying ECA Hardware Versions Using the show controllers cbus Command

If you have Cisco IOS software and CIP2 microcode images loaded and running that support the latest ECA (see Table 3-3 and the section "ESCON Channel Adapter Hardware, Software, and Microcode Prerequisites"), then you can also verify which ECA model you have installed by using the show controllers cbus command to view the ECA's hardware version.

Refer to the arrow in the following partial-display example of the show controllers cbus command; the latest ECA model is indicated by "hw version 02":

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 C50602C3
    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 earlier ECA, then hw version 01 or hw version 00 is displayed, as shown in the following example:

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

If you see the following error messages displayed, this indicates that your Cisco IOS software and CIP2 microcode do not support the latest ECA installed in your system. You must, therefore, 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 3-3 and the section "ESCON Channel Adapter Hardware, Software, and Microcode Prerequisites."

%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

If you see the following messages, your Cisco IOS software and CIP2 microcode support the latest ECA installed in your system:

%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

CIP2 Interface Types

The CIP2 interfaces are combinations of a bus and tag (also called an original equipment manufacturer's interface [OEMI] and a parallel I/O interface) channel adapter and an Enterprise Systems Connection (ESCON2) channel adapter.

The bus and tag adapter is called the Parallel Channel Adapter (PCA), and the ESCON adapter is called the ESCON Channel Adapter (ECA). The PCA and ECA connect directly to the CIP2, and any combination of the two adapters can be used.

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 CIP2 carrier.

CIP2 Channel Adapter Types

There are three CIP2 carrier types, which offer the following five channel-adapter interface combinations (corresponding CIP2 product numbers are included):

• Single PCA on a PCA/ECA carrier (CX-CIP2-PCA1[=])

• Combination PCA and ECA (CX-CIP2-ECAP1[=])

• Single ECA on a dual ECA carrier (CX-CIP2-ECA1[=])

• Dual ECA on a dual ECA carrier (CX-CIP2-ECA2[=])

• Dual PCA on a dual PCA carrier (CX-CIP2-PCA2[=])

(Add an equal sign (=) to the product number when you order interface processors as spares.) The ECA has a female, duplex connector, and the PCA has a female, DB-78 connector.

Figure 3-4 shows the ECA and PCA interface combinations.

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, default memory configuration for the CIP2)

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

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

CIP2 Interface Cables

This section describes the network interface cables used with the CIP2.

ESCON Cable

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

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 (shown in Figure 3-6) 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.

The 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 discussed on the following page. (The IBM part number is 89F8392; however, this is subject to change.)

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

The select/bypass switch is required to allow the cable to be separated from the PCA without "opening" the select-out loop. The switch is located on the rear of the PCA connector.(See Figure 3-7.) The switch is labeled S (for select) and B (for bypass).

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.

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.

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. 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.

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.

VA and VB Cables

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 for the VA cable is 12G8058; however, this 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 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 for the VB cable is 12G7933; however, this is subject to change.

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. (See Figure 3-8.) VA and VB cables are 56 inches (1.42 meters) in length.

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.

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. (See Figure 3-6.) For attachment instructions, refer to the section "Attaching the CIP2 to the Channel" on page 3-19.

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.

Table 3-2 lists the specifications for the ESCON2 and bus and tag interfaces.

Attaching the CIP2 to the Channel

The CIP2 can be connected to the channel using the bus and tag cables (for the PCA) and/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

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 If the select/bypass switch is in the select position when the PCA connector is detached, other devices on the channel and the mainframe operating system can be negatively affected.

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

Step 3 Attach the PCA connector of the Y cable to the PCA. (See Figure 3-9.)

Step 4 Attach the female (light-gray) end of the Y cable (see Figure 3-10a) 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. (See Figure 3-10b.) Do not attach a VB cable.

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.

Step 5 If required, extend the length of the Y cable connections (between the VA and VB cables) with a straight-through cable (shown in Figure 3-11), which is available from IBM. (This cable is not available from Cisco Systems.)

Step 6 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. (See Figure 3-12.)

Step 7 Leave the select/bypass switch (see Figure 3-7) in bypass mode until the PCA connector is attached to the PCA.

Step 8 Connect the Y cable to the PCA.

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

Step 10 Boot up the router.

Step 11 Configure the interface on the router.

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

It is also possible to connect the PCA to the host or mainframe using the straight-through cable (CAB-PCA-S) as shown in Figure 3-13.

This connection technique uses the Y cable and eliminates the requirement for the VA and VB cables from the host and to the next control unit, respectively. A straight-through cable can also be used from the Y cable to the next control unit; however, if no control unit exists, use a terminator.

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. (See Figure 3-7.)

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. (See Figure 3-9.)

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. (See Figure 3-7.)

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.

This completes the Y-cable detachment procedure.

Attaching the ESCON Cable

USe the following procedure to attach 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. (See Figure 3-14.) 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.

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 ESCON cable connection procedure.

Using LEDs to Check CIP2 Status

Each CIP2 model has several status LEDs on its faceplate, one row for each of the ports. (See Figure 3-15.)

After you connect cables to the CIP2, observe the LED states and the console display. When the system has reinitialized all interfaces, the enabled LED on the CIP2 should go on. The console screen will also display a message as the system discovers each interface during its reinitialization. After system initialization, the enabled LED goes on to indicate that the CIP2 is enabled for operation.

The following conditions must be met before the CIP2 is enabled:

• The CIP2 is correctly connected to the backplane and receiving power.

• The system bus recognizes the CIP2.

• A valid version of CIP2 microcode is loaded and running.

If any one of these conditions is not met, or if the initialization fails, the enabled LED does not go on.

The following sequences for the CIP2 LEDs include the present, loaded, signal, and online LEDs. The enabled LED is not part of these sequences.

On cold boots, the following LED sequences apply:

The following LED sequence indicates that the CIP2 is waiting for commands from the main system processor:

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:

The following sequence indicates that the CIP2 is downloading microcode:

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

Verify that the CIP2 is connected 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, the system should recognize the new interface, but leave it configured as down.

• If you replaced a CIP2, the system should recognize the interface and place it in the same state (up or down) it was in before you removed the first CIP2.

• If the router fails to boot, displays an error message, or fails to recognize the CIP2, remove the CIP2 and reboot the router. If the router boots successfully, verify that the currently running system software and microcode meet the minimum requirements for CIP2 operation. (See the sections "CIP2 Hardware and Software Prerequisites," on page 3-2, and "CIP2 Microcode" on page 3-33.)

Step 2 When the ECA or PCA interface is up, check the activity of the interface with the CIP2 LEDs. 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. (See Figure 3-15.) If it does, proceed to Step 7. If it does not, proceed to the following step.

Step 4 If the enabled LED on the CIP2 fails to go on, the CIP2 card connector might not be fully seated in the backplane. 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, proceed to Step 7. If it does not, 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 section "If You Need More Information," in the chapter "Using Interface Processors," to configure the new interface. (This does not have to be done immediately, but an interface will not be available until you configure it.)

If this installation was a replacement CIP2, use the show interfaces or show controllers cbus EXEC commands to verify the status of the interface. (For complete descriptions of the show commands, refer to the publications listed in the section "If You Need More Information," in the chapter "Using Interface Processors.")

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.

CIP2 Microcode

This section discusses CIP2 microcode upgrade and configuration requirements.

For the Cisco 7000 series and Cisco 7500 series routers, CIP2 microcode is available on floppy diskettes, Flash memory cards (which also include the Cisco IOS release compatible with the microcode version), and via Cisco Connection Online (CCO). (To access CCO, refer to the section "Cisco Connection Online," in the chapter, "Using Interface Processors.")

Starting with Cisco IOS Release 11.1 or later, CIP2 microcode images are shipped separately from the Cisco IOS software. For new Cisco 7000 series and Cisco 7500 series routers that shipped with Cisco IOS Release 11.1 or later, the CIP2 microcode is shipped preinstalled on the Flash memory card.

For Cisco Release 11.1 or later software upgrades, 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 diskettes shipped with Cisco IOS Release 11.1 diskettes for all Cisco 7000 series and Cisco 7500 series routers

• On floppy diskettes 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)

CIP2 Microcode Upgrade Overview

This section presents an overview of the procedures for upgrading unbundled CIP2 microcode for the Cisco 7000 series and Cisco 7500 series routers.

For CIP2 microcode images that shipped on floppy diskettes or were obtained from CCO, complete the following steps:

Step 1 UPload the CIP2 microcode image (and the Cisco IOS image if not on ROMs) on floppy diskettes 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.

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.

Step 7 Download the CIP2 microcode image to the Flash memory card in slot 0 or to onboard Flash memory, if you have a Cisco 7000 or Cisco 7010 with an older RP (and no Flash memory card).

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.

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.

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.

Table 3-3 specifies the name of the 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 section "CIP2 Hardware and Software Prerequisites," on page 3-2.

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.

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.

Use the following procedure to configure the microcode for a CIP2 on a router configured with Cisco IOS Release 11.1(5) or later.

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 slot 0: 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)

Enter the privileged EXEC command interpreter (refer to the section "Using the EXEC Command Interpreter" in the chapter "Using Interface Processors") and proceed as follows:

Step 1 Copy a new CIP2 microcode image into your system's Flash memory. (Refer to the section "CIP2 Microcode Upgrade Overview," in this chapter, and to the section "Upgrading Interface Processor Microcode Images" in the chapter "Using Interface Processors.")

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

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.

Running Diagnostic Tests

Six diagnostic tests check for the proper operation of your CIP2 and its PCA and ECA interfaces: including the processor, I/O devices, the serial link controller, and wrap functions. All diagnostic tests are run every time the adapter is started. They cannot be run independently.

The test routines are 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 will run in two modes: optical and electrical.

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, the wrap diagnostics will be repeated as follows:

• Until a failure occurs

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

• Until you enable the second adapter (as in a dual channel-attached 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 0:

Router(config)# interface channel 0/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.