Oracle Fabric Interconnect :: What are the different conditions that will trigger Host_Bus_Busy messages?
(Doc ID 1518890.1)
Last updated on JANUARY 14, 2021
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.
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 () message to the ESX SCSI mid-layer in response to which we see HOST_BUS_BUSY in vmkernel.log.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document