ESXi experiences PSOD due to nfnic driver
Article ID: 317954
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
This article provides information on how to resolve an ESXi host PSOD event related to nfnic and fnic initiators in the same zone.
Symptoms:
Symptoms:
- PSOD due to nfnic driver
0x450a402a2d10:[0x41801d90ac15]PanicvPanicInt@vmkernel#nover+0x439 stack: 0x41801dc8a000, 0x41801dc89f48, 0x450a402a2db8, 0x4302e2fd3c48, 0x450a00000001
0x450a402a2db0:[0x41801d90aea1]Panic_WithBacktrace@vmkernel#nover+0x56 stack: 0x450a402a2e20, 0x450a402a2dd0, 0x4c20, 0x4c20, 0x11b5ea
0x450a402a2e20:[0x41801d907c91]NMI_Interrupt@vmkernel#nover+0x3c2 stack: 0x0, 0xfc8, 0x2032342075706370, 0x6165627472616548, 0x494d4e2074
0x450a402a2ea0:[0x41801d943ffc]IDTNMIWork@vmkernel#nover+0x99 stack: 0x0, 0x0, 0x0, 0x0, 0x0
0x450a402a2f20:[0x41801d9454f0]Int2_NMI@vmkernel#nover+0x19 stack: 0x0, 0x41801d960067, 0xfd0, 0xfd0, 0x0
0x451ad8e1b4e8:[0x41801d91b5e9]Timer_GetCycles@vmkernel#nover+0x2 stack: 0x430dfd28a290
0x451ad8e1b4f0:[0x41801d92b633]Util_Udelay@vmkernel#nover+0x38 stack: 0x1
0x451ad8e1b510:[0x41801e2945d7]fnic_term_allio@(nfnic)#<None>+0x48 stack: 0x1
0x451ad8e1b5a0:[0x41801e29474c]fnic_cleanup@(nfnic)#<None>+0xd stack: 0x430dfd28a290
0x451ad8e1b5c0:[0x41801e294812]fnic_reset@(nfnic)#<None>+0x5f stack: 0x1
0x451ad8e1b600:[0x41801e2949ba]fnic_host_reset@(nfnic)#<None>+0xf3 stack: 0x1
0x451ad8e1b640:[0x41801e294f48]fnic_device_reset@(nfnic)#<None>+0x401 stack: 0x430d00000414
0x451ad8e1b760:[0x41801e2967df]fnic_abort_cmd@(nfnic)#<None>+0x780 stack: 0x459c0000000a
0x451ad8e1b810:[0x41801e296f48]fnic_abort_initiator_cmds@(nfnic)#<None>+0xe9 stack: 0x430b00000353
0x451ad8e1b890:[0x41801e2974cf]fnic_taskMgmt@(nfnic)#<None>+0x560 stack: 0x430b9e49c000
0x451ad8e1b970:[0x41801db7b62a]SCSIIssueAdapterTaskMgmt@vmkernel#nover+0x2eb stack: 0x43073d591400
0x451ad8e1ba00:[0x41801db8d3ca]vmk_ScsiIssuePathTaskMgmt@vmkernel#nover+0x24b stack: 0x80000001af599320
0x451ad8e1ba70:[0x41801e3a6fdb][email protected]#v2_5_0_0+0x2b8 stack: 0x0
0x451ad8e1bb10:[0x41801db6c1c2]SCSIDeviceTaskMgmt@vmkernel#nover+0x3f3 stack: 0x2700
0x451ad8e1bba0:[0x41801db6c3d0]SCSIDeviceIssueTMs@vmkernel#nover+0x51 stack: 0x10d7ec34a493280
0x451ad8e1bbf0:[0x41801db6d1cb]SCSI_DeviceVirtReset@vmkernel#nover+0x2ac stack: 0xd23780
0x451ad8e1bc60:[0x41801d865f5c]FSDisk_Ioctl@vmkernel#nover+0x925 stack: 0x418047000000
0x451ad8e1bd40:[0x41801e7328aa][email protected]#nover+0x4cb stack: 0x418046000000
0x451ad8e1be90:[0x41801e7bbe6a]FS3ReclaimHBCB@esx#nover+0xdb stack: 0x0
0x451ad8e1bf30:[0x41801d8ea442]HelperQueueFunc@vmkernel#nover+0x30f stack: 0x431065a0f6f8
0x451ad8e1bfe0:[0x41801db09132]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0
0x450a402a2db0:[0x41801d90aea1]Panic_WithBacktrace@vmkernel#nover+0x56 stack: 0x450a402a2e20, 0x450a402a2dd0, 0x4c20, 0x4c20, 0x11b5ea
0x450a402a2e20:[0x41801d907c91]NMI_Interrupt@vmkernel#nover+0x3c2 stack: 0x0, 0xfc8, 0x2032342075706370, 0x6165627472616548, 0x494d4e2074
0x450a402a2ea0:[0x41801d943ffc]IDTNMIWork@vmkernel#nover+0x99 stack: 0x0, 0x0, 0x0, 0x0, 0x0
0x450a402a2f20:[0x41801d9454f0]Int2_NMI@vmkernel#nover+0x19 stack: 0x0, 0x41801d960067, 0xfd0, 0xfd0, 0x0
0x451ad8e1b4e8:[0x41801d91b5e9]Timer_GetCycles@vmkernel#nover+0x2 stack: 0x430dfd28a290
0x451ad8e1b4f0:[0x41801d92b633]Util_Udelay@vmkernel#nover+0x38 stack: 0x1
0x451ad8e1b510:[0x41801e2945d7]fnic_term_allio@(nfnic)#<None>+0x48 stack: 0x1
0x451ad8e1b5a0:[0x41801e29474c]fnic_cleanup@(nfnic)#<None>+0xd stack: 0x430dfd28a290
0x451ad8e1b5c0:[0x41801e294812]fnic_reset@(nfnic)#<None>+0x5f stack: 0x1
0x451ad8e1b600:[0x41801e2949ba]fnic_host_reset@(nfnic)#<None>+0xf3 stack: 0x1
0x451ad8e1b640:[0x41801e294f48]fnic_device_reset@(nfnic)#<None>+0x401 stack: 0x430d00000414
0x451ad8e1b760:[0x41801e2967df]fnic_abort_cmd@(nfnic)#<None>+0x780 stack: 0x459c0000000a
0x451ad8e1b810:[0x41801e296f48]fnic_abort_initiator_cmds@(nfnic)#<None>+0xe9 stack: 0x430b00000353
0x451ad8e1b890:[0x41801e2974cf]fnic_taskMgmt@(nfnic)#<None>+0x560 stack: 0x430b9e49c000
0x451ad8e1b970:[0x41801db7b62a]SCSIIssueAdapterTaskMgmt@vmkernel#nover+0x2eb stack: 0x43073d591400
0x451ad8e1ba00:[0x41801db8d3ca]vmk_ScsiIssuePathTaskMgmt@vmkernel#nover+0x24b stack: 0x80000001af599320
0x451ad8e1ba70:[0x41801e3a6fdb][email protected]#v2_5_0_0+0x2b8 stack: 0x0
0x451ad8e1bb10:[0x41801db6c1c2]SCSIDeviceTaskMgmt@vmkernel#nover+0x3f3 stack: 0x2700
0x451ad8e1bba0:[0x41801db6c3d0]SCSIDeviceIssueTMs@vmkernel#nover+0x51 stack: 0x10d7ec34a493280
0x451ad8e1bbf0:[0x41801db6d1cb]SCSI_DeviceVirtReset@vmkernel#nover+0x2ac stack: 0xd23780
0x451ad8e1bc60:[0x41801d865f5c]FSDisk_Ioctl@vmkernel#nover+0x925 stack: 0x418047000000
0x451ad8e1bd40:[0x41801e7328aa][email protected]#nover+0x4cb stack: 0x418046000000
0x451ad8e1be90:[0x41801e7bbe6a]FS3ReclaimHBCB@esx#nover+0xdb stack: 0x0
0x451ad8e1bf30:[0x41801d8ea442]HelperQueueFunc@vmkernel#nover+0x30f stack: 0x431065a0f6f8
0x451ad8e1bfe0:[0x41801db09132]CpuSched_StartWorld@vmkernel#nover+0x77 stack: 0x0
Environment
VMware vSphere ESXi 6.7
Cause
Multiple software initiators like nfnic and fnic in the same zone take the Error Escalation path in Report LUNs.
Resolution
To resolve this issue, upgrade the nfnic driver to version 4.0.0.24.
Note: This updated driver should be available from your hardware vendor.
Workaround:
Put initiators in different zones to avoid the issue.
Note: This updated driver should be available from your hardware vendor.
Workaround:
Put initiators in different zones to avoid the issue.
Additional Information
About Installing and Administering VMware vSphere Update Manager
“esxcli software vib” commands to patch an ESXi 5.x/6.x hostImpact/Risks:
Host may become inaccessible to vCenter management. Virtual machines may become inaccessible.
Feedback
Yes
No
Powered by
