Pim Configuration Data; Sls Entry - Avaya G430 Manual

5. PIM data set and SLS MIB delivered to the Branch Gateway through SNMP
6. Security codes (passwords) sent over SSH connection to CLI
7. Provisioning and Installation Manager (PIM) for remotely provisioning Branch
Gateways, network-wide. PIM is installed on an enterprise management server, not on
the primary Communication Manager server.
NOTE: The SLS data must be configured manually in the Branch Gateway if the PIM is not
available.
The required Communication Manager translations for SLS include fields on the Station and
Branch Gateway screens. See
more information about the information types and how to administer Communication Manager
for SLS.

PIM configuration data

SLS also requires PIM configuration data, some of which the Branch Gateway extracts from
the Avaya Aura
copies the provisioning data over a secure communication path to non-volatile RAM (NVRAM)
on the Branch Gateway. After the initial data collection, PIM retains a copy of the data set for
each Branch Gateway. This set is compared with subsequent data sets to determine if anything
has changed:
• If the data set changes, the newer data set is pushed down to the Branch Gateway
• If the data set does not change, the data set in NVRAM remains unchanged
Users can schedule when to collect and push data, perform scheduled and manual backups,
and enable and disable SLS, as well as display (but not change) the data to ensure correct
information. See
If PIM is unavailable, the SLS data set can be manually configured in the Branch Gateway CLI.
For information on configuring SLS, both manually and via PIM, see
rules on page 120.

SLS entry

When SLS is enabled, the MGC list displays a fifth element called SLS. This element is always
past the Transition Point. After the Link Recovery search concludes for the primary MGC list
(entries above the Transition Point), it searches the alternate MGC list (entries below the
Transition Point), ending with SLS, the last choice for the Branch Gateway.
When the Link Recovery search settles on the SLS entry in the MGC list, the Branch Gateway
registers with SLS (resident on the Branch Gateway) for its call control.
Administering Avaya G430 Branch Gateway
Configuring Communication Manager for SLS
®
Communication Manager translations. PIM aggregates the required data and
Using PIM to manage SLS administration on the gateway
Standard Local Survivability (SLS)
on page 120 for
on page 133.
SLS configuration
October 2013 107