
Avaya Media Processing Server Series System Reference Manual
Page 194 # P0602477 Ver: 3.1.11
Troubleshooting
The information below describes how the ZAP and VMM (Voice Memory Manager)
software manage synchronization events when various types of errors and exceptions
occur.
For a procedural narrative concerning zap, see the Avaya Media Processing Server
Series System Operator’s Guide.
Problem Description
Cannot connect to VMM. If the VMM process is not running on the remote node, the
synchronization attempt is abandoned and rescheduled
for a later time.
Multiple threads of VMM have
an activated version of this
MMF file.
If multiple threads of VMM have their own copies of the
MMF file open with write permission, both instances
perform online updates.
Cannot delete an element. The failure is indicated in the update-results log file, and
the next element is processed.
Cannot update an element. The failure is indicated in the update-results log file, and
the next element is processed. All elements that cannot
be verified are updated from the reference MMF file.
Remote node is down. The MAC file is not copied to the remote node. An error
message is generated to the console, and the failure is
recorded in the synchronization-distribution log file. The
update is also rescheduled for a later time, and fails
altogether after the configured number of retry attempts.
(See -r <retries> on page 192.)
Network connection
interruption.
If the network connection goes down between the
reference and remote nodes during the transfer of any file
(MAC file, log file, etc.), the file is retransmitted once the
connection is re-established. If the connection is down for
an extended time (such that the transfer times out), the
synchronization process is rescheduled for a later time.
Remote system goes down
while processing updates.
The synchronization process is rescheduled for a later
time. The elements that have already been processed for
updating are not updated again at that time.
Reference node goes down
while creating MAC file.
The synchronization process is aborted. The process
must be manually restarted at a later time.
Reference node goes down
while distributing MAC file.
The distribution attempt is restarted automatically at a
later time, after the system comes back up.
Insufficient disk space on the
remote system to store update
package.
The MAC file is not copied to the remote node and
appropriate error messages are generated to the console
and log files. The synchronization is rescheduled for a
later time, and fails altogether after the configured number
of retry attempts. (See -r <retries> on page 192.)
Insufficient space on the
reference system to create
update package.
The MAC file is not created, and appropriate error
messages are generated to the console and log files. The
synchronization process is aborted and must be manually
restarted at a later time.
Comentarios a estos manuales