TD 92483GB
2008-06-05/ Ver. B
Installation and Operation Manual
UPAC- Unite Packet for Messaging and Alarm
45
6
Select the check box
Persistent
, if a fault should remain until the input is not active
any longer.
7
Enter the description of the event.
8
Click “Save”.
Removing Auxiliary Equipment
Remove auxiliary equipment by clicking the “Delete” symbol. A dialogue window opens,
click “OK” to remove the auxiliary equipment.
10.1.3 SNMP Traps
SNMP (Simple Network Management Protocol) can be used by IP equipment to
communicate that there are for example faults in the equipment.
The UPAC can be configured to generate a Status Log when receiving an SNMP Trap. The
Status Log will include the IP address that the trap was sent from and text entered in the
configuration. The information received in the trap can be added to the configured text.
The default action is to generate a Status Log with level “Information” for every received
trap. The log level can be changed in the Log Setup.
It is possible to add SNMP Trap actions to get different behaviour depending on the
sender’s IP address and the information in the trap. The actions will be matched in the
order displayed on the overview page and only one action will be executed.
By using wildcard *, several IP addresses can be matched in one action, for example
“172.20.*.*” matches all IP addresses starting with 172.20. Wildcard* can also be used
to match parts of the SNMP Trap message, for example “Error*” matches all messages
starting with the word Error while “*Error*” matches all messages including the word
Error.
Received traps can be discarded by selecting “No Log” in the Log Setup. This can be used
either to discard traps from a specified address or with a specific message, or in the default
action to discard all traps that are of no interest (i.e. the ones that are not matched by the
configured actions).
Information Received in Traps
The information in a trap is defined by the Management Information Base (MIB). It is
defined by the equipment vendor and contains information about which traps the
equipment can send. The received trap includes a hierarchically structured number called
object identifier (OID) and optional variables.
For example, traps sent from Airespace equipment will have an OID starting with
1.3.1.6.4.1.14179, where 1.3.1.6.4.1 identifies that it is an enterprise specific trap and
14179 stands for Airespace.
When the UPAC receives a trap, it creates a string starting with the OID followed by a
hyphen (-). Any received variables are added to the string after the hyphen. The filter set
up in the SNMP trap action is matched against the created string.
Example:
When a Cisco access point restarts, a trap with OID 1.3.6.1.4.1.9.0.0 is sent. The first
variable holds the uptime for the access point. The UPAC creates a string with the
following appearance; 1.3.6.1.4.1.9.0.0-4 days, 21:56:52.90.
When setting up the SNMP trap actions, consult the MIB provided by the vendor for more
information about the traps. In addition, set up the default action to include the received
