1) You might receive the error "Login failed. Service is not available at this time" if the SANNav IP is not added in the SNMP Configuration of the switch as an snmp user.
Kindly refer below screenshot:
2) "connection timed out" error might be received when not all SANnav services are up and running or if there are Firewall restrictions or if the Server to Switch communication is failing.
Kindly refer below screenshot:
1) Fix for Login issue: "Login failed. Service is not available at this time"
- Checked SNMP config on switch and did not find the SANnav IP listed.
- Added the SANnav IP to snmp list by creating the same user as that of fabos "admin".
- Ping was working from the server to switch and vice versa.
- We did restart the Sannav services on the server:
[user@sannav.lab bin]$ ./restart-sannav-status.sh
- When checked the services, found the below services were down.
[user@sannav.lab bin]$ ./check-sannav-status.sh
Following services are currently down
performancemanagement-middleware
fe-consolidated-2
- Rebooted the SANnav server, then checked for the services and found all of them to be up and running.
- Then we were able to login to the SANnav server via Web Portal successfully.
2) Fix for Fabric Discovery: "connection timed out"
- To check if any firewall restrictions, kindly check the below command on SANnav server:
# firewall-cmd --list -all
If any restrictions observed kindly check the installation guide which mentions the list of opens that needs to be opened.
- Apart from those fabric discovery timed out errors there are also many connection errors on SNMP and HTTP as well in the SANnav server logs:
For example:
"Failed to discover a Fabric with seed switch 10.xx.xx.xx. Connection timed out",
"Failed to discover a Fabric with seed switch 10.yy.yy.yy. Connection timed out",
switch-asset-collectors-mw - [ERROR] 2020-08-18 00:18:48.438 [http-nio-7021-exec-1] com.brocade.dcm.connector.snmp.AbstractSnmpConnector - Error in SNMP get. Device 10.xx.xx.xx, Request timed out or device is unreachable
2020/08/17 23:42:51 [error] 6#6: *3956 connect() failed (113: No route to host) while connecting to upstream, client: 10.x.y.z, server: spectre_ssl, request: "POST /auth/login HTTP/2.0", upstream: "http://10.x.y.z:8021/auth/login", host: "10.yy.yy.yy", referrer: "https://10.yy.yy.yy/"
- The below Action Plan helped resolved the connection timeout issues:
a) Stop SANnav services
b) Modify SANnav "server.properties" file by changing the communication protocol from SANnav Server to the switch as follows:
# Server to Switch Communication preference
# 0 --> HTTP Only
# 1 --> HTTPS Only
# 2 --> First HTTPS and then HTTP
dcm.server.switch.comm.preference=0
c) Restart SANnav server
d) Retried the fabric discovery and the switches were discovered successfully.