Requires Free Membership to View
Here are the instructions:
- Configure Nagios to generate SNMP traps for any alerts you wish to send to Patrol. I use the snmptrap application that comes with Net-SNMP to do this, combined with a global or service-specific event handler. Or you could configure Patrol to be one of your standard notification methods, like email, pager or mobile phone. Below is an example of a SNMP trap that combines OIDs and Nagios macros that could be sent to Patrol. This will almost certainly need to be modified to suit your environment.
define command { command_name notify-pem-service-trap command_line /usr/bin/snmptrap -d -v 1 -c public pemprod.testing.com .1.3.6.1.4.1.2789.2005 '' 6 '' '' .1.3.6.1.4.1.2789.2005.1 s "Notification Type: $NOTIFICATIONTYPE$" .1.3.6.1.4.1.2789.2005.2 s "Service: $SERVICEDESC$" .1.3.6.1.4 .1.2789.2005.3 s "Host: $HOSTALIAS$" .1.3.6.1.4.1.2789.2005.4 s "Address: $HOSTADDRESS$" .1.3.6.1.4.1.2789.2005.5 s "State: $SERVICES TATE$" .1.3.6.1.4.1.2789.2005.8 s "DateTime: $SHORTDATETIME$" .1.3.6.1.4.1.2789.2005.7 s "Additional Info: $SERVICEOUTPUT$" } - Configure BMC Patrol to receive and process the incoming trap and assign the data to the relevant host and service being monitored. You will generally need to send at least the hostname, service, service state and any relevant host or service output to BMC Patrol.
This was first published in June 2007

Join the conversationComment
Share
Comments
Results
Contribute to the conversation