Hi Wencheng,

If only the IP is changed in the appliance server and the hostname doesn't change(In case where RCM and RCE is configured via hostname and hostname resolves to the new IP address), no need to run the configure.sh script in the RCM/RCE server. It should continue to work as it is.

If both the Server IP and hostname is changed, please perform the following steps in the Setups.

Sentinel Server: 

Login as novell user

1.Run the “configure.sh” script in the sentinel server present in <sentinel_Installation_directory>/opt/novell/sentinel/setup folder.

2.Go to “package_configure” folder present in the <sentinel_Installation_directory>/opt/novell/sentinel/setup folder.

3. Run the following commands

     ./jms.sh configure

     ./db.sh configure

    ./server.sh configure

    ./webserver.sh configure

4. Then perform restart of sentinel server service

RCM/RCE:

Login as novell user

5. In the RCM/RCE machines, run the “configure.sh” script present in <Sentinel_Installation_directory>/opt/novell/sentinel/setup folder.(Make sure your new server hostname resolves to IP address)

Try running the "netstat -an | grep <portnumber>" and see whether it is connecting to sentinel server.

In case if an Elastic search cluster is present in the setup make sure you manually edit the elasticsearch.yml file to include the new server IP.

If any third-party integrations available with Sentinel server, make sure you manually edit those IPs to point it to the latest Sentinel Server IPs.