Identify Cluster Issues after IP/Hostname change

From DocWiki

Revision as of 15:57, 14 September 2011 by Cchetty (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Identify Cluster Issues after IP/Hostname change

Problem Summary Identify Cluster Issues after IP/Hostname change
Error Message N/A
Possible Cause N/A
Recommended Action

Using CET tool check whether nodeconfig object and DB component config have been updated or not.

For following things a remote user will be needed to login to the server.

1. /opt/cisco/uccx/ClusterData/profile.ini on both nodes should be updated with new IP in case of IP Address change.

2. If it's a HA setup then /opt/cisco/uccx/conf/intraclustercomm.ips should be updated with new IP on other node in case of IP Address change.

3. /usr/local/cm/db/informix/etc/sqlhosts.uccx should be updated with new information.

4. In /opt/cisco/uccx/desktop/conf/sitesetup/prefs.cfg, LDAP Host 1, LDAP Host 2, and/or IOR HOSTNAME should have been updated with new IP in case of IP address change.

5. In /usr/local/thirdparty/jakarta-tomcat/webapps/TUP/CAD/Maintenance/TUP.ini, LDAP Server A and/or LDAP Server B should have been updated with new IP in case of IP address change.

Release Release 8.0(1)
Associated CDETS #

Rating: 0.0/5 (0 votes cast)

Personal tools