Updating the IP address of the ESA

Update the configurations on the ESA after updating the IP Address of the ESA machine.

Perform the steps on one system at a time if multiple ESAs must be updated.

Updating the IP address on the Primary ESA

Update the ESA configuration of the Primary ESA. This is the designated ESA that is used to log in for performing all configurations. It is also the ESA that is used to create and deploy policies.

Perform the following steps to refresh the configurations:

Recreate the Docker containers using the following steps.
1. Open the OS Console on the Primary ESA.
  1. Log in to the CLI Manager on the Primary ESA.
  2. Navigate to Administration > OS Console.
  3. Enter the root password.
2. Stop the containers using the following commands.
```
/etc/init.d/asrepository stop
/etc/init.d/asdashboards stop
```
3. Remove the containers using the following commands.
```
/etc/init.d/asrepository remove
/etc/init.d/asdashboards remove
```
4. Update the IP address in the config.yml configuration file.
  1. In the OS Console, navigate to the /opt/protegrity/auditstore/config/security directory.
```
cd /opt/protegrity/auditstore/config/security
```
  2. Open the config.yml file using a text editor.
  3. Locate the internalProxies: attribute and update the IP address value for the ESA.
  4. Save and close the file.
5. Start the containers using the following commands.
```
/etc/init.d/asrepository start
/etc/init.d/asdashboards start
```
Update the IP address in the asd_api_config.json configuration file.
1. In the OS Console, navigate to the /opt/protegrity/insight/analytics/config directory.
```
cd /opt/protegrity/insight/analytics/config
```
2. Open the asd_api_config.json file using a text editor.
3. Locate the x_forwarded_for attribute and update the IP address value for the ESA.
4. Save and close the file.
Rotate the Audit Store certificates on the Primary ESA.
For the steps to rotate Audit Store certificates, refer here.

Use the IP address of the local node, which is the Primary ESA and the Lead node, while rotating the certificates.

Monitor the cluster status.
1. Log in to the Web UI of the Primary ESA.
2. Navigate to Audit Store > Cluster Management.
3. Wait till the following updates are visible on the Overview page.
  - The IP address of the Primary ESA is updated.
  - All the nodes are visible in the cluster.
  - The health of the cluster is green.
  Alternatively, monitor the log files for any errors by logging into the ESA Web UI, navigating to Logs > Appliance, and selecting the following files from the Enterprise-Security-Administrator - Event Logs list:
  - insight_analytics
  - asmanagement
  - asrepository

Updating the IP Address on the Secondary ESA

Ensure that the IP address of the ESA has been updated. Perform the steps on one system at a time if multiple ESAs must be updated.

Perform the following steps to refresh the configurations:

Recreate the Docker containers using the following steps.
1. Open the OS Console on the Secondary ESA.
  1. Log in to the CLI Manager on the Secondary ESA.
  2. Navigate to Administration > OS Console.
  3. Enter the root password.
2. Stop the containers using the following commands.
```
/etc/init.d/asrepository stop
/etc/init.d/asdashboards stop
```
3. Remove the containers using the following commands.
```
/etc/init.d/asrepository remove
/etc/init.d/asdashboards remove
```
4. Update the IP address in the config.yml configuration file.
  1. In the OS Console, navigate to the /opt/protegrity/auditstore/config/security directory.
```
cd /opt/protegrity/auditstore/config/security
```
  2. Open the config.yml file using a text editor.
  3. Locate the internalProxies: attribute and update the IP address value for the ESA.
  4. Save and close the file.
5. Start the containers using the following commands.
```
/etc/init.d/asrepository start
/etc/init.d/asdashboards start
```
Update the IP address in the asd_api_config.json configuration file.
1. In the OS Console, navigate to the /opt/protegrity/insight/analytics/config directory.
```
cd /opt/protegrity/insight/analytics/config
```
2. Open the asd_api_config.json file using a text editor.
3. Locate the x_forwarded_for attribute and update the IP address value for the ESA.
4. Save and close the file.
Rotate the Audit Store certificates on the Secondary ESA. Perform the steps on the Secondary ESA. However, use the IP address of the Primary ESA, which is the Lead node, for rotating the certificates.
For the steps to rotate Audit Store certificates, refer here.
Monitor the cluster status.
1. Log in to the Web UI of the Primary ESA.
2. Navigate to Audit Store > Cluster Management.
3. Wait till the following updates are visible on the Overview page.
  - The IP address of the Secondary ESA is updated.
  - All the nodes are visible in the cluster.
  - The health of the cluster is green.
  Alternatively, monitor the log files for any errors by logging into the ESA Web UI, navigating to Logs > Appliance, and selecting the following files from the Enterprise-Security-Administrator - Event Logs list:
  - insight_analytics
  - asmanagement
  - asrepository

Last modified February 7, 2025