Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario descargar pdf (Pagina 177)

Common Configuration

# P0602477 Ver: 3.1.11 Page 177

Synchronizing MMF Files Across Nodes

Presently available on Solaris platforms only.

In instances where many nodes utilize the same MMF files, and changes to these files

would mean putting an undo burden on network facilities, management, and customer

use, the Z

ero Administration for Prompts (ZAP) utility is used to automate the

process.

This automated MMF file synchronization facility provides a means of administering

updates to and maintaining consistency between all activated instances of an MMF

file which reside on different nodes on a network. It determines if a set of MMFs

contain identical elements and provides the capability to rectify any differences

between files. In addition, reports illustrating the differences between the source and

target MMF files and the results of modifications made to the target MMF files are

generated.

By definition, the ZAP facility requires a master MMF file be designated as the

reference file. This file can exist on any node in the network. All additions, deletions,

and modifications must be made to this designated file only, preferably through the

use of PeriStudio (see the PeriStudio User’s Guide and the Avaya Media Processing

Server Series System Operator’s Guide for further information).

ZAP requires the presence of the /etc/vpsrc.sh file on every node that is

synchronized. This file is usually present as part of the standard MPS installation.

ZAP and MMF files on the MPS

In an MPS system, when ZAP updates any MMF file, it is required that there exists a

copy of that MMF file for each component in the system. It is recommended that a

directory be created for each of the MPS components on the MMF partition and all the

files, that ZAP operates on, be duplicated under these directories. Make sure that the

/opt/vps/mpsN/etc/vmm-mmf.cfg files on the system are updated to reflect

the change in the file locations.

For example:

On an MPS 500 (with components mps1 and mps2), the MMF “myPrompts” needs

to be updated periodically by ZAP. Hence, the following directories must be created:

/mmf/mps1

/mmf/mps2

The MMF “myPrompts” must be copied into each of these directories. The files

$MPSHOME/mpsN/etc/vmm-mmf.cfg must have the following line added:

mmfload /mmf/mpsN/myPrompts

1 2 ... 172 173 174 175 176 177 178 179 180 181 182 ... 305 306

Sin comentarios

Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 177