3 verifying eva4000 storage failover configuration, D in section 6.1.3 and, Bed in section 6.1.3 – HP StorageWorks Scalable File Share User Manual
Page 138
Verifying, diagnosing, and maintaining the system
6–8
6.1.3 Verifying EVA4000 storage failover configuration
This section only applies to systems where EVA4000 storage arrays are used and are configured with
redundant Fibre Channel fabric (that is, systems where two Fibre Channel switches are used).
Testing the Fibre Channel fabric failover configuration involves turning off one side of the Fibre Channel
fabric, and verifying that the system continues to operate. This test assumes that the LUNs are presented
correctly, as verified by the
syscheck
command (see Section 6.1.1).
To test the Fibre Channel fabric failover configuration, perform the following steps:
1.
Turn off the power to (or remove the power cable from) the Fibre Channel switches on one of the Fibre
Channel fabric connections.
2.
From the administration server, shut down the MDS server and all Object Storage Servers, by entering
the commands shown in the following example:
sfs> shutdown server south[2-4]
3.
Shut down and reboot the administration server, by entering the following command on the
administration server:
sfs> shutdown -r now
4.
When the administration server reboots, log in to the administration server and boot the MDS server,
as follows:
sfs> boot server south2
5.
Boot the Object Storage Servers, as follows:
sfs> boot server south[3-4]
6.
Enter the
show lun
command and examine the output to verify that each LUN is visible to two
servers in a server pair. The following example output shows LUNs that are presented correctly:
sfs> show lun
LUN Array Role Used by Size(GB) Preferred Server Visible to
--- ----- ----- ---------- -------- ---------------- ----------
1 1 adm south1 40 - south[1-2]
2 1 service south1 1 - south[1-2]
3 1 unknown - 290 - south[1-2]
4 1 unknown - 290 - south[1-2]
5 1 unknown - 290 - south[1-2]
6 1 unknown - 290 - south[1-2]
7 2 service south3 1 - south[3-4]
8 2 unknown - 290 - south[3-4]
9 2 unknown - 290 - south[3-4]
10 3 unknown - 290 - south[3-4]
11 3 unknown - 290 - south[3-4]
The following example output shows a situation where the LUNs on array 3 have some problems:
sfs> show lun
LUN Array Role Used by Size(GB) Preferred Server Visible to
--- ----- ----- ---------- -------- ---------------- ----------
1 1 adm south1 40 - south[1-2]
2 1 service south1 1 - south[1-2]
3 1 unknown - 290 - south[1-2]
4 1 unknown - 290 - south[1-2]
5 1 unknown - 290 - south[1-2]
6 1 unknown - 290 - south[1-2]
7 2 service south3 1 - south[3-4]
8 2 unknown - 290 - south[3-4]
9 2 unknown - 290 - south[3-4]
10 3 unknown - 290 - south4
11 3 unknown - 290 - south4
LUNs 10 and 11 are not visible to the
south3
server; however, the LUNs on array 2 (LUNs 7 through
9) are visible to the
south3
server. This indicates that the HBA on the
south3
server is operating