We are going to move the FMS server to another physical location in which will adopt and new subnet which means the IP is going to change. What needs to be configure to get the system back function once the move is in place?
A new license key would be needed for the FMS since it is bound by the IP, so contactlicensing@quest.com.
On the FMS server, check the DBVARS file and if HOSTNAME, NSSHOST, and DBHOST fields use the server name for resolution then no change is required. Just make surethe FMS server nameis resolvable on both the FMSserver and clients. This would also hold trueto allthe clients for those fields in the DBVARS file pointing to the FMS server name.
But if its IP specific then a modification to the DBVARS file on the server andon each client to match the new IP on the FMS server would be required in the following fields after a Stop has been made to the client process from the Ops console on the Server or via the command line on each client host from the foglight home directory ./foglight stopfgl (solaris) foglight stopfgl(windows)
HOSTNAME=<new></new>[NEW FMS SERVER IP]
NSSHOST=<new></new>[NEW FMS SERVER IP]
DBHOST=<new></new>[NEW FMS SERVER IP]
Restart the client process (rapsd) on each client host. From the command line,
(Solaris)
FGLHOME/script
./stopfgl
./startfgl
(Windows)
FGLHOME\script
startfgl
stopfgl
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy