Westermo RedFox Series - Manual (Page 566)

Westermo OS Management Guide
Version 4.17.0-0
❼ Enable/Disable: By default, the trigger is enabled.
❼ Condition: By default, the alarm condition is set to high. That is, usage
levels below the falling threshold are considered normal, and tempera-
tures above the rising threshold is considered an alarm situation.
❼ Severity: By default, active severity is WARNING and inactive severity
is NOTIFY.
❼ Action: By default, the trigger is mapped to the default action profile
(action 1).
In this example a PoE trigger is created to give an alarm if the usage rises
above 80%.
Example
viper:/config/alarm/#> trigger poe
viper:/config/alarm/trigger-2/#> threshold rising 80 falling 75
viper:/config/alarm/trigger-2/#> condition high
viper:/config/alarm/trigger-2/#> end
viper:/config/alarm/#> show
Trigger
Type Enabled Action Source
===============================================================================
1 frnt YES 1 Instance 1
2 poe YES 1 1
Action Targets
===============================================================================
1 snmp log led
===============================================================================
Summary alarm traps: Disabled
viper:/config/alarm/#>
24.3.2.11 Microlok Trigger Configuration Example
Syntax trigger microlok
Context Alarm Configuration context
Usage Create a Microlok session summary alarm trigger, and enter the Alarm
Trigger Configuration context for this trigger.
Additional settings for link-alarm triggers are listed below. As of WeOS
v4.17.0 there can only be one Microlok Gateway instance, thus the gate-
way instance (i.e., instance 1) is implicit.
566 ➞ 2015 Westermo Teleindustri AB