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

<var-bind>

<tag>n:message</tag>

</var-bind>

<var-bind>

<tag>n:sequenceNumber</tag>

</var-bind>

</var-bind-list>

</mapping>

<notification-type>jboss.snmp.agent.coldstart</notification-type>

<var-bind-list wrapper-class="org.jboss.jmx.adaptor.snmp.agent.NotificationWrapperSupport">

<var-bind>

<tag>a:startTime</tag>

</var-bind>

<var-bind>

<tag>a:trapCount</tag>

</var-bind>

</var-bind-list>

</mapping>

</notification-map-list>

There are two deficiencies in this file, the correlation of the OIDs to the MIB and the handling of the trap

payload:

OID Correlation As previously mentioned in the introductory SNMP discussion about

MIBs and OIDs, the enterprise OID in the above file (1.2.3.4.5.6.7) is used

as a placeholder for an OID. It does not correspond to a MIB that defines

manageable objects in JBoss. Therefore, when HP SIM receives the trap,

it will not be able to interpret the OID and will issue an unknown OID

error. In order for this solution to be fully functional, a MIB describing

the manageable attributes must be created. Once there is a valid MIB, it

must be registered with the SNMP manager and the

notifications.xml file must be rewritten to reflect the true OIDs in

the MIB.

Trap Payload Handling A SNMP Trap legal payload consists of three data types; the variable

itself, the variable type, and the value of the variable. These are contained

in a <var-bind> tag as in the following example:

<var-bind>

<tag>a:startTime</tag>

</var-bind>

There are only two values being sent within the <var-bind> tags; the

variable denoted by <tag> and the value denoted by <oid>. There is

no tag to describe the variable type as in a legal payload, however, HP

SIM is capable of dealing with this.

To extract the tagged values, a wrapper class implementing the

org.jboss.jmx.adaptor.snmp.agent.NotificationWrapper interface must be supplied. At

runtime and based on the specific implementation, the value specified using the <tag> element is passed

Configuration Details 15