Primary or Replica Instance Network Settings Updates
In the Operations Console, you can update the network settings for an RSA Authentication Manager primary or replica instance. The IPv4 network settings created during Quick Setup are used for most purposes. In a replicated deployment, if you change the IPv4 hostname or IP address on the primary instance, you must use the Operations Console to update the replica instance with the new information. On the Amazon Web Services virtual appliance, the Hyper-V virtual appliance, and the VMware virtual appliance, you can create IPv6 network settings to support IPv6-compliant agents. The Azure virtual appliance only supports IPv4 network settings.
AM supports dual network interface card (NIC) configurations on the hardware appliance, the Amazon Web Services virtual appliance, the Hyper-V virtual appliance, and the VMware virtual appliance. All AM services are available on both NICs. For example, you can use one AM deployment to authenticate users from two networks by configuring the agents on each network to send authentication requests to different NICs. The Azure virtual machine supports one NIC, and one IP address for the NIC. Features that require more than one NIC are not available on the Azure virtual machine.
Advanced administrators can log on to an instance and run commands that create IPv4 and IPv6 static routes. Static routes send data through a network on a fixed, predictable path. Both persistent and non-persistent static routes are supported. For instructions, see Static Routes.
If the primary or replica instance IPv4 network settings are incorrect and you cannot access the Operations Console, you can log on to the appliance operating system and change the settings. On a virtual appliance, use the Hyper-V Virtual Machine Manager, the VMware vSphere Client, or Secure Shell (SSH). On a hardware appliance, an Amazon Web Services appliance, or Azure appliance, use SSH. For instructions, see the Recovery from Incorrect Network Settings.
Note: Network setting recovery procedures require knowledge of an operating system-level Linux text editor, such as the vi editor.
If you cannot access the hardware appliance operating system to correct the network settings, shut down the appliance and remove the machine from service.
If a malfunctioning hardware appliance cannot be recovered, restore the backup image that you created when you first deployed the appliance. For more information, see “Using Clonezilla to Back Up and Restore the RSA Authentication Manager 8.4 Hardware Appliance”.
If a backup image is not available, you can apply the original hardware appliance system image.
Related Articles
Promotion for maintenance fails: Unable to apply the data updates from the primary instance 281Number of Views Create IPv6 Network Settings on a Primary or Replica Instance 38Number of Views Replica Radius server will not synchronize, Primary status is listed as Standalone 274Number of Views Update the Primary Instance Hostname and IP Address on a Replica Instance 171Number of Views Attach the Replica Instance to the Primary Instance 320Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) How to install the jTDS JDBC driver on WildFly for use with Data Collections in RSA Identity Governance & Lifecycle RSA Authentication Manager 8.8 Setup and Configuration Guide Artifacts to gather in RSA Identity Governance & Lifecycle