This article provides information that this is an expected behavior
qlnativefc
driver shows the same WWNN
and WWPN
for both NVMe
and SCSI
adapters in FC HBA devices, leading to what appears to be duplicate entries for HBAs.ocalcli storage core adapter list
command shows following output: # localcli storage core adapter list
vmhba3 qlnativefc_unstablelink-up fc.xxxxxxxxxxxxacac:xxxxxxxxxxxxacac (xxxx:xx:xx.0) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter
vmhba4 qlnativefc_unstablelink-up fc.yyyyyyyyyyyyacad:yyyyyyyyyyyyacad (yyyy:yy:yy.1) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter
vmhba64 qlnativefc_unstablelink-up fc.xxxxxxxxxxxxacac:xxxxxxxxxxxxacac (xxxx:xx:xx.0) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter
vmhba65 qlnativefc_unstablelink-up fc.yyyyyyyyyyyyacad:yyyyyyyyyyyyacad (yyyy:yy:yy.1) QLogic Corp QLE2772 Dual Port 32GFC PCIe Gen4 x8 Adapter
vmhba3
and vmhba4
are SCSI adapters vmhba64
and vmhba65
are NVME adapters which shows same slots
and same WWNN:WWPN
Since the same port is used for both NVMe
and SCSI
adapters, the WWNN
and WWPN
are identical for these adapters. Therefore, the same WWNN
and WWPN
will be displayed.
1. To Disable NVMe set the parameter by running this command for qlnativefc
:
# esxcfg-module -s 'ql2xnvmesupport=0' qlnativefc
2. Reboot the host to disables NVMe support.
Note: FC NVMe adapter and NVMe LUN devices which connected to adapter will not be accessed.
When using the lpfc
Driver, to work around this issue if you do not want to use NVMe devices:
1. Set the parameter by running this command:
# esxcli system module parameters set -m lpfc -p lpfc_enable_fc4_type=1
2. Reboot the host to disables NVMe support.
When using the lpfc Driver, if want to use NVMe devices (revert the changes back)
1. Set the parameter by running this command:
# esxcli system module parameters set -m lpfc -p lpfc_enable_fc4_type=0
2. Reboot the host to enable NVMe support.