QLogic FC HBA goes 'link down' intermittently
search cancel

QLogic FC HBA goes 'link down' intermittently

book

Article ID: 426882

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • QLogic FC HBA goes 'link down' intermittently

In(182) vmkernel: cpu29:2103604)qlnativefc: vmhba4(b1:0.1): qlnativefcAsyncEvent:643:ISP System Error - mbx1=496eh mbx2=10h mbx3=10d3h mbx4=30h mbx5=ech mbx6=0h mbx7=0h.
In(182) vmkernel: cpu57:2098174)qlnativefc: vmhba4(b1:0.1): qla27xxFwdump:1243:Attempting to take firmware dump
In(182) vmkernel: cpu57:2098174)qlnativefc: vmhba4(b1:0.1): qla27xxFwdump:1280:-> Firmware dump saved to buffer, instance 1

  • An ESXi host has periodic Fibre Channel storage connectivity issues
  • Loss of paths are reported.

Wa(180) vmkwarning: cpu2:2098263)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:235: NMP device "naa.xxxxxxxxxxxxxxxxxxx" state in doubt; requested fast path state update...
Wa(180) vmkwarning: cpu10:2098265)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:235: NMP device "naa.xxxxxxxxxxxxxxxxxxx" state in doubt; requested fast path state update...

  • The link comes back after some time without any user intervention.

Environment

  • vSphere VMware ESXi 8.0U3
  • Issue observed with QLE2772 FC card, but may impact other FC cards.

 

Cause

This is caused by firmware issue, related to SBUS timeout.

 

In(182) vmkernel: cpu29:2103604)qlnativefc: vmhba4(b1:0.1): qlnativefcAsyncEvent:643:ISP System Error - mbx1=496eh mbx2=10h mbx3=10d3h mbx4=30h mbx5=ech mbx6=0h mbx7=0h.
In(182) vmkernel: cpu57:2098174)qlnativefc: vmhba4(b1:0.1): qla27xxFwdump:1243:Attempting to take firmware dump
In(182) vmkernel: cpu57:2098174)qlnativefc: vmhba4(b1:0.1): qla27xxFwdump:1280:-> Firmware dump saved to buffer, instance 1
In(182) vmkernel: cpu57:2098174)qlnativefc: vmhba4(b1:0.1): qlnativefcAbortIsp:4014:Inside qlnativefcAbortIsp
In(182) vmkernel: cpu57:2098174)qlnativefc: vmhba4(b1:0.1): qlnativefcAbortIspCleanup:6004:Performing ISP error recovery - ha= 0x4312d74ef000.

Resolution

  • Issue is fixed in firmware binary 9.15.09 or higher. 
  • Engage Marvel support for any future firmware version recommendations and firmware upgrade assistance.