46 Second-Generation Channel Interface Processor (CIP2) Installation and Configuration
CIP2 Microcode Guidelines
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 error messages displayed, this indicates that 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 section “ESCON Channel Adapter Software, Hardware, 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 error 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
Note Running CIP2 microcode versions earlier than cip21-11 and cip22-12 with the latest ECA,
will always result in error messages. Running CIP2 microcode versions earlier than cip21-14 and
cip22-15 with the latest ECA, 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 section “If You Need More Information” on page 2.
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, page 47
• Additional Flash Memory Commands, page 48
• Recovering from Locked Blocks, page 49
