IP Address or hostname changed - what is needed to do on FMS? On the FglAM clients? (4228980)

ON THE FMS side:

If the IP Address changes, on a non HA FMS there are no further steps on the FMS side for it to continue to run (if the IP Address was being used to connect into the Admin Console, don't forget to point the browser to the new IP Address to open up the Admin Console).

An HA FMS  the IP address change may need to be reflected in the $FMS_HOME/server/default/deploy/cluster-service.xml file on both that FMS and the other FMS in the HA environment (NOTE: the changes require a FMS restart)

NOTE: The filename has changed in Foglight 5.9.1 to $FMS_HOME/config/jgroups-config.xml

If the hostname of the FMS changes, a new license for the may be requested for the FMS by emailing license@quest.com 

(Note: Please check hosts=   entry in the license file. If the value is unlimited then no new license file is needed)

Instructions for importing the new license into the FMS will come from our licensing department along with the new license.

ON THE CLIENT side:

When the FglAM client was installed, the installation asks  to point at the hostname of the FMS or the ip address. Depending on what was chosen:

-if the FMS' IP Address is configured, and the FMS IP Address has changed, update this information in the appropriate client configuration file.

- If the FglAM client points to the FMS' hostname, andn the FMS' hostname has changed, update this information in the client configuration file. The file and location to update is the same for IP Address change or Hostname change. Below displays the appropriate file:


FglAM client:
FglAM_Home/state/default/config/fglam.config.xml

Make the change to the server_name_or_ip_address, in BOTH http and https locations (even if if not currently using https - this is still needed), save the file, restart FglAM.

(notice also the 'port' number - this is where the client side pointer to the port number is changed if set to other than default or changed on FMS)

SQL PI:

For SQL PI is necessary to review the DBSS-SPI and SPIRepository agents. By doing a review of the _001.log in both agents, the "Known host names" and "The best host name" properties should show if the configuration was made with hostname or Ip Address.

In addition, the following properties needs to be reviewed:

- spirpHost

- repository.storage.host

- parpHost

The above properties should have the same value as the "Know host names".

Lastly, the port connectivity needs to be tested (connectivity to port 5029 where the SQL PI repository resides).

Move a FMS:
SOL56684

Foglight External Backend Database move:
If moving a FMS external backend database, combine this solution also with the changes needed in SOL42249