HP OSMS white paper: How to Monitor JBoss v4.0.3 SP1 with HP SIM using SNMP

2006-04-17 18:42:37,552 DEBUG [org.jboss.jmx.adaptor.snmp.trapd.TrapdService] V1 Trap from agent /10.1.1.149 on port 32771
IP Address......... 10.1.1.149
Enterprise Id...... .1.2.3.4.5.6.7
Generic ........... 3
Specific .......... 0
TimeStamp ......... 3600335
Length............. 4
Community string... public
Varbind[0] := .1.2.3.4.5.6.7.5 --> 3600335
Varbind[1] := .1.2.3.4.5.6.7.6 --> 4
Varbind[2] := .1.2.3.4.5.6.7.7 --> heartbeat report
Varbind[3] := .1.2.3.4.5.6.7.8 --> 3
The corresponding "Link Up" event in HP SIM is similar to the following:
Figure 5 Link Up Event Example
Conclusion
This white paper has demonstrated how you can monitor JBoss with HP SIM using SNMP. The SNMP
agent provided by JBoss is used to intercept JMX notification and convert them into SNMP traps for HP
SIM to consume. The conversion done by the SnmpAgentService is an example only and does not
convert the JMX notifications into traps with valid OIDs or complete trap payloads. In order to do this, a
MIB defining the SNMP manageable objects in JBoss must exist and the trap payload created by the
notification must be modified.
The basic steps to accomplish this are as follows:
1. Obtain a valid Enterprise OID for JBoss from the Internet Assigned Numbers Authority (IANA) if
one does not already exist. For more information, go to the IANA Web site at:
http://www.iana.org/cgi-bin/enterprise.pl
2. Create a MIB file to define OIDs for all manageable objects in JBoss (Presumably, this would be all
of the possible JMX notifications emitted by MBeans). Alternatively, you could define a MIB file
containing only those JMX notifications that are emitted by your applications Mbeans.
3. Create a notifications.xml file to map each JMX notification to the corresponding OID defined
in the MIB file.
Conclusion 21