Oracle Fabric Interconnect :: What are the different conditions that will trigger Host_Bus

Asset ID:	1-75-1518890.1
Update Date:	2017-07-11
Keywords:

Solution Type Troubleshooting Sure

Solution 1518890.1 : Oracle Fabric Interconnect :: What are the different conditions that will trigger Host_Bus_Busy messages?

Applies to:

Oracle Fabric Interconnect F1-15 - Version All Versions to All Versions [Release All Releases]
Oracle Fabric Interconnect F1-4 - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Purpose

The reason why we "Host_Bus_Busy" message in vmkernel.log is because Qlogic sends out "CS_Timeout" response message. This time the Xsigo vhba host driver would return DID_Bus_Busy (H:0x2) message to the ESX SCSI mid-layer in response to which we see HOST_BUS_BUSY in vmkernel.log.

Troubleshooting Steps

There could be various reason why Qlogic chip sends “CS_Timeout”. Here are the few reasons.

If the Qlogic chip does not receive response from the target then we can see CS_Timeout (LUN is busy or oversubscribed).
For some reason if the packet was not sent out from Qlogic chip and it time out from its internal queue (which is rare condition).

Host Log
Jul 25 08:49:03 vmkernel: 1:06:10:02.171 cpu0:42727)NMP: nmp_CompleteCommandForPath: Command 0x2a (0x41027f410940) to NMP device "naa.60030d9062683106f579d95b8ea65920" failed on physical path "vhba1:C0:T0:L1"H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

Jul 25 08:49:03 vmkernel: 1:06:10:02.171 cpu0:42727)ScsiDeviceIO: 1688: Command 0x2a to device "naa.60030d9062683106f579d95b8ea65920" failed H:0x2 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

Please refer the below vMWare KB article.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&externalId=1029039

Attachments

This solution has no attachment