MSA2000 Controller Replacement

download MSA2000 Controller Replacement

of 4

Transcript of MSA2000 Controller Replacement

  • HP StorageWorks

    2000 G2 Modular Smart ArrayController module replacementinstructions

    This document details procedures for replacing a failedcontroller module in an HP StorageWorks 2312/2324Modular Smart Array (MSA2312/MSA2324).

    Copyright 2008, 2009 Hewlett-Packard Development Company,L.P.

    Second edition: July 2009

    The information in this document is subject to change without notice.

    Printed in China.

    www.hp.com

    *500916-002*

    About this documentIllustrations in this document may show a controller module with aconnection interface that differs from your controller module. Replacementprocedures are the same for all MSA2312/2324 controller modules.

    The Storage Management Utility (SMU) and the Command Line Interface(CLI) can be used to manage MSA2000family storage enclosures. Tasksin this document demonstrate using the CLI.

    Obtain the latest version of these instructions from the HP website athttp://www.hp.com/go/msa. Select MSA SAN Arrays, select yourproduct, and go to Support.

    Before you begin

    CAUTION:

    When replacing a controller in an operational controllerenclosure, ensure that less than 10 seconds elapse betweeninserting the controller into a slot and fully latching it in place.Failing to do so might cause the controller to fail. If it is notlatched within 10 seconds, remove the controller from the slotand repeat the process.

    CAUTION:

    Parts can be damaged by electrostatic discharge. Use properanti-static protection: Keep the replacement component in the ESD bag until needed. Wear an ESD wrist strap grounded to an unpainted surface

    of the chassis. If an ESD wrist strap is unavailable, touch an unpainted surface

    of the chassis before handling the component. Never touch connector pins.

    Verifying component failureUse the following methods to verify component failure:

    Check the Fault/Service Required LED (back): Amber = Fault condition

    Check that the OK LED (back) is off. Check the event log for errors.

    Page 1

  • Recording configuration settings

    IMPORTANT:

    When replacing the controller in slot A, configuration settingswill be reset to the values of the replacement controller. (Thisdoes not occur when replacing the controller in slot B.) Recordsystem settings before replacing a controller module.

    To obtain key settings using the CLI, enter the following commands:

    System information:show system

    User names, passwords, and user types:show users

    Date and time settings:show controller-date

    Email and SNMP notification settings:show snmp-parameters

    NTP configuration:show ntp-status

    Volume mapping information:show volume-maps

    Snapshot scheduling information:show schedules

    WWN nicknames:show hosts

    Enabling Partner Firmware Upgradenl

    (dual-controller configurations only)In a dual-controller configuration, the Partner Firmware Upgrade optionensures that both controllers have the most recent version.

    To see the current Partner Firmware Upgrade setting, enter the followingcommand:show advanced-settings

    If Partner Firmware Upgrade is disabled, enter the following command:set advanced-settings partner-firmware-upgradeenablednl

    nl

    nl

    nl

    nl

    nl

    nl

    nl

    Removing the controller module

    CAUTION: In a single-controller configuration, if transporting the Com-

    pactFlash to a replacement controller, remove the controlleronly after the cache is copied to CompactFlash, which is indic-ated by the Cache Status LED being off.

    In a single-controller environment, I/O must be stopped andthe enclosure must be powered off prior to the replacement.

    In a dual-controller environment, if the failed controller is firstshut down, the controller may be hot-replaced in an operation-al enclosure.

    1. In a dual-controller configuration, verify that the partner controlleris online by entering the command:

    show redundancy-mode

    2. Shut down the failed controller by entering the command:

    shutdown a|b, where a or b represents the controller.The blue OK to Remove LED (back) illuminates to indicate that thecontroller can be removed safely.

    3. Illuminate the UID (Unit Identification) LED of the enclosure thatcontains the controller module to remove by entering the command:

    set led enclosure 1 on

    4. Locate the enclosure whose UID LED (front right ear) is blue, andwithin it, the controller module whose OK to Remove LED is blue.

    5. Disconnect any cables connected to the controller.

    6. Turn the thumbscrews until the screws disengage from the controller.

    7. Press both latches downward to disconnect the module from themidplane.

    Page 2

  • 8. Pull the module straight out of the enclosure.

    Transporting CompactFlashnl

    (single-controller configurations only)

    CAUTION:

    CompactFlash must stay with the same enclosure. If theCompactFlash is used/installed in a different enclosure, dataloss or corruption will occur.

    1. If the controller has failed or does not start, make sure thattransporting the cache is the appropriate action to take as specifiedin the user guide.

    2. Carefully remove the CompactFlash from the controller, label itData, and set it aside.

    3. Carefully remove the CompactFlash from the replacement controller,and set it aside.

    4. Insert the CompactFlash that you removed from the failed controllerand labeled Data into the replacement controller.

    Installing the controller module

    NOTE:

    You can install a controller into an enclosure that is poweredon.

    1. Loosen the thumbscrews; press the latches downward.

    2. Slide the controller into the enclosure as far as it will go (1).

    3. Press the latches upward to engage the controller (2); turn thethumbscrews finger-tight (3).

    4. Reconnect the cables.

    IMPORTANT:

    In a dual-controller configuration, if the firmware versions differbetween the two controllers, Partner Firmware Upgrade bringsthe older firmware to the later firmware level.

    Page 3

  • Verifying component replacementAfter replacing the controller, check that the OK LED (back) illuminatesgreen, indicating that the controller has completed initializing and isonline.

    If the enclosure UID is on, do the following to turn it off:

    set led enclosure 1 off

    If the Fault/Service Required LED is amber, the module has not goneonline and likely failed its self-test. Check the event log for errors andput the module online by restarting a controller. To restart a controller,enter the following command:

    restart sc a|b, where a or b represents the controller.

    Verifying configuration settingsAfter replacing a controller, verify that system configuration settings areset properly for your environment. Repeat the commands shown inRecording configuration settings on page 2 and compare the currentvalues with those recorded before the installation. If necessary, changethe settings to their previous values. For more information, see onlinehelp or the HP StorageWorks 2000 Family Modular Smart Arrayreference guide.

    Verifying the firmware versionAfter replacing a controller, verify that the latest firmware is installed onall controllers in the controller enclosure. Go to the website for your MSAmodel and, if newer firmware is available, download the firmware fromthe Web and install this latest version on the controller(s). For moreinformation on firmware updates, see the HP StorageWorks 2000 FamilyModular Smart Array reference guide.

    Additional informationSee the MSA website: http://www.hp.com/go/msa

    Page 4

    MSA2000 G2 Controller replacement instructionsAbout this documentBefore you beginVerifying component failureRecording configuration settingsEnabling Partner Firmware Upgrade (dual-controller configurations only)Removing the controller moduleTransporting CompactFlash (single-controller configurations only)Installing the controller moduleVerifying component replacementVerifying configuration settingsVerifying the firmware versionAdditional information