Specifications

9032277-03 Software Superseded by CS2/MMS2
5-13
SPECTRUM_5.0rev1.P41
Included in P48.
(Also refer to the Notes on corrected anomalies, on Page 5-12.)
SPECTRUM_5.0rev1.P42
Creating a model by IP via CLI, creates the device as Pingable. This has been
resolved by having it create a device with the correct model type.
(Also refer to the Notes on corrected anomalies, on Page 5-12.)
SPECTRUM_5.0rev1.P43
After installing P23 the following message is printed out in the VNM.OUT file:
status=1 status=1, repeatedly. This was caused by debug output left in the
code. This has been removed.
RMONEthProbes are not being created after installing P23. This was caused
by code that was trying to filter out SMB10 interfaces. This has been resolved
by backing out the code to filter out the SMB10 interfaces.
When using the RMONEthProbe for the FEPIM Port on a 6E233-49 the
Monitor Point watches will intermittently fail.
When you removed a probe as a monitor point it used to invalidate the actual
probe instances because the hex conversion was used, so it was invalidating
the wrong probe. The solution is to use the decimal conversion.
The current RMON code was not searching free slots in EtherStatsTable for
more than 50 instances.This will cause a problem 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