Asentria SiteBoss 530 User Manual
95
•
SMS: sms(
phone# or index
)
Send an SMS message to a specific phone number or
index
which refers to a phone number configured in the
Actions Definition menu.
•
Talert: talert(
ipaddress or index
)
Send a talert (Asentria Alarm via TCP).
°
ipaddress
is the destination machine;
°
index
is the IP address configured with
action.ip
. E.g.,
action.ip[index].
•
Trap: trap(
ipaddress or index
)
Send an SNMP trap. The parameters are the same as for the talert keyword. In order to send a trap there
must be a route for it. Since a trap is an unacknowledgable action, the way the unit knows if a trap is
successful is if it was able to leave the unit. In order for a trap to leave the unit there must be an IP route to its
host. A trap action without a route to its host is considered a failure. "Without a route" means, for example,
that:
°
if the host is meant to be on a local net but cannot be ARPed
°
if the host is meant to be off all local nets but the router cannot be ARPed
°
if the above two conditions exist and PPP cannot be raised as a backup route.
Each action can take a varying amount of time depending on what's going on in the unit. E.g., a trap may take less
than a second to send if there is a route for it on a network interface that is already up (like Ethernet). Otherwise, if the
unit is configured to bring up PPP in case the trap cannot be sent on an already-up interface, then the trap may take a
minute to send while the unit brings up PPP.
The unit starts all actions up to the first pause keyword at the same time. E.g., if you have an action list like
trap(1);email(1);modem(1);pause(60);trap(2)
then the unit will start the first 3 actions, pause for a minute, then start
the last action.
Wherever you can configure an event you can configure its actions. Generally this is with the
*.actions
setting key
that applies to the event you want to monitor. You can also configure email actions (in the action list syntax) for a user
profile's login challenge destination (e.g.,
sec.user.challenge.telnetsendto
). Not all actions are applicable to
all events: switch actions can be caused only by sensor events and data events.
Summary of Contents for SiteBoss 530
Page 6: ......
