Specifications

SPECTRUM Software Release Notice (SSRN)
For SPECTRUM 6.6 with Service Pack 5 CD release
Page 12
Document 5156
- SPECTRUM no longer polls the status of a port for which it's received
a LinkDown trap, to monitor when it comes back up. This was done
for performance and consistency reasons. If the user wants the status
of a port polled, they can make the pipe connected to it “live,” or set
PollPortStatus on the port model to TRUE. Note that Cisco devices
running pre-12.0 IOS will not send a LinkUp trap, and therefore
enabling a Live Pipe or PollPortStatus on links/interfaces of interest
would be required to get automatic LinkDown alarm clearing.
- Automatic Alarm Clearing: It is important to note that any port status
alarm will be automatically cleared by SPECTRUM if both of the port's
ok_to_poll and PollPortStatus attributes are set to FALSE.
• Warning message(s) may occur in the install log. These warnings do
not imply a problem and can be ignored. For example: “Warning:
Attribute 0x114e2 does not appear to be a valid attribute for modeltype
0xXXXXXXX. Default value not set.”
• AlarmNotifier will only pass the most recent event for an alarm update
if the new SHOW_ALL_EVENTS .alarmrc parameter is set to FALSE. By
default, this new parameter is set to FALSE, thereby changing the out-
of-box behavior of AlarmNotifier. For AlarmNotifier integrations that
depend on the prior default behavior of all associated events being
passed with alarm updates, SHOW_ALL_EVENTS should be set to TRUE
in the .alarmrc.
• CLI output change - CLI “show attributes” output for multiple attributes
are now reported in the same order as they were requested. This
restores the behavior that existed prior to the 6.5.1 release. (*** This
may require certain CLI scripts to be adapted to support this output
change.)
• AutoDiscovery behavior change - When you run a container based
discovery (with Map Topology unchecked), AutoDiscovery now
attempts to move all models (both new and pre-existing) that
correspond to entries in the result set into the chosen container.
Previously, a container-based discovery (with Map Topology
unchecked) would only put new models in the container. The current
work-around is to set the IsMovable attribute to FALSE for all existing
device models before performing any container-based discoveries. To
do this using Search Manager (for device models selected from search
results), select Management > Set Attribute Values and set
Topologically Relocate Models to False.