Reassigning the server IP address and host name to another server

Edit online

If you are using the server host name to connect your agents to the Cloud APM server, after the server upgrade is finished, you must reassign the IP address and host name of the V8.1.3 Cloud APM server to the upgraded V8.1.4 server. As part of this reassignment, you are also changing the host name setting in the Db2® configuration on the V8.1.4 Cloud APM server.

Before you begin

If you plan to install new agents after you reassign the IP address and host name of the server, create new configuration packages for the agent images (see step 2 in Configuring the downloaded images). Otherwise, the agents will not connect to the Cloud APM server or show in the Cloud APM console.

Procedure

Complete the following steps as the root user on the V8.1.4 upgraded Cloud APM server:

Stop all of the server components by entering the following command in the /usr/bin directory:
```
apm stop_all
```
Reassign the IP address from the V8.1.3 Cloud APM server to the V8.1.4 server:
1. To determine the IP address and the number of network adapters on the 8.1.3 server, run the following command from this server:
```
ip addr
```
2. To determine the IP address and the number of network adapters on the new upgraded V8.1.4 server, run the following command from this server:
```
ip addr
```
3. If there is only one network adapter on the V8.1.3 server, enter the following command to shut down this server system and free up the IP address for reuse:
```
shutdown -P now
```
  If there are multiple network adapters on the V8.1.3 server, enter the following command to shut down the network adapter that is configured with the IP address on the server and free up the IP address for reuse:
```
ip link set dev ADAPTER down
```
  where ADAPTER is the adapter name from sub step 2.a.
4. Enter the following commands on the V8.1.4 server to reassign the V8.1.3 IP address to the V8.1.4 server. This V8.1.3 IP address becomes the IP address for the V8.1.4 server:
```
TEMP=/tmp/adapter.$$ 
sed 's/IPADDR=.*$/IPADDR='"IP"'/' /etc/sysconfig/network-scripts/ifcfg-ADAPTER >$TEMP
```
  where IP is the V8.1.3 server IP address, and ADAPTER is the adapter name from the sub step 2.b.
  Enter the following command to complete the reassignment:
```
cp $TEMP /etc/sysconfig/network-scripts/ifcfg-ADAPTER
```
  Enter this command to restart the network adapter:
```
/etc/init.d/network restart
```
The V8.1.4 network adapter is now using the V8.1.3 IP address as its IP address.
Change the IP address and host name of the server that is used to start the Cloud APM console. This is the address that users enter to start the console from their web browsers, for example: https://myserver:9443 or http://myserver:8080. Change to the install_dir/ccm directory and run the following command:
```
configure_server_address.sh
```
When prompted, enter the new server host name and IP address.
Update the server agent file names. The server agents include the Synthetic Events agent, the Transaction Events agent, and optionally, the Bluemix® Integration agent. Change to the install_dir/serveragents/bin directory and run the following command:
```
update_config_files.sh
```
Change the Cloud APM server references on the Db2 server to the new IP address and host name:
1. On the V8.1.4 Cloud APM server, update the DB2SYSTEM registry variable to match the V8.1.3 Cloud APM server host name:
```
source /home/db2apm/sqllib/db2profile
db2set -g DB2SYSTEM=host_name
```
  where host_name is the host name of the V8.1.3 server.
2. If your Db2 database is on a local system, modify the host name on the V8.1.4 Cloud APM server by editing the /home/db2apm/sqllib/db2nodes.cfg file and replacing the V8.1.4 host name with the V8.1.3 server host name.
3. If your Db2 database is on a local system, update the Db2 administrator's configuration file by entering the following commands:
```
su - db2apm -c 'db2 update admin cfg using DB2SYSTEM host_name'
su - db2apm -c 'db2 update admin cfg using SMTP_SERVER host_name'
```
  where host_name is the host name of the V8.1.3 server.
Restart the server components by entering the following command in the /usr/bin directory:
```
apm start_all
```
Override the host name of the Cloud APM server in the Central Configuration Services component.
1. If you are not already logged in to the Cloud APM console, log in now.
  (See Starting the Cloud APM console.)
2. Click System Configuration > Advanced Configuration and click Agent Central Configuration.
3. In the Host Name Override field, enter the new IP address or fully qualified host name of the Cloud APM server.
After you click Save, the new host name is updated in the Central Configuration Services component.
On the systems where your agents are installed, connect the agents to the new server IP address and host name.
See Configuring agents to connect to a different server or to use HTTPS communication.
If you have reports packages for the Response Time Monitoring Agent and the WebSphere® Applications agent installed, you must reinstall the reports packages for both agents.
For more information, see Installing reports. Restart the Tivoli Common Reporting server, complete the steps in the sub topics under Restarting Jazz for Service Management application servers.

Results

The V8.1.4 Cloud APM server becomes the new active server.