User guide

eWON 500-2001-4001-4002 User Guide - eWON Configuration
eWON 500®2001®4001®4002® Version 4_3_0 - User Guide - 10/5/05 - ©ACT'L sa - Page 27
4.3.2.1 Communities
The communities are defined here. These are acting like a "login-password" feature.
Please refer to the SNMP standard for detailed explanations.
Up to five different communities can be set up in the eWON.
Each community has different read and write attributes.
In the eWON, each of them can be specified for read and/or write right.
The standard public community is defined here as read-only.
4.3.2.2 Hosts
The hosts that can access the communities and/or receive the generated SNMP traps have to be specified.
If the checkbox Access SNMP from Any Host is selected, any IP address will be granted to browse the SNMP tree of the eWON.
The traps are always sent to known IP addresses, defined in the following fields.
Each host is determined by its IP address and by the community he is working on.
For each host, the user can specify whether he can receive traps and/or browse the SNMP tree.
A MIB file describing the SNMP structure and OID of the eWON is available on our web site.
Traps can originate from three different events:
The parameters for Basic traps are as follows:
The parameters for Alarm traps are as follows:
System traps
At cold boot and at soft reset, the eWON sends system traps
with identification 0 and 3 respectively.
Basic scripting traps The sendtrap Basic function can send a trap at user request.
Alarm event traps The eWON automatically sends a trap on alarm, containing alarm information.
Table 8: events that generate a SNMP trap
Param 0 Text string [0...255]
Param 1 Integer 32bits
Table 9: Basic SNMP traps parameters
Param 0 Tag name (Text [0..63])
Param 1 Alarm message (Text [0..255])
Param 2 Value of the Tag in alarm (Integer 32bits)
Param 3 Alarm status (Integer)
Param 4 Alarm Type (Integer)
Table 10: Alarm traps parameters