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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Correct procedure for dissolving a cluster on MCD 4.2

Status
Not open for further replies.

joebrown123

Technical User
Mar 21, 2012
26
GB
What is the correct way to dissolve a cluster of 3300's on MCD 4.2??

I can't find a procedure on MOL or any of the supporting docs.

I have a cluster of 7 3300's that all need to be standalone and setup with inter site dialing via a PNI number instead. The customer isn't bothered about sharing forms and wants to have to dial a 4 digit prefix depending on the user/site he is calling.

Do I just delete the elements from the Cluster assignment form on one system and the sharing will remove them from all the other systems therefore deleting the cluster?? Do I need to disable sharing first?? My main concerns are that the remote directory numbers don't get removed from each system.

Many Thanks
Joe
 
You would need to at least remove any resilency programming for sets or PRI's first. Otherwise you might have to follow this to remove one element at a time. Try the help files.

Knowledge Base Article
Article ID #
11-5163-00014 Article Type
How-To Guide


Article Title
How to remove a Controller from an existing Cluster Publish Date
Jan-10-2012


Description/Symptoms
How to remove A network element from a cluster


Body/Solutions
If you are going to remove a controller from a sds network you cannot just power down and remove controller.
You must leave controller running and delete all extensions and have them sync to all other controllers in network . Then delete the switch out of cluster and delete network element

Details can be found in the online 3300 help under: SDS - Removing a Data-Sharing Element


I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Thanks for the reply LoopyLou.

I have read that doc your referring to but I need to keep the systems running standalone. From what I understand I will need to delete all the users from the element, remove it from the cluster and then recreate the users.

If I remove an element from the cluster the other systems will still see the users in the remote directory form. Could I not then delete the users from the remote directory?? I know it can't be done through the standard login of ESM but with the right commands they can be deleted. Do you think this could cause any issuses with the databases???
 
I don't know the commands to remove them other then through the EMS. We had a multi-system site where one location powered down their 3300 before they demolished the building. I did not work the case but our tech had to do a lot of work with product support to clean up everthing. And that was MCD 4 where we still had access to the RDN form. Looks like a big headache. Did they say why they wanted to break the cluster?

I'd tell you a UDP joke but I'm afraid you won't get it. TCP jokes are the best because you always get them.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top