Thanks Tom, let me step through this. I reserved my lab (same as yours) and connected the sandbox. Then from my shell on my mac, i connected to the jumphost/devbox.   You can see from the home directory, i see the same as you. Welcome to the Open NX-OS Sandbox You can find sample code and information in the GitHub Repo at: https://github.com/DevNetSandbox/sbx_nxos This repo has been cloned to this devbox at the directory: cd ~/code/sbx_nxos A Python 3.6 virtual environment with relevant moduels is available by activating with: source ~/code/sbx_nxos/venv/bin/activate [developer@devbox ~]$virl ls --all Running Simulations ╒══════════════╤══════════╤════════════════════════════╤═══════════╕ │ Simulation │ Status │ Launched │ Expires │ ╞══════════════╪══════════╪════════════════════════════╪═══════════╡ │ ~jumphost │ ACTIVE │ 2018-08-02T19:21:08.764190 │ │ ╘══════════════╧══════════╧════════════════════════════╧═══════════╛ [developer@devbox ~]$ First enable the venv environment and the move the code folder, then the sbx folder as per the instruction from login. In this folder you can see the topology.virl file, however as we have not brought up the topology we see nothing on the virl nodes or virl ls [developer@devbox ~]$ls code Desktop sync_log.txt sync_version thinclient_drives venv [developer@devbox ~]$source venv/bin/activate (venv) [developer@devbox ~]$cd code/sbx_nxos/ (venv) [developer@devbox sbx_nxos]$ls ansible-playbooks guestshell learning_labs LICENSE nx-api other pull-requests.md readme_images README.md requirements.txt sbx-mgmt topology.virl venv (venv) [developer@devbox sbx_nxos]$ (venv) [developer@devbox sbx_nxos]$virl nodes Environment default is not running (venv) [developer@devbox sbx_nxos]$virl ls Running Simulations ╒══════════════╤══════════╤════════════╤═══════════╕ │ Simulation │ Status │ Launched │ Expires │ ╞══════════════╪══════════╪════════════╪═══════════╡ ╘══════════════╧══════════╧════════════╧═══════════╛ (venv) [developer@devbox sbx_nxos]$ To bring up the nexus/topology issue virl up from this directory (that last part is very important! Once you do that we can see our nexus devices, at this stage these are building. It will take around 5 - 10 mins to bring up the devices, the might show as active, but these do take time and if you logged in with the virl console (for example virl console nx-osv9000-1, you would see the device starting up)   (venv) [developer@devbox sbx_nxos]$virl up Creating default environment from topology.virl (venv) [developer@devbox sbx_nxos]$virl ls Running Simulations ╒═════════════════════════╤══════════╤════════════════════════════╤═══════════╕ │ Simulation │ Status │ Launched │ Expires │ ╞═════════════════════════╪══════════╪════════════════════════════╪═══════════╡ │ sbx_nxos_default_0jlb6i │ ACTIVE │ 2019-09-08T16:38:48.800535 │ │ ╘═════════════════════════╧══════════╧════════════════════════════╧═══════════╛ (venv) [developer@devbox sbx_nxos]$virl nodes Here is a list of all the running nodes ╒══════════════╤═════════════╤═════════╤═════════════╤════════════╤══════════════════════╤════════════════════╕ │ Node │ Type │ State │ Reachable │ Protocol │ Management Address │ External Address │ ╞══════════════╪═════════════╪═════════╪═════════════╪════════════╪══════════════════════╪════════════════════╡ │ nx-osv9000-1 │ NX-OSv 9000 │ ABSENT │ N/A │ N/A │ N/A │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-2 │ NX-OSv 9000 │ ABSENT │ N/A │ N/A │ N/A │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-3 │ NX-OSv 9000 │ ABSENT │ N/A │ N/A │ N/A │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-4 │ NX-OSv 9000 │ ABSENT │ N/A │ N/A │ N/A │ N/A │ ╘══════════════╧═════════════╧═════════╧═════════════╧════════════╧══════════════════════╧════════════════════╛   (venv) [developer@devbox sbx_nxos]$virl console nx-osv9000-1 Attempting to connect to console of nx-osv9000-1 Trying 10.10.20.160... Connected to 10.10.20.160. Escape character is '^]'. 2019 Sep 8 16:41:49 %$ VDC-1 %$ netstack: Registration with cli server complete 2019 Sep 8 16:42:04 %$ VDC-1 %$ %USER-2-SYSTEM_MSG: ssnmgr_app_init called on ssnmgr up - aclmgr 2019 Sep 8 16:42:04 %$ VDC-1 %$ %VMAN-2-INSTALL_STATE: Installing virtual service 'guestshell+' 2019 Sep 8 16:42:13 %$ VDC-1 %$ %USER-0-SYSTEM_MSG: end of default policer - copp 2019 Sep 8 16:42:13 %$ VDC-1 %$ %COPP-2-COPP_NO_POLICY: Control-plane is unprotected. 2019 Sep 8 16:42:15 %$ VDC-1 %$ %CARDCLIENT-2-FPGA_BOOT_GOLDEN: IOFPGA booted from Golden 2019 Sep 8 16:42:15 %$ VDC-1 %$ %CARDCLIENT-2-FPGA_BOOT_STATUS: Unable to retrieve MIFPGA boot status Now we can see the nexus are active   (venv) [developer@devbox sbx_nxos]$virl nodes Here is a list of all the running nodes ╒══════════════╤═════════════╤═════════╤═════════════╤════════════╤══════════════════════╤════════════════════╕ │ Node │ Type │ State │ Reachable │ Protocol │ Management Address │ External Address │ ╞══════════════╪═════════════╪═════════╪═════════════╪════════════╪══════════════════════╪════════════════════╡ │ nx-osv9000-1 │ NX-OSv 9000 │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.101 │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-2 │ NX-OSv 9000 │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.102 │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-3 │ NX-OSv 9000 │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.103 │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-4 │ NX-OSv 9000 │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.104 │ N/A │ ╘══════════════╧═════════════╧═════════╧═════════════╧════════════╧══════════════════════╧════════════════════╛ (venv) [developer@devbox sbx_nxos]$ (venv) [developer@devbox sbx_nxos]$ping 172.16.30.101 PING 172.16.30.101 (172.16.30.101) 56(84) bytes of data. 64 bytes from 172.16.30.101: icmp_seq=1 ttl=254 time=1.72 ms 64 bytes from 172.16.30.101: icmp_seq=2 ttl=254 time=1.79 ms 64 bytes from 172.16.30.101: icmp_seq=3 ttl=254 time=1.80 ms 64 bytes from 172.16.30.101: icmp_seq=4 ttl=254 time=1.78 ms 64 bytes from 172.16.30.101: icmp_seq=5 ttl=254 time=1.75 ms ^C --- 172.16.30.101 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 1.726/1.773/1.806/0.047 ms From here we can access these a few ways, ssh via virl (venv) [developer@devbox sbx_nxos]$virl ssh nx-osv9000-1 Attemping ssh connectionto nx-osv9000-1 at 172.16.30.101 Warning: Permanently added '172.16.30.101' (RSA) to the list of known hosts. User Access Verification Password: Cisco NX-OS Software Copyright (c) 2002-2018, Cisco Systems, Inc. All rights reserved. [removed] nx-osv9000-1# Or from ssh from my terminal on my deskstop/mac   STUACLAR-M-R6EU:~ stuaclar$ ssh cisco@172.16.30.101 The authenticity of host '172.16.30.101 (172.16.30.101)' can't be established. RSA key fingerprint is SHA256:iyOorfieUeJoKFz1dgCtW+2/euXC0SDhj2Xep3eEdqc. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added '172.16.30.101' (RSA) to the list of known hosts. User Access Verification Password: Cisco NX-OS Software Copyright (c) 2002-2018, Cisco Systems, Inc. All rights reserved. Nexus 9000v software ("Nexus 9000v Software") and related documentation, [removed] nx-osv9000-1# The same steps can be followed for the other devices. ... View more

Thanks Tom, That link takes me to my reservation page oddly - can you name the sandbox and copy the url from here please - https://devnetsandbox.cisco.com/RM/Topology   Thanks! ... View more

Tom, could you share the link to the sandbox you are reserving please, let me see if I can replicate and as we have a few Nexus based sandbox want to ensure I am checking the same one you are.    Thanks! ... View more

Hey Fred, per reply in our devnet support team space. dCloud has this image, our multi-ios virl sandbox will be upgraded to v19.2 .x soon, but i do not have a firm date for this as of yet.   Hope this helps. ... View more

Hey Andy,   Seeing unreachable, is a red herring, this was a known bug in older versions (one i saw often on this lab), i am not sure what causes the test to fail.   The IP address are created dynamically (unless other wise configured), you will see on your virl file    {{ gateway }} - will be replaced with the default gateway of the flat network More details here --> https://developer.cisco.com/codeexchange/github/repo/CiscoDevNet/virlutils/   Some ideas/questions   Via the virl console - check the running configuration for the device IP address and gateway are correct For usernames is this your topology or the four node Nexus one please, check the configuration, as you know console can have a different username/password for console access (you are correct ssh should be cisco/cisco) One issue we have here, i cannot see your virl topology which makes troubleshooting hard as we could be looking at unknown issues, if we can stick to the four node Nexus one - i can check this with you and we can ensure the instructions, build is  correct. If you want to keep importing you own devices use this sandbox please as it runs newer versions of the Nexus code --> https://devnetsandbox.cisco.com/RM/Diagram/Index/6b023525-4e7f-4755-81ae-05ac500d464a?diagramType=Topology   Thanks! ... View more

Geoffrey, i spoke with the ENT team on accessing GitHub from the devbox and outbound access. The response is as follows: "DevNet Sandbox is currently assessing the security posture of key sandboxes, in order to keep them available and useful to the whole community. This assessment is an ongoing process. Requirements from the community are being taken into account and will be folded into this continuity work in the coming weeks.” Hope this helps. ... View more

No problem let me reply inline to each question   How do I access the virl console? You can do this from the devbox/jumphost in sandbox with:  virl console [device name] You said you "enabled the venv". What does that mean, what is it's purpose and how do I enable this?   Virtualenv is a tool that lets you create an isolated Python environment for your project. It creates an environment that has its own installation directories, that doesn’t share dependencies with other virtualenv environments (and optionally doesn’t access the globally installed dependencies either). You can even configure what version of Python you want to use for each individual environment. It's very much recommended to use virtualenv when dealing with Python applications.   Why did you have to move to the following directory?   To bring up (with virl up command) the topology of Nexus switches (which is a topology.virl) this is with that directory. You do not have to do this btw - Once you find an interesting topology, you can either pull the topology into your current environment or launch it directly pull topology to local directory (as topology.virl)   Why didn't bouncing the lab bring my nodes up?   Maybe because of the above reason, you need to be in the directory of the topology.virl file. When you ran the `virl ls --all` you are looking in all directory's as the `--all` will do that. Think of adding the `--all` as a global search function.   From what i can see though - you have built your own topology, this is fine - but you might want to try the built in one to get familiar with how this works or your are troubleshooting learning bringing up new topology's as well as mastering how this works.   Hope this helps, let me know otherwise   ... View more

I reserved the NXOS virl lab just now, here is the outputs, i ssh'd into the devbox/jump host, enabled the venv and moved to the following directory - from there, i issues the virl up command and the network came up   (venv) [developer@devbox sbx_nxos]$pwd /home/developer/code/sbx_nxos   (venv) [developer@devbox sbx_nxos]$virl nodes Here is a list of all the running nodes ╒══════════════╤═════════════╤═════════╤═════════════╤════════════╤══════════════════════╤════════════════════╕ │ Node │ Type │ State │ Reachable │ Protocol │ Management Address │ External Address │ ╞══════════════╪═════════════╪═════════╪═════════════╪════════════╪══════════════════════╪════════════════════╡ │ nx-osv9000-1 │ NX-OSv 9000 │ ACTIVE │ UNREACHABLE │ telnet │ 172.16.30.101 │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-2 │ NX-OSv 9000 │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.102 │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-3 │ NX-OSv 9000 │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.103 │ N/A │ ├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤ │ nx-osv9000-4 │ NX-OSv 9000 │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.104 │ N/A │ ╘══════════════╧═════════════╧═════════╧═════════════╧════════════╧══════════════════════╧════════════════════╛ I can ping the devices and ssh to them ok   (venv) [developer@devbox sbx_nxos]$ping 172.16.30.102 PING 172.16.30.102 (172.16.30.102) 56(84) bytes of data. 64 bytes from 172.16.30.102: icmp_seq=1 ttl=254 time=1.71 ms 64 bytes from 172.16.30.102: icmp_seq=2 ttl=254 time=2.10 ms ^C --- 172.16.30.102 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 1.710/1.905/2.101/0.200 ms (venv) [developer@devbox sbx_nxos]$virl ssh nx-osv9000-2 Attemping ssh connectionto nx-osv9000-2 at 172.16.30.102 Warning: Permanently added '172.16.30.102' (RSA) to the list of known hosts. User Access Verification Password: Cisco NX-OS Software Copyright (c) 2002-2018, Cisco Systems, Inc. All rights reserved. [removed] http://www.gnu.org/licenses/lgpl.html *************************************************************************** * Nexus 9000v is strictly limited to use for evaluation, demonstration * * and NX-OS education. Any use or disclosure, in whole or in part of * * the Nexus 9000v Software or Documentation to any third party for any * * purposes is expressly prohibited except as otherwise authorized by * * Cisco in writing. * *************************************************************************** nx-osv9000-2# I noticed in your last post you only have three switches now? This does not look like the open NX-OS lab on virl, which sandbox is this now please?   Thanks! ... View more

Thanks for the update - using virlutil - destroy the topology and relaunch it (you can do this with virl down) or you can also stop/start the switches on their own, they get stuck in booting sometimes - the best way to check this is virl console btw.   HTH   ... View more

Thanks, i am speaking with the Sandbox engineering team now for you to see what the alternative is here. Please standby. Thank you. ... View more

Hey there, if you can advise on which sandbox you are seeing this issue - it can be raised with our engineering team. As you noted the  internet access policy within our sandbox reservation instances has undergone some changes.   Hope this helps. ... View more

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? ... View more

For the always on SBX you can only access the ports that are open these are detailed in the instruction per sandbox, for example you would connect like   (venv) STUACLAR-M-R6EU:~ stuaclar$ ssh developer@ios-xe-mgmt-latest.cisco.com -p 8181 Password: Welcome to the DevNet Sandbox for CSR1000v and IOS XE The following programmability features are already enabled: - NETCONF - RESTCONF Thanks for stopping by. csr1000v-1>en Password: csr1000v-1# Hope that helps. :) ... View more

You should be able to reach the switches on their mgmt IP address from your local machine and the centos/devbox in the sandbox. They do take a while to load up btw. This sandbox is build using virlutils - https://github.com/CiscoDevNet/virlutils when you are on the centos/devbox you can issue the virl commands to see the status, from the centos/devbox you can also use the console access.   HTH ... View more

Leo, what part are you stuck with please - can you share the error you are seeing? You can share this issue with us in the devnet webex team space for a quicker reply should you need https://developer.cisco.com/site/spark-chat/   Cheers! ... View more