Log in to the Cluster Control Manager (CCM) console as the customer user.
To switch to the root user, type su - and press Enter.
Run the following command to view the last log entries for one of the microservices:
for i in $(kubectl get pods | grep async-oceana-adapter | awk '{print $1}'); do echo "**** Logs for Pod $i *****"; echo " "; kubectl logs $i async-aggregator-interface | tail -n 100; done
If the logs do not display the messages flowing from Avaya Oceana®, verify that Avaya Oceana® is operational.
If the logs display the messages flowing from Avaya Oceana®, run the following command:
for i in $(kubectl get pods | grep async-aggregator-interface | awk '{print $1}'); do echo "**** Logs for Pod $i *****"; echo " "; kubectl logs $i async-oceana-adapter | tail -n 100; done
If you observe any errors in calling Cloud Provider, do the following:
Check whether the security details of Cloud Provider are correct.
Check whether Cloud Provider in non-operational.
Check whether there is an intermittent problem with any Network Interface Card (NIC) where the Avaya Common Services cluster is installed.
If you do not find any errors and the messages appear to be sent to Cloud Provider, it might take a few minutes for Cloud Provider to propagate the messages to a customer. You can contact the DevOps team to check if there is an outage in Cloud Provider.
