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

Avaya Media Processing Server Series System Reference Manual

Page 178 # P0602477 Ver: 3.1.11

Ensure that any previous references to the MMF in vmm-mmf.cfg file are removed.

MMF Abbreviated Content (MAC) File

For any form of synchronization, an MMF Abbreviated Content (MAC) file

is created from the designated master file and placed into the

$MPSHOME/common/zap/distribution directory of the reference node and

$MPSHOME/common/zap directory of the target node(s). By default this file uses

the base name of the reference MMF file that is specified. The -m <mac_name>

option allows a pre-existing MAC file to be specified during an update (where

mac_name indicates the path and name of the file).

The MAC file is compressed to reduce the time and load the transfer places on the

network. It uses attributes and a 32-bit Cyclic Redundancy Checking (CRC) value

for each element in the reference MMF file to compare it to the target MMF file.

This 32-bit CRC value represents the elemental data without having to actually store

the data in the MAC file. Thus, the MAC file is much smaller in size than its MMF file

counterpart.

The MAC file is decompressed when verification commences. The verification

process compares each element in the target MMF file against its counterpart in the

MAC file, and consists of a comparison of each element’s attributes followed by its

32-bit CRC value. If either of the comparisons is found to be inconsistent, the element

is flagged as requiring an update: after all comparisons are completed, these elements

are downloaded from the source and updated on the target. Conversely, the target

MMF file is also checked for elements that were not found in the MAC. In this case,

the extraneous elements are deleted from the target file.

If multiple element names exist with the same encoding, ZAP only uses the first

element with the duplicated name and encoding from the source MMF file to update

the target MMF file. This is due to the fact that VMM only uses the first item in the

source MMF file with a particular name and encoding as a reference; therefore, only

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

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

however, none of the remaining duplicate elements is updated. A warning is placed

into the update results log file indicating that multiple elements with the same

encoding are present in the MMF file (see Log Files on page 188).

If duplicate element names with different encodings exist in an MMF file, only one

copy of an element is added to the target MMF, and this element is the one in the

source that has the highest EAP number. The condition caused by duplicate element

names can be eliminated by assigning unique names to all elements within an MMF

file.

The following paragraphs offer suggestions for running ZAP, though the modes are

not mutually exclusive (that is, either form can be used in either instance).

Basic Implementation (Low Volume/Traffic)

In environments where network traffic saturation is not a concern or there are few

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

Comentarios a estos manuales

Sin comentarios

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

Comentarios a estos manuales

Relacionado con productos y manuales para Barebones Pc / Estación De Trabajo Avaya Media Processing Server Series System (Software Release 2.1)