Specifications

9032277-04 Software Superseded by CS3/MMS3
5-91
Patches Issued Since the CS2/MMS2 Release
The problem is there is excessive polling with SPECTRUM 5.0rev1,
which results in a "sluggish" system.
The resolution is to correct two aspects of performance and polling in
SPECTRUM. First, a new method was created to make performing
external reads more efficient by treating each each list attribute to be
read as a separate entity. Second, a a new gather_ext_list method in
CsModel will cause an additional get_next request to go to the device.
The request will contain no objects to get. If the device responds with
no error, the dcm layer will seg-fault as it has not allocated any space
to store the response.
--
The problem is when a duplicate model of a ZX-250 is created
SPECTRUM does not produce an alarm. This is occurring because
there is no MAC address on the ATM interface of this device. It is the
ATM interface that holds the IP address of this device. The current
inference handler responsible for asserting a duplicate alarm requires
a valid MAC address attribute from the device. Because the ATM
interface has no MAC address the device model and duplicate model
don't have one a MAC address either and the inference handler
looking for duplicate models by MAC address fails to assert an alarm.
The resolution is to re-write the inference handler so that the model is
no longer required to have a valid MAC address attribute for the
duplicate model alarm to be asserted.
--
The problem is when mapping traps in the Event Configuration
Editor, if the value of specific trap ID or if any octet in an OID
mapping was greater than 64k, ECE will not save the trap. For
example the OID string would have the 65926 present in one single
octet (1.3.4.5.6.65926.7.8). The error message is, "Entry not saved.
Invalid Trap ID, must be dot separated OID string." The problem does
NOT exist if trap is mapped directly through the flat files.
The resolution is to have SPECTRUM duplicate the trap id string as it
is received from the text widget and then clean up the memory after
validating the string. Also, the maximum value for oid strings was
increased to greater than 64K (ie 75000).
--