Ericsson LBI-39224 - Manual (Page 215)

LBI-39224
3-185
Warning Trigger
A warning trigger will set the output event active on receipt of a
warning with the specified group/sub-group at the MOM. Since
warnings are never cleared (one-shot event) all warning triggers
will require manual deactivation using the CEC/IMC Manager's
I/O configuration screen
Deactivate button. The output will
remain active until it is manually reset from the CEC/IMC
Manager.
Error/Warning Message Group and Error/Warning Msg Sub
Group
All Error/Warning triggers are specified by the group/sub-group
used in the error/warning log. When an error/warning trigger is
selected, the message group/sub-group fields are displayed. For
example, for error message Exx-yyy, xx represents the Message
Group and yyy represents the Message Sub Group. (See "Log
Event State Changes" for an example of an error message.) Enter
the desired message group/sub-group from the list of error/warning
conditions found in Logged Error/Warning Definitions.
Console Mask
Auxiliary I/O events are assigned to consoles by selecting the
corresponding check box in the Console Mask field (upper right
quadrant of the dialog box). For an output event this specifies which
consoles may trigger the event. For example, if "Alt+F1" is specified
as the event trigger (see "Activate" above) and consoles 1 and 6 are
selected in the console mask, then the event can be triggered by
pressing Alt+F1 at either console 1 or console 6. In the case of a
toggled event (changes state with each key press) key presses from
different consoles can toggle the current state. For example, console 1
may toggle the event active and console 6 may toggle the event back to
the inactive state. An input event's message will be displayed
simultaneously at all consoles specified in the console mask whenever
the input goes active.
Log Event State Changes
When this check box is selected (default) the CEC/IMC Manager will
log an "Auxiliary I/O - State Change" warning whenever the I/O event
changes state. This provides a history of each activation/deactivation of
the I/O event. If a defined event is expected to occur frequently, such
as "station busy" at a console, the event logging should be disabled to