Cisco SDWAN vManage GUI Not Working

[pnkjmalik11]

Hi There,

When i am trying to access the vManage from Google Chrome Browser its not accessible, giving error "This Site Can't be Reached". However, CLI mode is properly accessible from Putty.

Ping is successful from both end Windows CMD side & vManage CLI side.

Kindly find the below logs for your reference.

[Flavio Miranda]

Hi

 Can I see the outout of the command

show interface | i tab

And try to access using port 443.

[pnkjmalik11]

Hi Flavio,

Kindly find the below output:

vManage# show interface | tab

IF IF IF TCP

AF ADMIN OPER TRACKER ENCAP SPEED MSS
RX TX
VPN INTERFACE TYPE IP ADDRESS STATUS STATUS STATUS TYPE PORT TYPE MTU HWADDR MBPS DUPLEX ADJUST UPTIME
PACKETS PACKETS
---------------------------------------------------------------------------------------------------------------------------------------
------------------------
0 eth0 ipv4 123.10.10.10/24 Up Up - null transport - 50:f8:da:00:a0:00 - - - 0:00:0
3:36 273 56
0 system ipv4 1.1.1.1/32 Up Up - null loopback - - - - - 0:00:0
4:55 0 0
512 eth1 ipv4 192.168.1.11/24 Up Up - null mgmt - 50:f8:da:00:a0:01 - - - 0:00:0
3:34 258 5

vManage#

[pnkjmalik11]

[pnkjmalik11]

Hi 

I have tried to access with Port 443 as well but no luck.

Now, i restart all the nms services and finally i got the GUI mode access.

[MHM Cisco World]

Check net cloud IP

[Kanan Huseynli]

Hi,

Share show run vpn 0 and show run vpn 512

[pnkjmalik11]

Hi Kanan,

Please find the below output:

vManage# show running-config vpn 0
vpn 0
interface eth0
ip address 123.10.10.10/24
ipv6 dhcp-client
tunnel-interface
allow-service all
allow-service dhcp
allow-service dns
allow-service icmp
no allow-service sshd
no allow-service netconf
no allow-service ntp
no allow-service stun
allow-service https
!
no shutdown
!
ip route 0.0.0.0/0 123.10.10.1
!
vManage# show running-config vpn 512
vpn 512
interface eth1
ip address 192.168.1.11/24
no shutdown
!
!
vManage#

[pnkjmalik11]

Hi @Kanan Huseynli  @MHM Cisco World  @Flavio Miranda 

kindly find the attached logs from windows pc side. 

GUI mode is still not accessible.

[Flavio Miranda]

Can you give a try in 123.10.10.10 IP?

[Kanan Huseynli]

Hi,

do telnet 192.168.1.11 443 or telnet 192.168.1.11 8443 from this PC's cmd.

Also, share outputs from vmanage cli:

request nms application-server status

request nms application-server diagnostics

Meanwhile, if server status is running and everything seems OK (below the same outputs from my labs, do general comparison), then stop&start application server:

request nms application-server stop (wait ~1min)
request nms application-server start(wait some minutes and try gui access again).

By the way, what cpu/ram did you give vmanage as resource?

vmanage# request nms application-server status 
NMS application server
Enabled: true
Status: running PID:41950 for 206692s

vmanage# request nms application-server diagnostics 
NMS application server
Checking cluster connectivity...
Pinging server 0 on 172.20.1.2:8443...
Starting Nping 0.7.80 ( https://nmap.org/nping ) at 2023-06-20 12:36 +04
SENT (0.0016s) Starting TCP Handshake > 172.20.1.2:8443
RCVD (0.0016s) Handshake with 172.20.1.2:8443 completed
SENT (1.0029s) Starting TCP Handshake > 172.20.1.2:8443
RCVD (1.0029s) Handshake with 172.20.1.2:8443 completed
SENT (2.0043s) Starting TCP Handshake > 172.20.1.2:8443
RCVD (2.0043s) Handshake with 172.20.1.2:8443 completed

Max rtt: 0.060ms | Min rtt: 0.017ms | Avg rtt: 0.037ms
TCP connection attempts: 3 | Successful connections: 3 | Failed: 0 (0.00%)
Nping done: 1 IP address pinged in 2.00 seconds

Disk I/O statistics for vManage storage
---------------------------------------
avg-cpu: %user %nice %system %iowait %steal %idle
3.00 0.16 1.07 0.01 0.00 95.76

Device tps kB_read/s kB_wrtn/s kB_dscd/s kB_read kB_wrtn kB_dscd

[pnkjmalik11]

Hi

vManage# request nms application-server diagnostics
NMS application server
Checking cluster connectivity...
Pinging server 0 on localhost:8443,8080...
Starting Nping 0.6.47 ( http://nmap.org/nping ) at 2023-06-21 05:52 UTC
SENT (0.0022s) Starting TCP Handshake > localhost:8080 (127.0.0.1:8080)
RECV (0.0022s) Handshake with localhost:8080 (127.0.0.1:8080) completed
SENT (1.0037s) Starting TCP Handshake > localhost:8443 (127.0.0.1:8443)
RECV (1.0037s) Handshake with localhost:8443 (127.0.0.1:8443) completed
SENT (2.0049s) Starting TCP Handshake > localhost:8080 (127.0.0.1:8080)
RECV (2.0049s) Handshake with localhost:8080 (127.0.0.1:8080) completed
SENT (3.0341s) Starting TCP Handshake > localhost:8443 (127.0.0.1:8443)
RECV (3.0342s) Handshake with localhost:8443 (127.0.0.1:8443) completed
SENT (4.1359s) Starting TCP Handshake > localhost:8080 (127.0.0.1:8080)
RECV (4.1359s) Handshake with localhost:8080 (127.0.0.1:8080) completed
SENT (5.2374s) Starting TCP Handshake > localhost:8443 (127.0.0.1:8443)
RECV (5.2374s) Handshake with localhost:8443 (127.0.0.1:8443) completed

Max rtt: 0.123ms | Min rtt: 0.010ms | Avg rtt: 0.041ms
TCP connection attempts: 6 | Successful connections: 6 | Failed: 0 (0.00%)
Nping done: 1 IP address pinged in 5.24 seconds

Disk I/O statistics for vManage storage
---------------------------------------
avg-cpu: %user %nice %system %iowait %steal %idle
50.84 0.00 10.88 0.48 0.25 37.55

Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
vdb 16.26 61.14 207.54 83770 284360
vManage# request nms application-server status
NMS application server
Enabled: true
Status: running PID:19514 for 592s
vManage#

[Kanan Huseynli]

show telnet results and then restart nms application server

[pnkjmalik11]

Hi

After restart all nms services yesterday i was able to access the GUI mode, today again I'm facing the same issue.

GUI mode is not accessible. 

[pnkjmalik11]

Hi 

Kindly find the today's error screenshots.