WuGeDe
Enthusiast
Enthusiast

FC HBA storage adapter listed twice?

Hello guys

I have an ESXi where my FC HBA is listed as vmhba0 and vmhba1 and also a second time as vmhba64 and vmhba65.

Why is that the case?

Please have a look at my attached pictures.

ESXi is running 7.0.1, 17551050 and vcsa is 7.01 17327586

Thank you much for help!

WuGeDe_0-1614177252539.pngWuGeDe_1-1614177305576.png

 

Tags (2)
0 Kudos
7 Replies
a_p_
Leadership
Leadership

Has the host been upgraded recently, then you may have hit a known issue. Although it is possible to fix this using appropriate commands (not officially supported), it's recommended that you open a support case to have it fixed.

André

0 Kudos
WuGeDe
Enthusiast
Enthusiast

Hello @a_p_ 

Yes I patched this host to the latest patches / updates via Lifecycle Manager.

0 Kudos
a_p_
Leadership
Leadership

What I'm thinking of is the issue discussed at https://communities.vmware.com/t5/VMware-vSAN-Discussions/Strange-device-controller-phenomenon-after...

Again, in case that's it, then rather than trying to fix the issue yourself, consider to open a support case with VMware.

André

0 Kudos
WuGeDe
Enthusiast
Enthusiast

Yes @a_p_  I found that vmware KB2127274 also. But it only refers to versions prior to 6.7.

If I look at my esx.conf file I can not find these duplicate entries there mentioned in the KB.

I opened a case and if I got a solution post it here.

0 Kudos
a_p_
Leadership
Leadership

That's why I pointed you to the other discussion. With vSphere 7 some settings are now stored in the ConfigStore rather than the esx.conf file.

André

0 Kudos
WuGeDe
Enthusiast
Enthusiast

Yes you are right. I agree.

0 Kudos
WuGeDe
Enthusiast
Enthusiast

Here is the answer I got on my case:

Below is the reply from our engineering team:

This is expected for qlnativefc driver. qlnativefc driver uses one port to support scsi and nvme device. It will create NVMe adapter and scsi adapter for same port.
The wwnn and wwpn are same for NVMe and SCSI adapter,  

vmhba3 qlnativefc_unstablelink-up fc.2000f4e9d454acac:2100f4e9d454acac (0000:05:00.0) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter
vmhba4 qlnativefc_unstablelink-up fc.2000f4e9d454acad:2100f4e9d454acad (0000:05:00.1) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter
vmhba5 qlnativefc_unstablelink-up fc.20000024ff54a464:21000024ff54a464  (0000:85:00.0) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA
vmhba6 qlnativefc_unstablelink-up fc.20000024ff54a465:21000024ff54a465  (0000:85:00.1) QLogic Corp ISP2532-based 8Gb Fibre Channel to PCI Express HBA 
vmhba64 qlnativefc_unstablelink-up fc.2000f4e9d454acac:2100f4e9d454acac (0000:05:00.0) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter
vmhba65 qlnativefc_unstablelink-up fc.2000f4e9d454acad:2100f4e9d454acad (0000:05:00.1) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter

If you don't want to use NVMe device, it can set parameter as:

$esxcfg-module -s 'ql2xnvmesupport=0' qlnativefc
$reboot

It will disable nvme adapter.

 

0 Kudos