Server Alarms - Avaya Support

Table 200: ESS Error Log Entries 2 of 2
ESS (Enterprise Survivable Server)
Notes:
a. Error Type 1: This error only applies to an ESS. An ESS server has become the master of
an IPSI Port Network.
Investigate and attempt to retire the alarm with the following steps:
1. Avaya Fault and Performance Management can be used to obtain a network view of the
Enterprise Survivable Server configuration. Note any network fragmentation or server
outages (Main or ESS).
2. Use the SAT command status ess port-network to identify which ESS Cluster IDs
each Port Network (IPSI) is connected to. This command may be executed on either a
Main server or ESS. With a fragmented network, it may be necessary to execute this
command on each server in the system configuration to acquire a complete view of IPSI
connectivity.
3. Using either Avaya Fault and Performance Management or SAT sessions to each server,
determine the extent of any server or network outages.
4. Resolve any server outages. If possible, bring the Main server(s) back online first.
Note: Bringing
Error
Type
Aux
Data
Associated Test Alarm
Level
On/Off
Board
Recommended Action
513 (c) None MIN OFF Connection not established between
ESS server and IPSI. Resolve any
ESS server and/or network problems.
Use the PING command to verify
connectivity to IPSI circuit packs.
2 of 2
Note:
a Main server back online will not cause Port Networks to immediately
switch back to it. Restoring Port Network control to a Main server in a stable
network requires proactive interaction. See step 7 below.
5. Resolve network fragmentation and outage issues per local practice.
6. Use either Avaya Fault and Performance Management or the SAT commands
status ess port-network and status ess clusters to verify that all servers
and network resources are operational.
Communication Manager Release 5.0 Issue 4 January 2008 785