You can verify the status of the different Avaya Analytics™ pods collectively or individually after the installation is complete. If any of the services are not working as described in the respective steps in this procedure, contact your system administrator or Avaya support.
Procedure
Log in to the Cluster Control Manager (CCM) console as the customer user.
Switch to being the root user by entering the command su.
To check the status of Cluster Control Manager (CCM), run the following command:
ccm status
The page displays the following:
The status of all the staged products on CCM. For a successful installation, the status must be DEPLOYED for all the products, and all the pods must be running.
The current and previous versions of the Avaya Analytics™ components.
Optional To check only the current versions of Avaya Analytics™ components, run the following command:
swversion
To check the status for all pods, run the following command:
kubectl get pods -A
The page displays information about the respective pods with the following columns:
READY: Indicates the number of pods running for the respective pod. For a particular pod status to be successful, all the instances for the pod must be running. For example, 2/2 indicates that the status is running as expected. While 1/2 indicates an error in the status, even if the STATUS column displays Completed or Running.
Note:
The Async messaging service will show a Running state with 1/2 by design.
STATUS: Indicates whether the pod is running or completed. If the pod has any errors, the column displays Error.
RESTARTS: Indicates the number of times the pod has restarted.
AGE: Indicates the duration for which the pod runs. The format is d:h:m:s, where d is the number of days, h is the number of hours, m indicates the time in minutes and s is time in seconds.
To check the status of the Breeze authentication and token validation certificates, run the following command:
kubectl get secrets| grep breeze-security
Ensure that the page displays the TYPE as Opaque.
To check the status of Breeze authentication, run the following command:
kubectl get pods| grep breeze-auth
The page displays the following information for each column:
READY: 1/1
STATUS: Running or Completed.
RESTARTS: The number of times the pod is restarted. This column can also be blank or 0.
AGE: The duration for which the pod is running.
To check the status of Streams REST, run the following command:
kubectl get pods| grep streams-rest
The page displays the following for each column:
READY: 1/1
STATUS: Running or Completed.
RESTARTS: The number of times the pod is restarted. This column can also be blank or 0.
AGE: The duration for which the pod is running.
To check the status of Data Publisher, run the following command:
kubectl get pods| grep data-publisher
The page displays the following for each column:
READY: 1/1
STATUS: Running or Completed.
RESTARTS: The number of times the pod is restarted. This column can also be blank or 0.
AGE: The duration for which the pod is running.
To check the status of Ref Input Adaptor, run the following command:
kubectl get pods| grep ref-input
The page displays the following for each column:
READY: 1/1
STATUS: Running or Completed.
RESTARTS: The number of times the pod is restarted. This column can also be blank or 0.
AGE: The duration for which the pod is running.
To check the status of the Historical Reporting pods, run the following command:
kubectl get pods -n mstr
The page displays the following for each column:
READY: 1/1
STATUS: Running or Completed.
RESTARTS: The number of times the pod is restarted. This column can also be blank or 0.
