Filter
Top Products
A-56
User Guide for Resource Manager Essentials 4.1
OL-11714-01
Appendix A RME Troubleshooting Tips and FAQs
Software Management
–
I, II sup > = 3.1(1) & < 4.1(1) 16 MB
–
I, II sup > = 4.1(1) 16 MB
–
III sup3 > = 3.1(1) 32 MB
Images that are 8 MB RAM are available in 3.1 and 3.2 software releases only for Supervisor Engine
I and II cards.
Software Management tries to use CISCO-MEMORY-POOL MIB to determine the available
memory on a device. The MIB is implemented from 4.1(1) Supervisor Engine software (on all
different Supervisor Engine card types—I, II, and III).
–
If a device runs the software that implements this MIB, Software Management performs a
memory check between the image requirement and the size of DRAM that is on the device.
–
If the device does not have enough RAM to run the image, Software Management generates a
verification warning.
–
If the current software on the device is earlier than 4.1, Software Management generates a
generic verification warning about memory requirements.
Q.
Are there restrictions on the downgrade of the software on the Supervisor Engine card and other
modules?
A.
You can downgrade Supervisor Engine card software to version 4.1(1) or later.
For example, if a Supervisor Engine card runs 4.2(1) software, you can downgrade the software to
4.1(2) or 4.1(1). However, you cannot downgrade the same Supervisor Engine card to 3.2(1b). If a
Supervisor Engine card runs 3.2(2), you cannot downgrade the software to 3.1(1) or 2.4(1).
There are no restrictions for the downgrade of software on other modules, such as ATM, FDDI, and
Token Ring. However, you should check the release notes of new software before you attempt
downgrades on modules.
Q.
Do you need to reconfigure the device when you downgrade the Supervisor Engine software?
A.
When you downgrade Supervisor Engine software, parts of the configuration may be lost. You must
check the configuration file and reconfigure as necessary. Use the backed up Software Management
configuration file from the Job Schedule directory as a reference, or use the backed up configuration
file from the Config Archive.
Q.
In the 4.1(1) software release and later, Supervisor Engine III cards allow the storage of
configuration files on Flash cards. Does Software Management preserve the backed up configuration
files on Flash during a software upgrade?
A.
Software Management erases a Flash card on Supervisor Engine III if the free space on the Flash
card cannot store the target software image. Software Management does not erase files of sizes that
are less than 1 MB during software upgrades. Since configuration files generally do not exceed 1
MB, Software Management does not erase these files.
Q.
Does Software Management allow you to upgrade epsboot images on Token Ring cards on Cisco
Catalyst 5500/5000 devices?
A.
Software Management does not allow upgrades of epsboot images on Catalyst 5500/5000 devices.
An epsboot string in the file names can identify epsboot images. Epsboot upgrades are not often
necessary. You can perform the upgrades with the Supervisor Engine card command-line interface
(CLI).
Q.
Why does the Add Image to Repository (Source: Cisco.com) task not display Token Ring LAN
Emulation (LANE) or Permanent Virtual Circuit (PVC)-only ATM software images?