Verifying communication between the MPP servers and all other servers

About this task

All planned Experience Portal servers must be able to communicate with each other using either:

A Domain Name Server (DNS) to translate hostnames to their corresponding IP addresses
The /etc/hosts file to map the IP addresses and hostnames

	Important:
	If the servers cannot communicate with one another, you will encounter installation errors and be forced to rerun the installation.

In addition, the servers must also be able to communicate with all external servers such as the PBX, application servers, speech servers, and the Communication Manager.

Procedure

Log on to Linux on the Experience Portal MPP server.
Verify that the MPP server can communicate with the EPM server by hostname or IP address:
1. Enter the ping -c 4 <epm_hostname> command, where:
  
  <epm_hostname> is the hostname of the EPM server.
2. Wait for the system to respond with the contact information.
3. If this check fails, enter the ping -c 4 <epm_ipaddress> command, where:
  
  <epm_ipaddress> is the IP address of the EPM server.
4. Wait for the system to respond with the contact information.
5. If both of these checks fail, you need to manually map the hostnames as described in Manually mapping hostnames to connect the primary EPM with other servers.
6. If your Experience Portal system contains an auxiliary EPM server, repeat this step for the auxiliary EPM server.
Verify that the MPP server can communicate with the external servers by hostname 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 Aura® Session Manager.
2. Wait for the system to respond with the contact information.
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 contact information.
5. If both of these checks fail, you need to manually map the hostnames as described in Manually mapping hostnames to connect the primary EPM with other servers.
6. Repeat this procedure for each external server in your Experience Portal system.
If you have additional MPP servers in your Experience Portal system, repeat this procedure for each MPP server.