HP Operations Manager for Windows

Node Info Policy Parameters


Caution CAUTION:
The node info policy is used primarily for troubleshooting and support purposes. The parameters documented here are a small subset that may help you to address some issues. Be aware, however, that you can substantially reduce the performance of the agent if you use these parameters incorrectly. In most cases, you will use a node info policy only if you are working with Hewlett-Packard to resolve a problem or to achieve a management scenario that requires advanced configuration techniques. Hewlett-Packard consultants may direct you to use parameters that are not listed in this documentation.

OPC_RESOLVE_IP
Description: Specifies the IP-address of the managed node's primary manager. This parameter can be used if name resolution is not working correctly in your network environment. Note that any changes dictated by an agent-based flexible management policy will override the value set here.
Type: string, a.b.c.d (for example, 15.136.120.1)
Default: (not set)
OPC_COND_FIELD_ICASE
Description: Toggles the case-sensitivity of policy conditions that match the object, application, or message group fields. TRUE = case-insensitive. FALSE = case-sensitive.
Type: Boolean
Default: TRUE
OPC_INT_MSG_FLT
Description: If TRUE, agent-internal messages (mainly HPOM-internal status- and error-messages) are passed to the HP Operations agent and can be filtered through opcmsg policies. This allows you to add your own actions, instruction text and so on. Information on how to configure filtering of server-internal messages (mainly agent health checks) can be found in the topic Agent Health Check
Type: Boolean
Default: FALSE
OPC_LE_CLOSE_MSG_DLL
Description: The default value is TRUE. This causes the Windows message DLL for EventLog messages to be closed after every read. This might increase CPU usage of the log file encapsulator process but it prevents the agent from locking DLLs, allowing software to be updated while the HP Operations agent runs.
Type: Boolean
Default: TRUE
OPC_AGENT_LOG_SIZE
Description:

Specifies the maximum size for the agent log files (opcerror, opcerro1, opcerro2, opcerro3) in increments of 1/10 KB (default 10000 * 1/10 KB = 1000 KB = 1 MB). When the current log file reaches 1/4 of that maximum size (default 1/4 * 1000 KB = 250 KB), it is moved to the next name (opcerror opcerro1 opcerro2 opcerro3 deleted) and a new opcerror log file is created.

This parameter is valid for the DCE agent only.
Type: int
Default: 10000
OPC_BUFLIMIT_ENABLE
Description:

Enable or disable checking of buffer-file limit on agent. Checks applied on msgagtdf-file. If TRUE the file will not grow unchecked and fill the disk if the management server becomes temporarily unavailable. The message agent counts the number of discarded messages, started actions, and message operations like acknowledge requests, and forwards them when the server becomes available again.

This parameter is valid for the DCE agent only.
Type: Boolean
Default: FALSE
OPC_BUFLIMIT_SIZE
Description:

If buffer-file limitation is set on agent, this value describes the limit for msgagtdf-file in kilobytes.

This parameter is valid for the DCE agent only.
Type: int, kilobytes
Default: 10000
OPC_BUFLIMIT_SEVERITY
Description:

Allows you to define a severity that overrides the buffer file limit, and allows messages of that severity, or higher, to be added to the buffer file.

This parameter is valid for the DCE agent only.
Type: string : normal, warning, minor, major, critical
Default: major
OPC_NAMESRV_CACHE_SIZE
Description: HP Operations agent processes use a name-resolution cache in the trap interceptor process to improve performance. If the cache is full, least frequently used entries are replaced by new ones. If a node is the SNMP target for over 100 nodes, it is useful to enlarge the cache.
Type: int
Default: 100
OPC_NAMESRV_DISABLE_CACHE
Description: Enable or disable the HPOM name-service cache. This can be useful if the node names in your environment change frequently.
Type: Boolean
Default: FALSE
OPC_MSI_CREATE_NEW_MSGID
Description: Control the how message-IDs are created when messages are sent to the message stream interface (MSI).

1 = Create a new message ID each time a message attribute is changed or the copy-operator is called.
2 = Set no new message ID when attributes are changed if this message was sent to only one instance. (The message must be 'diverted' for that, not 'copied' so that the HP Operations server or other MSI API-users has also a copy of it.) If you apply the API copy-operator to a message, the copy is no longer 'diverted' and later attribute changes lead to a new message ID. Note that the message original message-ID attribute which is accessible for API-users contains the original message ID, if it was changed (otherwise it contains a null-id).
3 = Same as 2, except that the copy-operator immediately creates a new message ID for the copy.
4 = Message IDs are not modified at all. The API-user is responsible for it.
Type: int, 1 <= n <= 4
Default: 2
PROXY
Description: Sets the proxy for any HP BTO Software HTTP clients running on the computer. Clients can be Reporter or Performance Manager (running on the management server) or the Service Discovery agent (running on a managed node). The format is PROXY port +(a)-(b); proxy2:port2 +(c)-(d); and so on. The variables a, b, c and d are comma separated lists of hostnames, networks, and IP addresses that apply to the proxy. Multiple proxies may be defined for one PROXY key. '-' before the list indicates that those entities do not use this proxy, '+' before the list indicates that those entities do use this proxy. The first matching proxy is used.

Example:
PROXY web-proxy:8088-(*.veg.com)+(*.lettuce.veg.com)
Meaning: the proxy 'web-proxy' will be used with port 8088 for every server (*) except hosts that match *.veg.com, for example, www.veg.com. The exception is hostnames that match *.lettuce.hp.com. For example, romaine.lettuce.veg.com the proxy server will be used.

Refer to the HP Operations Manager for Windows Firewall Configuration white paper for more information.
Type: string
Default: not set
CLIENT_BIND_ADDR(app_name)
Description: Sets the address for the specified application's HTTP client. Valid application names are com.hp.openview.CodaClient (on the management server) and com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML (on the managed node).

Example:
CLIENT_BIND_ADDR(com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML) 65.114.4.69

Refer to the HP Operations Manager for Windows Firewall Configuration white paper for more information.
Type: string
Default: not set
CLIENT_PORT(app_name)
Description: Sets the port number for the specified application' HTTP client. Valid application names are com.hp.openview.CodaClient (on the management server) and com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML (on the managed node).

Example:
CLIENT_PORT(com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML) 8003

Refer to the HP Operations Manager for Windows Firewall Configuration white paper for more information.
Type: string
Default: not set
SERVER_BIND_ADDR(app_name)
Description: Sets the address for the specified application's OpenView HTTP server. Valid application names are com.hp.openview.Coda (on the managed node) and com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML (on the management server).

Example:
SERVER_BIND_ADDR(com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML) 65.114.4.69

Refer to the HP Operations Manager for Windows Firewall Configuration white paper for more information.
Type: string
Default: not set
SERVER_PORT(app_name)
Description: Sets the port number for the specified application's OpenView HTTP server. Valid application names are com.hp.openview.Coda (on the managed node) and com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML (on the management server).

Example:
SERVER_PORT(com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML) 8001

Refer to the HP Operations Manager for Windows Firewall Configuration white paper (available from your Hewlett-Packard representative) for more information.
Type: string
Default: SERVER_PORT(com.hp.openview.Coda) 381
SERVER_PORT(com.hp.openview.OvDiscoveryCore.OvDiscoveryInstanceXML) 6602
OPC_IP_ADDRESS
Description:

When a node has several IP addresses, this parameter configures the agent to always use a specific IP address.

This parameter is valid for the DCE agent only.
Type: string (for example, 192.168.1.1)
Default: not set (the agent uses the first IP address it finds)
OPC_ALTERNATIVE_AGENT_IDS
Description: Sets alternative agentIDs for a particular node. Usually used in cluster environments.

Example:
OPC_ALTERNATIVE_AGENT_IDS agentid1,agentid2

See Managing cluster-aware applications for more information.

Type: string
Default: Not set
SNMP_SESSION_MODE
Description: Determines how the HP Operations agent intercepts SNMP events. To intercept SNMP V2 events on Windows managed nodes, disable the standard Windows SNMP service, which does not support SNMP V2 events. Set the keyword SNMP_ SESSION_MODE to NNM_LIBS in the node's opcinfo file. The keyword supports the following values:

TRAPD: Use the Operations event interceptor (opctrapi).

NO_TRAPD: Use direct port access mode.

TRY_BOTH: Try both, the trap daemon and direct port access mode.

NNM_LIBS: Use the OpenView NNM libraries (shipped with the Operations agent) to receive events.

The opcinfo file can be found in these locations:

AIX: /usr/lpp/OV/OpC/install/opcinfo

UNIX: /opt/OV/bin/OpC/install/opcinfo

Windows: <drive>: \usr\OV\bin\OpC\install\opcinfo
Type: int
Default: Not set

Related Topics: