Specifications

9032277-04 Software Superseded by CS3/MMS3
5-101
Patches Issued Since the CS2/MMS2 Release
The problem is with the DLCI_port model type. In SPECTRUM, the
port would toggle between GREEN and RED (up and down) after a
DLCI connection was made then broken on a router supporting DLCI.
There is an attribute called "dlcistate" which is one of 11 internal/
external attributes for the DLCI_port model type. In one particular
case, when the connection between two DLCI ports broken, nine out of
the 11 external reads fail on the near end router -- dlciState is one of
them. These failed attributes get put into an unsupported external
attributes list for that model, and write 0 values to the corresponding
internal attributes. Then these failed external attributes are NEVER
read again. That's why after the disconnection, the internal attribute
dlciState was not consistent with the external attributes. However
due to another code error, if the read of dlciState was within 10
seconds from a previous read, the old value of 2 was returned. That's
why the dlciState toggling between 0 and 2 (up and down).
The resolution is to use the first three external reads after a
disconnection to build the unsupported external attributes list. An
attribute will be added to the list only if it has failed on for all three
reads. This will prevent attributes from being added to this list
prematurely and NEVER read again.
--
The problem is when opening the application view of the HubCat5500
the view takes between 60 and 90 seconds to fill in the icons. While
this is occurring there is an hour glass that does not allow the user to
do anything else with the graph.
The resolution is to disable all refreshes until all the models are fully
realized. Then the entire window refreshes at once.
--
The problem was the ability to view the ifAlias value for each interface
was needed for Gen_IF_Port and Serial_IF_Port models. This
information was needed to find where a particular device was on the
network at a faster rate than it could be found before.
The resolution was to create a new model type called "RFC2233MIB"
and three new attributes for it called, "ifAlias", "ifStackLastChange",
and "ifTableLastChange". RFC2233MIB was derived from the IETF
model type. The "ifAlias" attribute was also added to the
"data_relay_prt" model type so that the interface models get the new
attribute.