cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
286
Views
0
Helpful
3
Replies
Highlighted
Beginner

How does VMware assign vmnic labels to Cisco UCS blade servers?

I have around 10 UCS B200M4 blades in a VMware cluster. They all use the following setup for networking in VMware:

 

Local dvSwitch:

Management: vmnic4 & vmnic5

 

Distributed dvSwitch:

Storage: vmnic1 & vmnic3

Data: vmnic0 & vmnic2

 

In UCS Manager, the NICs above are configured as follows:

MLOM NIC 1 = ESXi_Data_A

MLOM NIC 2 = MGT_B

MLOM NIC 3 = STO_A

VIC NIC 1 = ESXi_Data_B

VIC NIC 2 = MGT_A

VIC NIC 3 = STO_B

 

I added a new blade to the chassis, B200M4, created a Service Profile from the same template as the existing servers, yet I got the following configuration:

 

Local dvSwitch:

Management: vmnic1 & vmnic4

 

Distributed dvSwitch:

Storage: vmnic2 & vmnic5

Data: vmnic0 & vmnic3

 

In UCS Manager, the NICs above are configured as follows:

MLOM NIC 1 = ESXi_Data_A

MLOM NIC 2 = MGT_B

MLOM NIC 3 = STO_A

VIC NIC 1 = ESXi_Data_B

VIC NIC 2 = MGT_A

VIC NIC 3 = STO_B

 

Ideally I wanted the new server to use the same "vmnic" labels in the respective switches, as in the other hosts, but for some reason, it seems that the NICs were presented to VMware in a different order and thus given different vmnic labels.

 

I'd like to understand what I did wrong and how I can avoid this in the future?

Everyone's tags (3)
3 REPLIES 3
Cisco Employee

Re: How does VMware assign vmnic labels to Cisco UCS blade servers?

Hello JDMills,

You have done nothing wrong. This has been a known issue where vnics on ESXi host are mismatched from UCSM Service profile. We do have a bug filed for this: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuv34051
You can try the workarounds, but we have found that those workaround aren't always successful. Reinstalling the OS has a better success rate on resolving this issue. Cisco and VMWare have worked on resolving this issue, but due to the nature of how UCSM presents the vnics and how ESXi determines the vnic naming, we have yet to resolve this issue.
Here is a KB article by VMWare on how VMware ESXi determines the order in which names are assigned to devices: https://kb.vmware.com/s/article/2091560

-Josh
Beginner

Re: How does VMware assign vmnic labels to Cisco UCS blade servers?

Thank you Josh, your reply was very helpful.

Beginner

Re: How does VMware assign vmnic labels to Cisco UCS blade servers?

Just for information. I encountered this issue also on a B200M5 with 3.2(3j).

The issue is also depending on the Board Controller Firmware.

In my case I have 2 versions. v11 and v12. The reason for that is that 3.2(3j) is released with v11 but newer UCS blades came with v12.

 

When you install ESXi on a v11 Board Controller version you get the following order:

 

vHBA1 -> vmhba0

onboard SATA controller -> vmhba1

vHBA2 -> vmhba2

 

With a v12 version you get this:

onboard SATA controller -> vmhba0

vHBA1 -> vmhba1

vHBA2 -> vmhab2

 

Although all PCU bus addresses are the same it will be discovered for whatever reason differently depending on the Onboard Controller firmware version.

 

Cheers,

Fred

CreatePlease to create content
Content for Community-Ad
August's Community Spotlight Awards