If Notify management server if node communication address changes is selected, then no further action should be required. Check to see if the new IP address is shown in the IP address field. If not, correct the IP address.
If Domain Name(FQDN) is selected, verify that the old name resolves to the new address and leave the setting unchanged.
NOTE:
By default, after the management server resolves a node's domain
name to an IP address, it stores this IP address in its node cache
to increase performance. If Domain Name(FQDN) is selected,
but Notify management server if node communication address
changes is not selected, and you then change the node's IP
address, the management server might continue to use the old IP
address from its cache. To rebuild the management server's node
cache, restart the OvEpMessageActionServer service. (For more
details, see Optimize HPOM node name
resolution.)
Follow these steps on the managed node to change the FQDN. During this process you may see several error messages stating that the agent cannot read the encrypted policies. After you have changed the name, reinstall the agent packages on the node to resolve the problem.
HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\ITO\Hostname
If the old name of the node was specified in the Primary node name field, correct it.
If Notify management server if node communication address changes is selected, then no further action should be required. Check to see if the new node name is shown in the Domain Name(FQDN) field. If not, correct the name.
If Notify management server if node communication address changes is not selected, but Domain Name(FQDN) is selected, then you need to correct the name manually. Make sure that the new name resolves to the IP address of the node.
For more details, see Configure action-allowed and secondary managers.
Each node must be able to resolve the new management server name. For details, see the help topic Resolve the IP address of the management server.
opcagt -kill
vpstat -3 -r STOP
ovconfchg -edit
A text editor starts and displays the settings file.
HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\ManagementServer\DBAccess\OvOWInstance
HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management
Server\MsgActSrv\MGMT_SERVER
HKLM\SOFTWARE\Hewlett-Packard\OVEnterprise\Management
Server\MsgActSrv\NAMESRV_LOCAL_NAME
If the old name of the management server was specified in the Primary node name field, correct it.
Check also the Message Identification tab to see if the old name of the management server was specified there. If yes, correct it.
If Domain Name(FQDN) is selected, verify that the new name resolves to the IP address of the management server.
Optional. Change the display name of the management server on the General tab.
Open a command prompt and enter:
SetMgmtServer
The output will be similar to this:
setmgmtserver Agent package 'C:\Program Files\HP OpenView\\packages\Windows\OvEpMsgActAgt.FM' Management server name was updated from 'old_serv.rose.hp.com' to 'hpom_serv.rose.hp.com' SYSTEM account installation: enabled Authentication enforcement: disabled Forced user account switch: disabled
Each node must be able to resolve the new management server name. For details, see the help topic Resolve the IP address of the management server.
HKLM\Software\Hewlett-Packard\OVEnterprise\Management
Server\MsgActSrv\MGMT_SERVER
HKLM\Software\Hewlett-Packard\OVEnterprise\Management
Server\MsgActSrv\NAMESRV_LOCAL_NAME
HKLM\Software\Hewlett-Packard\OVEnterprise\Agent\ManagementServer
HKLM\Software\Hewlett-Packard\OpenView\Common\MgmtServerName
HKLM\Software\Hewlett-Packard\OpenView\Common\MgmtServerIP
with the virtual server IP address.SetMgmtServer.exe /servername <virtual HPOM server name>
The basic procedures to change the IP address or Fully-Qualified Domain Name (FQDN) of a management server in a flexible management environment are the same as for standalone servers. In addition, update the flexible management policies with the new IP address or FQDN of the management server and deploy them as necessary.
If Notify management server if node communication address changes is not selected in the node's properties, you must manually update the node's properties on all servers in the environment. The easiest way to achieve this is to modify the node properties on one management server, and then use the ovpmutil tool to download and upload the node information.