Specifications

9032277-04 Software Superseded by CS3/MMS3

5-87

Patches Issued Since the CS2/MMS2 Release

Router. When the Bridge went physically down both the bridge and

the router went GRAY. The Bridge should have gone RED and the

Router GRAY but that did not happen since the Bridge was connected

to the FDDIMac_NM.

The resolution was to add functionality so that if contact to a device is

lost and that device has a non-manageable neighbor upstream, that

upstream device will now go RED instead of GRAY. The inference

handler responsible for this functionality will always respond that the

device is up when asked ARE_YOU_UP, and that the device is not

down when asked ARE_YOU_DOWN.

The problem is that when just one single non-instantiated model type

is identiﬁed with "Model by IP" for a device (i.e. IBM 0x10203) it will

not get modeled and an error message will appear:

Device may not be responding to SNMP requests. Timeout and

retry values may be too low or community name public may be

incorrect.

The resolution was to update the code to make sure that the identiﬁed

model type can be instantiated. If the model cannot be instantiated

then it is removed from the list and a Generic SNMP Device is

created.

The problem was DS3 interfaces (ifType 30) were being created as

Gen_IF_Ports instead of Serial_IF_Ports for Cisco Routers.

The resolution was to modify SPECTRUM code so that DS3 (ifType30)

interfaces would be modeled with a Serial_IF_Ports model type.

The problem was if a CSIIfPort turned ORANGE then the interface

double click zone located in the upper left hand corner of the CSIIfPort

icon in the DevTop View would turn BLUE.

The resolution was to add a means for the icon to handle an ORANGE

color condition when the CSIIfPort turned ORANGE. The double click

zone should now also turn ORANGE.