Specifications

Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-92 CS3 and MMS3
The problem is that there is now way for SPECTRUM to integrate
devices or find a particular interface by using Secondary IP address.
Since SPECTRUM does not store secondary ip addresses in the
database, there's no way of being able to do a find on them.
SPECTRUM only puts one of possibly many IP Addresses in the
"ip_address" attribute of an interface model. SPECTRUM uses the
term "secondary ip address" to indicate the other ip addresses of the
interface. However, the MIB really does not distinguish between a
"primary" and "secondary" interface. SPECTRUM just calls the first
one (in canonical order) the primary interface - all others are
secondary. The secondary addresses are not stored in any attribute,
and are store in a scratchpad only if the "Secondary Address Panel" is
viewed for a particular interface.
The resolution to this problem is one new inference handler has been
introduced and one has been modified:
a. CsIHIPAddressList, will be attached to the device.
CsIHIPAddressList::trig_model_activate() will read the MIBII
ipAdEntAddr list attribute, if it exists on a given device model. ( if
derived from IP ) This response list will be stored in the new
deviceIPAddressList attribute requested.
b. CsIHIPAddressList::trig_timer will be registered to re-scan this
ipAdEntAddr with the polling interval, in hours, stored in the newly
requested attribute deviceIPAddressListPollInt.
c. CsIHIPAddressList::trig_attr_change will be registered to watch
INTERFCE_STATE, if it exists on this device model. If the change
goes to 'Active', then a possible IP table modification is assumed, and
the ipAdEntAddr table is rescanned, and the outstanding timer is
unregistered, then a new timer is registered.
Thus CsIHIPAddressList maintains a snapshot of the complete list of
IP addresses on a device model.
--
The problem is the SPECTRUM VNM is filtering alarms is the
following scenario:
SPECTRUM is monitoring a piece of hardware, Sentinel, that tracks
contact closures. A contact closure is when any of the devices
connected to the Sentinel (e.g. Telcom Switch) is switched on or off.
The Sentinel has an SNMP Agent which provides proxy management