Server Port Specification File

Standard HPOM patterns can be used. A description of all available patterns is available elsewhere in the HPOM for Windows online help.

NOTE:
Patterns without anchoring match values may be prefixed or suffixed by anything.

The RPC client reads the file before opening a connection to an RPC server and tries to find a matching pattern. The first match completes the operation. If no match is found (or the file does not exist or has not been configured), the variable OPC_COMM_LOOKUP_RPC_SRV decides whether to perform an endpoint mapper lookup. If an endpoint mapper lookup is not performed or it fails, the communication failure is handled in the usual way.

A configured port value of 0 is the same as if no matching entry is found and causes the RPC client to perform a regular endpoint mapper lookup (unless disabled entirely).

This can be used in a similar way to HPOM suppress conditions to specify an entry at the very beginning to filter out all nodes (by pattern) that still have an endpoint mapper running.

For all other nodes that do not match this suppress condition, the RPC client continues to search for a match in the remaining entries of the file.

File Syntax

Empty lines are ignored.
Comments start with the character #” but it must be the very first character. A line containing configuration data must not have trailing comments.
Specify configuration data using 4 standard elements, separated with white spaces:
- SelectionCriteria
  NODE_NAME - Node name pattern or exact match (case sensitive)
  NODE_ADDRESS - IP Addresses pattern or exact match (case sensitive)
- SrvType
  opcctla - contacting the agent
  opcmsgrd - contacting the management server (message interface)
  opcdistm - contacting the management server (distribution interface)
- Port - Port number to contact this RPC server
- Node - Node name or address pattern for this rule

An example of the server port specification file on the management server is shown below:

`#`
`# SelectionCriteria`	`SrvType`	`Port`	`Node`
`# ------------------`	`-----------`	`-------`	`----`
`NODE_NAME`	`opcctla`	`12345`	`‹*›.hp.com`
`NODE_ADDRESS`	`opcctla`	`12346`	`15.136.‹*›`
`NODE_ADDRESS`	`opcctla`	`12347`	`^192.‹1 -lt ‹#› -lt 10›.‹*›`
`NODE_ADDRESS`	`opcctla`	`12347`	`<>1.2.3.4<> for conditions in templates; ^1.2.3.4$ to configure 1.2.3.4.`

NOTE:
If the caret (^) is used as the first character in a pattern, only expressions discovered at the beginning of lines are matched. For example, "^ab" matches the string "ab" in the line "abcde", but not in the line "xacde".

If the dollar sign is used as the last character of a pattern, only expressions at the end of lines are matched. For example, "de$" matches "de" in the line "abcde", but not in the line "abcdex".

File Modification Test

The RPC client checks the server port specification file. It re-loads it if it has been changed, indicated by a different size or modification time, before opening a connection to an RPC server.

Name/Address Conversion

It is possible to specify either node name patterns or IP address patterns in the port specification file. Internally, the RPC clients typically use the IP address of the destination server as node identification. So the client will try to find a match to the internally used IP address in the port specification file. If the file contains name patterns, then first a name resolution has to be done for the internally used IP address (using gethostbyaddr) and then the returned list of node names and aliases will be compared with the name pattern of the port specification file. Therefore it is favorable to specify IP address patterns in the server port specification file to avoid executing the resolution step. Entries in the port specification file will never be resolved because they are always considered as patterns and are not necessarily complete hostnames or IP addresses.

File protection

It is recommended that the port specification file is protected by applying the appropriate operating system access restrictions. The file will only be read by the HP Operations services and processes and the most restrictive permission settings would be the following:

UNIX

If, for example, the HP Operations agent on UNIX runs as user root, the most restrictive permission setting would be:

-r-------- 1 root sys ‹file›

In the case that the HP Operations agent is not run under the user root, the file owner should be appropriately set for that user.

Windows

Allow Read for the SYSTEM account (or the HP-ITO-Account in case the Windows agent runs as HP-ITO-Account) as shown below:

Click to zoom in/out

The location of the file can be defined as needed, but it is recommended to put it into a static HP Operations configuration directory and give the file an appropriately descriptive name.

Related Topics: