IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Make sure the Managing Server's host name gets resolved to the correct IP address

The data collector obtains the Managing Server Kernel's network address from the Managing Server. If a host name is specified for the Kernel, there is a possibility that one of the resolved IP addresses cannot reach the Managing Server from the data collector, and the connection to the data collector will fail with a Connection refused error message.

To avoid a failed connection, instead of the host name, specify a valid IP address for the Managing Server in the MS_home/bin/setenv.sh and MS_home/etc/ms.properties files. Perform the following procedure:

  1. To determine IP addresses for a given Managing Server host name, issue the following command from the data collector server: 
    nslookup MS_hostname

  2. To test basic connectivity, on the data collector server, for each IP address listed in the output from the previous step, issue the following command: 
    ping ip_address
  3. On the Managing Server server, in the MS_home/bin/setenv.sh file, set the following properties to the IP address of the Managing Server:

    • KERNEL_HOST01

    • am_socket_bindip

    • am_socket_exportip

    For example: 

    KERNEL_HOST01=9.12.20.220
am_socket_bindip=9.12.20.220
am_socket_exportip=9.12.20.220
  4. On the Managing Server server, in the MS_home/etc/ms.properties file, set the following property, as follows: 
    kernel.hosts=MSipAddressCBSPort:RFSPort:RMIPort
    For example: 
    kernel.hosts=9.12.20.220:9122:9120:9118

This solution usually works except when there is a firewall with Network Address Translation (NAT) enabled. In that case, make network changes so that all the resolved IP addresses can reach the Managing Server.


Parent topic:

Customization for the Managing Server on UNIX and Linux

+

Search Tips   |   Advanced Search