virtual access GW1000M Series - Page 321

35: Event system
_______________________________________________________________________________________________________
_____________________________________________________________________________________________________
© Virtual Access 2017
GW1000 Series User Manual
Issue: 1.9 Page 321 of 350
UCI: va_eventd.<forwarding
label>.severity
Opt: severity
Only generate events with a severity in the severity range. This
is optional. Severity must be a range in the form severity1-
severity2.
Example: va_eventd.@forwarding[0].severity=emergency-
warning
Severity levels
debug
info
notice
warning
error
critical
alert
emergency
UCI: va_eventd.<forwarding
label>.target
Opt: target
Target to send the event to. This parameter refers to the target
name as defined in a target config section.
Table 114: Information table for event system forwarding rules
35.7.6 Va_eventd: connection testers
There are two types of connection testers:
 ping connection tester, and
 link connection tester.
Multiple connection testers can be defined and each forwarding section can be given a
label for identification. For example:
To define a connection tester label of Tester1 using package options, enter:
config conn_tester ‘Tester1’
To define a forwarding label of Tester1 using UCI, enter:
va_eventd.Tester1=conn_tester
In the examples below no connection tester label has been defined.
35.7.6.1 Ping connection tester
A ping connection tester tests that a connection can be established by sending pings.
If successful, the event system assumed the connection is valid for a configurable
amount of time.
35.7.6.2 Ping connection tester using UCI
va_eventd.@conn_tester[0]=conn_tester
va_eventd.@conn_tester[0].name=pinger
va_eventd.@conn_tester[0].enabled=1
va_eventd.@conn_tester[0].type=ping