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

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 306
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 186
Common Configuration
# P0602477 Ver: 3.1.11 Page 187
Exception Processing
If a remote node fails to respond or a MAC file cannot be transferred, an attempt is
made at a later time to retransmit the file. The number of retries is preconfigured at
three, but may be specified otherwise using the -r option. The time interval between
retries is likewise preconfigured and can be changed through use of the -d option: the
default is 30 minutes, but at a minimum this interval must be set to ten minutes. It is
also possible to schedule a date and/or time for the synchronization to take place. This
is accomplished by using the -t option. These options can be used individually or in
combination.
When using ZAP with groups (see Advanced Implementation (High Volume/Traffic)
on page 181), the retry count specifies the maximum number of retry attempts made
directly by the reference node.
Inconsistencies detected during synchronization are resolved by either deleting
extraneous elements from the target MMF file and/or downloading all unreferenced
elements in the MAC file from the reference node and adding them to the target MMF.
Any errors recorded during this process are added to the update results log file. Every
individual update and delete request is processed regardless of whether or not an
unsuccessful operation has occurred during the procedure. The procedure is
performed on all target nodes independently, and can proceed simultaneously or
individually, depending on how the process was initiated (see Basic Implementation
(Low Volume/Traffic) on page 178.
The -A command line option enables ZAP to generate an alarm upon completion of
synchronization on each MPS, regardless of whether an attempt was successful or not.
This alarm contains one of the statuses found in the following table.
Each time any MPS finishes ZAP processing with a status of Completed or
NotActive, it generates an alarm message. If processing on every MPS on a node
fails or succeeds, only one alarm message is generated for the entire node. If every
node in a group experiences failed processing, one alarm message is displayed for
each node in the group.
The synchronization alarms instituted by the -A option appear in the following
format:
ZAP: Sync of [<mmf_name>] on [<target_node.mps#>]
has completed with status [<status>].
Completed Synchronization was successful
Failed Synchronization and all retry attempts were unsuccessful.
NotActive The MMF file on the particular MPS was not active and
therefore could not be synchronized.
Terminated
By User
The process was killed by the user, either by pressing C
TRL-C,
issuing a kill <PID> command, or by some other means.
Vista de pagina 186
1 2 ... 182 183 184 185 186 187 188 189 190 191 192 ... 305 306

Comentarios a estos manuales

Sin comentarios