The HP NNM integration for HPOM is an example of agentless monitoring with SNMP. It includes SNMP policies that allow HPOM to receive HP NNM SNMP events. The HP NNM server itself serves as a proxy for agentless monitoring. The HP NNM Adapter installation configures the HP NNM server as a managed node in HPOM and automatically deploys SNMP interceptor policies to the HP NNM server. This is the first step in enabling agentless monitoring of the HP NNM monitored nodes. The next step requires the HPOM administrator to configure the nodes in HPOM using the node configuration editor as described in Configure monitored nodes individually. There are also many predefined services and tools for use with HP NNM monitored nodes.
The monitored nodes are discovered in a separate HP NNM discovered nodes group and can be manually added to HPOM. With the HP NNM Adapter, monitored nodes are not configured with the type SNMP, but with their discovered operating system type. Therefore, make sure that you change the operating system type if you do not intend to install an agent on these nodes.
NOTE:
The HP NNM integration is an example of a solution where the HP NNM
server acts as proxy, generating messages for all nodes managed by
HP NNM. These monitored nodes must be configured in HPOM.
Otherwise, HP NNM-related messages of those nodes will not be
received by the management server.
The SNMP interceptor policy type monitors SNMP events, and allows filtering based on originating node, event object ID or when a character pattern that you choose is found in an SNMP event.
The following example shows how one SNMP interceptor policy is able to monitor large volumes of SNMP events after establishing a small number of rules:
Each rule looks for a certain event object ID:
NOTE:
It is recommended that a specific SNMP interceptor policy is only
deployed to one proxy system.
|
‹$OPC_MGMTSV›
‹$A›
is
the variable containing the hostname of the originating host in the
following example for the HP Systems Insight Manager. The variables
differ from application to application, so carefully check the SNMP
event and variable definitions.
The following example shows how the variable ‹$A›
is used to set the node property of the outgoing message. This
assumes that the originating node is configured as a managed node.
See Configure monitored nodes
individually for details.
If source type MIB is selected, an SNMP GET is performed
on the specified object ID (OID). By default, the collection is
made on the local managed node but can be made remotely by
specifying the optional hostname. The following example shows how
the MIB with the OID .1.3.6.1.4.1.232.0.16075
is
monitored on node gordimer
:
Related Topics: