None
Prior to migrating an existing cluster to support Remote Directory Number Synchronization, all directory entries must be listed in either the Telephone Directory form or in the Local-only Directory Number List form of the master element (the master element is the cluster element that you use to initiate the migration). This command identifies the following directory number inconsistencies in the system database so you can resolve them prior to performing the migration:
Directory numbers that have no Telephone Directory entry and are not listed in the Local-only Directory Number List form
Directory numbers that have a Telephone Directory entry and are also listed in the Local-only Directory Number List form.
Refer to Mitel Knowledge Base article 09-3070-00008, "Migrating to RDN Synchronization via SDS," on Mitel Online for instructions on how to migrate a network to RDN synchronization.
If a directory entry is configured in the Local-only Directory Number List form and the same number is also configured in the Telephone Directory form, the system data will conflict. If you perform a migration without first resolving the conflict, the migration process creates the entry as a local-only directory number and a an error log is generated to notify you of this issue.
If a directory entry exists in the system database, but is not listed in either the Telephone Directory form or the Local-only Directory Number List form and you proceed with the migration, the telephone directory information for the entry will be lost.
The output of the command is saved in a .csv file that you can download to your PC hard drive and then import into the Local-only Directory Number List form.
System Response:
Command Started Successfully
Checking for readiness to migrate
...processed 100 entries.
...processed 200 entries.
...processed 300 entries.
...processed 400 entries.
MIGRATION PRECHECK
DN 2932 has no Teldir entry and is not resilient or a remote number.
DN 2933 has no Teldir entry and is not resilient or a remote number.
DN 2934 has no Teldir entry and is not resilient or a remote number.
DN 2935 has no Teldir entry and is not resilient or a remote number.
DN 2936 has no Teldir entry and is not resilient or a remote number.
DN 2937 has no Teldir entry and is not resilient or a remote number.
DN 2938 has no Teldir entry and is not resilient or a remote number.
DN 2939 has no Teldir entry and is not resilient or a remote number.
DN 2940 has no Teldir entry and is not resilient or a remote number.
DN 3333 has no Teldir entry and is not resilient or a remote number.
DN 3334 has no Teldir entry and is not resilient or a remote number.
Before migrating your network, you must either create a Teldir entry for the DNs in the above list, or else add the DN to the Local-only Directory Number List form.
Checking for possible inconsistency.
DN 2002 has a Teldir entry and appears in the Local-only Directory Number List.
WARNING: Before migration, for the above entries: you should either clear their appearance in the Local-only Directory Number List, or else remove their Teldir entry and/or RDN entry. Migrating in an inconsistent state will cause loss of Teldir information for these records.
Output saved at http://<IP_address>/GDMMigratePrecheckOutput.csv
Command completed.
