HP Operations Manager

Configure managed nodes


The Node Configuration editor allows you to specify the managed nodes that you can monitor with HP Operations Manager for Windows. Operators monitor nodes and services and use the available tools to perform routine maintenance and also resolve problems that have critical business impact. Configuring a managed node is a multi-step process:

The managed nodes that you specify are listed in the Nodes folder of the console tree. You must configure each managed node individually.

Configure nodes using the wizard

To quickly configure a new node, use the Node Configuration wizard. This will provide the minimum amount of information you need to bring the node under management.
Note NOTE:
At any time you can exit the wizard by clicking Expert Mode. This returns you to the Node Configuration editor, where you can more completely specify the characteristics of this node. You cannot return to the wizard from the Node Configuration editor. When you add another node, the wizard opens again.

To open the wizard

  1. Open the Node Configuration editor, if it is not already open.
  2. In the Nodes tree, right-click Nodes and select New Node to open the wizard.
  3. In the Base Settings dialog box, type the fully-qualified domain name in the box provided. You must supply this information to proceed. The system will discover information about this node and display it in the following screen.
  4. Continue to specify the settings you want for this node as you proceed through the wizard screens.

To configure managed nodes manually

  1. Open the Node Configuration editor, if it is not already open.
  2. In the Configure Managed Nodes dialog box, specify the node or node group you want to manage by copying nodes from the Discovered Nodes list to the Nodes list or by creating new nodes or node groups.
  3. In the Nodes list, right-click the node you want to configure to open the Node Properties dialog box. Use the tabs to display information about the selected node and to configure it:
    • General: specify information about the environment, such as system name and owner.
    • Network: specify information such as primary node name, communications path, domain, heartbeat polling, and aliases.
    • Messages: view alias names and create new aliases.
    • System: specify information about the specific node, such as manufacturer, model, system type, operating system, and version.
    • Tools: specify tools available on the managed node.
    • Node Groups: view the parents of the selected node.
  4. Click Apply to see the effects of your changes.
  5. Click OK to confirm your changes and close the dialog box.
    Note NOTE:
    When you bring new nodes under management, a prerequisite check runs automatically when you click Apply or OK. This opens the Prerequisite Check Component dialog box, which displays the status of the process, the names of the nodes being checked, and the results of the check, including details and recommended actions. See the help topic Check prerequisites for managed nodes for complete details.
  6. Click Cancel to close the Node Configuration editor without saving your changes.
Note NOTE:
Special configuration may be required if you want to manage nodes over a firewall. Refer to the HP Operations Manager for Windows Firewall Configuration white paper for more information. Contact your HP BTO software representative to obtain a copy of this paper.

Automatic agent installation

The HP Operations agent is automatically installed on a managed node when you deploy a policy to the managed node. In some situations, you may want to install the agent manually. See Related Topics for details.

Managing intelligent devices

Using SNMP, you can manage intelligent SNMP devices such as printers, routers, and computers with unsupported operating systems and manage them from HPOM. See Related Topics for details.

Server and cluster failover behavior

HPOM for Windows monitors the availability of server components such as the Windows Management Interface (WMI), the server itself, and the cluster resource group (if your environment contains clusters.)

In the event of a failure of one or more of these components, some activities may be temporarily unavailable, until WMI or the server is restored. See Related Topics for details.

Related Topics: