HP Operations Manager for Windows

Node Info Policy Type


The node info policy type provides a way to modify configuration information on a managed node. It is primarily a tool for configuring the agent to communicate through a firewall, and a troubleshooting tool to be used when working with a Hewlett-Packard consultant.

A node info policy writes values in the nodeinfo file. This file is created automatically when HP Operations installs an agent on a node. Deploying a node info policy to a node will cause the values in the node info policy to be written to the end of the node info file. Removing the policy deletes the values. If values are defined twice in this file, the value that is defined last (from top to bottom) is the value that is used.

Note NOTE:
If you want to set some of these values and want to ensure that they are never changed by a node info policy, you can write most of them in the opcinfo file, as well.( The only exceptions are parameters that set values relating to HTTP communication. These values may only be set in the nodeinfo file.) Information in the opcinfo file takes precedence over the nodeinfo file.
The node info policy type provides a simple editor where parameters can be typed. Each parameter consists of a name and a string value. Only ASCII characters are permitted. The string value may not contain new line characters. Example:

OPC_MGMT_SERVER endive.veg.com

The name starts at the beginning of the line and ends at the first white space (space or tab). The value starts after the white spaces and ends at the end of the line. Parameter can be disabled by inserting a number sign (#) at begin of the name.

It is important to be somewhat cautious when writing and deploying node info policies. If a parameter is defined in more than one policy, the value in the policy that was deployed last is the value that will be used. However, when a node info policy is removed from the node, the value for the parameter is not rolled back to previous value but rather is set to the default value. This can make it difficult to know what the configuration state on the node actually is. To prevent confusion, it is recommended either to deploy only one node info policy per node, or to create one node info policy for each specific parameter or unique group of parameters that you want set.

Related Topics: