Upgrade Procedure; Troubleshooting - IBM V7000 Introduction And Implementation Manual

13.7.2 Upgrade procedure

The following procedure upgrades drive firmware on a drive that is in the control enclosure or
expansion enclosures. If the upgrade would cause any volumes to go offline, the force option
is required.
To upgrade drive firmware, follow this procedure:
1. Run the following command for the drive that you are upgrading:
Command: lsdependentvdisks -drive drive_id
If any volumes are returned, continuing with this procedure takes the volumes offline. To
avoid losing access to data, resolve any redundancy errors to remove this problem before
you continue with the upgrade procedure.
2. Locate the firmware upgrade downloads at the following IBM website:
http://www.ibm.com/support/entry/portal/downloads/hardware/puresystems/pureflex
_system/storage_node/flex_system_v7000
This website also provides a link to the Software Upgrade Test Utility. This utility indicates
if any of your drives are not running at the latest level of firmware.
3. Using scp or pscp, copy the firmware upgrade file and the Software Upgrade Test Utility
package to the /home/admin/upgrade directory by using the management IP address.
4. Run the applydrivesoftware command. You must specify the firmware upgrade file, the
firmware type, and the drive ID.
Command: applydrivesoftware -file filename -type firmware -drive drive_id
To apply the upgrade even if it causes one or more volumes to go offline, specify the
-force option.
Attention: Do
Gate Array (FPGA) firmware, unless directed to do so by an IBM service representative.

13.8 Troubleshooting

This section describes IBM Flex System V7000 Storage Node error events reporting and
notification, and can help in understanding the error codes.
For more details on using FSM for troubleshooting tasks, see the following website:
http://publib.boulder.ibm.com/infocenter/flexsys/information/index.jsp?topic=%2Fco
m.ibm.acc.4939.doc%2Fsite_qicfgsys_FSM.html
602
IBM Flex System V7000 Storage Node Introduction and Implementation Guide
not
use the -type fpga option, which upgrades Field Programmable