topic Re: [Nexus 9000v]Mac addreses of network adapters donot match in Routing

[Nexus 9000v]Mac addreses of network adapters donot match

nsom — Tue, 02 May 2023 16:57:12 GMT

Hi I have deployed a cisco 9000v switch, By default while deploying the ova I got option of 6 network adapters, one connected to management pg, others I have connected to a port group that I created in dvs.
When I logged in to the switch and I check the mac addresses of the data ports like mgmt0,eth1/1,eth1/2, etc, only the mgmt0 mac address matches with the first network adapter in the vm settings page, the rest of the mac addresses should correspond to rest of the data ports staring from eth1/1, however that's not the case, I am not sure if it's expected or not.
I deployed switch on esxi host via vcenter client. Please find the screenshots of mismatching ports attached.
Just wanted to mention again only the first network adapter mac address matches with the mgm0 mac address in switch.
I couldn't find a dedicated doc for cisco 9000v deployment using vds(in the doc it is mentioned that it only works with standard vswitch which I guess is not correct)

Re: [Nexus 9000v]Mac addreses of network adapters donot match

pieterh — Tue, 30 May 2023 18:34:03 GMT

maybe I'm missing something, but I see only a single interface in your screenshot?
second: you have set the MAC-address as "automatic" so VMware may dynamically assign a mac address
try the command

show platform vnic mapped

last: I'm a little old-school: the second file is text-output,
so you could also post this as text (two-lines=160 bytes max. versus image=68Kbytes)

Re: [Nexus 9000v]Mac addreses of network adapters donot match

nsom — Tue, 30 May 2023 18:37:16 GMT

The mac ip of the port eth1/1



switch# show int eth1/1
Ethernet1/1 is up
admin state is up, Dedicated Interface
Hardware: 100/1000/10000 Ethernet, address: 0050.569b.a212 (bia 0050.569b.a212)

Now as per the 9000v doc, the interface adapters shown in the edit settings of the cisco switch on vcenter page. the screenshot that I attached, should map in sequential order with the mac addreses of the eth ports of the switch, i.e
network-adapter2 should be mapped to eth1/1 and so on and so forth.
network-adpater1 mac addreses matches with the mgmt0 port as I already mentioned.

how do I know which eth ports actually correspond to the interface adapters shown in vcenter.
show platform command doesn't exist when I try to run it on the switch.



switch(config)# show platform
^
% Invalid command at '^' marker.

Re: [Nexus 9000v]Mac addreses of network adapters donot match

pieterh — Tue, 09 May 2023 10:23:01 GMT

I know on nexus, many show commands are accepted in config mode
but still I'd first try the command NOT in config mode

Re: [Nexus 9000v]Mac addreses of network adapters donot match

nsom — Tue, 30 May 2023 18:38:48 GMT

The output is same for both, I have tried that out first before posting it here.


switch# show platform
^
% Invalid command at '^' marker.

This data is from cisco 9000v doc
```
The Cisco Nexus 9000v uses vNICs that are entered from the KVM/QEMU command line or from the GUI on ESXi for networking either externally or internally within a hypervisor server. The first NIC is always used as the Cisco Nexus 9000v management interface. The subsequence NICs are used as data Cisco Nexus 9000v Guide, Release 9.3(x) 4 Cisco Nexus 9000v Cisco Nexus 9000v Guidelines and Limitations ports as e1/1, e1/2, ... e1/9.
```
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/93x/nx-osv/configuration/guide/b-cisco-nexus-9000v-guide-93x.pdf

Re: [Nexus 9000v]Mac addreses of network adapters donot match

nsom — Tue, 09 May 2023 13:02:25 GMT

My concern here is why these addresses donot match, and if they don't would it impact the connectivity of the 9000v switch with the nested esxi hosts I ma trying to connect to.

Re: [Nexus 9000v]Mac addreses of network adapters donot match

nsom — Tue, 30 May 2023 18:39:20 GMT

I was able to solve the issue by mentioning the vmk interface through which I was trying to achieve the ping.
I would really like to thank wonderful folks out here to provide their valuable suggestions

[root@esxi-nested-04:~] ping 192.168.20.1 -I vmk1

PING 192.168.20.1 (192.168.20.1): 56 data bytes

64 bytes from 192.168.20.1: icmp_seq=0 ttl=255 time=0.985 ms