Specifications

SPECTRUM Software Release Notice Page 48
Event Configuration Editor
The Event Configuration Editor allows creation, deletion, modification, and browsing of
the following information in SPECTRUM: Alert Map, Event Disposition, Event Format,
and Alarm Probable Cause files.
Known Event Configuration Editor Anomalies
in SPECTRUM 6.5
Problem 1: When you edit EventDisp to allow an alarm or log an event on
just one model type, the change you made for one vendor becomes true for
many vendors. This causes all model types to respond to in the same way
to a specific trap. Redefining an event contained in the EventDisp file in a
vendor-specific directory is ignored since the event is also in the Aprisma
EventDisp file. SPECTRUM does not allow overriding a definition in the
EventDisp file once an event is defined in the table.
Solution: This problem will be corrected in a future release of
SPECTRUM.
Problem 2: When you make Frequency or Persistent Event extensions to
the EventDisp files using a text editor (such as vi, or emacs), and you later
modify those same Events through the Event Configuration Editor, it could
overwrite or drop any Frequency or Persistence changes.
Solution: Use a text editor such as vi or emacs to make these
modifications and do not use them in the Event Configuration Editor.