In this topic, you can find information about common issues and solutions from VMware Telco Cloud Service Assurance User Interface.
Issues | Causes | Solution |
---|---|---|
The EDAA operations on Notifications like Acknowledge, UnAcknowlege, BrowseDetails, and Containment fails, even though the EDAA and SAM Presentation server is UP and RUNNING. | The SAM configuration from a DM adapter is getting deleted because of which EDAA operations in VMware Telco Cloud Service Assurance are failing with 404 error. | Run the following command inside any of the Pod running in a Kubernetes cluster:
|
While logging in to VMware Telco Cloud Service Assurance, with any non-preconfigured users (other than admin, maint, default, or oper), following error message appears Unexpected error while handling authentication request to identity provider. |
|
|
While logging in to VMware Telco Cloud Service Assurance, with any non-preconfigured users (other than admin, maint, default, or oper), following error message appears Failed to process request, cause JSONObject["groups"] is not a JSONArray. | User is trying to log in which is not associated to any group. | Associate the user to a group and configure Role for the group in VMware Telco Cloud Service Assurance. |
User unable to log in to the VMware Telco Cloud Service Assurance user interface. |
|
|
After successful login, VMware Telco Cloud Service Assurance user interface displays that, the user’s group is not authorized / mapped to any VMware Telco Cloud Service Assurance role. | User is not associated to any usergroup in keycloak native Or LDAP. |
|
UserGroup is not mapped to a VMware Telco Cloud Service Assurance. | Log in to the VMware Telco Cloud Service Assurance user interface as an admin user and create the VMware Telco Cloud Service Assurance role to usergroup mapping. | |
A non-admin user is only able to see a subset of navigational links on the VMware Telco Cloud Service Assurance user interface. | User's Role does not have permissions to access all the VMware Telco Cloud Service Assurance navigational links. |
|
A non-admin user is only able to see a subset / none of the datapoints on the Grafana dashboards. | 1.User's Role is restricted by a defined policy filter that allows access only to a subset of data. |
|
Sometimes Topology instance count does not match between VMware Telco Cloud Service Assurance and SAM. | Some of the error conditions are not handled. When such error appears, retry mechanism is not implemented, due to which some device are missed to add to the ArangoDB. | Follow below procedure to sync the entire topology in VMware Telco Cloud Service Assurance: Admin user deletes SAM from Administration > Smarts Integration > Broker > SAM(delete). When delete operation is performed, associated notification or/and Topology objects related to SAM are deleted from VMware Telco Cloud Service Assurance. VMware Telco Cloud Service Assurance deletes Notification/Topology asynchronously, and based on size of Topology and number of live notifications, clean-up could be time consuming. Typically for 100K events time taken for deletion would be around 30 minutes and Topology delete for about 20k devices would be around 15 minutes. Wait till both notifications and topology objects are deleted.
Verifying Clean-up of topology in
VMware Telco Cloud Service Assurance:
Re-Adding SAM in VMware Telco Cloud Service Assurance:
Re-add the SAM in
VMware Telco Cloud Service Assurance so that all topology objects are resynced and count match occurs between
VMware Telco Cloud Service Assurance and SAM:
Note:
Re-adding SAM in VMware Telco Cloud Service Assurance procedure should not be done immediately after deletion is performed. |