HP Operations Manager for Windows

Identify the originating node


In agentless monitoring, events on the monitored nodes are detected and processed by policies on the proxy system. Based on the deployed policies, HPOM messages are generated and forwarded to the HPOM management server by the proxy agent.

It is important that whenever a message is generated, the HPOM management server can identify the node generating that message. Otherwise the message would be filtered out and would not have any influence on the status of an HPOM service. Therefore, it is very important that the incoming message belongs to one of the following:

Configure the proxy system

The system used as the proxy system for agentless monitoring must be configured as a managed node in the HPOM management server.

If you only configure the proxy system as a managed node (and not the agentless nodes as shown in the next section), then you have to make sure that all messages that are created by agentless monitoring specify the proxy system as the originating node. This is required because all messages have to be associated with a managed node. If policies set the node property to another node, and this node is not configured as managed node in HPOM, then the corresponding message is discarded.

In addition, you can put the originating node name in the message, for example in the message text or the object box, so that you do not loose this information. This setup can be used if it is not necessary to distinguish between several monitored nodes, and if you do not use the monitored node names in HPOM service definitions. The proxy system is treated as the owner of the problem and messages are shown as messages belonging to the proxy system itself.

Configure monitored nodes

Besides the proxy server, which must be configured as a managed node in HPOM and has an HP Operations agent running on it, it is also recommended to also configure the monitored nodes in HPOM.

The advantage of configuring the monitored nodes in HPOM is that policies can set the node name to the originating node and messages will then show up as messages of the originating node in the message browser. It also allows you to create and use services that are hosted-on monitored nodes. You can configure agentless nodes in the following ways:

Integrate discovered agentless nodes

In most cases, the nodes that you should monitor agentlessly are already discovered by HP BTO Software integrated products such as HP NNM. You can normally find theses nodes within the Discovered Nodes groups, which are accessible from the Configure Managed Nodes dialog box:

They can be drag-and-dropped directly into the managed node list from the Discovered Nodes group.

Add agentless nodes individually

It is also possible to add a monitored node by right-clicking any group in the Nodes list to display the shortcut menu and select New Node from that menu. To manage devices such as printers, routers, computers with unsupported operating systems, and computers without the need for full HP Operations agent monitoring, you must ensure that they have an IP address or a primary node name.

The monitored nodes should be set up as follows:

Configure external nodes

It is also possible to add a monitored node by right-clicking any group in the Nodes list to display the shortcut menu and select New External Node from that menu. Specify a pattern that matches the fully qualified domain names (FQDN), IP addresses, or node names of the agentless nodes. The advantage of setting up agentless nodes as external nodes is that one external node can represent multiple agentless nodes. This means that fewer nodes must be configured.

Related Topics: