HPE EVA Storage

MSA 2012 SAS controller failure

 
kins
Occasional Advisor

MSA 2012 SAS controller failure

Hi,

I have 2 controllers in an MSA 2012sa and 2 HBAs in the server that is attached. The server connects to port 1 on each controller.

There are 4 volumes, 2 owned by each controller. Controller A failed and only 2 volumes were accessible. I have MPIO installed on the server with a round-robin policy.

How come the second controller didn't take over from the failed controller? I gave controller B read/write access to the volumes while ctrl A is down and I can see them on the server.
3 REPLIES 3
Taohung
Frequent Advisor

Re: MSA 2012 SAS controller failure

When controller A is failed, you must check two operations
1) Check that all volumes owned by controller A belong to controler B. ( See the information of volumes)

2) Check the mapping information. all volumes owned by controller A must be accessed by sas port a1,a2,b1,b2.

3) Check the mapping information. all volumes owned by controller A must be accessed by all servers.
kins
Occasional Advisor

Re: MSA 2012 SAS controller failure

Controller B is the current owner of the 4 volumes
Controller A is the preferred owner of 2 but is dead.

Both hosts have rw access to a0, a1, b0, b1 on all volumes.
Will this not show 2 volumes for each volume in Windows disk manager? Is this ok?

Under General Configuration < System Configuration < SCSI < Advanced Options
Host control of write-back cache is disabled. Should this be enabled? Do the controllers on the MSAs come with batteries?

Controller failure trigger is not checked. Shouls it be?

Auto write through behaviors:
notify other controllers is not checked. Shold is be?
kins
Occasional Advisor

Re: MSA 2012 SAS controller failure

Also are the controllers in the MSA hot pluggable?