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

Avaya Media Processing Server Series System Reference Manual

Page 188 # P0602477 Ver: 3.1.11

where <mmf_name> is the base name of the MMF file that was to be updated,

<target_node.mps#> identifies the node (as listed in the vpshosts file of the

node on which the MMF file update is attempted) and MPS number on which the

synchronization attempt took place, and <status> is the end result in accordance

with those listed previously.

If the.mps# portion of the alarm text is omitted, the status message refers to all

selected MPS’ on the target node.

For example, a successful synchronization of the MMF file named test_mmf on

MPS number 238 located on the node identified as is29538 appears in the

Alarm Viewer as follows:

Fri Oct 16 15:14:13 <consoled> 02040 Severity 1

ZAP: Sync of [test_mmf] on [is29538.238] has

completed with status

[Completed].

Log Files

Several log files are generated during ZAP execution. These log files are stored in the

$MPSHOME/common/log directory of the reference node, and can be viewed using

any ASCII text editor. Administration of all ZAP log files (i.e. when the files should

be removed) is left to the discretion of the user. The files are generated on an

individual basis or can be combined (see Consolidation of Log Files on page 190).

After synchronization retries are exhausted, an error message is displayed on the

console and entered into the synchronization distribution log file. This log file is

generated by the node originating the synchronization request with the name

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 of the element(s) that have been

selected for updates, and MMDDCCYY indicates the date the file was generated. In

addition to errors encountered during the synchronization process, this file contains

information regarding the distribution and completion status for all MMF file

synchronization requests. It also contains information on which nodes were not

notified of the updates and the reason thereof. If a zap.network.cfg file were

present but incorrectly formatted and thus not usable, this error is entered into the log

file as well. This file is appended to and never overwritten. A new file is created on a

daily basis for each unique MMF file and selected elements that are synchronized

during the day, and all log files for previous days are left intact.

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

selected_elements portion of the log file name appears as ALL_ELEMENTS.

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

Sin comentarios

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