Filter
Top Products
A-54
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Appendix A RME Troubleshooting Tips and FAQs
Software Management
Q.
What connection mechanism does Software Management use to upgrade Channel Interface
Processor (CIP)?
A.
Software Management uses the Telnet interface to the device to copy the CIP image to the flash.
Software Management uses TFTP (via Simple Network Management Protocol [SNMP]) for the
configuration upgrade to add the boot command to load CIP microcode.
Q.
Does Software Management change the configuration file for the Channel Interface Processor (CIP)
upgrade?
A.
To load the new CIP microcode, the CIP upgrade process adds these configuration commands:
microcode cip flash new_cip_image_name
microcode reload
Q.
Does Software Management supports CIP2?
A.
Yes, Software Management supports CIP2 images for CIP supported device types.
Q.
In which order does Software Management upgrade modules on a Cisco Catalyst 5500/5000 device?
A.
Software Management upgrades the Supervisor Engine module on the device before other modules.
Software Management upgrades the remainder of the modules in slot-number order. For example,
Software Management upgrades the module on Slot 3 before Slot 5.
Q.
Does the Supervisor Engine card reboot after the upgrade of all modules?
A.
If you elect to reboot devices immediately after the upgrade of software, Software Management
reloads the Supervisor Engine card. The reload of the card results in the reload of all modules, before
the upgrade of software on other intelligent modules. This process supports instances in which the
new module requires a newer version of Supervisor Engine software.
If you choose not to reboot the device after the download of software, you then must reload the
Supervisor Engine module manually. You also should consider that software that you have newly
loaded on a module may require new Supervisor Engine software.
If a new Supervisor Engine software is necessary, you should reload the Supervisor Engine module
before you load the new software to the other intelligent modules (such as ATM, FDDI, and Token
Ring).
For example, you may download 3.1(1) FDDI software and 4.1(1) Supervisor Engine software in a
single job. The 3.1(1) FDDI software may require 4.1(1) Supervisor Engine software. Then, you
must reset the Supervisor Engine module before you can upgrade the FDDI software. In such cases,
you must have already chosen the Reboot Immediately option.
Q.
Does Software Management determine if the newly deployed Supervisor Engine software or module
software is compatible with the module types (or module hardware versions)?
A.
Software Management does not verify whether the newly deployed Supervisor Engine software
supports all modules that are available on the chassis.
Usually, with the upgrade of Supervisor Engine software to a newer release, the software provides
backward compatibility for all the modules that exist on the chassis. However, you should check the
release notes of the Supervisor Engine software or module software to be sure that the software
versions are compatible.
Q.
Does Software Management support the upgrade of software on redundant Supervisor Engine
card-based systems?