Specifications

Patches Issued Since the CS2/MMS2 Release

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

5-76 CS3 and MMS3

The problem was that the RMONFilter and RMONPacketCapt had an

OID set by sys_oid_verify when the did not need one. Further, the

OID was identical to the one set for a HubSynTR3xxx model. This was

causing problems when modeling a HubSynTR3xxx with Model by IP.

Upon modeling a HubSynTR3xxx with model by IP the device would

get a yellow alarm and model mismatch error.

The resolution was to remove the sys_oid_verify value for the

RMONFilter and RMONPktCapt model types. Since these models are

applications the value was not needed.

The problem was Frame-Relay DTE models were not being created for

the CSX400 model type. There is a model type rfc1313App, which is

speciﬁc to the CSX400 model type, but the Frame Relay manager uses

fr1315App to create the DTE's.

The resolution was to add Manages Meta-Rule between CSX_Device

and FrmRlyAppDerPt.

The problem was that any model type whose default value for

System_Desc_Verify equaled GENERIC_SNMP_DEVICE would cause

that device (i.e. HubCat5509) to be created instead of a Generic SNMP

Device model type.

The resolution was to change the value of System_Desc_Verify to be

<blank> instead of "GENERIC_SNMP_DEVICE" so that if a customer

models a device for which they do not have a Management Module it

will be correctly modeled as a Generic SNMP Device.

The problem was when RMON Probes were used as monitor point for

LAN 802.3 and LAN 802.5 they would not show the same ﬁgures as

the RMON Segment View or as other RMON Software (i.e. HP

NetMetrix).

The resolution was to correct the following formulas:

a. WatchUtil - which provides the TR_Mon_Util attribute to the

LAN802.5 GIB view. The formula was changed from:

TR_Mon_Util=TR_Mon_Bytes_Per_Second/TR_Mon_Ring_Speed