Configuring HP Operations managed node systems

The following RPC communication from managed nodes to the HP Operations management server is affected:

RPC Client	RPC Server	Direction	Explanation
`opcmsga`	`OvEpMsgActSrv`	Mgd Node Mgmt Server	HP Operations messages and action responses.
`opcdista (UNIX) opcctla (Windows)`	`OvEpMsgActSrv`	Mgmt Server Mgd Node	Distribution agent asks server if new distribution data is available (only used with HPOM for UNIX, not needed for HPOM for Windows). Can be switched off using the `OPC_NO_CFG_RQST_AT_STARTUP TRUE` variable setting.

Setting of Variables by Process

Most parameters for communication without the endpoint mapper on the managed node are configured in the opcinfo file. It is sometimes very important to apply settings to selected processes only, using the following syntax:

An entry OPC_RESTRICT_TO_PROCS starts a section that only applies to the specified process. All following entries are only evaluated for this one process. A second OPC_RESTRICT_TO_PROCS entry starts a section that only applies to the next specified process.

Specify all entries that should apply to all processes before the first occurrence of a OPC_RESTRICT_TO_PROCS section.

Example

`OPC_COMM_RPC_PORT_FILE`	`/tmp/port_conf.txt`
`OPC_RESTRICT_TO_PROCS`	`opcctla`
`OPC_COMM_REGISTER_PORT_RANGE`	`5001`

In this case, the specified port specification file is valid for all processes, while the port setting is only valid for the control agent, opcctla.

RPC Servers - opcinfo File Variables for RPC Servers on Managed Node Systems

Key	Type	Default	Explanation
`OPC_COMM_REGISTER_RPC_SRV`	Boolean	TRUE	Selects whether to register RPC server interfaces with endpoint mapper.
`OPC_COMM_PORT_RANGE`	string	empty	Specifies exactly one port to be used by the RPC server. Must be set for the control agent.

NOTE:
Make sure that the configured OPC_COMM_PORT_RANGE for the control agent (opcctla) contains only one port and that no other process uses this port.

RPC Clients - opcinfo File Variables for RPC Clients on Managed Nodes

Key	Type	Default	Explanation
`OPC_COMM_PORT_MSGR`	Int	0	Specifies at which port the message interface of the Message Action Server (`OvEpMsgActSrv`) is listening on the management server. For the HP Operations management servers, this must be the same value as used for `OPC_COMM_PORT_DISTM`.
`OPC_COMM_PORT_DISTM`	Int	0	Specifies at which port the deployment interface of the Message Action Server (`OvEpMsgActSrv`)is listening to configuration requests from the agent. For the HP Operations management servers, this must be same value as used for `OPC_COMM_PORT_MSGR`. This setting is needed if the `opcinfo` file of the agent does not contain the variable setting: `OPC_NO_CFG_RQST_AT_STARTUP TRUE`.
`OPC_COMM_RPC_PORT_FILE`	String	empty	Complete path pointing to a server port specification file as described below.
`OPC_COMM_LOOKUP_RPC_SRV`	Boolean	TRUE	Whether to perform an endpoint mapper lookup if no matching port is found in the server port specification file.

The settings OPC_COMM_PORT_MSGR and OPC_COMM_PORT_DISTM can be used if only one management server will be contacted, or all management servers are configured to use the same RPC server ports.

If multiple management servers with different port settings are used, a server port specification file must be configured using the OPC_COMM_RPC_PORT_FILE variable.

The server port specification file, if configured, is evaluated first. If not, the two additional opcinfo values (OPC_COMM_PORT_MSGR and OPC_COMM_PORT_DISTM) are evaluated. If these have a value of 0, they are considered as not set. See also Internal Process Handling.

An example of the server port specification file on a managed node is shown below:

`#`
`# SelectionCriteria`	`SrvType`	`Port`	`Node`
`# ------------------`	`-----------`	`-----`	`----`
`NODE_NAME`	`opcmsgrd`	`5000`	`primaryserver.hp.com`
`NODE_NAME`	`opcdistm`	`5000`	`primaryserver.hp.com`
`NODE_NAME`	`opcmsgrd`	`6000`	`backupserver.hp.com`
`NODE_NAME`	`opcdistm`	`6001`	`backupserver.hp.com`

somename.hp.com matches <*>somename.hp.com<*>
^somename.hp.com matches$ exactly somename.hp.com matches

NOTE:
The keywords used in the SrvType column refer to processes of the HPOM for UNIX management server. These keywords are also used with the HPOM for Windows management server, even though the corresponding interfaces or roles are implemented in one single process in HPOM for Windows (in the message action server).

Related Topics: