Troubleshooting guide

Voice Networking
167
Sync Operations
Table 57: Troubleshooting Sync Operations
Symptom Possible Cause Corrective Action
The Sync operation has not
displayed any signs of progress
for more than one hour (that is the
operation appears to be hung).
Your Internet Explorer session is
timing out before the sync
operation is complete.
Install the required Internet Explorer
registry file on your PC. The registry file
extends your Internet Explorer session
and prevents it from timing out before the
Sync is complete. Refer to Mitel
Knowledge Base article 07-3829-00006
on Mitel Online for instructions.
Specified data has not been
synchronized after you complete
a Start Sharing operation.
The Start Sharing operation
does not synchronize all the
shared data across the
elements. Only data in the
Network Elements form and
Cluster Element Definition form.
It adds the element to the
sharing community (member
elements) and begins the
sharing of data at the specified
scope.
If you want to synchronize the shared
system form data across the elements,
you should compare the forms and then
perform a Sync operation. See
“Comparing Forms and Synchronizing
Data” in the System Administration Tool
online help.
Cannot sync from the local
element to a remote element.
The IP addresses assigned to
the elements in the Network
Elements form are not unique.
Ensure that each element in the Network
Elements form is assigned a different IP
address.
The system name or type for the
network element on the local and
remote nodes do not match.
Ensure that the same system name or
type is assigned to the element in the
Network Element Assignment forms of
both the local and remote element.
Synchronizations take too long. Traffic on the network is slowing
the rate of record updates.
Perform the synchronization during a
period of low network traffic (for example,
after business hours).
Large amounts of data are being
synchronized across many
elements.
Perform concurrent synchronizations to
reduce the amount of time required to
complete the synchronizations.
After a sync operation, large
numbers of data distribution
update errors appear in the SDS
Distribution Errors form.
The remote element did not get
the updates because the
network connection to that
element was down.
Fix the network issue. Retry the
distribution updates. See “Resolving
Pending Updates or Errors” in the
System Administration Tool online help.
Many data distribution update
errors appear in SDS Distribution
Errors form after a concurrent
sync operation.
During a concurrent
synchronization, both the master
and member elements reject
changes coming from other
network elements. Rejected
changes create distribution
update errors on the master
element.
See “Resolving Pending Updates or
Errors” in the System Administration Tool
online help.
Page 1 of 2