Changing the IP address and FQDN on the primary System Manager server when the secondary is nonoperational

Last Updated : Mar 04, 2014 |

Procedure

Disable the Geographic Redundancy replication if not already disabled.
On the primary System Manager server, change the IP address or FQDN or both. For instructions, see Changing the IP address and FQDN in System Manager.

Wait for about 30–40 minutes before you perform the next step.
Log on to the web console of the primary System Manager server, and verify that System Manager is up and running.
Bring the secondary System Manager server to operation.
Log in to the CLI of the secondary System Manager server with administrator privilege CLI user credentials and perform one of the following:
- If you changed both the IP address and FQDN, type the following:
  
  #sh $MGMT_HOME/utils/ipfqdnchange/pairIpFqdnChange.sh -OLDIP <Old IP of the primary server> -NEWIP <New IP of the primary server> -OLDFQDN <Old FQDN of the primary server> -NEWFQDN <New FQDN of the primary server>
- If you changed the IP address, type the following:
  
  #sh $MGMT_HOME/utils/ipfqdnchange/pairIpFqdnChange.sh -OLDIP <Old IP of the primary server> -NEWIP <New IP of the primary server>
- If you changed FQDN, type the following:
  
  #sh $MGMT_HOME/utils/ipfqdnchange/pairIpFqdnChange.sh -OLDFQDN <Old FQDN of the primary server> -NEWFQDN <New FQDN of the primary server>
On the secondary System Manager server, verify that the Geographic Redundancy page displays the new IP address or FQDN of the primary System Manager server.
Enable the Geographic Redundancy replication.

Send Feedback