Troubleshooting guide

Troubleshooting Guide
166
Errors show that data has been
distributed to a network element
in a way that is not consistent with
the data in the Remote Directory
Number form.
An administrator made an
incorrect entry to the Remote
Directory Number form at an
element somewhere in the
network and the change has
been propagated by SDS.
Delete the inconsistent record from the
Remote Directory Number form, and
reprogram it appropriately.
On 5235 IP Phones, some
application keys that are
programmed on the set (for
example, the History key) do not
function after the set fails over or
fails back from the resilient peer
controller.
The Multiline Set Keys form data
is shared, but the High End Set
data is not shared.
In the SDS Form Sharing form, share
both the Multiline Set Keys form data and
the High End Set data. SDS will then
share the application set key data.
Instruct the 5235 IP Phone users to
reprogram the application keys on their
sets
A 5235 IP Phone user is unable to
reprogram or clear a
programmable key.
In the Multiline Set Keys form,
the ”Line type” for the key is
stuck at “phone apt”.
In the Multiline Set Keys form change the
“line type” for the key to “Not Assigned”.
The user can then reprogram the key.
Errors show that login status for a
hot desk user has been
improperly shared between the
user's primary and secondary
ICP.
A failover occurred between the
time the user logged in from one
device and then another. For
example, an external hot desk
user logs in from their cell phone,
there's a failover, and before a
failback can occur, they log into
from their office desk phone.
Perform a sync operation from the local
element to the remote peer.
There are many SDS Data
distribution errors occurring on
the department/location forms.
Performing a Form Comparison
results in conflicts for
department/location.
A change to the department field
is not distribute throughout the
network or cluster.
In a heavily congested clustered
hospitality deployment, if there
are a many hospitality
operations being performed at
the same time (either via PMS or
GSA or a combination of both),
then there is the possibility that
department/location operations
may result in distribution errors.
Perform an SDS synchronization of the
department/location forms. This will
update all users that reference the
department/location fields with the new
department/location strings.
When adding a new element to a
migrated network, you receive
either of the following error
messages after you initiate the
Start Sharing operation:
“Synchronization failed. You must
migrate this node to the new data
model before attempting to join
the SDS network”
“Synchronization failed. The
target for this operation must
migrate to the new model first”.
You attempted to add a
non-migrated element to the
GDM network.
Follow the procedure described in
“Adding an Element to the Migrated
Network” in the System Administration
Tool online help.
Table 56: Troubleshooting Sharing Operations
Symptom Possible Cause Corrective Action
Page 5 of 5