Upgrade Enterprise 6.2/OPS 9.2 for the support of GDM clusters only 1

[Layne5]

Hi,

we're going to upgrade a cluster from MCD 4.0 to MCD 4.1.
We're trying to upgrade the ENT/OPS too but with no luck.
1/Upgrading ENT succeeds with no errors, but when launching it, we get "could not create table ALERTUSERPROPS" and "wrapper stopped" in the event viewer.

2/Inspite this error i tried to proceed with the OPS upgrade, but then i also get issues.
I made sure there were no outstanding pending changes, deleted all scheduled Telephone Directory activities, ... as in the docs, BUT when i want to delete Location and Distribution Lists, or Portable directory groups, i get "you cannot delete a PDG with resilient users programmed" or "the current entry is being referenced by another application, please remove all references to this entry".

Does this mean i have to delete all users from the "Telephone directory-Editor"???

Thanks

 

[nytalkin]

OPS MGR is not supported in 4.1 ENT MGR has some support for several ENT MGR features. You need to refer to the 4.1 RN.

NO GOOD DEED GOES UNPUNISHED!

 

[nytalkin]

Remote Directory Number (RDN) Synchronization is now the only method to distribute telephone directory entries among the element databases in a network or cluster. The OPS Manager application may still be used, but only to monitor alarms and perform backups and restores. Full OPS Manager functionality is restricted to elements that have pre-MCD Release 4.1 software and have not yet migrated to RDN Synchronization.



NO GOOD DEED GOES UNPUNISHED!

 

[Layne5]

Hi, I was aware of the restrictions, the OPS would only be used to perform backups. Therefor i used the SW "EM 6.2/OPS 9.2 for the support of GDM clusters only".
But still i get these errormessage(s). Anyone already did an upgrade from a "normal" EM/OPS to an "EM 6.2/OPS 9.2 for the support of GDM clusters only"?

 

[Supernova99]

It is not worth upgrading Ops/Ent Man
It is too much work to clear out the old directory and settings

My advice is to start again you can restore Entman from the backup then sysnc the elements to Opsman and then setup your backups

Ever since 4.1 I have done it this way and beleive me it is much quicker than trying to reove the cluster settings.
Even your archived backups become useless once going to GDM.

Perform Entman Backup
Copy Entman Backup to desktop or somewhere easy to find
Take a few screenshots of any schedules you are using
uninstall Opsmanger
delete the Mitel directories
clear the hardware ID on AMC
re-install Entman
Restore Entman from backup
Install OpsMan
Sync EntMan to OpsMan
Restore schedules

Share what you know - Learn what you don't

 

[Layne5]

Hi!

Thanks for your answer!
Indeed it's a lot of work to clear out the old directory and settings...

Thanks, i will folow your procedure!

Best regards,

Jean-Marc