High-End Set Handset Config errors?

[acejavelin]

Doing a migration of a cluster from 9.0/OPSMAN to MCD4.0, getting things all in sync getting ready to convert to RDN and go up again... getting a weird error I can't find...

Forms Comparison:

Comparing High-End Set Handset Config between Cityhall and Policedp

Detail:
Record (DN:1405, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1424, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1594, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1860, Handset Mode:1, Left Handset Type:1) only exists on Cityhall
Record (DN:1937, Handset Mode:1, Left Handset Type:1) only exists on Cityhall

Summary:
147 records compared
147 records match
5 records only exist on Cityhall

Everything else is in sync between 11 nodes except this... This one is new to me... any ideas on how to correct this?

EDIT: All of these devices exist as primary in Policedp and resilient in Cityhall, we removed the resiliency, verified they were gone from Cityhall, then put the resiliency back in place and the problem still exists. Weird.

[ralph]

Record (DN:1405, Handset Mode:1, Left Handset Type:1) only exists on Cityhall

That does seem weird to me.
What happens if you delete one of the phones then compare again?

Ralph

[acejavelin]

Well, we removed the resiliency on these phones, then did a compare and things looked fine, redid the resiliency and the COMPARE errors are back, but no erros in sync... very strange. We are still awaiting engineering from Mitel to give us a resolution but since there are no errors in teh sync, we are going to go ahead with the DB conversion to RDN tonight at 5 and start the next round of updates to MCD 4.2. The highest we can go with the current 6510 VM that the customer has.

If the problem still exists after an upgrade (and thus reload of database) we are just supposed to delete and remove the sets completely. Tech support had no further information on what this really was, they just got that answer from engineering.

[acejavelin]

Hmmm... very odd but it seems after the upgrade of system to MCD 4.2 the errors just went away, all syncing is working and it is showing no errors at all. Perhaps it was just a minor database corruption and during the upgrade(s) it was cleaned out, hoping so anyways...

One site left to upgrade to 4.2 but can't do it until tomorrow at 7:30am, then it is just clean-up and tweak... So there is finally a light at the end of the tunnel on my most dreaded project of the last two years, which turned out to be much less problematic than I thought. 

[wiseguy]

This doesn't sound like a database corruption, but more like a missmatch. Erase resiliency for these phones and set data sharing to no in the system options.
When complete change datasharing back to yes and do a new share and sync with data repair set to enabled on the system were the phones reside.

[acejavelin]

Tried all that stuff... All sites are up to MCD 4.2 and the sync now completes with no errors, but if you do a manual form comparison it still shows the forms are different, but there is really no place to fix it.

Very odd. So far all is good though, even if the phones are forced to their resilient pair everything works as normal.

Guess that is a problem for another day, should it arise... Don't really want to keep messing with these phones, 4 of the 5 are 5235's with at least one PKM and are "main" phones for various emergency services like fire and PD.

[boycey9]

Complete guess but worth a look, The only thing left handset says to me is Turret programming.

[acejavelin]

Yeah, pretty much gave up on this... Everything works and there are no sync errors, it still shows some forms are out of sync if I do a manual compare of the two forms, but even if the phones fail over then back everything is working correctly.