Техническое Руководство для Cisco 7500 SERIES ROUTE SWITCH PROCESSOR 16

The following Cisco IOS releases are compatible with the RSP16:

12.1(12)E and later

12.0(21.02)S and later (1GB memory is available as of Cisco IOS Release 12.0(22)S1).

For the latest compatible software releases, refer to the Software Advisor at

http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl

.

Use the show version and show hardware commands to display the router’s current hardware and
software configurations. The show microcode command lists the bundled microcode (and target
hardware) version for each processor type. The show controller cbus command shows the microcode
version you are running. The show diagbus command shows the hardware version and revision of the
RSP16 board.

For additional descriptions of show commands, refer to the Configuration Fundamentals Configuration
Guide and Configuration Fundamentals Command Reference publications, which are available online,
on the Documentation CD-ROM, or as printed documents.

If the required system software and microcode are not available in your system, contact a customer
service representative for upgrade information. (To obtain assistance, see the

.)

Your router configuration, protocols and features might require more than the 128 MB of DRAM that is
shipped with the RSP16. To upgrade DRAM, see the

.

To ensure proper operation of a system configured for HSA or HA, note the guidelines below:

With HSA and HA, the RSP16 can interoperate with another RSP16, or with an RSP8.

To ensure that the standby RSP16 operates properly, the active and the standby RSP16 should have
the same DRAM configuration and boot ROM version.

Removing the active RSP16 while the system is operating might cause the system to crash; however,
the system reloads with the standby RSP16 as the new active RSP16. To prevent system problems,
do not remove the active RSP16 while the system is operating.

Microcode 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 latest available microcode image for each processor type
is bundled and distributed with the system software image.

Overriding the bundle can result in incompatibility among the various interface processors in the system.
We recommend that you use only the microcode image that is bundled.