2 Node Win 2003 Cluster and EVA 8000

[Globkins]

I have a EVA 8000 and bl20p blades connected to it.
I have made a 2-node Windows 2003 cluster on 2 blades.
A quorum disk is on the EVA, this VDISK is presented to both blades.
The cluster works, I can move resourses from one node to another from management console.
When I shutdown a node that ownes the cluster resourses, they move to the second node properly.
But when I try to imitate the emergency - power off the node that ownes the cluster resourses without proper shutdown, the resourses don't move to another node and the cluster service on the another node stops with the error:

Event_ID 1177
Cluster service is shutting down because the membership engine failed to arbitrate for the quorum device. This could be due to the loss of network connectivity with the current quorum owner. check your physical network infrastructure to ensure that communication between this node and all other nodes in the server cluster is intact.

When I tried to start cluster service manually on this node, it answered with error:

Event_ID 1034

The disk associated with cluster disk resource 'Quorum disk' could not be found. the expected signature of the disk was DD77D37F4. If the disk was removed from the server cluster, the resource should be deleted. If the disk was replaced, the recource must bedeleted and created again in order to bring the disk online. If the disk has not been removed or replaced, it may be inaccessible at this time because it is reserved by another server cluster node.


Only when I have booted the first node (that owned cluster resourses before the test), the cluster service on the second node started.

what is wrong?
I thought, that when emergency on one none occurs, the cluster must work and resourses must move to another node. Or not?

[Urban Petry]

Your cluster definitely should be able to cope with the situation you tested.

I guess the problem is related to SCSI reservations. Do you use load balancing for the cluster disks? If so how did you enable it? At installation time or later on?

Take a look a the following chapters in the MPIO documentation (installation and reference guide):
"HP MPIO EVA DSM persistent reservations clear utility"
"Enabling support for load balancing in MSCS environments"

Urban

[Ivan Ferreira]

Do you already have service pack 1 applied? This service pack solves a problem when SAN is used for the shared storage.