Specifications

Corrected and Known Anomalies
Network Configuration Utilities (NCU)
Software Release Notes Page 89
Network Configuration Utilities (NCU)
Known NCU Anomalies in SPECTRUM 6.0
Problem 1: After a download with a forced reboot, the Firmware Download
Tool does not currently check to ensure that the reboot is successful and
that the rebooted device(s) are in a known good state. The Status column
in the Firmware Download Window therefore does not accurately update,
and displays REBOOTED rather than SUCCESS.
Solution: Check the state of the device by checking the SPECTRUM
model condition. The condition should, in most cases, return to the same
condition that existed before the reboot. In addition, the Event Log can be
checked to watch the devices lose contact and then regain it. This will be
corrected in a future release of SPECTRUM Network Configuration
Utilities.
Problem 2: Community strings are not updated on certain older
SmartSwitch 9000 blades, whose SPECTRUM device models include the
SS9000ChasApp model type, when using the Modify Community Strings
Tool. Those blades include:
9E106-06; 9E132-15; 9E133-36; 9E138-36; 9F116-01; 9F120-08; 9F122-12;
9F125-08; 9F240-08; 9F241-12; 9F310-02; 9F312-12; 9F315-02; 9T122-08;
9T122-24.
Solution: This will be corrected in a future release of SPECTRUM Network
Utilities.
Problem 3: The Modify Community Strings Tool does not allow you to
modify community strings on devices with which SPECTRUM has no
contact (orange, red, gray, brown, and blue alarms).
Solution: Make certain that the SPECTRUM model community name
matches any one of the valid community names on the device. Telnet to the
device and change the community strings via local management. You can
also change the SPECTRUM community string in the information GIB
using the GIB Editor. See the GIB Editor User’s Guide for more
information. This will be corrected in a future release of SPECTRUM.