Unable see nodes in my virl simulation and change directory to code/sbx_nxos/

[thavall000]

Unable see nodes in my virl simulation and change directory to code/sbx_nxos/.

can someone help.

Logs:

(venv) [developer@devbox ~]$virl ls --all
Running Simulations
╒═══════════════════════════╤══════════╤════════════════════════════╤═══════════╕
│ Simulation │ Status │ Launched │ Expires │
╞═══════════════════════════╪══════════╪════════════════════════════╪═══════════╡
│ datacenter_default_VUYJve │ ACTIVE │ 2020-06-14T21:34:37.960539 │ │
├───────────────────────────┼──────────┼────────────────────────────┼───────────┤
│ spanningtree │ ACTIVE │ 2020-06-15T01:19:41.326731 │ │
├───────────────────────────┼──────────┼────────────────────────────┼───────────┤
│ ~jumphost │ ACTIVE │ 2020-06-14T21:34:39.580440 │ │
╘═══════════════════════════╧══════════╧════════════════════════════╧═══════════╛
(venv) [developer@devbox ~]$virl nodes
Environment default is not running
(venv) [developer@devbox ~]$

(venv) [developer@devbox ~]$virl nodes
Environment default is not running
(venv) [developer@devbox ~]$virl up
Pulling from default
Error pulling default - repo not found
Pulling from default
Error pulling default - repo not found
Pulling from default
^C
Aborted!

Aborted!
(venv) [developer@devbox ~]$

(venv) [developer@devbox ~]$cd code/sbx_nxos/
-bash: cd: code/sbx_nxos/: No such file or directory
(venv) [developer@devbox ~]$ls
Desktop Downloads sd-wan-ansible-pipeline-code sync_log.txt sync_version thinclient_drives venv virlfiles virl.log virl-renew virlutils
(venv) [developer@devbox ~]$

[bigevilbeard]

Hey there,

Two issues here, both are separate.

Running virl ls --all will show you all the simulations running over ALL folders, this of this as a global command. Therefore each simulation is running within a folder/directory, hence when you run virl nodes you are running a local folder command. There is no need to perform virl up and again this will not work as there is no .virl file within the folder you are in. I would check in the Download folder and look for a virl file called topology.virl 

If you are using Multi-IOS Sandbox the the folder/code `sbx_nxos` is not there on this sandbox Open NX-OS on VIRL 

Hope this helps.

[CSCO11744899]

Hi

I am having the same problem:

(venv) [developer@devbox virl_sbx_mgmt]$virl ls --all
Running Simulations
╒════════════════╤══════════╤════════════════════════════╤═══════════╕
│ Simulation │ Status │ Launched │ Expires │
╞════════════════╪══════════╪════════════════════════════╪═══════════╡
│ ansible_part_3 │ ACTIVE │ 2021-04-04T09:06:47.442211 │ │
╘════════════════╧══════════╧════════════════════════════╧═══════════╛

(venv) [developer@devbox virl_sbx_mgmt]$virl nodes ansible_part_3
Environment ansible_part_3 is not running

Please help

Regards,

Andon

[bigevilbeard]

You need to

cd ~/code/sbx_nxos
source ~/code/sbx_nxos/venv/bin/activate
virl up

You can run (note to does take sometime for the devices to show as 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  │ UNREACHABLE │ 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                │
╘══════════════╧═════════════╧═════════╧═════════════╧════════════╧══════════════════════╧════════════════════╛

[CSCO11744899]

That is fine for the standard topology.

I was asking for a specific one which I ran as per this course https://developer.cisco.com/video/net-prog-basics/05-netdevops.

See attached virl file.

I did find the workaround though.

I have used the command:

cml use ansible_part_3

and then virl nodes worked correctly.

So it may be me not knowing how to work with cml and virl.

Here is a list of all the running nodes
(py3venv) [developer@devbox virl_sbx_mgmt]$ virl nodes
╒══════════════╤═════════════╤═════════╤═════════════╤════════════╤══════════════════════╤════════════════════╕
│ Node │ Type │ State │ Reachable │ Protocol │ Management Address │ External Address │
╞══════════════╪═════════════╪═════════╪═════════════╪════════════╪══════════════════════╪════════════════════╡
│ ios-xev-1 │ CSR1000v │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.111 │ N/A │
├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤
│ ios-xev-2 │ CSR1000v │ ACTIVE │ REACHABLE │ telnet │ 172.16.30.112 │ N/A │
├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤
│ 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 │
├──────────────┼─────────────┼─────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤
│ ~mgmt-lxc │ mgmt-lxc │ ACTIVE │ REACHABLE │ ssh │ 172.16.30.105 │ 172.16.30.106 │
╘══════════════╧═════════════╧═════════╧═════════════╧════════════╧══════════════════════╧════════════════════╛

(py3venv) [developer@devbox virl_sbx_mgmt]$ virl ls
Running Simulations
╒══════════════╤══════════╤════════════╤═══════════╕
│ Simulation │ Status │ Launched │ Expires │
╞══════════════╪══════════╪════════════╪═══════════╡
╘══════════════╧══════════╧════════════╧═══════════╛
(py3venv) [developer@devbox virl_sbx_mgmt]$ virl ls --all
Running Simulations
╒════════════════╤══════════╤════════════════════════════╤═══════════╕
│ Simulation │ Status │ Launched │ Expires │
╞════════════════╪══════════╪════════════════════════════╪═══════════╡
│ ansible_part_3 │ ACTIVE │ 2021-04-05T09:13:37.855187 │ │
╘════════════════╧══════════╧════════════════════════════╧═══════════╛

I hope that will help others.

Regards,

Andon