Pim Configuration Data - Avaya G250 Administration Manual

Figure 5: Standard Local Survivability data sources and communication paths
Figure notes:
1. H.248 call signaling and configuration
data
2. CCMS messages through Clear
Channel
3. Media Gateway Maintenance Channel
4. PIM extracts Communication Manager
translation subset through OSSI
NOTE: The SLS data must be
configured manually in the gateway if
the PIM is not available.
The required Communication Manager translations for SLS include fields on the Station and
Media Gateway forms. 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 G250/G350 extracts from the
Avaya Communication Manager translations. PIM aggregates the required data and copies the
provisioning data over a secure communication path to non-volatile RAM (NVRAM) on the
G250/G350. After the initial data collection, PIM retains a copy of the data set for each
G250/G350. 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 media gateway
●
If the data set does not change, the data set in NVRAM remains unchanged
●
H.248 Control Link
1
Communication
2
Manager
4
Communication
Manager
Translations
Configuring Communication Manager for SLS
H.248 Control Channel
CCMS Channel
IP
3
MGM Channel
Provisioning and
Installation
Manager (PIM)
7
5. PIM data set and SLS MIB delivered to the
gateway through SNMP
6. Security codes (passwords) sent over
SSH connection to CLI
7. Provisioning and Installation Manager
(PIM) for remotely provisioning gateways,
network-wide. PIM is installed on an
enterprise management server, not on the
primary Communication Manager server.
Gateway
CLI
6
5
cydscomm LAO 071106
on page 147 for
Issue 5 June 2008 135