Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SDS sync problem

Status
Not open for further replies.

Jakt99

Technical User
Dec 19, 2009
236
AU
I know I have screwed up somewhere.....The story goes:

Have two operational Cxi II recently connected togather thru IP WAN. Before activating SDS on systems, both running MCD 4.2 (upgraded from MCD 4.0, in RDN mode or non ops mgr working).

When private WAN install was completed, I initially set up IP trunking between two sites to provide call connectivity. That part is all sweat can call between sites.

Next step clustering and sds for directory dialling and sharing telephone directory only (Site configs are varsty different to bother cleaning up and sharing other forms. Thus have:

Enabled SDS sharing in sys option form
IN SDS form sharing: everything turned off, except for telephone directory.

Next set up cluster
Cluster name: acme

Site A name: HQ (Parent office)
IP address 10.0.0.1 / 24
pbx / ICP 11
CEID 861
Feat DN 799
extn range 300-399

Site B name: Remote office
IP address 10.0.1.1 / 24
pbx / ICP 12
CEID 863
Feat DN 798
extn range 500-599

Systems are both member of acme

Next performed data sharing from HQ system, all good there.

Next performed sync from HQ with remote site, and prompted with usual window for data migration or data repair and forms to select to sync (Ticked telephone directory) and started sync.

An error occurred with with sync, and reviewing logs at remote sight indicated "unknown user ID" (CEID missing perhaps??) for each telephone directory entry attemptimg to sync. Other log messages for SYNC'd forms for pickup groups etc logs were successful, even though none set up and either site.

SDS update all shows failure as well.

Yet if I add a new extension on either site, the telephone directory and remote DNs forms update respectivity. So systems are sharing. The existing database phones wont merge with a sync. Any ideas?

 
were these systems clustered before?
Did you use the migration precheck before upgading to GDM?
Have either system got another CEID present e.g. 862?
Check in both the network element form and the cluster element form



Share what you know - Learn what you don't
 
Supernova99

THanks for reponse, to answer your questions

- Clustered before hand = No ( I created from scratch )
- Migration precheck performed = Yes ( I performed before upgrading sites to MCD 4.2)
- Existance of another CEID 862 in either controller = No




 
It does not sound as if your cluster programming is complete.

Have you completed the CEID digits refernces for both systems on each system.

i.e. does system 1 have an entry for system 2.

Additionally, your ICP numbering is odd (11 and 12) the cluster numbers must match. Cluster member 11 would be ICP 11 for example.

**********************************************
What's most important is that you realise ... There is no spoon.
 
LoL....I had exactly the same thing last week. After speaking to Mitel Tech Support it became clear that I had gotten a bit giddy on the Sync. You need to make sure after you have started sharing that the first 'sync' you do, you only sync the 'hosted services' & 'User' catagories. once this was completed, I then synced the tel dir, then everything else and hey presto :)
 
KwbMitel

CEID referenced? If I understand you correctly, then yes, both controllers are referenced in each other in respective network element forms and ARS.


Bobcheese
Hmmm.........Interesting........Basically Mitel support stating a two step sync process from the master controller.....

I'll give it a go
 
I wrote down this walkthrough, maybe it can be useful.

To start SDS on an existing cluster or to add a new 3300 to a synchronized cluster:

1-adjust date and time
2-prepare the ARS for the CEID digits
3-SDS-Start Sharing
4-Name the Network Elements
5-Start sharing again (at the cluster level)
6-Sync user and sevice hosting (at this point just sync with data migration not anything else might work)
7-Sync Telephone Directory (if you had previous Telephone directory assignment)

To migrate from ops to sds

1)one last sync with ops
2)start sharing again at the cluster level
3)sync user profiles
4)migration precheck command in maintenance
5)deprogram any scheduled directory synchronization
6)migrate
 
Thanks Bobcheese and CharlesBr

You suggested steps sync-ing user and service hosting 1st, then tel dir, worked a treat. Wont forget that one in a hurry.

 
no problems glad to be some help. Its definately something you only get wrong once
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top