Specifications

9032277-04 Software Superseded by CS3/MMS3

5-35

Patches Issued Since the CS2/MMS2 Release

SPECTRUM_5.0rev1.P53

Included in SPECTRUM_5.0rev1.P101

SPECTRUM_5.0rev1.P54

Included in SPECTRUM_5.0rev1.P101

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 ﬁrst 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.

SPECTRUM_5.0rev1.P55

Obsoleted by SPECTRUM_5.0rev1.P100

SPECTRUM_5.0rev1.P56

Included in SPECTRUM_5.0rev1.P101