Specifications

Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-86 CS3 and MMS3
The problem was that an error shows up in the SPECTRUM Control
Panel when the Event Configuration Editor is launched from it. This
occurs on the Windows_NT platform only and the error message is:
errorCsTSsteae_VendorError: The directory cannot be found.
Configure trap mappings will not be available
This occurred even though the user had full permissions to the entire
CsVendor directory, and the $SPECROOT, $SG_INSTALL_ROOT. The
ECE starts without a problem from the command line.
The resolution was to correct the way the CsVendor directory was
being built and implemented. The error message should no longer
occur and the ECE should be able to be launched from the
SPECTRUM Control Panel.
--
The problem was that WA_Links were sometimes turning RED
incorrectly. This issue came about when a customer tried to change
the community name of a router connected to a WA_Link. The router
turned ORANGE and the WA_Link turned RED. This is due to the
way WA_Links monitor the state of their connected ports. Every
Polling_Interval, the WA_Link checks its status, first by it's normal
algorithm, and then by examining its connected ports. This checking
was based only on SNMP contact (read by Dev_Contact_Status). In a
case where a WA_Link gets triggered and sees that one of its
neighbors is down and the other is up will cause the WA_Link to turn
RED. This could prove to be a false alarm if only SNMP contact is lost,
but ICMP (read by Contact_Status) contact still remains.
The resolution was to implement ARE_YOU_DOWN and
ARE_YOU_UP actions to first check SNMP contact via the traditional
"ECHO_ACTION". If the ECHO_ACTION fails during an
ARE_YOU_DOWN request, then SPECTRUM will check to see if
ICMP is enabled for the device (by reading Contact_Status). If so,
then we'll try the SUPPORT_OTHER_PROTOCOL action (ICMP
ping) on the device. If that fails, then the device is really down. If it
succeeds, then the device is up. A similar process will be performed for
the ARE_YOU_UP action.
--
The problem was a customer had a bridge that was connected to a
GenFDDIMac_NM. The other side of the Bridge connected to a