| Event Id | 9 |
| Source | HBA_DRIVER_NAME |
| Description | The device, \Device\ScsiPort0, did not respond within the timeout period. |
| Event Information | According to Microsoft: In this case, the 2 node AS1 and the 4 node AS2 configurations can both be placed on the same SAN and can share the same storage subsystem. It is also possible to have AS3 in the same SAN as long as it uses storage subsystem SD2 (and not SD1) and is completely isolated from all other clusters. This is because it is using a different HBA than was tested with the multi-cluster submission. A key issue that needs to be addressed is the isolation of the different clusters that are attached to the SAN. The SAN must be configured so that a set of cluster disks are only accessible by one cluster and are completely hidden from the rest of the clusters. One or more mechanisms may be employed to accomplish this isolation such as defining zones on the switch or enabling LUN masking on the storage subsystems. The use of Fiber Channel Arbitrated Loops (FC-AL) is not supported because hubs typically do not allow for the clusters to be isolated from each other. The best way to configure multiple clusters that are attached to the same storage subsystem is to involve the storage subsystem vendor. A clustered SAN environment can be very complex, and if zones or LUN masking are not configured properly, a cluster failure on one of the clusters may affect a totally separate cluster. |
| Reference Links | Support for Multiple Clusters Attached to the Same SAN Device Support for booting from a Storage Area Network (SAN) |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.