Hostname Change

HPE recommends the following workflow:

You can use the opr-change-hostname script to update OMi, the RTSM, and the agent to be able to run after a change to the hostname and IP address of the server(s) in your OMi deployment. It can also be used to prepare the database for a disaster recovery system. If an error occurs, the script can be run again with the same parameters, after fixing the environment.

Location

<OMi_HOME>/opr/support/opr-change-hostname.[sh|bat]

Parameters

1. Enter the new load balancer hostname in the infrastructure settings for the virtual servers. To do so, select:

   Administration > Setup and Maintenance > Infrastructure Settings

   Choose Foundations, select the Platform Administration - Host Configuration table. Update the following settings:

   • Default Virtual Gateway Server for Application Users URL
   • Default Virtual Gateway Server for Data Collectors URL

2. Disable OMi on all gateway and data processing servers.

3. Change the hostname of the load balancer and reboot the system if required by the operating system. Make sure the new name and IP address are resolved correctly.

4. Only for OMi versions earlier than 10.10. Every forwarded event includes a list of servers that have a copy of this event. By default, when the event is modified on one server, it notifies all servers in the list of the change. When the hostname changes, the servers cannot be notified of the event changes anymore. You must therefore update the hostname of the load balancer in all events on all servers that have a copy of the event.

   Run the following SQL statement on the event database of the OMi server whose load balancer name was changed and of all OMi servers that have forwarded events to that server:

   UPDATE EVENT_FORWARDING_INFO SET DNSNAME='<new_host_FQDN>' WHERE DNSNAME='<old_host_FQDN>';

   UPDATE EVENT_FORWARDING_INFO SET IPADDRESS='<new_host_IP>' WHERE IPADDRESS='<old_host_IP>';

5. Enable OMi on the data processing servers first and then on all gateway servers.

6. You may need to update other HPE Software applications that integrate with OMi. For more information, see Additional Tasks: Update Integrations

1. Disable OMi on all gateway and data processing servers.

2. Change the hostname of the database server according to the instructions provided by the database vendor. Reboot the system if required by the operating system. Make sure the new name and IP address are resolved correctly.

3. Edit the OMi configuration file <OMi_HOME>/conf/topaz.config.

   Replace the old database hostname with the new database hostname in the following settings:

   ManagementDb.dbServer

   ManagementDb.dbHost

   ManagementDb.ConnectString

4. Run the configuration wizard to update OMi with the new database hostname. Run the wizard on a data processing server first, then on all other servers.

5. Enable OMi on all data processing and gateway servers.

• North-bound integrations. If the hostname of the load balancer or the gateway server (in a deployment without a load balancer) changes, you must also update the load balancer or gateway hostname in the integrating software. For example, if OMi is integrated with Service Manager, you must update the OMi gateway or load balancer hostname in the Service Manager Integration Manager.

• Operations Manager integrations. If the hostname of the load balancer or the gateway server (in a deployment without a load balancer) changes, you must update the Operations Manager (OM) integration to communicate with OMi under the new name.

  OM for UNIX or Linux:

  • Update the gateway server or load balancer name in the list of target servers to forward topology data.

    To check the current target servers, run the following command:

    ovconfget -ovrg server om.svcdiscserver ForwardingTargets

    If necessary, change the target servers and restart the service discovery server process:

    ovconfchg -ovrg server -ns om.svcdiscserver -set ForwardingTargets <new_load_balancer or gateway_name or list_of_servers>

    ovc -restart opcsvcdisc

  • Edit the forwarding policy file and update the gateway server or load balancer name. If the IP address has also changed, you must update the IP address of the gateway server or load balancer in the following file:

    /etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/msgforw

    To activate the changes, run the following commands:

    ovconfchg -edit

    ovc -restart opcforwm

  • Update the node that represents the gateway server or load balancer in the Node Bank:

    /opt/OV/contrib/OpC/opcchgaddr -sync IP <old_host_IP> <old_host_FQDN> IP <new_host_IP> <new_host_FQDN>

  • For OM for UNIX or Linux, it is not necessary to update the events in the database with the new hostname of the OMi gateway server or load balancer. OM for UNIX or Linux only stores the ID of the node representing the OMi gateway server or load balancer with the events in the database.

  OM for Windows:

  • Update the gateway server or load balancer name in the list of target servers to forward topology data:

    1. In the console tree, right-click Operations Manager, and then click Configure > Server.... The Server Configuration dialog box opens.

    2. Click Namespaces, and then click Discovery Server. A list of values appears.

    3. Update the hostname of the gateway server or load balancer in List of target servers to forward discovery data.

    4. Click OK to save your changes and close the Server Configuration dialog box.

    5. Restart the OvAutoDiscovery Server process for your changes to take effect.

  • Edit the forwarding policy and update the gateway server or load balancer name, then redeploy the policy. If the IP address has also changed, you must update the IP address of the gateway server or load balancer in the forwarding policy.

    1. In the console tree, select Policy management > Server policies grouped by type > Server-based Flexible Management.

    2. Double-click the existing policy that you want to edit. The Server-based Flexible Management Editor dialog opens.

    3. Update the gateway server or load balancer name in the MSGTARGETMANAGERS section. Update the IP address if required.

    4. Click Check Syntax to check for syntax errors in the new policy text. After correcting any syntax errors, click Save and Close.

    5. Redeploy the server-based flexible management policy on the OM for Windows management server.

  • Every forwarded event includes a list of servers that have a copy of this event. By default, when the event is modified on one server, it notifies all servers in the list of the change. When the hostname changes, the server cannot be notified of the event changes any more. You must therefore update the hostname of the gateway server or load balancer in all events on all servers that have a copy of the event.

    Run the following SQL statement on the OM for Windows database:

    update OV_MS_ServerList set ServerName='<new_host_FQDN>' where ServerName='<old_host_FQDN>'

    If the IP address of the gateway server or load balancer has changed, run the following statement:

    update OV_MS_ServerList set ServerIpAddr=0 where ServerName='<new_host_FQDN>'

  For more information on setting up an OMi-OM integration, see the Integrate section.

• Operations Agent integrations. If the hostname of the load balancer or the gateway server (in a deployment without a load balancer) changes, you must reconfigure the agents to communicate with the server under the new name. During the name change, the agents are unable to connect to the server and will buffer events. As soon as the connection is established again, the agents will start sending data to the server again.

  1. If a flexible management policy is deployed to the agent, update the gateway server or load balancer hostname in the policy and redeploy it.

  2. If the OMi server runs on a Linux operating system, make sure the PATH variable contains the correct path to the OMi command-line interfaces, type:

     export PATH=/opt/HP/BSM/opr/bin:$PATH

  3. Change the manager settings of the agent by using the opr-agt command-line interface, for example:

     opr-agt <connection> -set_config_var sec.core.auth:MANAGER=<new_host_FQDN> <targets>

     opr-agt <connection> -set_config_var sec.cm.client:CERTIFICATE_SERVER=<new_host_FQDN> <targets>

  4. Update the primary manager setting of the agent by using the opr-agt command-line interface, for example:

     opr-agt <connection> -primmgr <targets>

  See also opr-agt Command-Line Interface.

• OpsCx integrations. If the hostname of the load balancer or the gateway server (in a deployment without a load balancer) changes, you must reconnect OpsCx to OMi by using the bsmc-conf command-line interface with the ‑force option, for example:

  bsmc-conf ‑srv <new_host_FQDN> ‑force ‑admin_user <user> <password>

• SiteScope integrations. If the hostname of the load balancer or the gateway server (in a deployment without a load balancer) changes, you must reconfigure SiteScope to communicate with OMi under the new name.

  In SiteScope, navigate to Preferences > Integration Preferences. Update the following integrations:

  • BSM integration on <OMi server> (This integration represents the SiteScope connected server in OMi). Edit the integration and update the OMi server or load balancer name.

  • HP Operations Manager integration on <OMi server> (This integration represents the event integration with OMi.) Edit the integration and update the OMi server or load balancer name. Then click Connect to reconfigure the agent.

To update the IP address of the Data Flow Probe, see the RTSM - Data Flow Management section.

• TLS setup. If you run OMi in a hardened environment, you must request new server certificates from your certificate authority and install the certificates as described in Hardening Workflow. This is because the certificates are issued to the FQDN of the external access point of OMi and include that name in the certificate's SAN list.

• Reverse proxy setup. If the hostname of the load balancer or the gateway server (in a deployment without a load balancer) changes, you must also update the reverse proxy with the new name of the gateway server or load balancer.