The following information about changing the hostname for a primary or replica instance only applies to the Azure virtual appliance.
After changing the hostname in the primary or replica instance Operations Console, you can access the Azure virtual machine with the new hostname. However, to update the hostname in the Azure portal, you must restore a snapshot to create a new virtual machine with the new hostname. You can keep the original IP address by reusing the original NIC, and you can keep the original virtual machine data by swapping the virtual machine disk.
Before you begin
On the primary or replica instance that you are updating, log on to the Operations Console, and change the hostname.
Start the new virtual machine. After 10 to 15 minutes, the new virtual machine is available with the new hostname, the original IP address, and the original virtual machine data.
Note:If the hostname change is successful, RSA recommends saving space by removing the original virtual machine, the original disk, and the snapshot from step 1.
After you finish
Update the DNS server with the new hostname or IP address.
The Azure appliance requires you to configure a DNS server in the virtual network or use the DNS server provided by Azure. Any on-premises Authentication Manager primary instance or replica instances must use the DNS server that is configured in the virtual network.
In a replicated deployment, after updating your DNS server, 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.
If you installed an SSL certificate that is signed by a third-party certificate authority (CA), changing the hostname causes the deployment to revert to the SSL certificate signed by the Authentication Manager CA that is enabled when the instance is deployed.
To install a new SSL certificate, import a new SSL certificate that is signed by the third-party certificate authority and whose common name (CN) is the new hostname. For instructions, see Replacing the Console Certificate.
If your deployment includes a web tier, do the following:
Primary instance hostname updated in a deployment with replica instances
The web tier obtains the primary instance hostname from a replica instance. After you update the primary instance hostname on every replica instance, wait five minutes for the web tier to update. You can then make additional replica instance hostname changes as needed.
Primary instance hostname updated in a deployment with no replica instances
Reinstall the web tier. Perform the following procedure to retain all existing web-tier configuration and customization settings:
Wait five minutes for the web tier to update. You can then make additional hostname changes as needed.
In a replicated deployment, the web tier obtains the replica instance hostname from the primary instance. The waiting period allows the web tier to maintain communication with the Authentication Manager instances.
Update any external clients, such as RADIUS clients and SNMP, to use the new hostname.