How to migrate Prime 3.5 from one segment to another.

[David Ritter]

I need to move from x.x.160.x to x.x.162.x.  TAC provided the following:

https://community.cisco.com/t5/wireless-mobility-documents/steps-to-change-the-ip-address-on-a-prime-infrastructure-pi/ta-p/3163169

it does not work!!

cli in as admin

after executing NCS stop

I configure the new ip:

tcl345/admin(config-GigabitEthernet)# ip address 172.25.162.100 255.255.255.0

Changing the hostname or IP may result in undesired side effects,
such as installed application(s) being restarted.
Are you sure you want to proceed? [y/n] y

the system is GONE.  it is still pointing to the old gateway and can't be changed

i'm betting that when I answer 'y' to the question..  it switches to the new ip (running-config) but does not actually update the startup-config until after it links.. 

Since the VM assigned segment has not yet changed, it does not save the startup-config.  trying to take on the new ip on the old gw.  Fortunately I can reboot.

can I console into the VM root and re-run setup and just change the default ip gateway there without having to recreate all the rest of the entries?  and then change interface segment?

[Mark Elsen]

 - Perhaps you could change the ip parameter(s) using standard Linux shell commands (after becoming root) and then just reboot the Prime server when it is  on the new segment.

 M.