HP Scalable File Share G3 MSA2000fc How To

HP Scalable File Share G3 MSA2000fc How To Abstract This document provides best practices for critical or sensitive MSA2000fc storage operations and configuration information specifically for the HP SFS G3.2-0 product solution. This document is intended for anyone who installs and uses HP SFS. The information in this guide assumes that you have experience with the Linux operating system and associated user commands and tools, the Lustre File System, Smart Array storage administration, HP rack-mounted servers and associated rack hardware, basic networking concepts, network switch technology, and network cables. HP Part Number: 5900-1230 Published: November 2010 Edition: 1

Copyright 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Windows is a U.S. registered trademark of Microsoft Corporation. UNIX is a registered trademark of The Open Group.

Contents 1 Introduction to HP SFS G3.2...5 1.1 HP SFS G3.2 hardware configuration...5 1.2 Recommended MSA vdisks and volumes for HP SFS G3 file systems...5 2 Controlling the PFU feature on CE...6 2.1 Changing or viewing the PFU setting from SMU interface on MSA2212fc...6 2.2 Changing or viewing the PFU setting from SMU interface on MSA2312fc...6 2.3 Changing or viewing the PFU settings from CLI on MSA2212fc...7 2.4 Changing or viewing the PFU settings from CLI on MSA2312fc...7 3 Upgrading controller module firmware on controller modules attached to HP SFS...8 3.1 Obtaining firmware...8 3.2 Preparing for upgrade...8 3.3 Upgrading controller firmware using SMU for MSA2212fc...8 3.4 Upgrading controller firmware using SMU for MSA2312fc...9 3.5 Upgrading controller firmware (J200*.bin) using FTP and CLI interface for MSA2212fc and MSA2312fc...9 4 Verifying cabling between MSA2212fc G1 controller ports and zoned SAN switch for MSAs connected to HP SFS G3 servers...12 5 Replacing failed controller modules and upgrading controller firmware...14 6 Powering on and off MSA2000 enclosures...17 7 Shutting down and restarting controllers...18 7.1 Restarting...18 7.1.1 Restarting MSA2212fc array controllers...18 7.1.2 Restarting MSA2312fc array controllers...18 7.2 Shutting down...18 7.2.1 Shutting down MSA2212fc array controllers...19 7.2.2 Shutting down MSA2312fc array controllers...19 7.3 Restarting and shutting down MSA2212fc and MSA2312fc using CLI...19 8 Downloading MSA2000 controller logs...20 9 MSA2000 G1,G2 (MSA2212fc and MSA2312fc) important advisory...21 10 Support and other resources...22 10.1 Contacting HP...22 10.1.1 Before you contact HP...22 10.1.2 HP contact information...22 10.1.3 Subscription service...22 Contents 3

10.1.4 Documentation feedback...22 10.2 Related information...22 10.3 Typographic conventions...23 Glossary...25 4 Contents

1 Introduction to HP SFS G3.2 HP SFS G3.2 uses the Lustre File System on MSA2000fc storage hardware to provide a storage system for standalone servers or compute clusters. HP SFS G3.2 consists of a software set required to provide high performance and highly available Lustre File System service over InfiniBand or 10 GigE for the following HP MSA2000fc storage product generations or releases: MSA2212fc Product of MSA2000 G1 storage product family MSA2312fc Product of MSA2000 G2 storage product family 1.1 HP SFS G3.2 hardware configuration The typical HP SFS G3 system configuration consists of the base rack containing: ProLiant DL380 MDS, MGS, and OSS HP MSA2212fc or MSA2312fc enclosures Management network ProCurve switch SAN switches InfiniBand or 10 GigE switches KVM switch TFT console display Supported storage array drives are SAS and SATA. 1.2 Recommended MSA vdisks and volumes for HP SFS G3 file systems MSA2212fc or MSA2312fc storage arrays for HP SFS G3 configurations consist of a CE with two controllers (dual-controller configuration) and up to three connected DDE. Each enclosure contains 12 disks. For MGS and MDS storage, HP SFS G3 uses RAID10 vdisk with 10 data drives and two spare drives. For OST storage, HP SFS G3 uses RAID6 vdisk with nine data drives, two parity drives, and one hot spare. Use the create volume command to create a single volume occupying the full extent of each vdisk. In summary, HP recommends the following HP SFS vdisk and volume configuration: One enclosure contains one vdisk. The vdisk contains one volume. The volume becomes one Lustre Target OST, MDT, or MGT. IMPORTANT: The size of a Lustre MGT, MDT, or OST is limited to 8 TB. Therefore, any volume created on the MSA2212fc or MSA2312fc must be less than or equal to 8,796 GB. Single volume or multiple volumes less than or equal to 8,796 GB must be created from any vdisk that is larger than 8,796 GB due to the number and size of disks used. 1.1 HP SFS G3.2 hardware configuration 5

2 Controlling the PFU feature on CE PFU is an enclosure-level setting applicable to both controllers in the CE. The PFU feature is enabled by default for MSA2000 G1 and MSA2000 G2 product families. If you enable PFU on MSA2212fc and MSA2312fc dual-controller systems, then the system also updates the partner controller when firmware is updated on one controller. Enable or disable PFU for both controllers by logging in to either of the controllers. IMPORTANT: In some instances, the PFU feature does not produce the intended results during firmware upgrade, leading to issues such as management controller hang and upgrade process hang. HP recommends disabling the PFU feature on the MSAs attached to HP SFS setup. NOTE: When a failed controller is replaced with a new controller and booted, the PFU is read from the active partner controller or the CE. 2.1 Changing or viewing the PFU setting from SMU interface on MSA2212fc 1. Disable PFU through SMU. Click Manage General Configuration System Configuration. 2. Click the Disabled radio button for Partner Firmware Upgrade. 3. To save any changes, click Change System Configuration. Figure 1 System configuration 2.2 Changing or viewing the PFU setting from SMU interface on MSA2312fc 1. In the Configuration View panel, right-click the system and select Configuration Advanced Settings Firmware. 6 Controlling the PFU feature on CE

Figure 2 Firmware settings 2. To enable the firmware update settings, check the Partner Firmware Update box, or to disable the update setting, clear the box. 3. Click Apply to save your changes. 2.3 Changing or viewing the PFU settings from CLI on MSA2212fc # show job-parameters Job Parameters -------------- Background Scrub : Enabled Partner Firmware Upgrade: Enabled Utility Priority : Low Dynamic Spare Scan Rate: Disabled # # show job-parameters Job Parameters -------------- Background Scrub: Disabled Partner Firmware Upgrade: Enabled Utility Priority: High # To enable PFU on any controller module: # set job-parameters partner-firmware-upgrade enabled To disable PFU on any controller module: # set job-parameters partner-firmware-upgrade disabled 2.4 Changing or viewing the PFU settings from CLI on MSA2312fc # show advanced-settings Background Scrub: Disabled Partner Firmware Upgrade: Disabled To enable PFU on any controller module: # set advanced-settings partner-firmware-upgrade enabled To disable PFU on any controller module: # set advanced-settings partner-firmware-upgrade disabled 2.3 Changing or viewing the PFU settings from CLI on MSA2212fc 7

3 Upgrading controller module firmware on controller modules attached to HP SFS HP SFS G3 uses MSA2212fc and MSA2312fc dual-controller, redundant, and fault-tolerant cabling connections to handle single controller failure or breakdown conditions in any controller failover pair. The PFU feature is enabled by default on each controller in the MAS2000 controller family. When enabled, HP SFS G3 requires disabling the PFU feature before starting a firmware upgrade from the SMU or CLI interface. CAUTION: Do not cycle power or restart devices during a firmware update. If the update is interrupted or if a power failure occurs, the module might become inoperative. If this occurs, contact HP technical support. The module might have to be returned to the factory for reprogramming. IMPORTANT: Before upgrading the controller firmware, ensure that the storage system configuration is stable and is not reconfigured or changed. If any configuration changes are in progress, monitor them with SMU and wait until they are completed before proceeding with the upgrade. HP recommends a full backup prior to the upgrade. 3.1 Obtaining firmware 1. Go to http://www.hp.com/go/msa. 2. Click Support & Drivers. 3. Select your product. 4. Click Download drivers and software. 5. Select an operating system. 6. Download the appropriate controller firmware for your product. IMPORTANT: Download and install only the firmware for your system. 3.2 Preparing for upgrade HP recommends upgrading MSA2000 controller firmware offline to prevent HP SFS file system inconsistencies and possible data corruption. Before starting MSA controller firmware updates on HP SFS: 1. Unmount HP SFS clients and targets (MGT, MDT, and OSTs) on HP SFS server nodes to halt host I/O to the storage system. For more information, see section 5.4 Stopping the File System in the HP Scalable File Share User Guide G3.2-0. 2. Disable PFU on MSA CEs using SMU or CLI. You can use the SMU or CLI interface to upgrade MSA2212fc and MSA2312fc controller firmware. The following sections provide a general outline of installation instructions for updating controller module firmware on MSA2212fc and MSA2312fc controllers. IMPORTANT: Read the installation instructions provided with the controller firmware release. If you need any clarification or assistance is needed, contact HP support before proceeding. 3.3 Upgrading controller firmware using SMU for MSA2212fc 1. Place the downloaded firmware package.bin file in a temporary directory. For example, the firmware file name format is neptunesw-j200p46-01.bin. 2. Log in to SMU on controller A as a manage user with the correct password. 8 Upgrading controller module firmware on controller modules attached to HP SFS

3. Confirm that PFU is disabled on this controller. For details on how to verify the PFU status, see Controlling the PFU feature on CE (page 6). CAUTION: In dual-controller configurations such as HP SFS G3, attempting to update controller modules at the same time by logging in to both controllers will fail and leave one or both controllers in an uncertain state. The following steps upgrade the controllers individually. 4. Select Manage Update Software Controller Software. 5. Click Browse to select the firmware.bin file you downloaded and extracted, for example neptunesw-j200p19-01.bin. 6. Click Load Software Package File. When loading is complete, the current version of the firmware on controller A and the new version in the firmware package appear. 7. Click Proceed With Code Update. The update might take up to 10 minutes to complete. To see the progress of the code load, refresh your browser frequently. 8. When the code load to controller A is complete, you are logged out. Wait one minute before logging back in to SMU on controller A as a manage user. 9. When the code load is complete, select Monitor Advanced Settings Controller Versions to verify all firmware components are updated. 10. After you have confirmed the controller firmware on controller A is upgraded successfully, log in to controller B. Upgrade the controller firmware on controller B by performing steps 3 to 9. 3.4 Upgrading controller firmware using SMU for MSA2312fc 1. Place the downloaded firmware package.bin file in a temporary directory, for example, the firmware file name format is mercurysw-m110r28-02.bin. 2. Log in to SMU on controller A as a manage user with the correct password. 3. Confirm that PFU is disabled on this controller. For details on how to verify the PFU status, see Controlling the PFU feature on CE (page 6). CAUTION: In dual-controller configurations such as HP SFS G3, attempting to update controller modules at the same time by logging in to both controllers will fail and leave one or both controllers in an uncertain state. The following steps upgrade the controllers individually. 4. Locate the firmware file in the extracted folder, for example, mercurysw-m110r28-02.bin. 5. In the SMU Configuration View panel, right-click the system and select Tools Update Firmware. A table appears which lists the installed firmware versions. 6. Click Browse to select the firmware.bin file you downloaded and extracted, for example, mercurysw-m110r28-02.bin. 7. Click Install Controller-Module Firmware File. The firmware loads and restarts. This might take 10 minutes to complete. Wait for the progress messages to inform you that the update is complete. 8. Verify the proper firmware version for this controller module appears in the SMU display. 9. After you have confirmed the controller firmware on controller A is upgraded successfully, log in to controller B. Upgrade the controller firmware on controller B by performing steps 3 to 8 above. 3.5 Upgrading controller firmware (J200*.bin) using FTP and CLI interface for MSA2212fc and MSA2312fc 1. Place the downloaded firmware package.bin file in a temporary directory on the management host connected to the Ethernet port on the controller pairs (A and B). For example the firmware file name is neptunesw-j200p46-01.bin for MSA2212fc arrays and mercurysw-m110r28-02.bin for MSA2312fc arrays. 3.4 Upgrading controller firmware using SMU for MSA2312fc 9

2. On a management host connected to the Ethernet port on controller A, start a Telnet session between the IP on controller A to a CLI session as a manage user. 3. Confirm that PFU on this controller is disabled: For MSA2212fc # show job-parameters Job Parameters -------------- Background Scrub : Enabled Partner Firmware Upgrade: Disabled Utility Priority : Low Dynamic Spare Scan Rate: Disabled For MSA2312fc: # show advanced-settings Background Scrub: Disabled Partner Firmware Upgrade: Disabled 4. If FTP access to the controllers is not enabled: # set protocols ftp enabled 5. Exit the controller Telnet or SSH session. 6. From the management host terminal Telnet session (in this instance HP SFS servers), use FTP to go to the controller IP address. IMPORTANT: Use a command-line FTP client. A GUI-based FTP client might not download the firmware successfully. For example: # ftp 10.1.0.1 The FTP server displays a series of instructions. 7. Log in as a manage user with the correct password. CAUTION: In dual-controller configurations such as HP SFS G3, attempting to update controller modules at the same time by logging in to both controllers fails and leaves one or both controllers in an uncertain state. Use the following steps upgrade the controllers individually. 8. ftp> put <firmware-bin-file> flash where firmware-bin-file is the file path (if the file is not in the current directory) and file name, for example: ftp> put /root/filename.bin flash A series of status messages identifies the commands performed. These commands take up to 10 minutes to complete. A status message indicates the code load completed successfully and returns to the prompt. TIP: To ensure that the firmware flashes correctly, you can force the flashing: ftp> put path/filename.bin flash : force 9. After the firmware installation is complete, exit the FTP session: ftp> quit 10 Upgrading controller module firmware on controller modules attached to HP SFS

10. Start a new Telnet session on controller A as a manage user. To verify the firmware versions: # versions Output for MSA2212fc : Controller A Versions --------------------- Storage Controller CPU Type Storage Controller Firmware Storage Controller Memory Storage Controller Loader : 15.010 Management Controller Firmware: W420R58 Management Controller Loader : 12.013 Expander Controller Firmware : 3206 CPLD Revision : 27 Hardware Revision : LCA 56 Host Interface Module : 26 Host Interface Module Model : 1 Output for MSA2312fc: : Pentium-III 700MHz : J200P46 : F300R22 Controller A Versions --------------------- Storage Controller CPU Type: Sempron 3000+ 1800MHz Storage Controller Code Version: M110R28 Memory Controller FPGA Code Version: F300R22 Storage Controller Loader Code Version: 19.009 Management Controller Code Version: W441R13 Management Controller Loader Code Version: 12.015 Expander Controller Code Version: 1106 CPLD Code Version: 8 Hardware Version: 50 Host Interface Module Version: 50 Host Interface Module Model: 0 If the controller displays the appropriate versions for all firmware components, the code load is successful. 11. After confirming the upgrade of controller firmware on controller A is successful, log in to controller B. Upgrade the controller firmware on controller B by performing steps 3 to 10. 12. After all controller pairs in all MSA CEs are upgraded to the appropriate firmware level, start all HP SFS servers and file system components (MGT, MDT, and OSTSs). For more information, see section 5.3 Starting the File System in the HP Scalable File Share User Guide G3.2-0. 3.5 Upgrading controller firmware (J200*.bin) using FTP and CLI interface for MSA2212fc and MSA2312fc 11

4 Verifying cabling between MSA2212fc G1 controller ports and zoned SAN switch for MSAs connected to HP SFS G3 servers This section describes how to verify the cabling between MSA2212fc G1 controller ports and the zoned SAN switch for MSAs connected to SFS G3 servers so they work even under single controller failure in any of the controller pairs. The MSA controller and the SAN switch cabling diagram as shown in the HP Scalable File Share User Guide G3.2-0, Section 1.3.1 Hardware Configuration, Figure 1-2 Server Pairs is only functional for MSA2000fcG2 or G3 product families. This cabling does not work as expected by HP SFS G3 with MSA2000fc G1 (MSA2212fc) in the event of single controller failure in any of the controller pairs because: MSA2000fc G1 (MSA2212fc) does not support ULP. LUNs are mapped to the WWNs of the owning controller. The WWNs failover in crossed mode. Controller A port 0 fails over to controller B port 1 and vice versa. The port carries the LUN along with it. For HP SFS G3 controller failover with MSA2000fc G1 (MSA2212fc), the cabling must be crossed. Connect A0 and B1 to one zoned SAN switch. Connect B0 and A1 to another zoned SAN switch. For this controller failover cabling configuration, see Figure 3 (page 12). Figure 3 MSA2000fc G1 cabling between zoned SAN Switch and MSA2212fc controller port for redundant dual controller configuration Although HP recommends using the HP StorageWorks 2012fc Modular Smart Array User Guide as a reference for MSA cabling, instances of incorrect cabling between s SAN switch and MSA2000fc G1 controllers (MSA2212 fc) have occurred. If you are using MSA2000fc G1 (MSA2212 fc) with HP SFS G3, and cabling between zoned SAN switches and MSA2212fc controllers is not crossed for controller failover configuration, contact HP SWD support to correct your cabling. 12 Verifying cabling between MSA2212fc G1 controller ports and zoned SAN switch for MSAs connected to HP SFS G3 servers

IMPORTANT: Before performing any cabling correction actions, the HP SFS file system must be offline. After all MSA and SAN procedures are completed, bring the HP SFS file system back online. 13

5 Replacing failed controller modules and upgrading controller firmware The firmware version on the factory-provided replacement or spare controller might not match the controller firmware on the active partner controller module of the MSA enclosure. If PFU is enabled on the MSA enclosure when the new controller is replaced and booted, then the controller at the higher firmware level automatically triggers PFU to upgrade firmware on the partner controllers. IMPORTANT: HP recommends HP SFS customers perform MSA2000 controller firmware upgrades offline only, even when replacing a failed single controller, to prevent HP SFS file system data from inconsistencies and possible data corruption during online controller firmware upgrade. To replace a failed controller and upgrade controller firmware (if needed): 1. Disable the PFU on this enclosure. a. Log in to SMU or CLI interface on the active controller. b. For MSA2212fc: # set job-parameters partner-firmware-upgrade disabled c. For MSA2312fc : # set advanced-settings partner-firmware-upgrade disabled 2. Confirm the PFU is disabled on the affected enclosure. From the remaining active controller: a. For MSA2212fc: # show job-parameters Job Parameters -------------- Background Scrub: Disabled Partner Firmware Upgrade: Disabled Utility Priority: High b. For MSA2312fc: # show advanced-settings Background Scrub: Disabled Partner Firmware Upgrade: Disabled 3. Using the following documents, perform the procedures for replacing a failed controller module in an HP StorageWorks MSA2000 product family. Follow the instructions provided in these documents to replace the failed controller up to the step for booting the new controller. IMPORTANT: To prevent HP SFS file system data from inconsistencies and possible data corruption, HP does not recommend using PFU to perform the controller firmware upgrade, even though these documents suggest using PFU. HP StorageWorks 2000 Modular Smart Array Controller Module Replacement Instructions http://bizsupport2.austin.hp.com/bc/docs/support/supportmanual/c02066832/ c02066832.pdf HP StorageWorks 2012fc Modular Smart Array controller module replacement instructions http://bizsupport1.austin.hp.com/bc/docs/support/supportmanual/c01394181/ c01394181.pdf 14 Replacing failed controller modules and upgrading controller firmware

4. After the replaced controller is booted up, verify all the firmware version components on both controller pairs. # show versions Controller A Versions --------------------- Storage Controller CPU Type Storage Controller Firmware Storage Controller Memory Storage Controller Loader : 15.010 Management Controller Firmware: W420R35 Management Controller Loader : 12.013 Expander Controller Firmware : 2042 CPLD Revision : 27 Hardware Revision : LCA 56 Host Interface Module : 26 Host Interface Module Model : 1 Controller B Versions --------------------- Storage Controller CPU Type Storage Controller Firmware Storage Controller Memory Storage Controller Loader : 15.010 Management Controller Firmware: W420R58 Management Controller Loader : 12.013 Expander Controller Firmware : 3206 CPLD Revision : 27 Hardware Revision : LCA 56 Host Interface Module : 26 Host Interface Module Model : 1 # : Pentium-III 700MHz : J200P19 : F300R21 : Pentium-III 700MHz : J200P46 : F300R22 IMPORTANT: Before upgrading the controller firmware, ensure that the storage system configuration is stable and is not reconfigured or changed. If any configuration changes are in progress, monitor them with SMU, and wait until they are completed before proceeding with the upgrade. HP recommends a full backup prior to the upgrade. a. If the replaced controller and its partner controller are at the same firmware version level, no further actions are necessary. b. If the replaced controller is at a lower firmware level than its partner: i. Unmount all HP SFS clients and targets (MGT, MDT, and OSTs) on all HP SFS server nodes to halt all host I/O to the storage system. For more information, see section 5.4 Stopping the File System in the HP Scalable File Share User Guide G3.2-0. Use the SMU or CLI interface to upgrade the firmware on the replaced controller, as described in Upgrading controller module firmware on controller modules attached to HP SFS (page 8). NOTE: Perform the upgrade only on the replaced controller, not all controllers. ii. After both controller pairs in affected MSA enclosures are at same firmware level, start all HP SFS servers and file system components (MGT, MDT, and OSTSs). For more information, see section 5.3 Starting the File System in the HP Scalable File Share User Guide G3.2-0. 15

c. If the replaced controller is at a higher firmware level than its partner controller: i. Unmount all HP SFS clients and targets (MGT, MDT, and OSTs) on all HP SFS server nodes to halt all host I/O to the storage system. For more information, see section 5.4 Stopping the File System in the HP Scalable File Share User Guide G3.2-0. CAUTION: In dual-controller configurations such as HP SFS G3, attempting to update controller modules at the same time by logging in to both controllers fails and leaves one or both controllers in an uncertain state. The following steps upgrade the controllers individually. CAUTION: Do not cycle power or restart devices during a firmware update. If the update is interrupted or if a power failure occurs, the module could become inoperative. If this issue occurs, contact HP technical support. The module might have to be returned to the factory for reprogramming. ii. iii. iv. Because the replaced controller is at a higher firmware level, use this maintenance window to upgrade the controller firmware on all other MSA controllers. Upgrade to the same version as the replaced controller, or to the latest firmware available for your MSA controller type (MSA2212fc or MSA2312fc). Use the SMU or CLI interface to upgrade the firmware on the all other MSA controllers, as described in Upgrading controller module firmware on controller modules attached to HP SFS (page 8). After all controllers are upgraded to the same firmware level, start all HP SFS servers and file system components (MGT, MDT, and OSTSs). For more information, see section 5.3 Starting the File System in the HP Scalable File Share User Guide G3.2-0. 16 Replacing failed controller modules and upgrading controller firmware

6 Powering on and off MSA2000 enclosures Before powering on the enclosure for the first time: 1. Install all hard drives in the enclosure so the connected host controller can identify and configure them when you power on the system. 2. Connect the cables and power cords to the enclosure as explained in the Installation Poster. 3. Power on the enclosures and associated data host in the following order: a. Drive enclosures b. Controller enclosure c. Data hosts last (if they are powered down for maintenance purposes) To power on the system: 1. Press the power switches at the back of each drive enclosure to the On position. 2. Wait for the drive in the enclosure to perform a full spin up. The drive is ready when the LEDs stop blinking. 3. Press the power switches at the back of the controller enclosure to the On position. 4. Start the data hosts, in this instance all HP SFS servers and file system components (MGT, MDT, and OSTSs). For more information, see section 5.3 Starting the File System in the HP Scalable File Share User Guide G3.2-0. To power off the system: 1. Stop all I/O from hosts to the system. Unmount all HP SFS clients and targets (MGT, MDT, and OSTs) on all HP SFS server nodes to halt all host I/O to the storage system. For more information, see section 5.4 Stopping the File System in the HP Scalable File Share User Guide G3.2-0. 2. Use SMU to shut down both controllers. For information on shutting down controllers, see SMU online help or the CLI reference guide. Wait until SMU indicates that processing is complete. 3. Press the power switches at the back of the controller enclosure to the Off position. 4. Press the power switches at the back of each drive enclosure to the Off position. 17

7 Shutting down and restarting controllers You can restart processors in a controller module when SMU indicates a changed configuration setting that requires restarting or when the controller is not working properly. Shut down the processors in a controller module before you remove it from an enclosure or before you power off the enclosure for maintenance, repair, or a move. You can perform a restart on either the SC processor or the MC processor. A shutdown affects both SC and MC processors. 7.1 Restarting When restarting the SC, a shutdown is attempted with a proper failover sequence including stopping all I/O operations and flushing the write cache to disk before the controller restarts. The MC is not restarted because it provides status information to external interfaces. If you restart a MC, communication with it is lost until it successfully restarts. If the restart fails, the partner MC remains active with full ownership of operations and configuration information. CAUTION: If you restart both controller modules at the same time, access to the system and data is lost until the restart is complete. 7.1.1 Restarting MSA2212fc array controllers 1. Select Manage Restart System Shut Down/Restart. 2. In the Restart Controller panel, select a controller option. 3. Click Restart. A confirmation prompt appears. 4. Click OK to confirm the operation, or Cancel to stop it. If you click OK, a message indicates if the operation succeeded. 7.1.2 Restarting MSA2312fc array controllers 1. In the Configuration View panel, right-click the local system and select Configuration Shut Down or Restart Controller. 2. In the main panel, set the following options: Select the Restart operation. Select the type of controller processor to restart. Select whether to restart the processor in controller A, B, or both. 3. Click Restart now. A confirmation dialog appears. 4. Click Yes to continue. Otherwise, click No. If you click Yes, a second confirmation dialog appears. 5. Click Yes to continue. Otherwise, click No. If you click Yes, a message describes restart activity. 7.2 Shutting down Shutting down the SC in a controller module ensures a proper failover sequence, including stopping all I/O operations and writing to disk any data in write cache. If the SC in both controller modules is shut down, hosts cannot access the system data. Perform a shutdown before removing a controller module or powering down the system. 18 Shutting down and restarting controllers

IMPORTANT: You can continue using the CLI when either or both SCs are shut down, but information shown might be invalid. 7.2.1 Shutting down MSA2212fc array controllers 1. Select Manage Restart System Shut Down/Restart. 2. In the Shut Down panel, select a controller option. 3. Click Shut Down. A warning might appear that data access redundancy will be lost until the selected controller is restarted. This informational message requires no action. 4. Confirm the operation by clicking OK. 7.2.2 Shutting down MSA2312fc array controllers 1. In the Configuration View panel, right-click the local system and select Configuration Shut Down or Restart Controller. 2. In the main panel, set the following options: Select the Shut down operation. Select whether to restart the processor in controller A, B, or both. 3. Click Shut down now. A confirmation dialog appears. 4. Click Yes to continue. Otherwise, click No. If you click Yes, a second confirmation dialog appears. 5. Click Yes to continue. Otherwise, click No. If you click Yes, a message describes shutdown activity. 7.3 Restarting and shutting down MSA2212fc and MSA2312fc using CLI To restart: # restart mc sc a b both # show shutdown-status storage controller A is up storage controller B is up To shutdown: # shutdown a b both # show shutdown-status storage controller A is up storage controller B is up 7.3 Restarting and shutting down MSA2212fc and MSA2312fc using CLI 19

8 Downloading MSA2000 controller logs To assist HP service personnel diagnosing system issues, you might be asked to download and submit system log data. Download the logs by accessing the system FTP interface and running the get logs command. When both controllers are online, regardless of operating mode, get logs downloads the following data into a single file: User configuration settings from both controllers Event logs from both controllers SC debug logs from both controllers SC crash dumps from both controllers MC CAPI trace from the target controller MC debug log from the target controller Controller environment including data about attached disks and enclosures. HP recommends using a command-line-based FTP client. A GUI-based FTP client might not work properly. To download logs to a file: 1. In SMU, prepare to use FTP. a. Determine the network-port IP addresses of the system controllers. b. Verify that the system FTP service is enabled. c. Verify that your user profile has permission to use the FTP interface. 2. Open a Windows command prompt or a UNIX terminal window and navigate to the destination directory for the log file. 3. # ftp controller-network-address For example: # ftp 10.1.0.9 4. Log in as an FTP user. 5. ftp> get logs path/filename.txt Where filename is yyyymmdd_ftp_system-name_controller-id. For example: ftp> get logs/20080124_ftp_storage2_a.txt Wait for the message Transfer complete to appear. 6. Quit the FTP session. 7. If the issue being diagnosed appears to be a user-interface operation (such as SMU or CLI crashes or hangs), repeat step 3 through step 6 on the partner controller to collect the unique MC debug information. NOTE: Log files can exceed 5 MB. Before sending a log file to service personnel or attaching it to a bug-tracking system, compress the file with winzip or the tar compression tool. 20 Downloading MSA2000 controller logs

9 MSA2000 G1,G2 (MSA2212fc and MSA2312fc) important advisory HP StorageWorks MSA2000 G1 and G2 products lose defined configuration information upon replacement of controller A. All configuration information on controller A returns to factory default values. This issue does not occur with replacement of controller B. When controller A is replaced on the HP StorageWorks MSA2000 G1 and G2 system, user-defined configuration information might be returned to factory default values. For more details on this advisory, see: http://saw.cce.hp.com/km/saw/view.do?docid=emr_na-c01797449 For customers: (public link) http://h20000.www2.hp.com/bizsupport/techsupport/ Document.jsp?lang=e&cc=us&objectID=c01797449&jumpid=reg_R1002_USEN Fixed in J200P46 firmware version for MSA2000 G1 Controller (for our case MSA2212fc): ftp://ftp.hp.com/pub/softlib2/software1/pubsw-linux/p487091724/v58893/ 537811-003_msa2000_fw.htm 21

10 Support and other resources 10.1 Contacting HP 10.1.1 Before you contact HP Be sure to have the following information available before you contact HP: Technical support registration number (if applicable) Product serial number Product identification number Applicable error message Add-on boards or hardware Third-party hardware or software Operating system type and revision level 10.1.2 HP contact information For the name of the nearest HP authorized reseller: See the Contact HP worldwide (in English) webpage (http://welcome.hp.com/country/us/ en/wwcontact.html). For HP technical support: In the United States, for contact options see the Contact HP United States webpage (http:// welcome.hp.com/country/us/en/contact_us.html). To contact HP by phone: Call 1-800-HP-INVENT (1-800-474-6836). This service is available 24 hours a day, 7 days a week. For continuous quality improvement, calls may be recorded or monitored. If you have purchased a Care Pack (service upgrade), call 1-800-633-3600. For more information about Care Packs, refer to the HP website (http://www.hp.com/hps). In other locations, see the Contact HP worldwide (in English) webpage (http:// welcome.hp.com/country/us/en/wwcontact.html). 10.1.3 Subscription service HP recommends that you register your product at the Subscriber's Choice for Business website: http://www.hp.com/country/us/en/contact_us.html After registering, you will receive email notification of product enhancements, new driver versions, firmware updates, and other product resources. 10.1.4 Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, complete the form at http://www.hp.com/bizsupport/feedback/ww/webfeedback.html. Include the document title and manufacturing part number. All submissions become the property of HP. 10.2 Related information HP StorageWorks 2000 Modular Smart Array Controller Module Replacement Instructions http://bizsupport2.austin.hp.com/bc/docs/support/supportmanual/c02066832/ c02066832.pdf 22 Support and other resources

HP StorageWorks 2012fc Modular Smart Array controller module replacement instructions http://bizsupport1.austin.hp.com/bc/docs/support/supportmanual/c01394181/ c01394181.pdf HP StorageWorks 2000 Family Modular Smart Array firmware upgrade instructions ftp://ftp.hp.com/pub/softlib/software9/col22286/co-58820-1/486858-001.pdf HP StorageWorks MSA2012fc/MSA2212fc - How to Configure Soft Zones in Dual Controller Environment when Using Loop Topology on MSA Host Ports http://h20000.www2.hp.com/bizsupport/techsupport/ Document.jsp?lang=en&cc=us&objectID=c01693126&jumpid=reg_R1002_USEN HP StorageWorks 2000 G2 Modular Smart Array Reference Guide http://h20000.www2.hp.com/bc/docs/support/supportmanual/c01756042/ c01756042.pdf HP StorageWorks 2000 Family Modular Smart Array reference guide http://bizsupport1.austin.hp.com/bc/docs/support/supportmanual/c01565941/ c01565941.pdf HP StorageWorks 2012fc Modular Smart Array user guide http://bizsupport.austin.hp.com/bc/docs/support/supportmanual/c01394283/ c01394283.pdf HP StorageWorks 2000 G2 Modular Smart Array CLI Reference Guide http://h20000.www2.hp.com/bc/docs/support/supportmanual/c01755995/ c01755995.pdf HP StorageWorks 2000 Family Modular Smart Array troubleshooting guide http://www.dectrader.com/docs/set1/c01394278.pdf QuickSpecs - HP StorageWorks 2000fc Modular Smart Array http://h18000.www1.hp.com/products/quickspecs/12991_div/12991_div.pdf HP StorageWorks Carrier-Grade 2324fc Modular Smart Array user guide http://h20000.www2.hp.com/bc/docs/support/supportmanual/c01694375/ c01694375.pdf?jumpid=reg_r1002_usen 10.3 Typographic conventions This document uses the following typographical conventions: %, $, or # A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne, Korn, and POSIX shells. A number sign represents the superuser prompt. audit(5) Command Computer output Ctrl+x ENVIRONMENT VARIABLE A manpage. The manpage name is audit, and it is located in Section 5. A command name or qualified command phrase. Text displayed by the computer. A key sequence. A sequence such as Ctrl+x indicates that you must hold down the key labeled Ctrl while you press another key or mouse button. The name of an environment variable, for example, PATH. 10.3 Typographic conventions 23

ERROR NAME Function() Key Parameter Term User input Variable The name of an error, usually returned in the errno variable. The name of a function. The name of a keyboard key. Return and Enter both refer to the same key. The name of a parameter. The defined use of an important word or phrase. Commands and other text that you type. The name of a placeholder in a command, function, or other syntax display that you replace with an actual value. [] The contents are optional in syntax. If the contents are a list separated by, you must choose one of the items. {} The contents are required in syntax. If the contents are a list separated by, you must choose one of the items.... The preceding element can be repeated an arbitrary number of times. Indicates the continuation of a code example. Separates items in a list of choices. WARNING CAUTION IMPORTANT NOTE A warning calls attention to important information that if not understood or followed will result in personal injury or nonrecoverable system problems. A caution calls attention to important information that if not understood or followed will result in data loss, data corruption, or damage to hardware or software. This alert provides essential information to explain a concept or to complete a task. A note contains additional information to emphasize or supplement important points of the main text. 24 Support and other resources

Glossary CE controller enclosure CLI command-line interface DDE disk drive enclosure G1 generation 1 G2 generation 2 KVM keyboard, video, and mouse MC management controller MDS metadata servers MGS administration servers OSS object storage servers PFU partner firmware update SC storage controller SMU storage management utility ULP unified LUN presentation 25