Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Performing a Health Check of Infrastructure Components

 

After you install or upgrade CSO, you can run the components_health.sh script to perform a health check of all infrastructure components. This script detects whether any infrastructure component has failed and displays the health status of the following infrastructure components:

  • SaltStack

  • Cassandra

  • MariaDB

  • Swift

  • Redis

  • ArangoDb

  • Keystone

  • Elasticsearch

  • Elk Elasticsearch

  • Icinga

  • RabbitMQ

  • Etcd

  • Rsyslog

  • Kubernetes

  • ELK Logstash

  • ELK Kibana

  • ZooKeeper

  • Contrail Analytics

  • VRR

  • Microservices

To check the status of infrastructure components:

  1. Log in to the startupserver_1 VM as root.
  2. Navigate to the CSO directory in the startupserver_1 VM.

    For example:

    root@host:~/# cd Contrail_Service_Orchestration_6.1.0
    root@host:~/Contrail_Service_Orchestration_6.1.0#
  3. Run the components_health.sh script.

    To check the status of one of infrastructure components, run the following command:

    root@startupserver_1:/opt/Contrail_Service_Orchestration_6.1.0# ./components_health.sh --component=<component_name>

    Run the following command to check the health of all the infrastructure components.

    root@startupserver_1:/opt/Contrail_Service_Orchestration_6.1.0# ./components_health.sh

    After a couple of minutes, the status of each infrastructure component is displayed.

    For example:

If the components_health.sh script detects any service as unhealthy, then it displays an error message as shown in the following sample output.

To recover the service, you must run the recovery.sh script. See Recovering CSO Services.