Avaya ESS User Manual page 178

ESS Maintenance Object
11. Use the SAT command status ess clusters to verify that a translation file has been
sent to this ESS server. The translation file is only sent after a successful registration. If a
translation file has never been sent it is an indication of either serious network
connectivity issues or Avaya Communication Manager administration and/or
configuration errors. See above.
Note:
It may take several minutes for the ESS server to register with the Main server.
Note:
c. Error Type 513: This error only applies to an ESS server.
When a socket connection can not be established between the ESS server and an IPSI, this
error is generated and logged.
Follow these steps to investigate and attempt to retire the alarm:
1. On the Maintenance Web Interface use the ipsiversion command to verify that all
IPSIs have the current hardware and firmware. See the Minimum Firmware/Hardware
Vintages document found at:
2. From the Maintenance Web Interface pages of the ESS server that is not connecting,
initiate a PING to the administered IPSIs to verify connectivity between the ESS server
and IPSIs.
3. Firewalls or other security measures may preclude the server and IPSI from
communicating. Verify that these ports are open through the network between the server
and the IPSI:
5010 IPSI / Server control channel
●
5011 IPSI / Server IPSI version channel
●
5012 IPSI / Server serial number channel
●
4. Use the SAT command status ess port-network to identify which ESS Cluster IDs
a Port Network (IPSI) is connected to. This command may be executed at either a Main
server or ESS server. With a fragmented network it may be necessary to execute this
command at each server in the system configuration to acquire a complete view of IPSI
connectivity.
Figure 56
connection established with the server.
178 Avaya Enterprise Survivable Servers (ESS) Users Guide
http://support.avaya.com .
shows an example of an IPSI (the standby IPSI in PN 2) that does not have a