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

The IP address on the Foglight Management Server (FMS) is changing, or the hostname of the FMS may change in the future.

What needs to be modified in the FMS configuration wise so it will continue to run?

If there is any SQL PI repository, what needs to be modified?

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).

Note: If a bind address has been configured, this will need to be updated in [FMS_HOME]/config/server.config; for additional information refer to How to bind the FMS or FglAM to use a defined IP address? (4246515).

For an HA FMS the IP address change may need to be reflected in the following files:

• The [FMS_HOME]/config/jgroups-config.xml file for the JGroups configuration.
• The [FMS_HOME]/config/server.config file if a bind address configured.
• The [FMS_HOME]/config/restart_monitor.config file for the restart monitor configuration.

Note: For more information on the bind address and restart monitor for HA refer to Foglight HA: Best practice configuration for Foglight HA host with multiple NICs (4327155).

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 FglAM 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 and 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 configuration: [FglAM_HOME]/state/default/config/fglam.config.xml

The FglAM will need to be restarted for changes to take effect.

Notes:

• If a bind address has been configured; for additional information refer to How to bind the FMS or FglAM to use a defined IP address? (4246515).
• If additional VM parameters have been configured in [FglAM_HOME]/state/default/config/baseline.jvmargs.config they may need to be updated; for example, the ones used for On demand connections fail despite required ports being open (4312252).

SQL PI:

For SQL PI, if configured using an IP address or the hostname is changing, the SQL PI extension needs to be re-configured to update them; for more information refer to How to move the SQL Server PI repository to a different host or server (4310151).

Move a FMS:

What steps are needed when moving Foglight to a different hardware? (4310144)

Foglight External Backend Database move:

If moving a FMS external backend database, combine this solution also with the changes needed in Move Foglight external backend database to another server (Migrate Foglight | Migrate Database) (4260799)