Post Setup Validation

To ensure that the product is installed properly, the following validations need to be done.

As you follow this section, make note of any failures, unexpected behavior, or skipped steps by leaving a comment on this document.

Management System to Traffic Processor Communication

Purpose

To verify that all the application services are up and running.

Procedure

1. Open a web browser (Google Chrome or Firefox)
2. On the browser search bar type: https://< Management System IP address>
3. When the Management System page is loaded, use the customer user credentials (which are provided by Cisco) to login into the system.
4. Select the Platform, Servers, and then Management section.
5. Select the correct group (if it is not already selected) and expand the section for the instance.
6. Click on the STOP button.
7. Click on the START button.

Result

When the STOP button is clicked, the Traffic Processor service would stop, and the
instance's status would change to INACTIVE.

When the START button is clicked, the Traffic Processor service would start, and the
instance's status would change to ACTIVE.

Energy Reduction services setup

Purpose

To verify that all the application services are up and running.

Procedure

In the command line of the server:

cd /var/opanga/joule
sudo docker compose ps --format "table {{.Service}}\t{{.Status}}"

The output should show these containers as healthy:

• configuration-server
• mariadb
• minio-check
• power-state-controller

SERVICE                            STATUS
configuration-server               Up 2 hours (healthy)data-lifecycle-manager             Up 2 hours
mapgen-pipeline                    Up 2 hours
mariadb                            Up 2 hours (healthy)metadata-pipeline                  Up 2 hours
minio-check                        Up 2 hours (healthy)model-prediction-pipeline          Up 2 hours
model-training-pipeline            Up 2 hours
power-state-controller             Up 2 hours (healthy)ratio-based-default-pipeline       Up 2 hours
ratio-based-opst-3-mbps-pipeline   Up 2 hours
ratio-based-opst-7-mbps-pipeline   Up 2 hours
ratio-based-traingen-pipeline      Up 2 hours
tileserver                         Up 2 hours

This means that containers can connect to those they depend on.

Timezone in Environment files

Purpose

To verify that timezones in environment files are correct.

Procedure

Use the following command to get the server timezone:

timedatectl show --va -p Timezone

Use cat to check next files:

• /opt/opanga-services/conf/opanga-services.local.env
• /opt/fluent/conf/fluent.local.env
• /opt/redpanda-connect-pipelines/conf/redpanda-connect-pipelines.local.env

Result

Make sure all files have the correct timezone comparing the values in the file with the value obtained from the timadatectl command.

For opanga-services check TZ.
For fluent check TZ.
For redpanda-connect-pipelines check SYSTEM_TIMEZONE.

If any of the files has an incorrect value or no value, edit the file to have the correct timezone. For example, if timezone displayed by timedatectl is America/Los_Angeles:

[opanga@vm101 ~]$ timedatectl show --va -p Timezone
America/Los_Angeles[opanga@vm101 ~]$ cat /opt/opanga-services/conf/opanga-services.local.env
TZ=#other env variables

In this case, timezone is Los_Angeles, but TZ is empty, use any text editor to fix the property:

[opanga@vm101 ~]$ nano /opt/opanga-services/conf/opanga-services.local.env
TZ=America/Los_Angeles
#Other variables

Once the environment files with incorrect or missing timezone are correct, go to the path corresponding to the service that had the incorrect timezone:

• cd /opt/fluent/
• cd /opt/redpanda-connect-pipelines
• cd /opt/opanga-services/

Then restart the service using:

[opanga@vm101 ~]$ sudo docker compose down
[opanga@vm101 ~]$ sudo docker compose up -d

Kibana Timezone

Purpose

To verify that timezones in kibana is correct.

Procedure

1. Use the username/password stored in /opt/data-management-configuration/conf/data-management-configuration.local.env to log into Kibana website at https://< Management System IP address>/kibana

2. Click on the Menu button on the left as circled in red below:
   

   Kibana sidebar
   The menu navigation bar will pop up

3. Scroll down and choose Stack Management as highlighted in red below:
   

   Kibana Stack Management

4. Choose Advanced Settings as highlighted in red below:
   

   Kibana Advanced Settings

5. Find the time zone for date formatting as circled in red and change it to the server’s time zone.
   

   Kibana Time Zone

6. Make sure to click on Save Changes at the bottom of the screen after updating the time zone as shown below
   

   Kibana Save Changes