Changing IP on network element part of MCD 4.2 cluster with SDS 1

[ExCentigram]

We're moving a 3300 controller today....I know. I never get any notice. And my boss got the bright idea to change the IP address as well. So my question is - how do I do this as far as the cluster is concerned?
When we had 9.0 and opsman it was a horror show but now with MCD 4.2 it seems quite easy. Is it as easy as re-IPing the controller via bootChange and getting that all online then going in to the network elements form and it should just magically send the change to all the other elements?

 

[ExCentigram]

forget it, figured it out.

 

[mitelmitel]

Share your findings!

 

[kwbMitel]

You must reset all systems before full functionality will be restored after changing the IP of any that are sharing data.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Supernova99]

If you have a 5550 console you will need to do a 2nd reboot as well

Share what you know - Learn what you don't

 

[kwbMitel]

@ Supernova - Can you elaborate on 2nd reboot required if 5550 deployed?

**********************************************
What's most important is that you realise ... There is no spoon.

 

[Supernova99]

yes without rebooting the second time the console tries to reconnect to it's original IP address.
If you have ever noticed when it is connecting to the 3300 it (especially on a large cluster) it will scroll though each IP address in the cluster and then stores a list of these in a config file.
The console is looking at the ICP/PBX form to get this info, unfortunately it does not do this correctly after the first reboot after an IP address change.
Consequently the 3300 needs another reboot to make sure the ICP IP address is published correctly to the 5550.

Share what you know - Learn what you don't

 

[ExCentigram]

I used the console/serial cable to go in to the vxworks shell and stopped the boot - not to be attempted by the uninformed....
And then typed bootChange and changed the IP address. After the boot up I went in to ESM and changed the DHCP options and the NEID form

And to my great joy, because we've recently upgraded to MCD 4.2 and using SDS things were quite simple after that. Checked the NEID form, xnet PBX form and CEID form on cluster elements. The only one I had to change was the xnet PBX form with the new IP of the remote 3300. It was a beautiful thing