Specifications

Patches Issued After the CS1/MMS1 Release

Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1

5-26 CS3 and MMS3

from false to true and then reconﬁgure. This has been resolved by

changing the default value for Create_Sub_Interfaces to TRUE.

WA_Link monitor points are lost if one of the routers on either side is

rebooted. The problem is that the intelligence which ﬁnds and

maintains the monitor point for the container (in this case a WA_Link)

has not been designed to handle the case where all potential monitor

points which the container could use go down, i.e Contact_Status goes

LOST. When Contact_Status goes LOST, the intelligence clears out all

monitor point information for the container and should start watching

the CONTACT_STATUS of the currently selected monitor point. The

problem is that the setup of the watch is triggered by a write to the

LAN_SELECT_MP attribute for which we currently only trigger by

changes in the attribute, i.e. a new monitor point is selected. A

situation can arise where the same monitor point is written to the

attribute, thus causing the trigger to not go off. When this happens, we

are not watching any potential monitor point to see when it may

regain contact.

CiscoView will not launch since we do not pass the community name

parameter. This has been resolved by adding the community name

parameter.

The Performance view of Cisco Rtr HSSI interface is not showing

Error_Rate, Discard_Rate, or Packet_Rate. The problem is that the

value that is being stored into the attribute "Total_Packets" is larger

than a 32 bit Integer. So the overﬂow on the attribute crashes the

calculation which causes a failure to be displayed in the

Serial_IF_Port Performance View. This has been resolved by changing

the attribute "Total_Packets" from an integer to a counter.

Customer has Cisco Routers in their network that are utilizing Un

Number IP. When the customer Runs an ADISC, Model By IP (with

discover connection), or even a discover LAN, WA_Links are not being

created on the Serial Interfaces. This has been resolved by creating

the WA_Link regardless of whether the nexthop device was modeled

or not.

Annotated text moves across the SpectroGRAPH view to the right

(approx 1 to 2 pixels) each time a model is created or destroyed.

Zooming the annotations causes X,Y coordinates to be changed, which

causes this problem.