Specifications

Corrected and Known Anomalies
Enterprise Alarm Manager
Software Release Notes Page 68
Problem 5: When the Alarm Manager receives a Link Down trap from a
device modeled in the database, SPECTRUM asserts a Red alarm on the
interface model that generated the trap, and a Yellow alarm on the device.
If that same device receives a second Link Down trap from a different
interface, that interface also turns Red. But when the device receives a
Link Up trap from the second interface, SPECTRUM clears the red alarm
on the second interface and the Yellow alarm on the device model. This
results in a Red alarm on the first down interface model but no associated
Yellow alarm on the device model.
Solution: This problem will be corrected in a future release of
SPECTRUM.
Problem 6: When printing an alarm report with multiple probable causes
from the Alarm Manager using a Windows NT workstation, you may get the
following printing problems:
1. The second listed probable cause (not shown in Alarm Manager without
scrolling down) will bleed through the printout outside of the tab.
2. Selected alarms prints blacked out without being able to read it.
3. The probable cause column title bleeds through the scroll bar on the
Windows NT printout.
Solution: These printouts require that you use a Level 2 Postscript
printer which eliminates the printing problems.
Problem 7: Currently, alarm IDs may not be unique during a single
runtime session of SpectroSERVER. One possible outcome could be when
you attempt to clear one alarm, a different alarm is cleared instead.
Solution: The chance that this problem will occur is very low. This
problem will be corrected in a future release of SPECTRUM.