Name Change on 3300 Clustered Controller 1

[kwbMitel]

Does anyone know of a "Safe" way to change the name on a clustered controller quick and easy?

My experiences on the subject required me to remove all teh Tel-Dir and Remote Dir entries first and I do not consider this either easy or safe.

Thoughts? Suggestions?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[MitelInMyBlood]

Judas Priest! You like living dangerously, huh? This one scares me and I'm fearless. Make darn sure you've got a backup.

I think I'd first try taking the element out of the distribution group and take your beating there while a zillion pending changes occur and propagate. There's no magic bullet here. It's got to say adios to OPS and the other nodes have to know it went away.

When the dust settles, pull the network cable off of it and delete the element out of OPS and Emgr.

Rename the system as needed. May have to reboot it like we had to do when replacing an MC3E in the 2K.

Plug the network cable back in then add it back into Emgr/Ops like a brand new element.

There's two pretty good documents that may be of some help here, system administrator's guides, one for OPS, one for Emgr. I don't deal well with PDFs, I like a hard copy. If you've got a semi-fast duplex printer, both docs are worth the paper.

I do wish you well.

Take good notes. This would make a good FAQ.

 

[kwbMitel]

I'm kinda partial to deleting the Delta's and not letting them propagate and manually configure each system. I didn't think there was an easier way but I had to ask.

In my naive days I let my customer name the 4 controllers in the cluster. I expected Site1 Site2 etc but what I got was Shrek, Fiona, Donkey and Dragon. The support team for the customer has changed and they don't like the names.

You should have seen their faces when I suggested Puss for the next controller. Well worth the admission fee.

Oh well, hike up my britches and get to work I guess.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Lundah]

Wow. It's really not that difficult. If you're running Enterprise Manager and using auto-discovery, all you have to do is change the system name in the Network Element Assignment form on the 3300 in question. Enterprise Manager will pick up the name change at the next re-discovery interval, and update the EMan AND OpsMan database for you. I've done this myself, works fine.

But, as always when working with stuff like this, make sure you have database backups BEFORE making the change in case it all goes south on you.

 

[kwbMitel]

Actually, when you try to change the name in the network Element assignment form for the remote system the local system says that it can't because "References exist in the Remote Directory form"

If you delete the references in the RemDir the TelDir entries are also deleted. This creates delta's and before you know it things are way out of control.

My Plan will be as follows:

Backup all Systems
Export Tel Dir and Rem Dir on all systems
Turn off OPS Synchronization after synch'ing
Del TELDIR and REMDIR on all systems
Delete Delta's
Change names
Import (restore) TelDIR and RemDir
Delete Delta's
Re-Discover using Eman
Re-sync EMan to OPS

Spend next ???? fixing everything that went wrong.


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Lundah]

Gotcha. My situation was different, we're using SDS, so when you change the system name at the local element, SDS pushes the change out to the rest of the Cluster members.

 

[kwbMitel]

Eureka!

This site predates SDS (Originally 3.3) and I've been planning on enabling SDS but as you can imagine it will take some work.

However, based on what you're saying I should be able to configure SDS to only sync the Cluster Elements for now and it will take care of the renaming.

Sounds too good to be true. Mitel Magic


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Lundah]

SDS *MUST* synch 4 forms (NE Assignment, Cluster Element Assignment, Page Group Assignment, and something else which escapes me at the moment, check the docs). Everything else is either optional or unsharable. Very handy for larger clusters, or clusters that have lots of changes to the members.

 

[kwbMitel]

Will do, I will update with my results.

Definitely Star material if it works.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

Sorry, too good to be true strikes again.

Same warning/error "CEID index being changed is uded in Remote Directory Assignment Form.

I believe this is due to my resilient phones.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[paterson]

Is it possible to remove the resiliency of those phones first, then do as described by Lundah?



_______________________________________________________

What if I don't want to put a signature on my posts?

 

[kwbMitel]

I can't remove resiliency as there is too much for it to be worthwhile but there is more to this story.

As I mentioned before, the system returns an error when the name change is attempted. It returns you to the Save or Cancel option. Pressing save again results in the same error. Pressing cancel returns you to the network elements screen. At this point everything looks as it was. Refresh the screen and low and behold, the Name has been changed!

I've checked the other systems and the name change has propogated via SDS.

I had to wait a bit for Eman to auto-discover the name change. In the mean time, I changed the name again. Now Eman is showing the correct name but OPS is showing the Test Name but not the original name.

99% of the way there, enough to give Lundah a Star.

Thanks


*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.