Sandbox devices not available

[njccnp]

Connected to DNAC reserved Sandbox Lab 4, and still no luck. The instructions imply that once the VPN is connected, I should have access to the sandbox devices (on the 10.10.20.0 subnet). This is not the case. I cannot connect to any of the devices via ping or HTTP, etc. Annyconnect added a route to 10.10.20.0/24 with a gateway of 192.168.254.1, but that gateway address does not respond to pings. 

[bigevilbeard]

Not sure if this is your issue, but the tile shows 'some resources not available'. Typically all ICMP is denied over the VPN and the only ports you can access are listed in the sandbox instructions. Sometimes, the lab takes a little while to build also, which mean devices are still spinning up. Normally i wait an additional ten minute until after the second email before accessing the devices. port 80 and destination 10.10.20.85 should come up via your browser or via an API call.

You can always end the reservation and start a new one if after trying this you cannot access the devices.

Hope this helps.

[njccnp]

Well, it's been over two hours since that second email, and it's still not accessible. The DNAC itself is definitely one of the devices that is supposed to be available. There's even a link in the instructions to HTTP to it, and that also fails. I chose Lab 4 because (at that time) it was one of the only two that did not say "some resources are not available." I'm done trying for today, will try a reservation tomorrow if there are any available.

[bigevilbeard]

I tried - i could connect to the ISE and CML, but not GUI of DNAC. In the set up i could see, but i was able to ssh to the devbox and even ping the DNAC IP (you can do this as you are now on the local network)

16:04:39 Errors reported during Setup for resource [DevBox-afece57a] 

If you try and curl the DNAC from the devbox you get refused, which seems to be the issue.

(py3venv) [developer@devbox ~]$ curl -v http://10.10.20.85
* About to connect() to 10.10.20.85 port 80 (#0)
*   Trying 10.10.20.85...
* Connection refused
* Failed connect to 10.10.20.85:80; Connection refused
* Closing connection 0
curl: (7) Failed connect to 10.10.20.85:80; Connection refused

[njccnp]

That's interesting. When I was connected, the DNAC and ISE were both unavailable via HTTP, and also neither was replying to pings. Those are the two devices I specifically remember trying.