Specifications

Patches Issued After the CS1/MMS1 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-16 CS3 and MMS3
for devices with more than 50 instances in the etherstats table. The
solution is to increase the number of slots.
Token Ring Probes are failing as Monitor Points. This is being resolved
by adding the correct attributes to allow this to work correctly.
The TR_Mon_Ring_Speed watch is set to read the ifSpeed from the
MIB-II Interface Table. The problem occurs in that the OID suffix is
set to use the value of the attribute, mp_intefaceOIDref. This attribute
is set to 1, and unless changed by an Inference Handler, it will remain
1. This is true, regardless of the interface index of the RMON TR
Probe that is used to roll-up values to the Discrete LAN. This is being
resolved by modifying the monitor point inference handler and setting
the value of mp_intefaceOIDref to the value of the RMONTRProbe's I/
F index which is being copied into the Lan.
There is also an error in the Load Calculation. It is defined, using the
SpectroWATCH TR_Mon_Util. This is being resolved by correcting the
calculation.
The Check Configuration action button in the RMON profile GIB view
is not getting implemented for the RMONApp model. It responds with
“Attempt to invoke action failed. Error = Not implemented,0x2”. This
is being resolved by initiating the process to discover the RMON
groups by creating the RMONCreate model and triggering the correct
action.
(Also refer to the Notes on corrected anomalies, on Page 5-14.)
SPECTRUM_5.0rev1.P44
Capturing of host configs on SmartSwRtr fails with no explanation
The error states “Capture Failed” with no details.
To reproduce this, go to the configuration screen and perform a
capture. It will “think” for a while, and, if you have the “Configuration”
screen open off of the device, the “Manager Address” field will change
to the last known entry for the IP address and right after, you'll see
ECM fail.
The cause was that the attribute type of the ManagerCfgAddress was
incorrectly set to text-string where it should be of type IP ADDRESS.
The resolution was to correct the setting of the attribute type.
If the customer tries to do a capture on a large number of models of a
given model type, sometimes the process will hang and never return.