Re-IP a Primary Controller

[StardataMitel]

Hi Team,
We have been tasked to relocate a MiVB system that is part of a cluster. This will involve a change of IP.
The system is configured as the primary element for all handsets with the secondary being the local controller of that handsets.
I'm strugling to find any guidlibnes on IP changes when part of a cluster.
Is anybody able to point me in the direction of doc?

Otherwise this is the rough plan if how i think it will play out. Assuming all networking is correct between sites old and new.

System 1 (Primary Controller)
System 2
System 3

- Backup all systems
- Re-IP Sys 1
- Reboot Sys 1
- Change Sys 2 Network elelement-Sys 1 IP
- Change Sys 2 IP/PBX Networking-Sys 1 IP
- Change Sys 3 Network elelement-Sys 1 IP
- Change Sys 3 IP/PBX Networking-Sys 1 IP
- When Sys 1 Recovers, Peform SDS Sync from Sys 1
- Update DHCP options to point to correct conrtoller address (If required)
- Reboot handsets at all sites

 

[Billz66]

have done this recently - was also concerned but it all worked out fine

if its in the cluster , once you change it it will advertise itself to all cluster members
so your steps are fine but you dont need some of them

Sounds like its a virtual system with single IP?

dont forget to also change any other servers if you have them

- micollab network elements / mbg blades​

- mbg-icps​

- MICC media servers​

- Backup all systems
- Re-IP Sys 1
- Reboot Sys 1
- When Sys 1 Recovers, Sync not required

- Update DHCP options to point to correct controller address (If required)


- Reboot handsets at all sites ( for dhcp change )

If I never did anything I'd never done before , I'd never do anything.....