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

Common Configuration

# P0602477 Ver: 3.1.11 Page 189

If an elemental comparison finds inconsistencies between the MAC and target

MMF files, the MMF file is considered inconsistent and the errors are logged

to the update results log file. This 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 MPS 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 of the element(s) that have been

selected for updates. The file also contains information on modifications made to the

MMF file. This log file is generated by the remote (target) node: each target node and

MPS with an active MMF file has its own corresponding log file. The file is appended

to and never overwritten, but is automatically renamed as *.bak (backup) when it

reaches its predetermined size of 100K, and a new file created.

Upon completion of the zap process, all synchronized MMF files contain identical

elements and data, even though the elements may be stored at different positions

within the files. This result is known as logical equivalence. The synchronization

status log file contains the state of the synchronization process for each target node.

The file naming convention exists as

zap.status.refnode.mmf_name.selected_elemets.MMDDCCYY,

where refnode is the name of the reference node, mmf_name indicates the base

name of the reference MMF file, selected_elements is the name or EAP

number of the element(s) that have been selected for updates, and MMDDCCYY the date

the file was generated. A new file is created daily for each unique MMF file and

selected elements synchronized during the day, leaving the status of all prior days

intact.

The zap.debug.log file contains a history of each instance of ZAP processing

initiated from the node. This file is most often used by Avaya to troubleshoot

unexpected results that may occur, and can be used for informational purposes by

customers as well. The file is appended to and never overwritten, but is automatically

renamed as *.bak (backup) when it reaches its predetermined size of 1 MB, and a

new file created.

If a ZAP process is terminated during execution by pressing C

TRL-C or issuing a

kill <PID> command, ZAP attempts to update the applicable log files and delete

any temporary files that may have been created during processing. If ZAP is

terminated with the kill -9 <PID> command (highly discouraged), these

temporary files are not removed. If, after terminating an instance of ZAP, future

attempts at using the utility fail, all files named /tmp/zap.* must be removed

from the local and all remote nodes (this most often occurs when using the kill -9

command, and is one of the reasons it is highly discouraged).

1 2 ... 184 185 186 187 188 189 190 191 192 193 194 ... 305 306

Sin comentarios

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