Académique Documents
Professionnel Documents
Culture Documents
486858-002
Part number: 486858-002 First edition: March, 2008
Legal and notice information Copyright 2008 Hewlett-Packard Development Company, L.P. Hewlett-Packard Company makes no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. This document contains proprietary information, which is protected by copyright. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of Hewlett-Packard. The information is provided as is without warranty of any kind and 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. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. HP StorageWorks 2000 Family Modular Smart Array firmware upgrade instructions
Obtaining firmware
1. Download the MSA2000fc-J200XXX-xx.zip file, MSA2000i-J210XXX-xx.zip file, or MSA2000sa-J300XXX-xx.zip file containing the updated firmware. a. Go to http://www.hp.com/go/msa. b. Select MSA SAN Arrays, select your product, go to Support for your product, click the Download drivers and software link, and download the firmware for your product. IMPORTANT: Download and install only the correct firmware for your system. Install J200 firmware only on MSA2012fc and MSA2022fc controllers. Install J210 firmware only on MSA2012i controllers. Install J300 firmware only on MSA2012sa controllers. 2. Extract the binary file from the zip file to a location that your management host can access. The zip file contains a J200XXX-xx.bin, J210XXX-xx.bin, or J300XXX-xx.bin file for updating controller enclosures.
# show job-parameters
4. For dual controller configurations, if the PFU feature is disabled, type the following command to enable PFU:
# set job-parameters partner-firmware-upgrade enabled
5. Type the following CLI command to enable FTP access to the controllers:
# set protocols ftp enabled
6. Exit the telnet or SSH session. 7. In a Command Prompt (Windows) or terminal window (UNIX), FTP to controller As IP address. For example: ftp 10.1.0.9 The FTP server displays a series of instructions. IMPORTANT: successfully. Use a command-line FTP client. A GUI-based FTP client might not download the firmware
8. Log in as a Manage user with the correct password. CAUTION: In dual-controller configurations, attempting to update each controller module at the same time by logging onto both controllers will fail and leave one or both controllers in an uncertain state. Instead follow the instructions so that the controllers are upgraded sequentially. 9. Type the following command: ftp> put firmwarefile flash where firmwarefile is the filepath (if the file is in other than the current directory) and filename. For example: ftp> put c:\JXXXXXX-xx.bin flash
IMPORTANT: Install only the correct firmware for your system. Install J200 firmware only on MSA2012fc and MSA2022fc controllers. Install J210 firmware only on MSA2012i controllers. Install J300 firmware only on MSA2012sa controllers. A series of status messages identifies the commands being performed. These commands take up to ten minutes to complete. When a status message indicates that the code load has completed successfully, the update starts on the other controller and may take up to ten more minutes to complete.
10. Type the following command to exit the FTP session: ftp> quit 1 1. Start a new CLI session on controller A as a Manage user. Type the following command to verify the firmware versions:
# versions
When matching versions for all firmware components on both controllers are displayed, the code load has completed successfull