IBM Support

Effect of changing the IP address or Hostname of a server where ITM Components are installed

Technote (FAQ)


Question

What changes should be implemented on the server where IBM Tivoli monitoring components (TEMS, TEPS or agents) are installed and the IP address or hostname is changed ?

Answer

Follow the below steps if the ip address or hostname of the server changed where ITM components are active and running.
.
if the server has HUB TEMS installed and active:

a. The HUB TEMS must be reconfigured to use the new ip address

b. if this HUB TEMS is a standby TEMS, then the ACTIVE HUB TEMS must be configured to change the backup/standby TEMS ip address

c. All the Remote TEMS pointing to this HUB TEMS must be reconfigured to reflect the new ip address

d. All the agents reporting directly to this HUB TEMS must be reconfigured to reflect the new ip address including warehouse proxy and Summarization and Pruning agents

e. If your site is using firewall and Network address translation, you must reconfigure the TEMS to take care of the network address translation using implementation with partition file or correct the HUB TEMS address manually in the partition.txt file

More information about implementation with partition file, refer to the Administrator guide

If the HUB TEMS is configured to handle SOAP request, the soap server must be configured to handle new ip address or the kshxhubs file must be updated manually with the new HUB TEMS ip address.

For more information, refer to the URL below for errors received during the tacmd logon process:

http://www-01.ibm.com/support/docview.wss?uid=swg21405770

g. if you have TEC or Omnibus installed and support event synchronization for sending synchronization events to the monitoring server, the product must be reconfigured to reflect the new IP address of the HUB monitoring server

h. if the TEMS is connected via KDE_GATEWAY, make sure that the gateway configuration file is updated with proper TEMS address.

Note: On UNIX/Linux environment, if the hostname is changed, you must reinstall the HUB TEMS since, one of the install directory path has hard coded hostname.
Also, it is not recommended to move the TEMS from one server to another similar server due the hard coded hostname in the path and the hard coded soft links created in /opt/IBM/ITM directory during installation

if the server has Remote TEMS installed and active:

a. The Remote TEMS must be reconfigured to the new ip address

b. All the agents pointing to this Remote TEMS must be reconfigured to reflect the new ip address

c. If your site is using firewall and Network address translation, you must reconfigure the TEMS to take care of the network address translation using implementation with partition file or correct the HUB TEMS address manually in the partition.txt file

More information about implementation with partition file, refer to the Administrator guide

d. if the remote TEMS is connected via KDE_GATEWAY, make sure that the gateway configuration file is updated with proper TEMS address


Note: On UNIX/Linux environment, if the hostname is changed, you must reinstall the Remote TEMS since, the install directory has hard coded hostname.
Also, it is not recommended to move the TEMS from one server to another similar server due the hard coded hostname in the path and the hard coded soft links created in /opt/IBM/ITM directory during installation

if the server has TEPS installed and active:

a. Reconfigure the TEPS to use the new ip address or the hostname

b. Follow the below technote to change the DB2 configuration if the DB2 database is in the TEPS server

http://www-01.ibm.com/support/docview.wss?uid=swg21258834

c. Make sure that, the correct ip address or hostname is reflected on serverindex.xml file. This file is located on the below directory.


For Windows:
%candlehome%\CNPSJ\profiles\ITMProfile\config\cells\ITMCell\nodes\ITMNode.

For UNIX or Linux systems:

$candlehome/$BArch/iw/profiles/ITMProfile/config/cells/ITMCell/nodes/ITMNode.

Where

$candlehome is the ITM installation directory

$BArch is the platform


if the server has Agent installed and active:

a. Nothing needs to be done, if the agent pointing to the correct HUB TEMS or Remote TEMS or configure the agents to point to the correct HUB TEMS or Remote TEMS

b. if the agent is acting as a gateway proxy, the kde_gateway (The configuration variable KDE_GATEWAY is point to the XML configuration file name) configuration XML file must be updated with the correct ip address or hostname

For all the above steps, the corresponding components must be recycled.

Document information

More support for: IBM Tivoli Monitoring V6
ITM Tivoli Enterprise Mgmt Server V6

Software version: All Versions

Operating system(s): AIX, Linux, Windows

Software edition: All Editions

Reference #: 1405807

Modified date: 01 November 2010