Post installation/upgrade steps

Running Docker commands

Run the following commands after installing or upgrading the DSG to 3.3.0.0.

1. On the ESA CLI Manager, navigate to Administration > OS Console.
2. Run the docker ps command. A list of all the available docker containers is displayed. For example,

CONTAINER ID   IMAGE                                            COMMAND                  CREATED       STATUS       PORTS     NAMES
018a569bd7a6   gpg-agent:3.3.0.0.5                              "gpg-agent --server …"   9 days ago    Up 2 hours             gpg-agent-3.3.0.0.5-1
5a30bd37e576   dsg-ui:3.3.0.0.5                                "/opt/start-httpd.sh"    9 days ago    Up 3 hours             dsg-ui-3.3.0.0.5-1

3. Run the below commands to update the container configuration.
   

   docker update --restart=unless-stopped --cpus 2 --memory 1g --memory-swap 1.5g dsg-ui-3.3.0.0.5-1
docker update --restart=always --cpus 1 --memory .5g --memory-swap .6g gpg-agent-3.3.0.0.5-1
   The values of --cpus, --memory, and --memory-swap can be changed as per the requirements.

Updating the evasive configuration file

Run the following commands only if ESA is upgraded from 9.1.0.x to 10.0.x.

1. On the ESA CLI Manager, navigate to Administration > OS Console.
2. Add new mod evasive configuration file using the following command.
   nano /etc/apache2/mods-enabled/whitelist_evasive.conf
3. Add the following parameters to the mod evasive configuration file.
   

<IfModule mod_evasive20.c>  
DOSWhitelist 127.0.0.1
</IfModule>

4. Save the changes.
5. Set the required permissions for evasive configuration file using the following command.
   chmod 644 /etc/apache2/mods-enabled/whitelist_evasive.conf
6. Reload the apache service using the following command.
   /etc/init.d/apache2 reload

Verifying the DSG installation

This section describes the steps to verify the version details of the DSG instance.

To verify the version details of the DSG instance:

1. Login to the DSG Web UI.

2. Click the (Information) icon, and then click About.

3. Verify that the DSG version is reflected as DSG 3.3.0.0.

The DSG version details appear on the DSG Web UI successfully.

Pushing the DSG rulesets

This section describes the steps to push the DSG Rulesets in a cluster.

To push the DSG Rulesets:

1. Login to the ESA Web UI using the administrator credentials.

2. Navigate to Cloud Gateway > 3.3.0.0 {build number} > Cluster.

3. Go to Actions and click Deploy or Deploy to Node Groups to push the DSG Ruleset configurations to the DSG nodes. For more information about deploying the configurations, refer to the sections Deploying the Configurations to Entire Cluster or Deploying the Configurations to Node Groups.

The DSG Rulesets are pushed to the DSG nodes in a cluster or node groups.

Verifying the Startup Logs

This section describes the steps to verify the startup logs.

To verify the DSG startup logs:

1. Login to the DSG Web UI using the administrator credentials.

2. Navigate to Logs > Appliance.

3. Click Cloud Gateway - Event Logs, and select gateway.

   Verify that the startup logs do not display any errors.

The DSG startup logs are displayed on the DSG Web UI.

Enabling Scheduled Tasks on Insight

The DSG metrics logs that are generated over time can be scheduled for cleanup regularly. You can click Audit Store > Analytics > Scheduler, select the Delete DSG Error Indices, Delete DSG Usage Indices, or Delete DSG Transaction Indices, and then click Edit to modify the scheduled task that initiates the Indices file cleanup at regular intervals. The scheduled task can be set to n days based on your preference.

For more information about the audit indexes, refer to Understanding the index field values.

For more information about scheduled tasks, refer to Using the scheduler.