Verifying communication between the upgraded Experience Portal servers

Last Updated : Jun 05, 2026 |

If EPM is running on a dedicated server, ensure that EPM can still communicate with all MPP servers, PBXs, and application servers using their IP addresses. Optionally, verify that the EPM can communicate with the servers using their host names.

Procedure

  1. Log on to Linux on the Experience Portal Primary EPM server.
  2. Verify the Primary EPM server's IP address and host name:
    1. Enter the hostname -i command.

      This command must return the server’s IP address and not 127.0.0.1. If this check fails, you must manually map the host names. For more information about the Prerequisite Checker failure with UnknownHostException:localhost, see Implementing Avaya Experience Portal on multiple servers.

    2. Enter the hostname -s command.

      This command must return the server’s host name and not localhost. If this check fails, you must manually map the host names to connect the Primary EPM with other servers. For more information, see Implementing Avaya Experience Portal on multiple servers.

  3. Verify that the Primary EPM server can communicate with all MPP servers:
    1. Enter the ping -c 4 <mpp_hostname> command, where:

      <mpp_hostname> is the hostname of the MPP server you are testing.

    2. Wait for the system to respond with the ping details.
    3. If this check fails, you must manually map the hostnames to connect the Primary EPM with other servers. For more information, see Implementing Avaya Experience Portal on multiple servers.
    4. If your Experience Portal system contains more than one MPP server, repeat this step for each MPP server.
  4. If you have an Auxiliary EPM server, verify that the Primary EPM server can communicate with the Auxiliary EPM server:
    1. Enter the ping -c 4 <auxiliary_vpms_hostname> command, where:

      <auxiliary_vpms_hostname> is the hostname of the Auxiliary EPM server.

    2. Wait for the system to respond with the ping details.
    3. If the check fails, enter the ping -c 4 <Auxiliary_vpms_ipaddress> command, where:

      <Auxiliary_vpms_ipaddress> is the IP address of the Auxiliary EPM server.

    4. Wait for the system to respond with the ping details.
    5. If both the checks fail, you must manually map the host names.
  5. Verify that the Primary EPM server can communicate with the external servers by host name or IP address:
    1. Enter the ping -c 4 <server_hostname> command, where:

      <server_hostname> is the hostname of the one of the following external components attached to your Experience Portal system:

      • A PBX server.

      • An application server.

      • A speech server.

      • Communication Manager.

      • Avaya SIP Enablement Services.

    2. Wait for the system to respond with the ping details.
    3. If this check fails, enter the ping -c 4 <server_ipaddress> command, where:

      <server_ipaddress> is the IP address of the server whose hostname you specified in the previous ping command.

    4. Wait for the system to respond with the ping details.
    5. If either of these checks fail, you must manually map the hostnames to connect the Primary EPM server with the servers. For more information, see Implementing Avaya Experience Portal on multiple servers.
    6. Repeat this procedure for each external server in your Experience Portal system.