"Unable to login" error when logging in to Aria Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

NOTE:  VCF Operations for Networks was formerly named Aria Operations for Networks (AON), and prior to that was named vRealize Network Insight (vRNI).

 

Users are unable to login using Active Directory.

The admin user (admin@local) user was also unable to login even after the password was reset via the CLI.

When attempting a login with admin@local the error "Unable to login" displays in the GUI.

 

Upon SSH into the platform node with the support user, checking the service health, using the following command:

./check-service-health.sh

You will see the following:

DatabusGateway is running but not healthy

PolicyManager is running but not healthy

Note that command may freeze before reporting PolicyManager status and only upon forcing the exit do you see its status.

NOTE:  An additional symptom that may be seen is that the browser just presents a plain page.  If the user waits a few moments, a pop-up appears with the words "We're Sorry" followed by "we ran into a problem completing your request."

 

Environment

VMware Aria Operations for Networks 6.12
VMware Aria Operations for Networks 6.12.1
VMware Aria Operations for Networks 6.13
VMware Aria Operations for Networks 6.14

Cause

A java service has gotten stuck on the platform, causing some Aria Operations for Networks services to have issues, resulting in the inability to login to Aria Operations for Networks GUI.

Resolution

Do not reboot the Platform node(s) manually.

SSH into the Platform node 1 with the support user, and restart the services in question, using the following commands:

For a Simple deployment:

sudo systemctl stop databus-gateway.service
sudo systemctl start databus-gateway.service
sudo systemctl stop policy-manager.service
sudo systemctl start policy-manager.service

For deployments where Platform nodes are Cluster:

./run_all.sh sudo systemctl stop databus-gateway.service
./run_all.sh sudo systemctl start databus-gateway.service
./run_all.sh sudo systemctl stop policy-manager.service
./run_all.sh sudo systemctl start policy-manager.service

If the issue persists after the services have been stop/started, log a case with Broadcom Support for further assistance. See Creating and managing Broadcom support cases