[ST OMU] Management Server Node becomes Other(non-ip) node
Suddenly Operations Manager for Unix (OMU) Management Server node becomes Other (non-ip) type.
So all tool/applications which are initiated from Java GUI are failing.
When trying to delete the node from node bank and trying to add this node again using command prompt
the following warning is shown:
#abc:root> opcnode -add_node node_name='abc.mycompany.net' node_label='abc.mycompany.net' net_type=NETWORK_IP mach_type=MACH_BBC_LX26RPM_X64 node_type=CONTROLLED ip_addr='220.127.116.11' group_name=gn1
Warning: Mismatch between node name and IP address (according to the DNS)Please check to which IP address the hostname is resolved and if that IP is resolved back to the original hostname.
This happens only for the Management Server node and the behavior does not happen for other nodes.
This may happen in an environment, where Windows nodes are preinstalled with an agent and registered to the OMU Server at
a later point in time.
This will result in the "Add Node" screen with the Label and Hostanme field filled with the short hostname.
Then a Warning message will pop up:
Warning when creating Node: Mismatch between node name and IP address (according to the DNS)
Please check to which IP address the hostname is resolved and if that IP is resolved back to the original hostname.
The reason for this behaviour is that the name resolution does not work for the short hostname.
The /etc/host file should always match what is returned from DNS IP FQDN alias(shortname).
When adding a node it is always recommended to use the FQDN and not the shortname.
The node can be added when in the "Add node" screen the Hostname field is filled with the fully qualified Domain name (FQDN) of the managed node.
This is documented in the following KCS article: http://support.openview.hp.com/selfsolve/document/KM00774404
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you liked it I would appreciate KUDOs.