Open NX-OS with Nexus 9Kv, no VIRL nodes

ivoalmeida — Wed, 10 Jun 2020 14:26:16 GMT

Hi,

I can't reach any of the NX-OSv9K switches in my lab.

VIRL is up and running

(venv) [developer@devbox sbx_nxos]$virl up
Sim sbx_nxos_default_eYUKKV already running

but I can't see any virl nodes:

(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   │
╞════════╪════════╪═════════╪═════════════╪════════════╪══════════════════════╪════════════════════╡
╘════════╧════════╧═════════╧═════════════╧════════════╧══════════════════════╧════════════════════╛

And VIRL logs gives an error:

(venv) [developer@devbox sbx_nxos]$virl logs
Exception raised while running your command
Please open an issue and provide this info:
404 Client Error: Simulation "sbx_nxos_default_eYUKKV" not found. for url: http://10.10.20.160:19399/simengine/rest/events/sbx_nxos_default_eYUKKV

Off course I'm unable to reach them from from the DevBox:

(venv) [developer@devbox sbx_nxos]$ping 172.16.30.102
PING 172.16.30.102 (172.16.30.102) 56(84) bytes of data.
From 10.10.20.160 icmp_seq=1 Destination Host Unreachable
From 10.10.20.160 icmp_seq=2 Destination Host Unreachable
From 10.10.20.160 icmp_seq=3 Destination Host Unreachable

Regards

Re: Open NX-OS with Nexus 9Kv, no VIRL nodes

bigevilbeard — Wed, 10 Jun 2020 16:50:49 GMT

Have a look at this thread - same issue, https://community.cisco.com/t5/devnet-sandbox/open-nx-os-with-nexus-9kv-unable-to-reach-any-nx-osv9k/td-p/3954109

Re: Open NX-OS with Nexus 9Kv, no VIRL nodes

ivoalmeida — Wed, 10 Jun 2020 17:08:56 GMT

Already had, and followed the instructions.

But I still can't start the virl nodes 😞

Re: Open NX-OS with Nexus 9Kv, no VIRL nodes

bigevilbeard — Fri, 12 Jun 2020 16:14:07 GMT

I just grabbed a reservation now.

[developer@devbox ~]$ls
code  Desktop  Downloads  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  virl.log

(venv) [developer@devbox sbx_nxos]$virl ls --all
Running Simulations
╒═════════════════════════╤══════════╤════════════════════════════╤═══════════╕
│ Simulation              │ Status   │ Launched                   │ Expires   │
╞═════════════════════════╪══════════╪════════════════════════════╪═══════════╡
│ sbx_nxos_default_03dH7f │ ACTIVE   │ 2020-06-12T16:03:25.812234 │           │
├─────────────────────────┼──────────┼────────────────────────────┼───────────┤
│ ~jumphost               │ ACTIVE   │ 2018-08-02T19:21:08.764190 │           │
╘═════════════════════════╧══════════╧════════════════════════════╧═══════════╛

(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]$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=2.31 ms
64 bytes from 172.16.30.101: icmp_seq=2 ttl=254 time=2.17 ms
^C
--- 172.16.30.101 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 2.171/2.242/2.314/0.085 ms
(venv) [developer@devbox sbx_nxos]$

I would tear down the reservation you have, make a new one and follow the above - you should see the same. Beware it does take a little bit for the devices to build. I did not have to virl up at all here, as this should pre-load and bring up the devices.

Hope this helps.

topic Re: Open NX-OS with Nexus 9Kv, no VIRL nodes in DevNet Sandbox

Open NX-OS with Nexus 9Kv, no VIRL nodes

Re: Open NX-OS with Nexus 9Kv, no VIRL nodes

Re: Open NX-OS with Nexus 9Kv, no VIRL nodes

Re: Open NX-OS with Nexus 9Kv, no VIRL nodes