Cadet 1st Class
Cadet 1st Class
240 views

OM Agent HealthView in a NAT environment

Has anyone used OM agent HealthView in a NAT environment.

From what I can see the regular heart beats arrive OK but none of the links to agent info (like resource usage and process ID info) work correctly as the HealthView website attempts to use a local IP address to contact the OM agent, rather than the NAT IP address.

This looks to be the case even if the OPC_IP_ADDRESS variable is set on the OM agent. 

 

 

Labels (1)
0 Likes
2 Replies
Fleet Admiral Fleet Admiral
Fleet Admiral

Where is HV installed? On the Omi Server itself or one a seperate one?

How does the OMi Server conect to the nodes? Do you use host file to resolve the nat adresses?

 

0 Likes
Cadet 1st Class
Cadet 1st Class

The HealthView server is installed on a separate server. I didn't think it was supported on the OBM server, as I tried it and it caused problems. The documentation was very vague. 

The hostname resolution is done via DNS, OBM to OM agent and HV to OM agent communication works OK in all other areas (bbcutil -ping hostname.com). The OM agent node is loaded into monitored nodes in the CMDB with the NAT address. 

When debugging the HV, the periodic health checks include the non-NAT IP address and hostname. So it seems that HV is ignorant of NAT. 

e.g. 

/var/opt/OV/shared/server/hpcsrv/hpcsrv.conf

[hpcs.trace]
Debug_Level=ALL

tail -f /var/opt/OV/shared/server/hpcsrv/hpcsrvtrace.log

4: DBG: Tue May 7 10:03:55 2019: (20991): POST Data received for HPCS Server:{
"hpcsversion": "12.06.007",
"RegistrationInfo": [
{
"Method": "UP",
"MACAddress": "12:12:12:12:12",
"HostName": "hostname.com",
"IPAddress": "10.10.10.10",
"HBPInterval(s)": "300",
"Protocol": "https",
"Port": "383",
"MetColInterval(ms)": "10000",
"UUID": "12345678-1234-1234-1234-123412341234",
"Version": "12.06.007",
"HealthStatus": "0",
"HealthInfo": " Normal",
"IsVM": "1",
"AgentLastStartTime": "Mon May 06 16:48:12 2019",
"OS": "NT"
}
]
}

The periodic health checks arrive OK, but you can never drill down on a problematic node to gather more information about a failure or display performance information. 

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.