Specifications

Corrected and Known Anomalies
Event Configuration Editor (ECE)
Software Release Notes Page 87
Problem 4: 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 of SPECTRUM.
Problem 5: 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 process those events in a the
same way. A user-defined event contained in the EventDisp file in a
vendor-specific directory is ignored if the event has been defined in another
EventDisp File which has been read first.
Solution: This problem will be corrected in a future release of
SPECTRUM.