Enabling And Disabling Sls; Using The Cli To Manually Configure Sls Administration On The Gateway; Prerequisites; Planning And Preparing The Sls Data Set - Avaya G250 Administration

Configuring Standard Local Survivability (SLS)

Enabling and disabling SLS

To enable SLS on the G250/G350, type the set survivable-call-engine enable
command. The G250/G350 responds with "Survivable Call Engine is enabled."
To disable SLS on the G250/G350, type the set survivable-call-engine disable
command. The G250/G350 responds with "Survivable Call Engine is disabled."
Using the CLI to manually configure SLS administration on the
gateway
It is recommended to use PIM to configure the SLS data. However, if PIM is unavailable, you
can also configure the SLS data from the G250/G350 itself.

Prerequisites

Communication Manager Release 3.0 or later running on the host server
●
PIM or configuration of the G250/G350 through its CLI
●
Registration of the G250/G350 with Avaya Communication Manager
●
SLS enabled on the G250/G350 through its CLI
●
S8300 is not serving as an LSP
●
G250/G350 is not subtending to another external server (including ESS or another LSP in
●
another gateway)

Planning and preparing the SLS data set

It is recommended to plan the SLS coverage and gather information from Avaya
Communication Manager before creating the SLS administration data set at the gateway
command line. Strategic selection of the stations and trunks that participate in SLS can ensure
that vital communications are spared interruptions caused by network outages.
126 Administration for the Avaya G250 and Avaya G350 Media Gateways