Section 24.1.5, Sections 24.1.4 – Westermo RedFox Series User Manual
Page 544
Westermo OS Management Guide
Version 4.17.0-0
It is also possible to configure severity level ”NONE”. Alarm events with severity
NONE will not cause SNMP traps to be sent or events to be logged, however, such
events can still affect digital-out and ON LED targets.
Note
Severity levels can be configured independently for the events when an
alarm trigger becomes ”active” and ”inactive”. Default severity level are
WARNING for ”active” alarm events and NOTICE for ”inactive” alarm events.
24.1.3.5
Mapping triggers to actions
Triggers can be mapped to alarm actions (profiles) that are invoked when an
alarm event occurs, for more information see
. However, it is also
possible to leave a trigger unmapped, e.g., when defining a ping trigger to adjust
VRRP priority dynamically (see
24.1.4
Alarm actions - mapping triggers to targets
Instead of mapping triggers directly to alarm targets, each trigger is mapped to
an alarm action (alarm action profile). The alarm action specifies which targets to
use (SNMP traps, Logging, ON LED, and Digital-Out) when an alarm event occurs.
It is possible to configure several actions (action profiles). Each trigger can be
mapped to an individual action, but it is also possible for multiple triggers to
share the same action. This can be particularly useful when managing several
triggers of similar type, such as different types of RMON triggers.
By default a trigger is mapped to the default alarm action (index 1). The default
alarm action cannot be removed.
24.1.5
Alarm presentation (alarm targets)
When an alarm situation occurs, such as an FRNT ring failure, WeOS enables the
operator to be notified in numerous ways:
❼ SNMP trap: Alarms can be configured to generate SNMP traps
. See
for general information on SNMP.
2
As of WeOS v4.17.0 there is no support for SNMP traps for timer or hardware alarms.
544
➞ 2015 Westermo Teleindustri AB