This will have an impact on Spectrum. Although Spectrum is not bound to the IP Address, it does rely heavily on the Hostname and name resolution of all other Spectrum servers in the environment. This is true for a single stand-alone system, or a complex distributed deployment of CA SPECTRUM.
IP Address Changes:
After you have changed the IP of your SpectroSERVER or OneClick web server, make sure the SpectroSERVER(s) and the OneClick web server(s) can all ping each other by IP.
Likewise, make sure all machines that run Spectrum applications and/or integrations can ping the SpectroSERVER(s) and OneClick server(s) by IP, and vice-versa (make sure the servers can ping the machines running the apps). It might help to add the IPs and hostnames to the /etc/hosts files on all SpectroSERVERs and OneClick web servers. In Windows, the hosts file is in Windows\System32\drivers\etc. Edits to hosts files take effect immediately. Sometimes it takes DNS servers a while to catch up, and less frequently firewall ACLs need to get updated to let traffic through. In the latter case, the pings might succeed, while a firewall might block TCP. If that's the case, just have the ACLs edited to replace the old IPs with the new ones. See the Distributed SpectroSERVER Administrator Guide for details of the ports Spectrum uses.
Your managed devices will need to have the new SpectroSERVER IPs in their trap server lists, and if it's practical, you could remove the old IPs from those lists. You could accomplish this for the devices supported by the Network Configuration Manager (NCM), via an upload task. See the Network Configuration Manager User Guide for information on upload tasks.
After you change the IP on a SpectroSERVER machine, you need to save, initialize and load the database to stamp it with the new IP.
With few exceptions, Spectrum servers communicate via SSAPI and Corba. Both of these only use hostnames (not IP addresses).
The following is a list of files, that must be updated to use the new hostname.
On a SpectroSERVER:
On a OneClick Web Server:
Note: that if the hostname of the Main Location Server (MLS) is changed, then all SpectroSERVERs and OneClick servers in the distributed environment must be updated.
The link below is contains a script that can be used to make the needed changes to all of the above files. It can be run on a SpectroSERVER or a OneClick web server. If you are running the script from a Windows Server, you will need to execute the script from a 'bash -login' shell. CA does not support the script.
To run the script:
NOTE: In some instances with Windows systems running the OneClick web server, after the changes and service restarts are completed, connection errors are observed when the OCE server attempts to connect with the SpectroSERVER(s). A full reboot of the Windows OneClick web server should be run to see if it resolves the communications problems.
- Stop the SpectroSERVER and processd.
- Change the hostname on the server.
- Reboot the Server.
- Stop processd (go to /lib/SDPM and execute processd --stop, or you can stop the Spectrum processd service in Windows services)
- From a bash shell, execute the Change_Spectrum_Hostname.pl script as the Spectrum initial owner.
- Start processd
- Restart the SpectroSERVER and/or Tomact on the OneClick web server.