Recover from an Incorrect IP Address Change

Use this procedure to recover from an incorrect IPv4 IP address change that blocks access to the Operations Console on the primary instance or a replica instance.

The following procedure uses the eth0 interface as an example. You can update the eth1 interface by replacing eth0 with eth1.

Before you begin

This procedure assumes that you know how to use the vi editor.

Procedure

  1. Log on to the appliance with the user name rsaadmin and the operating system password that was specified during Quick Setup.

  2. Update the hosts file with the correct IP address:

    1. Use 'sudo vi' to open the hosts file at /etc/hosts.

    2. At local address, correct the IP address associated with the Fully-Qualified Domain Name (FQDN) of the virtual appliance.

    3. Save and close the hosts file.

  3. Update the ifcfg-eth0 file with the correct IP address:

    1. Use 'sudo vi' to open the ifcfg-eth0 file at /etc/sysconfig/network/ifcfg-eth0.

    2. Correct the IP address by changing the IP address value for IPADDR.

    3. Save and close the ifcfg-eth0 file.

  4. If you are correcting the IP address for the primary interface, such as eth0, then you must update the routes file with the correct IP address. This step is not required for a secondary interface. Do the following:

    1. Use 'sudo vi' to open the routes file at /etc/sysconfig/network/routes.

    2. Correct the IP address value for gateway IP.

    3. Save and close the routes file.

  5. Update the ifroute-eth0 file with the correct gateway IP address:

    1. Use 'sudo vi' to open the ifroute-eth0 file at /etc/sysconfig/network/ifroute-eth0.

    2. Correct the IP address value for gateway IP.

    3. Save and close the ifroute-eth0 file.

  6. Restart the network services. Type:

    sudo /sbin/service network restart

    and press ENTER.

  7. Restart RSA Authentication Manager services.

    1. Change the directory to /opt/rsa/am/server.

    2. Type:

      ./rsaserv restart all

      press ENTER and return to rsaadmin user.

After you finish

  • If you changed the IP address of the primary instance in a replicated deployment, you must log on to the replica instance Operations Console and update the primary instance hostname and IP address on the replica instance. A replica instance requires the primary instance hostname and IP address in order to communicate with the primary instance.

    For instructions, see Update the Primary Instance Hostname and IP Address on a Replica Instance.

  • Verify the changes by logging on to the Operations Console on the instance that you updated. Click Deployment Configuration > Instances > Status Report. Verify that the Status is normal.

    In a replicated deployment, check the replication status. Synchronize the replica instance if necessary. For instructions, see Synchronize a Replica Instance.

  • For instructions on what to do if your primary instance has a DNS Server, replica instances, trusted realms, web tiers, uses RADIUS, or have authentication agents, see Change the Primary Instance IPv4 Network Settings.

  • For instructions on what to do if your replica instance has a DNS Server, web tiers, uses RADIUS, or has authentication agents, see Change the Replica Instance IPv4 Network Settings.

Related Tasks

Recover from an Incorrect Gateway

Recover from an Incorrect Subnet Mask