ManageEngine® Applications Manager Sending Trap | ||
There are some circumstances where some Manager Applications also need to be intimated about occurrence of fault in the servers or applications being monitored. In such case, the alarms can be sent as traps to the manager applications and they can be viewed by any standard SNMP Manager such as Trap Viewer, HP Openview, IBM Tivoli etc. The supported versions of SNMP Trap are SNMPv1, SNMPv2c and SNMPv3
To configure an alarm as a trap and send it as an action, follow these steps:
Select the New Action link from the top menu.
Click Send Trap under the Actions menu in the left frame. This opens the Create Send Trap action screen.
Select the SNMP trap version (v1 / v2c / v3) from the combo box.
Specify the following details:
Any display name for the action.
The destination or the manager application host name to which the trap has to be sent.
The port number,
where the manager host is running.
The following are the details required to be filled for a trap PDU:
The OID (Object Identifier) of the management object of a MIB.
The community for the trap.
The message, which will be sent as trap varbinds.
The message can be enhanced by using Replaceable
Tags.
Note : Multiple Varbinds can be specified by having multiple
ObjectIDs and their values as comma separated in "ObjectID"
and " Message (Varbinds) " field respectively. For e.g., you
can give ObjID1, ObjID2, ObjID3 in the ObjectID field to represent 3 Object
IDs and correspondingly give ObjValue1, $RCAMESSAGE (the root cause message
will be passed through the replaceable tag - $RCAMESSAGE), ObjValue3 etc.,
in the varbinds field to specify the values. ObjID1 and ObjValue1 will
be passed as varbinds, same is the case with the other varbinds.
For SNMP Version V3:
Select one of the three Security Levels:
NoAuthNoPriv - Messages can be sent unauthenticated and unencrypted. Enter a UserName and Context Name.
AuthNoPriv - Messages can be sent authenticated but unencrypted. Enter a UserName, Context Name and an
Authentication Password. You can select an Authentication Protocol like MD5 or SHA from the drop-down list.
AuthPriv - Messages can be sent authenticated and encrypted. Enter a UserName, Context Name,an Authentication Password and a Privacy Password. You can select an Authentication Protocol like MD5 or SHA from the drop-down list. By default 'DES' encryption technique will be used.
Select the Generic type of trap PDU from the combo box. Specify the Enterprise OID for the trap You can also use the MIB Browser to provide the OID. In case, you want to upload a new MIB, then use the Upload Files/Binaries option. In case of SNMPv2c trap, mention the SNMP Trap OID.
Click Create Action to complete the configurations. This will list the trap action name and its details along with the other actions configured.
Click Add New for creating more trap actions or Delete (on selecting the respective action's check box) to delete the action.
After creating an send trap action, you can edit or execute that action. These two tasks can be performed from the "View Actions" page.
To edit the action,
click the Edit icon .
You can also have a
trial execution of the action. To do so, click the Execute
icon of that action.
Note: You can configure alarm actions (for eg., EMails to be sent) for unsolicited traps. Refer FAQ. |
Executing Program |
Execute MBean Operation |