Troubleshooting Avaya Analytics™ from the Cluster Control Manager console

Last Updated : Nov 30, 2021 |
Prolog information
You can troubleshoot common issues in Avaya Analytics™ by running the post-install scripts on the Cluster Control Manager (CCM) console. To complete the troubleshooting procedures in this chapter, you must log in to the CCM console as a customer user, where the customer username varies for every organization, and then switch to the root user. Root user access might not be required for some steps as indicated in the respective procedures.
To complete some of these procedures you require access to:
  • Cluster Control Manager IP address
  • System Manager IP address
  • Authorization Service Avaya Breeze® node SIPs
  • Avaya Oceana® Cluster 1 Avaya Breeze® Node SIPs
  • Avaya Control Manager
Note:
The post-install script might take some time to display the options after you run the ccm release orca analytics command or might display the following message: Failed to get auth token. Wait for some time or type the command again.
Other:
Do not delete nodes or VMs from your VMware.