Open NX-OS with Nexus 9Kv - Unable to reach any NX-OSV9K

[pdeoleo]

I can't reach none of the NX-OSv9K switches in my lab. I'm unable to reach them from my own computer (using AnyConnect VPN) or from the DevBox through a SSH connection.

[developer@devbox ~]$ping 172.16.30.101
PING 172.16.30.101 (172.16.30.101) 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

[bigevilbeard · Accepted solution]

I am sorry to hear you are having an issue with this lab, allow me to help. Change your directory to code/sbx_nxos

(venv) [developer@devbox ~]$cd code/sbx_nxos/
(venv) [developer@devbox sbx_nxos]$pwd
/home/developer/code/sbx_nxos

From here you can access the learning labs

(venv) [developer@devbox sbx_nxos]$cd learning_labs/
(venv) [developer@devbox learning_labs]$ls
LM-1451 intro-ansible  LM-5601 intro-nxos  poap  README.md  telemetry  yang

Bonus tip! Check to see if your switches are online

(venv) [developer@devbox learning_labs]$cd .
(venv) [developer@devbox sbx_nxos]$pwd
/home/developer/code/sbx_nxos
(venv) [developer@devbox learning_labs]$virl ls --all
Running Simulations
╒══════════════╤══════════╤════════════════════════════╤═══════════╕
│ Simulation   │ Status   │ Launched                   │ Expires   │
╞══════════════╪══════════╪════════════════════════════╪═══════════╡
│ ~jumphost    │ ACTIVE   │ 2018-08-02T19:21:08.764190 │           │
╘══════════════╧══════════╧════════════════════════════╧═══════════╛

You will a file 'topology.virl' here, you need to `virl up` from this folder

(venv) [developer@devbox sbx_nxos]$virl up
Creating default environment from topology.virl
(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 │ BUILDING │ N/A         │ N/A        │ N/A                  │ N/A                │
├──────────────┼─────────────┼──────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤
│ nx-osv9000-2 │ NX-OSv 9000 │ BUILDING │ N/A         │ N/A        │ N/A                  │ N/A                │
├──────────────┼─────────────┼──────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤
│ nx-osv9000-3 │ NX-OSv 9000 │ BUILDING │ N/A         │ N/A        │ N/A                  │ N/A                │
├──────────────┼─────────────┼──────────┼─────────────┼────────────┼──────────────────────┼────────────────────┤
│ nx-osv9000-4 │ NX-OSv 9000 │ BUILDING │ N/A         │ N/A        │ N/A                  │ N/A                │
╘══════════════╧═════════════╧══════════╧═════════════╧════════════╧══════════════════════╧════════════════════╛

Warning, this can take a little time! Pro tip: Coffee time! When this is ready, all nodes will say 'reachable' you can ping these. You can also ssh and console into the Nexus.

(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.91 ms
64 bytes from 172.16.30.101: icmp_seq=2 ttl=254 time=1.72 ms
^C
--- 172.16.30.101 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 1.722/1.818/1.915/0.105 ms
(venv) [developer@devbox sbx_nxos]

(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:
Aborted!

(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 '^]'.

nx-osv9000-1#

Hope this helps! :)

[pdeoleo]

Thakns A LOT. I think this is all I needed for learning ansible.

[pfyffe361]

I have been experiencing the same issue as described here. When I implement the solution indicated I get the attached erro, exception raised while running your command.

[bigevilbeard]

@pfyffe361 what command are you running please? It looks like you are trying to use a git pull?