Things to check when SMARTS Browser Based Web Console will not connect

Products

• Network Observability
• VMware Smart Assurance

Issue/Introduction

After configuring the Browser based Web Console via Webswing using the documented instructions the web page does not connect and a "took too long to respond" error shows.  This document provides information on what to check.

https://techdocs.broadcom.com/us/en/vmware-sde/telco-cloud/smarts/25-4/installing-smarts/smarts-installation-guide-for-sam--ip--esm--mpls--npm--otm--acm--mcast--asam-and-voip-managers/domain-managers-installation-guide/performing-an-installation/install-the-product/deploying-web-based-notification-console.html

 

Resolution

Review the logs in the following locations on the Console machine:

/opt/InCharge/CONSOLE/smarts/tomcat/webswing-console/logs
/opt/InCharge/CONSOLE/smarts/local/logs/webswing

Verify firewalld is disabled:

systemctl status firewalld

If it is running try stopping it and refreshing the page to see if you can then login:

systemctl stop firewalld

Run curl from the Console host to the SAM Broker:

curl -v -k https://<CONSOLEHOSTIP>:9443/smarts

Run that same curl command from the SAM broker.

Verify your SM_BROKER_DEFAULT and SM_WSC_PRIMARY URL are correct in the runcmd_env.sh file:

SM_BROKER_DEFAULT=<BROKERHOSTNAME>:426
SM_LICENSE=null
SM_SNMP_BUG_COMPATIBLE=TRUE
SM_INCOMING_PROTOCOL=1,0
SM_OUTGOING_PROTOCOL=1,0
SM_DEFHOME=/dev/null
SM_LOCALE=en_US
SM_ENCODING_OUTPUT=UTF-8
SM_FIPS140=FALSE
SM_LOG_ROLL_SIZE=200M
SM_BACKUP_FILE_LIMIT=5
SM_ALLOW_LEGACY_CRYPTO=TRUE
SM_TLS_MIN_VERSION=1.2
SM_TLS_MAX_VERSION=1.3
SM_WSC_PRIMARY_URL=https://<CONSOLEHOSTIP:9443/smarts