Use this screen to configure destinations for SNMP traps or informs (alarms and notable events) on the corporate network. This topic covers:
In order to use this screen:
Some form of corporate network management system (NMS) must be in place to collect the SNMP messages. See SNMP operation for details.
The SNMP ports must be enabled on the Ethernet interface to the corporate LAN. See Check or change SNMP status for details.
To set up or change inform request and trap destinations on the corporate network:
On the main menu under the SNMP section, click the Configure Trap Destinations link.
The Configure Trap Destinations screen appears. The table lists all the trap destinations that have been configured. Information includes:
Status: Shows if the configured destination is enabled or disabled.
Traps or inform requests (informs) are only sent to a destination if it is enabled.
Disabling a destination keeps the configuration data in the file, but stops traps and informs from being sent.
IP Address: Address of workstation with the NMS to which traps are sent. Must be entered in dotted decimal notation (for example, 192.168.1.1).
Notification: The type of trap to be sent: trap (alarm) or inform request. Informs are acknowledged traps (an SNMP layer acknowledgment that the trap was received).
SNMP Version: Version of the protocol to use in sending traps. Options are Version 1 (v1), Version 2c (v2c), and Version 3 (v3).
Requirements for the different
SNMP versions are described in SNMP
version-dependent information. The three final fields on this screen
are blank if SNMP Version 1 or Version 2c is used.
Community or User Name: The authentication mechanism used by the different SNMP versions.
Community Name Authentication is a plain text string used for SNMP v1 and v2c.
User Name is part of the user-based security model for SNMP v3. This character string indicates the user that is authorized to send traps to the destination.
V3 Security Model: The level of security to use when sending v3 traps. Options are None, Authentication, and Privacy. See Add or change trap destination for details.
Authentication Password (v3 only): Pass phrase for the user specified in the User Name field, used to digitally "sign" v3 traps.
Privacy Password (v3 only): Pass phrase for the user specified in the User Name field, used to encrypt v3 traps.
Choose the action you want to do next:
Add a new trap destination.
Click the Add button.
The Add Trap Destination screen appears. All the fields are blank.
See Add or change trap destination for details on filling out this screen.
Change a trap destination.
Select the trap destination you want to modify. Click the Change button.
The Change Trap Destination screen appears, prepopulated with trap information.
See Add or change trap destination for details on filling out this screen.
Delete a trap destination.
Select the trap destination you want to remove. Click the Delete button.
The screen redisplays the destination you selected, and prompts for confirmation.
If this is the correct trap to delete, click Delete. The trap destination is removed from the configuration file, and the main page redisplays.
To not delete this trap destination, click Do Not Delete. The main page redisplays, with the trap destination still present.
If an error message appears, see the next section.
When finished, continue working with the web administration interface as needed.
The Configure Trap Destinations screen may display the following error:
Unable to contact alarm agent: The Configure Trap Destinations page was unable to notify the server's alarm agent that the configuration file was changed. This error could occur following any add, change, or delete operation. To solve this:
Click the View Process Status link and verify that the G3 alarm agent is running.
The G3AlarmAgent should be listed as UP. If it is, proceed to step 2.
If the G3AlarmAgent is listed as DOWN, then the agent has had a major failure and requires fault isolation.
Select any destination and click the Change button. The Change Trap Destination screen appears.
Re-submit the page without making any changes by clicking the Change button.
This causes the configuration file to be re-created, and the alarm agent is notified again.
Add or change trap destination