HP OSMS white paper: How to Monitor JBoss v4.0.3 SP1 with HP SIM using SNMP
http://www.vmware.com/
Configuring the SNMP Service
The service resides in the /usr/local/jboss<version>/server/all/deploy/snmp-adaptor.sar
directory. As mentioned in the previous section, all three JBoss configurations (all, default and minimal)
were installed to ensure the availablitiy of the SNMP service.
NOTE: If JBoss is running, you must stop it using one of the following commands:
/etc/init.d/jboss stop
or
/usr/local/jboss<version>/bin/shutdown.sh
For this implementation, you must copy the files required to implement the SNMP service to the deploy
directory, /usr/local/jboss<version>/server/default/deploy/snmp-adaptor.sar using
the following command:
cp -r /usr/local/jboss<version>/server/all/deploy/snmp-adaptor.sar/ /
/usr/local/jboss<version>/server/default/deploy/snmp-adaptor.sar
NOTE: If the JBoss application server is running when the snmp-adaptor.sar directory is copied,
JBoss will attempt to load the new module as soon as it detects its presence. Since additional configuration
steps are necessary to enable the SNMP adaptor, it is advisable to either shutdown JBoss first or be sure
to restart JBoss after the changes have been made.
The SnmpAgentService service is configured with the following two files, which are located in the
deploy directory previously described:
• managers.xml — Configures where traps are sent.
• notifications.xml — Specifies the exact mapping of each notification type to a corresponding
SNMP trap.
The managers.xml file allows the definition of one or more receiving SNMP Managers, along with the
version of the SNMP protocol to use for forwarding traps. You must add one new <manager> entry in this
file to specify the HP SIM manager. In the following example managers.xml file, the HP SIM manager
is identified by the <manager> entry with IP Address 10.1.1.57 and port 160:
<?xml version="1.0"?>
<!--
$Id: OSMS_WP_Mon_Jboss_SNMP.xml,v 1.21 2006/09/13 18:09:55 loval Exp $
This file is used to configure the SNMP managers to which the generated
SNMP traps should be forwarded.
Each entry must specify:
- the manager's address (IP address or host name)
- the listening port
- the local binding address (optional)
- the local binding port (optional)
- the SNMP version to use (1 or 2)
More than one managers may be specified.
Note that traps are sent inside independent UDP packets so there is a
possibility to be re-ordered or completely lost. Also, even if the
forwarding IP address does not exist or nobody is listening on that
particular port, the trap will still be sent (however,
nobody will receive it); this is normal behaviour.
-->
<manager-list>
<!--
A default test manager to forward traps. It is controlled by the
"jboss.jmx:name=SnmpAgent,service=trapd,type=logger" MBean that
simply outputs received traps as log4j DEBUG messages
Configuration Details 13