Avaya G430 - Page 139

3. Enter set sls enable
The Branch Gateway responds with the message Survivable Call Engine
is enabled.
Prerequisites for using the CLI to manually configure SLS administration on
the Branch Gateway
Use PIM to configure the SLS data. However, if PIM is unavailable, you can also configure the
SLS data from the Branch Gateway itself.
Note:
Do not run two SLS data update sessions concurrently. The SLS data can be administered
locally using CLI, and centrally using PIM or an SNMP MIB browser. This can cause a
situation where one administrator can unknowingly undo the work of the other. For example,
if a local administrator enters trunk-group context just before a remote administrator
performs an SNMP write operation to change a trunk-group parameter, that parameter will
be overwritten with the current CLI values when the local administrator exits the trunk-group
context.
• Communication Manager Release 4.1 is running on the host server
• PIM or configuration of the Branch Gateway through its CLI
•
The Branch Gateway is registered with Avaya Aura
®
Communication Manager
• The SLS is enabled on the Branch Gateway through its CLI
• S8300 is not serving as an Survivable Remote Server
• Branch Gateway is not subtending to another external server (including Survivable Core
Server or another Survivable Remote Server in another gateway)
SLS data set preparation
It is recommended to plan the SLS coverage and gather information from Avaya Aura
®
Communication Manager before creating the SLS administration data set at the Branch
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.
Important:
Since you can administer your system for SLS either from the SAT or from the Branch
Gateway CLI, the two administration tasks must be synchronized with common data and
port usage as well as system-defined capacities. For example, if a physical DCP station port
Standard Local Survivability (SLS)
Administering Avaya G430 Branch Gateway October 2013 139