I need to change segments for my Prime and MSE's.
I gather this is accomplished at the root kernel level?
I don't see anywhere to change the IP's from the GUI..
Solved! Go to Solution.
Current attempts to re-address Prime have been from Prime's CLI. There was some caveat that changing the Prime's IP from the Linux level brakes the Oracle DB because it is not informed of the change if done outside of Prime.
However, the next test will be to change the IP on the inside, then change the GW on the outside via Linux and lastly the hosting segment in VMw.
Almost fixed. Someone forgot to say CLI into the Console rather than ssh to the management address.
Prime is back up and hopefully happy. I don't seem to have valid credentials for the GUI anymore so I have no convenient idea what's going on.
I can still ssh cli into the management IP and observe NCS is alive and well.
I created fresh username's but they don't work on the GUI
I suspect system is trying to AAA to tacacs+ and the strange device answering up from the new IP is being rejected.
the new usernames do work on the SSH cli session.
On CPI 2, There was a command to run to change ip properties in Prime by going into root shell and running:
/opt/CSCOlumos/bin/oracleDBadmin.sh hostnameupdate x.x.x.x --> new ip
After restarting, you could check the file /opt/CSCOlumos/conf/messaging.properties and validate the old IP doesn't exists anymore.
Not done any re-ip in version 3 lately.
Please to follow all the previous guidance from the VM console and NOT the live management IP.
And then insure you have someone around who can access the TACACS+ machine to ensure that your Prime, speaking from a new IP is not rejected. I am still awaiting that someone.. So my Prime is back on its original IP.
I have moved my MSE's to their addresses and reconstructed them in Prime. Since the MSE's do not reference Tacacs+ there are no GUI issues.