ESXi host running on Cisco UCS/VBLOCK lose access to volumes with the error: fnic : 2 :: Abort Cmd called

Products

• VMware

Issue/Introduction

Symptoms:

• VMware ESXi host running on Cisco UCS/VBLOCK lose access to storage volumes.
  
• In the /var/log/vmkernel.log file on the affected ESXi host, you see entries similar to:
  
  <YYYY-MM-DD>T<time>.541Z cpu3:34498345)PVSCSI: 1587: ctx=0xfffffa8031dbe5a0 cdb0=0x2a on scsi0:0 completed during reset (0x8)
  <YYYY-MM-DD>T<time>.965Z cpu24:33052)< 7 >fnic : 2 :: Abort Cmd called FCID 0x11100, LUN 0x3 TAG 66e flags 3
  <YYYY-MM-DD>T<time>.965Z cpu15:32981)< 7 >fnic : 2 :: abts cmpl recd. id 1646 status FCPIO_SUCCESS
  <YYYY-MM-DD>T<time>.965Z cpu24:33052)< 7 >fnic : 2 :: Returning from abort cmd type 2 SUCCESS
  <YYYY-MM-DD>T<time>.965Z cpu24:33052)< 7 >fnic : 2 :: Abort Cmd called FCID 0x11100, LUN 0x3 TAG 678 flags 3
  <YYYY-MM-DD>T<time>.965Z cpu15:32981)< 7 >fnic : 2 :: abts cmpl recd. id 1656 status FCPIO_SUCCESS
  
  </time></time></time></time></time></time>Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
  
• The VMware vCenter Server displays an error similar to:
  
  Lost access to volume xxxxxxxx-xxxxxxxx-xxxx-xxxxxxxx due to connectivity issues.

Cause

This issue occurs due to these Cisco bugs: CSCuh61202 or CSCus64439.

For more information, see Cisco bug search.

Note: You need to have a registered Cisco account to access the bug information.

Resolution

This is not a VMware issue.

To work around this issue, reboot the blade that is flooding traffic to the IOM. This will result in the Pause configuration being re-programmed.

Important: The preferred method to avoid this issue altogether, if an upgrade from 2.1(2) is to be performed, is to plan the upgrade such that the adapters/blades are upgraded prior to the infrastructure components. It is recommended to upgrade all components in the system from the blade to the FI in the same maintenance window so the system is not sitting in disparate versions. For more information, contact Cisco support.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Additional Information

Cisco UCS/VBLOCK 上运行的 ESXi 主机无法访问卷，并出现错误：fnic : 2 :: Abort Cmd called

Impact/Risks: