I have tried looking fo the guide how to de-cluster with other PBX’s offline but unable to find any.
I also tried Mitel knowledge base and no lucky.
Search for removeNE in the help manual
REMOVENE
Qualifiers:
<NETWORK ELEMENT NAME>
Purpose:
Removes the specified non-local element from the network.
The REMOVENE command does not distribute the deletions to other elements or nodes in the data-sharing network. To completely remove the element from the network, the command must be run on all the network elements. Thus, in a three-node network of MiVoice Business systems—A, B, and C—to remove node B, the command must be run on nodes A and C.
To remove an element from its Data Sharing Community only, use the REMOVESHARINGNE command.
NOTE: Removal can take a long time to complete. Do not attempt during peak busy periods.
Details:
The command supports removing all types of network elements, including an SX-2000. Deleting an SX-2000 element is the same as deleting a MiVoice Business element. For all other network element types, the command will delete the data sharing membership (if it is sharing) and hosted services (if they exist). It will not attempt to remove references to the node in other forms. You will have to locate and remove these references yourself.
The NE name must match an existing network element's name exactly, including letter case. The command entry interface rejects spaces; if the name contains spaces, you must remove them by renaming the element in the local Network Element form before issuing the command.
The removal process starts by deleting the element and all references to it from the Data Sharing Community (if applicable) and from the the database. Deletion of the references will NOT be distributed by SDS to other members of the sharing community. The process continues with the deletion of Remote Directory Number (RDN)s and Resilient DNs followed by removal of system services (ring groups, hunt groups, etc.) and user services (phone, voice mail, etc.) with the specified element as the primary host. If all RDNs and resilient DNs are successfully deleted, the specified element is purged from the Network Element form, completing the removal process.
NOTES
Except for the data-sharing membership change, data on the removed element and other nodes in its data-sharing community are otherwise unchanged. If you plan to reuse the removed element in another network, reformat the hard drive first and reinstall the MiVoice Business software. See the Technician's Handbook for more information.
When the last MiCollab server that is data-sharing with a MiVoice Business system is removed using this command, all MiCollab templates are deleted, while templates that had associated MiCollab services become editable and can be deleted from the System Administration Tool.
MiVoice Business Release 7.2 supports data sharing with only one MiCollab server.
Reasons for failed network element removal
A network element is considered removed when all references to it are deleted on the local element. Likewise with RDNs and resilient DNs. However, certain restrictions can prevent removal—for example:
the RDN is the agent skill group ID of ACD Path. The ID can't be blank so the administrator must intervene and either replace the ID or delete the path.
the network element targeted for removal is referenced in the SIP Peer Profile form. Another local form references one of the profiles. The REMOVENE command will only attempt to delete the profile (which will fail), but not the references to it in the other form. Again, the administrator must intervene to remove the reference (or delete the profile).
a resilient device has keys programmed. The command attempts to clear the keys and then tries to delete the device again but fails.
the network element is a DLM. The administrator must deactivate or reassign the DLM, then run the command again.
Each failed removal attempt generates a log along with an error summary for display in the command output window. Correct the error(s) found, and then run the command again.
Precautions
Removing a resilient element disables resiliency for all DNs that use the element as its secondary host. Any devices that are failed over to the element while the removal is in progress will lose service.
Changing device resiliency may fail if there is a hot desk user logged in. The failure generates an error in the command output window and requires that the administrator intervene by logging out the user and running the command again.
Other precautions:
do not have applications connected to element being removed.
do not have scheduled backups on elements being removed.
do not have IDS synchronizations running.
do not attempt a sync until after the command is run on all nodes in the network.
Example(s):
Entry: REMOVENE SWITCH_B
System Response with no failures:
Command Started Successfully
Deleting telephone directories...
Number of records processed: 500
Number of records processed: 1000
......
Total number of telephone directory records processed: 4153
Number of records to delete: 473
Number of records deleted successfully: 473
Searching for RDNs and resilient DNs to delete...
Number of records processed: 500
Number of records processed: 1000
......
Total number of DN Services records retrieved: 2758
Number of RDNs to delete: 468
Number of resilient DNs to delete: 10
Number of RDNs changed (blank out the secondary element): 9
Deleting RDNs...
Number of RDNs deleted: 468
Deleting resilient directory numbers primarily hosted on < NE name >...
Number of resilient DNs deleted: 10
Deleting Hosted User Services
Number of Hosted User Service records deleted: 450
Number of Hosted User Service records updated: 9
Deleting Hosted System Services
Number of Hosted System Service records deleted: 7
Number of Hosted System Service records updated: 0
Deleting SDS distribution errors to network element <NE name>...
Deleting references to network element <NE name>...
Network element <NE name> is removed successfully.
Command completed.
System Response with failures:
Command Started Successfully
Deleting telephone directories...
Total number of telephone directory records processed: 22
Number of records to delete: 13
Number of records deleted successfully: 13
Searching for RDNs and resilient DNs to delete...
Total number of DN Services records retrieved: 51
Number of RDNs to delete: 12
Number of resilient DNs to delete: 19
Number of RDNs changed (blank out the secondary element): 8
Deleting RDNs...
Failed to delete RDN: 4000 - Unable to remove reference to the number due to:
The number is programmed as the Primary Agent Skill Group ID in ACD Path form.
Failed to delete RDN: 4001 - Unable to remove reference to the number due to:
The number is programmed as the Primary Agent Skill Group ID in ACD Path form.
Number of RDNs deleted: 10
Deleting resilient directory numbers primarily hosted on <NE name >...
Failed to delete resilient DN: 8485001 - Unable to remove reference to the number due to:
At least one agent id must be programmed in an agent group.
Failed to delete resilient DN: 848503 - Unable to remove reference to the number due to:
The number is programmed as the Primary Agent Skill Group ID in ACD Path form.
Failed to delete resilient DN: 8485007 - Pickup group has only remote members.
Deleting Hosted User Services
Number of Hosted User Service records deleted: 10
Number of Hosted User Service records updated: 4
Deleting Hosted System Services
Number of Hosted System Service records deleted: 2
Number of Hosted System Service records updated: 4
Deleting SDS distribution errors to network element <NE name >...
Network element <NE name> is not removed due to reference to RDNs or resilient DNs.
Remove the references manually and then run the command again.
Command completed.
