Working with nxosv9k

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
horseinthesky
Posts: 21
Joined: Mon Mar 20, 2017 5:24 pm

Working with nxosv9k

Post by horseinthesky » Fri May 12, 2017 9:53 am

Hello
I've just started my acquaintance with nxosv9k image and i have a few issues with it:
1) If i would reboot the node which has some configuration it will boot into "loader>" and i can't get out of it.
I can only shutdown the node, wipe it and set "startup-config as exported". So i need to do it every time i begin working with my lab.
Is it possinble to make Nexus9K node boot correctly?
2) If i set node "startup-config as exported" and cfg has encrypter password:
username admin password 5 $5$CNKIEC$bH0I756andlTqDIttjJJRQv3LJei8JYA07VL9cWDmC6 role network-admin
i can't autenticate to the system: Login failed.
To fix it i need to manually change this string for every node to something like
username admin password <blablabla> role network-admin
How can i fix it once and for all.
3) I can't see any mac-addresses on any node/vlan/interface. Ping is working but mac-address tables are absolutely empty. How is that?
4) I've built a Back-to-Back vPC lab. Everything works fine until i brake something. (lab is in attachement)
For example i brake (shutdown) vPC peer-link on SW01. SW02 sees it and shuts down all vPC member ports (as it should). But now i have packet loss untill vPC peer-link is up again:
Router#ping 20.0.0.2 repeat 10000
Type escape sequence to abort.
Sending 10000, 100-byte ICMP Echos to 20.0.0.2, timeout is 2 seconds:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!....!!..!.!!.
!.!!!.!...!!!!!!...!!!!.!..!!!.!.!.!.!.!.!!!!!!.!...!...!.!..!!!!.!!.!
..!.!!..!...!!..!.!.!.!!!.!.!!!!.!.!!!!...!!!..!.!!..!.!!..!!..!!.!!.!
!!!..!!!.!..!.!!.!..!.!!!.........!!!.!!.!!.!.!!!!..!!...!!!..!..!!!..
.!........!!..!!..!..!....!!!..!!!!.!!!!..!!.
Why is that happen and how to fix it?
5) If i would completely shutdown SW01, SW02 will become "secondary, operational primary" and all traffic should go through it but instead i have no connectivity at all:
Router#ping 20.0.0.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 20.0.0.2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Image
You do not have the required permissions to view the files attached to this post.

Uldis (UD)
Posts: 5176
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Working with nxosv9k

Post by Uldis (UD) » Fri May 12, 2017 9:59 am

Before you post your bugs check how to section please

http://www.eve-ng.net/index.php/documen ... x9k-switch

horseinthesky
Posts: 21
Joined: Mon Mar 20, 2017 5:24 pm

Re: Working with nxosv9k

Post by horseinthesky » Fri May 12, 2017 11:15 am

Uldis (UD) wrote:
Fri May 12, 2017 9:59 am
Before you post your bugs check how to section please

http://www.eve-ng.net/index.php/documen ... x9k-switch
Ok, sorry. Didn't check it. 1 and 2 are fixed.
But where are mac-addresses and why is 4 to 5 behaves like this?

Uldis (UD)
Posts: 5176
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Working with nxosv9k

Post by Uldis (UD) » Sat May 13, 2017 11:29 pm

I tested your lab, but must modifiy initial configs, because if you do not add this before login, you cant login booted devices from your cfg:
no password strength-check

Next, your lab works.
Regarding issue 4, all nice no issues when shut peer keepalive link on SW1

and about point 5.:
But as we know that virtual nodes has no Layer 1 at all, this means your CSR router interface always is in UP/UP state, in real life it would be UP/DOWN if shuddown port e1/6 NX-SW1. But it is still in UP/UP.
If shutdown port G1 on CSR, your traffic runs to NX-SW2 nicely Output below when G1 on CSR is shutdown.

JUST keep in minds that virtual devices has not LAYER 1 physical status check !!!

as well bit modified your lab:

nexus access: admin/admin
You do not have the required permissions to view the files attached to this post.

horseinthesky
Posts: 21
Joined: Mon Mar 20, 2017 5:24 pm

Re: Working with nxosv9k

Post by horseinthesky » Sun May 14, 2017 8:23 am

Uldis (UD) wrote:
Sat May 13, 2017 11:29 pm
JUST keep in minds that virtual devices has not LAYER 1 physical status check !!!

as well bit modified your lab:

nexus access: admin/admin
Thank you for your time. I've tried to manually admin shutdown interfaces on working nodes but i guess qume is pretty bad to test Level2 features.

But i still don't understand why is there are no mac-addresses on any NXOS node?

Uldis (UD)
Posts: 5176
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Working with nxosv9k

Post by Uldis (UD) » Sun May 14, 2017 7:12 pm

In the mac address table it shows MAC where is ip address for keepalive e1/7 configured, same on all switches
You do not have the required permissions to view the files attached to this post.

horseinthesky
Posts: 21
Joined: Mon Mar 20, 2017 5:24 pm

Re: Working with nxosv9k

Post by horseinthesky » Sun May 14, 2017 8:07 pm

Uldis (UD) wrote:
Sun May 14, 2017 7:12 pm
In the mac address table it shows MAC where is ip address for keepalive e1/7 configured, same on all switches
And no Clients macs in VLAN10 and VLAN20

Uldis (UD)
Posts: 5176
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: Working with nxosv9k

Post by Uldis (UD) » Mon May 15, 2017 9:19 am

unfortunately its true, it is not eve bug but such image is from cisco...

Post Reply