A.2 Unable to Configure RCM/RCE Using Virtual IP in HA Setup

A.2.1 Issue:

Unable to configure RCM/RCE using virtual IP. Host is not reachable by hostname.

A.2.2 Fix:

Traditional HA

Perform the following steps to connect RCM/RCE in traditional HA mode for both fresh and existing setup:

  1. Add an entry in /etc/hosts file as given below on RCM/RCE box before installing/configuring RCM/RCE.

    <virtual ip> <FQDN of first_scuccessful_activenode_host>  <first_scuccessful_activenode_hostname>

    For example: 164.99.87.27 first_active_host.dom.name first_active_host

    IMPORTANT:Make sure that always this entry matches with the proper first successful active node hostname in HA environment specified in /etc/hosts file before running configure.sh

  2. Give virtual IP at the prompt while connecting RCM/RCE to the server.

    IMPORTANT:Although first successful active node is down and the other node is currently active, still use first successful active node name with virtual IP in /etc/hosts file.

Appliance HA

Perform the following steps to connect RCM/RCE in appliance HA mode for fresh setup:

  • Use only the hostname of the first successful active node in the HA cluster.

Perform the following steps to connect RCM/RCE in appliance HA mode for existing setup:

  1. Add an entry in /etc/hosts file as given below on RCM/RCE box before installing/configuring RCM/RCE.

    <virtual ip> <FQDN of first_scuccessful_activenode_host>  <first_scuccessful_activenode_hostname>

    For example: 164.99.87.27 first_active_host.dom.name first_active_host

    IMPORTANT:Make sure that always this entry matches with the proper first successful active node hostname in HA environment specified in /etc/hosts file before running configure.sh

  2. Give virtual IP at the prompt while connecting RCM/RCE to the server.

    IMPORTANT:Although first successful active node is down and the other node is currently active, still use first successful active node name with virtual IP in /etc/hosts file.