Survivability Overview

Last Updated : Feb 27, 2025 |

The Survivable remote server (formerly called Local Survivable Processor [LSP]) and the Survivable core server (formerly called Enterprise Survivable Server [ESS]) are survivable options available with Avaya Aura® Communication Manager.

  • Survivable Remote Server: When communication to the Primary Controller (main server) is lost, the survivable remote server option allows the IP telephones and one or more gateways to register with a Survivable remote server. if the Local Survivable Server (LSP) is selected on the Server Role page of System Management Interface (SMI), the survivable remote server takes control of gateways that has its address in the Media Gateway Controller (MGC) list. You must manually administer the MGC list. The IP telephones use an Alternate Gateway List (AGL) for gateway addresses. These addresses are automatically generated by Communication Manager and sent to the IP telephones upon registration. To understand the difference between a Survivable remote server and a Survivable core server see Processor Ethernet overview.

  • Survivable Core Server: When communication to the Primary Controller (main server) is lost, the survivable core server option allows the IP telephones and one or more gateways to register with a Survivable core server. If the Enterprise survivable server (ESS) is selected on the Server Role page of System Management Interface (SMI), the survivable core server takes control of gateways that has its address in the MGC list. You can manually administer the MGC list. The IP telephones use an Alternate Gateway List (AGL) for gateway addresses. These addresses are automatically generated by Communication Manager and sent to the IP telephones upon registration. The Survivable core server option provides survivability to an Avaya configuration by allowing survivable servers to be placed in various locations in the customer’s network.

    An ESS activates when the main Communication Manager encounters an error. The ESS functions as a backup for the main Communication Manager. To configure the Survivable License Grace Period (in days) field, the administrator navigates to the Survivable Processor screen on the main Communication Manager server and enters the preferred grace period. The valid values for this field are 30, 60, 90, and 180 days, and the default value is 30 days.

For more information about the supported servers and supported gateways, see Avaya Aura® Communication Manager Hardware Description and Reference.