Avaya Media Processing Server System Bedienungsanleitung PDF herunterladen (Seite 110)

Media Processing Server System Operator’s Guide

Page 110 # P0602484 Ver: 2.7

Synchronizing MMF Files Across Nodes (ZAP Utility)

In some configurations, applications across multiple nodes use the same MMF files.

The Z

ero Administration for Prompts (ZAP) utility automates the process of

administering updates to and maintaining consistency between all activated instances

of an MMF file across the network. It determines if a set of files contains identical

elements and provides the capability to synchronize the files. ZAP can modify MMF

files on all nodes list in a vpshosts file or in an alternate file; individual nodes or

Media Processing Servers; groups of Media Processing Servers; or specific elements

within an MMF file.

ZAP also generates reports illustrating the differences between the source and target

MMF files, and the results of modifications made to the target MMF files. By default

these log files are created whenever ZAP is used, and are never overwritten. While

administration of these files is left to the discretion of the user, this can eventually lead

to disk saturation if files are not off-loaded or deleted. To reduce this need for manual

intervention, use the -C option to combine these files into a corresponding

consolidated log file.

A synchronization distribution log file is generated by the node originating the

synchronization request. An update results log file is generated by remote (target)

nodes. Each of these nodes also contains a synchronization status log file. These files

are stored in the $MPSHOME/common/log directory of the reference node. The

synchronization distribution log file is named in the format

zap.distribute.refnode.mmf_name.selected_elements.MMDDCCYY

where refnode is the name of the node originating the synchronization request,

mmf_name indicates the base name of the reference MMF file,

selected_elements is the name or EAP number(s) that have been selected for

updates, and MMDDCCYY indicates the date the file was generated. This log file

contains information regarding the distribution and completion status for all MMF file

synchronization requests, information on which nodes were not notified of the updates

(and the reason thereof), and errors encountered during the synchronization process.

If all elements within an MMF have been selected for updating, the

selected_elements portion of the log file name appears as ALL_ELEMENTS.

The update results log file is named in the format

zap.results.target_node.mps#.mmf_name.selected_elements,

where target_node is the name of the remote node where the synchronization has

occurred, mps# is the number of the Media Processing Server on which the target

MMF file is located, mmf_name indicates the base name of the reference MMF file,

and selected_elements is the name or EAP number(s) that have been selected

for updates. The file contains information on modifications made to the MMF file, as

well as errors encountered due to inconsistencies between the reference and target

MMFs.

If an MMF contains multiple elements with duplicate names, ZAP uses only the first

duplicate element from the source MMF file to update the target MMF file; therefore,

only this first element needs to be updated and maintained. The element which

appears first in the target MMF file (i.e. with the lowest EAP number) is updated;

however, none of the remaining duplicated elements is. The update results log file

1 2 ... 105 106 107 108 109 110 111 112 113 114 115 ... 187 188

Kommentare zu diesen Handbüchern

Keine Kommentare

Avaya Media Processing Server System Bedienungsanleitung Seite 110

Kommentare zu diesen Handbüchern

Verwandte Produkte und Handbücher für Server Avaya Media Processing Server System