Specifications

9032277-04 Software Superseded by CS3/MMS3
5-23
Patches Issued After the CS1/MMS1 Release
2. Also during the discovery MAC addresses are found and connected
to the device. These are incorrectly modeled as Physical_Addr. The
Hub3ComSSTR_A should get placed in an 802_5 LAN container.
The resolution is that a new inference handler has been written to
handle the AutoDiscovery issue and the database attributes have been
modified so that the device will be placed in the correct container.
(Also refer to the Notes on corrected anomalies, on Page 5-14.)
SPECTRUM_5.0rev1.P51
After installing P41. Problems occurred with the HubCat5000 models.
Device/Chassis view is blank. DevTop/Chassis menu option is grayed
out. DevTop/Interface view gives Device not configured error.
The problem is that during the board creation phase, CsIHChasMgr
attempts to read boardType_Map from the CATStackApp model type.
It uses CsULMapper::buildMap to create a map, and buildmap does
not recognize Enum, just ENUM. The resolution is to change the
attribute from Enum to ENUM.
After setting the db flag for the following external attributes: ifType,
ifSpeed, and ifPhysAddress, the DEVTOP view for Cisco Routers
become unusable. The Inference Handler which reads these attributes
to create the port models uses the default read mode of "Most
Available". Setting the database flags on these 3 attributes causes the
read to get the attribute values from the database. This causes the
read to return an empty value for those attributes and the ports never
get created. Only with "Read Most Current" will the read attempt to
get the values from the device. The resolution to the problem is to
change the Inference Handler to use the "Read Most Current" mode
which causes the read to get the attribute values from the device even
if the attributes have their db flag set.
The SpectroSERVER, ArchMgr and LocServer processes all grow in
memory usage when running in the distributed environment. This
may be caused by bringing up two SpectroGRAPHs on the same
display. The resolution is to have the map manager (which is a
component in the SpectroSERVER, LocServer, and ArchMgr) stop
processing map updates for Z minutes once a map storm is detected.
The criteria for detecting a map storm is to receive X amount of map
updates in Y seconds. X, Y, and Z are configurable.
Purify detected a memory leak in CSIHLostAndFound. The resolution
is remove the leak as needed.