If you cannot log into the EPM web interface remotely, the primary EPM server may have lost its network connection or Tomcat may not be running.
To investigate this, you need to check the physical network connection and test the communication between the primary EPM server and the MPP servers. This procedure assumes that:
Your Avaya Experience Portal deployment consists of the EPM and MPP software running on two or more dedicated servers.
ICMP is not disabled on your system and you can ping one server from another.
Proposed Solution
Procedure
Log into Linux on another server in the Experience Portal network and enter the ping epm_identifier command, where epm_identifier is the hostname or IP address for the primary EPM server.
If the ping is unsuccessful:
Go to the physical primary EPM server and make sure that the network cable is properly connected.
Enter the ping command again.
If the primary EPM server responds to the ping command, log into Linux on the primary EPM server as any user.
Enter the ping mpp_identifier command, where mpp_identifier is the hostname or IP address for one of the MPP servers.
If the ping command is unsuccessful, repeat the ping command specifying another MPP in the Experience Portal system until you receive a successful ping message or you have tried contacting all available MPP servers..
If any MPP servers on the system respond to the ping command, then the network is functioning and the issue could be caused by problems with Tomcat on the primary EPM server. Follow the procedures in Troubleshooting vpms service issues.
If you cannot ping any MPP servers from the primary EPM server, restart the network connection for the primary EPM server. If there is:
More than one network connection, enter the /sbin/service network restart command.
A single network connection, enter the commands:
ifconfig ethxx down
ifconfig ethxx up
Where xx is the name of the ethernet connection that you are restarting. The default for an Avaya-provided server is eth0.
