Survivable core server error log entries and recommended actions

Last Updated : Sep 08, 2023 |
Survivable Core Server error log entries
Error type
Aux data
Associated test
Alarm level
On or Off board
Recommended action
1
None
MAJ
OFF
Survivable Core Server controlling Port Network or Port Networks: Resolve any server and network problems. Schedule or initiate an on-demand switchback of Port Networks to the Main server.
257
None
MIN
OFF
Survivable Core Server is not registered: Resolve any server and network problems.
513
None
MIN
OFF
Connection not established between Survivable Core Server and PROCR: Resolve any Survivable Core Server and network problems. Use the PING command to verify connectivity to PROCR.
769
None
MIN
OFF
This alarm is raised when a main server has administration for a duplicated Survivable Core Server that is missing the Server A IP address.
To retire the alarm, use the change survivable-processor command
to administer the Server A IP address for each Duplicated Survivable Core Server.
Notes:
Note:
  1. Error type 1: This error only applies to a Survivable Core Server.
    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 Survivable Core Server configuration. Note any network fragmentation or server outages for Main or Survivable Core Server.
    2. Using either Avaya Fault and Performance Management or SAT sessions to each server, determine the extent of any server or network outages.
    3. Resolve any server outages. If possible, bring the Main server Main servers back online first.
    4. Resolve network fragmentation and outage issues per local practice.
  2. Error type 257: This error applies to a Main or Survivable Core Server. This error is generated when a Survivable Core Server is translated on the Main but is NOT registered with the Main.
    For detailed information on maintenance commands, see Maintenance Commands for Avaya Aura® Communication Manager, Branch Gateways and Servers.
    For detailed information on administration commands, see Avaya Aura® Communication Manager Survivable Options.
    Follow these steps to investigate and attempt to retire the alarm:
    On the Main server:
    1. Enter display survivable-processor to verify that the Survivable Core Server is administered. A Survivable Core Server must be administered on the Main server before it can register with the Main server. Record these values for troubleshooting the Survivable Core Server.
    2. Use the display events command with a category of denial to display denial events related to Survivable Core Server. The Survivable Core Server registration denial events are in the 36xx range. See Survivable Core Server Denial Events in Avaya Aura® Communication Manager Denial Events for descriptions of individual Survivable Core Server denial events.
    3. Use the list trace ras ip-address command to monitor registration requests from the Survivable Core Server. This command displays registration requests from the Survivable Core Server and the associated response from the Main server. Note that under normal operation a Keep-Alive (KA) message is periodically sent from the Survivable Core Server to the Main server. This should not be confused with a registration failure.
    4. Firewalls or other security measures may prevent the Main server and Survivable Core Server from communicating. Verify that these ports are open through the network between the Main server and the Survivable Core Server:
      • 1719 Registration between the Survivable Core Server and the Main.
      • 21874 Filesync (rsync) between the Main server and Survivable Core Server.
    On the Survivable Core Server that is not registered:
    Caution:
    In the next steps, be careful to use the Close Window button to cancel out of the Configure Server page to avoid a reboot of the Survivable Core Server. Do not Update the system.
    1. Use the bash ping nnn.nnn.nnn.nnn command to verify connectivity between the Survivable Core Server and Main servers, where nnn.nnn.nnn.nnn is the IP address of the PROCR in the Main server that the Survivable Core Server is trying to register with. To determine which IP address the Survivable Core Server is attempting to register with, enter the Configure Server command from the Maintenance Web Interface on the Survivable Core Server to display the configure ESS screen.
    2. Firewalls or other security measures may prevent the Main server and Survivable Core Server from communicating. Verify that these ports are open through the network between the Main and the Survivable Core Server:
      • 1719 Registration between the Survivable Core Server and the Main server.
      • 21874 Filesync (rsync) between the Main server and Survivable Core Server.
    3. On the Maintenance Web Interface Configure Server pages:
      • On the Set Identities page, verify that the correct Server ID (SVID) is entered. This should be a unique value for each server. The SVID must be between 1 and 99. Gaps in the SVIDs for a configuration are allowed (10, 20, 30,...) but the servers may be consecutively numbered if desired. Each server in the system, duplex or simplex, Main or Survivable Core Server, requires a unique SVID.
      • On the Configure ESS page, verify that the correct platform type is selected and the correct PROCR and Main server IP addresses are entered. The Survivable Core Server will use these addresses to establish a connection with the Main server and register. On the Main server, enter display survivable-processor to verify that the Survivable Core Server is administered. A Survivable Core Server must be administered on the Main server before it can register with the Main server. Record these values for troubleshooting the Survivable Core Server.
      • On the Status Summary page, verify that the Cluster ID is correct. Verify that the individual server IDs are correct.
        Note:
        Note: The individual server IDs should be the same as those entered on the Set Identities page of the Configure Server procedure.
    4. On the SAT, enter display system-parameters customer-options.
      • Verify that the ESS Administration field is set to
      • Verify that the Enterprise Survivable Server field is set to
        Tip:
        Customer options may only be set with the Communication Manager license file. If the fields above are incorrect, obtain a new license file with corrected data.
    5. From the Maintenance Web Interface, click on the License File command. Verify that the license mode is
  3. Error type 513: This error only applies to a Survivable Core Server. A socket connection cannot be established between the Survivable Core Server and a PROCR.
    1. From the Maintenance Web Interface pages of the Survivable Core Server that is not connecting, initiate a ping to the administered PROCRs to verify connectivity between the Survivable Core Server and PROCRs.
    2. Firewalls or other security measures may prevent the server and PROCR from communicating. Verify that these ports are open through the network between the server and the PROCR.
  4. Error type 769: If the main Survivable Core Server detects a Survivable Core Server administration for a duplicated Survivable Core Server which is missing the server A IP address, an alarm is raised. In a translation upgrade, as the Main Survivable Core Server detects Survivable Core Server administration for a duplicated Survivable Core Server, an alarm is always raised after the upgrade to a Survivable Core Server system that has duplex ESS. Demand test descriptions and error codes
There are no demand tests for the Survivable Core Server maintenance object. The following table contains the explanation of the error codes from Tests 1605, 1606, and 1607 on the TEST RESULTS screen which is displayed from the following commands:
  • enable ess
  • disable ess
Error code
Description
1991
Requested Survivable Core Server cluster is not administered.
1992
Requested Survivable Core Server cluster is not registered.
1994
A Survivable Core Server cluster may not enable or disable other clusters for Survivable Core Server or main. It can only change its own enable or disable state.
1995
Survivable Core Server cluster is disabled.
1996
Port network does not exist.
2500
Internal operation failed
See also: