cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1541
Views
0
Helpful
10
Replies

SD-WAN Sandbox Connectivity Issues

Hi Cisco Team,

I am not able to  connect to Cisco Sandbox via VPN. I am following the instructions based on the email sent to me:

 

 

The connection is very flaky.

ping devnetsandbox-emea-gwy.cisco.com:20246

 

64 bytes from 92.242.140.21: icmp_seq=629 ttl=246 time=38.743 ms

64 bytes from 92.242.140.21: icmp_seq=630 ttl=246 time=39.430 ms

64 bytes from 92.242.140.21: icmp_seq=631 ttl=246 time=44.304 ms

64 bytes from 92.242.140.21: icmp_seq=632 ttl=246 time=42.258 ms

64 bytes from 92.242.140.21: icmp_seq=633 ttl=246 time=39.479 ms

64 bytes from 92.242.140.21: icmp_seq=634 ttl=246 time=38.146 ms

64 bytes from 92.242.140.21: icmp_seq=635 ttl=246 time=37.886 ms

64 bytes from 92.242.140.21: icmp_seq=636 ttl=246 time=42.445 ms

64 bytes from 92.242.140.21: icmp_seq=637 ttl=246 time=46.971 ms

64 bytes from 92.242.140.21: icmp_seq=638 ttl=246 time=39.816 ms

64 bytes from 92.242.140.21: icmp_seq=639 ttl=246 time=44.266 ms

64 bytes from 92.242.140.21: icmp_seq=640 ttl=246 time=37.187 ms

64 bytes from 92.242.140.21: icmp_seq=641 ttl=246 time=37.597 ms

64 bytes from 92.242.140.21: icmp_seq=642 ttl=246 time=39.992 ms

64 bytes from 92.242.140.21: icmp_seq=643 ttl=246 time=45.835 ms

64 bytes from 92.242.140.21: icmp_seq=644 ttl=246 time=40.683 ms

64 bytes from 92.242.140.21: icmp_seq=645 ttl=246 time=48.276 ms

64 bytes from 92.242.140.21: icmp_seq=646 ttl=246 time=40.012 ms

64 bytes from 92.242.140.21: icmp_seq=647 ttl=246 time=37.713 ms

64 bytes from 92.242.140.21: icmp_seq=648 ttl=246 time=50.303 ms

64 bytes from 92.242.140.21: icmp_seq=649 ttl=246 time=40.816 ms

64 bytes from 92.242.140.21: icmp_seq=650 ttl=246 time=38.983 ms

64 bytes from 92.242.140.21: icmp_seq=651 ttl=246 time=40.098 ms

64 bytes from 92.242.140.21: icmp_seq=652 ttl=246 time=38.949 ms

64 bytes from 92.242.140.21: icmp_seq=653 ttl=246 time=68.625 ms

64 bytes from 92.242.140.21: icmp_seq=654 ttl=246 time=46.343 ms

64 bytes from 92.242.140.21: icmp_seq=655 ttl=246 time=40.986 ms

64 bytes from 92.242.140.21: icmp_seq=656 ttl=246 time=42.243 ms

64 bytes from 92.242.140.21: icmp_seq=657 ttl=246 time=39.517 ms

64 bytes from 92.242.140.21: icmp_seq=658 ttl=246 time=49.120 ms

64 bytes from 92.242.140.21: icmp_seq=659 ttl=246 time=39.835 ms

64 bytes from 92.242.140.21: icmp_seq=660 ttl=246 time=39.916 ms

64 bytes from 92.242.140.21: icmp_seq=661 ttl=246 time=45.287 ms

64 bytes from 92.242.140.21: icmp_seq=662 ttl=246 time=38.286 ms

64 bytes from 92.242.140.21: icmp_seq=663 ttl=246 time=37.204 ms

64 bytes from 92.242.140.21: icmp_seq=664 ttl=246 time=40.207 ms

64 bytes from 92.242.140.21: icmp_seq=665 ttl=246 time=50.525 ms

64 bytes from 92.242.140.21: icmp_seq=666 ttl=246 time=41.673 ms

Request timeout for icmp_seq 667

Request timeout for icmp_seq 668

Request timeout for icmp_seq 669

Request timeout for icmp_seq 670

Request timeout for icmp_seq 671

Request timeout for icmp_seq 672

Request timeout for icmp_seq 673

64 bytes from 92.242.140.21: icmp_seq=674 ttl=246 time=39.283 ms

Request timeout for icmp_seq 675

Request timeout for icmp_seq 676

Request timeout for icmp_seq 677

Request timeout for icmp_seq 678

Request timeout for icmp_seq 679

Request timeout for icmp_seq 680

64 bytes from 92.242.140.21: icmp_seq=681 ttl=246 time=38.251 ms

Request timeout for icmp_seq 682

Request timeout for icmp_seq 683

Request timeout for icmp_seq 684

Request timeout for icmp_seq 685

 

Can you please fix the issue? 

 

Regards,

Shashi

10 Replies 10

Hi there, in this case you are not pinging the sandbox, but the VPN gateway - the sandbox is behind the VPN. When you had the VPN connected were you not able to access the vManage front page?

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

Hi, I am having the issue mentioned. I can not access the vmanage via gui, cli does work briefly then locks up on all devices, pings to the lab devices are timing out often, I have stopped and restarted the devices and also tried canceling the reservations and testing again. My local network is fine no issues. Any suggestions would be great. @bigevilbeard 

Sure - can you advise if this is the reserved sd-wan sandbox, the always on sd-wan sandbox or the virl version please?

 

Thanks!

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

The SD-WAN lab shows Ver 18.3

Thanks - Did you reserve this one and get VPN details?
Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

Yes, I got connected fine to the VPN, just high latency, I could login to device via cli and then it would lockup. I tried vmanage in multiple browsers it would not pull up at all. There seems to be an issue with that server.
I just now completed testing on the UCS Director lab and it ran with no issues.(Director,Manager,Central)

Thanks - in this case we need sandbox engineering team to comment here.
Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

I have the same issues on the sdwan reserved lab. High latency and packet loss to sdwan lab devices. Vmanage gui eventually opens but extremely slow. Template pushes timeout 9 out of 10 times. 

 

I have let the devnet sandbox engineering team aware of this issue
Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

Thanks