HP MSA 2040 HP MSA 2040 SAN Controller GL100R002 Firmware Release Notes (73828 - Page 5

Installation instructions, Installation notes and best practices, Before installing this firmware

Get HP MSA 2040 PDF manuals and user guides View all HP MSA 2040 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 5 highlights

• Some drive firmware Smart Components built before the GL100R002 release may not be compatible with GL100R002 firmware, causing the Smart Component to stall. HP recommends checking drive module firmware versions and upgrading them before upgrading controllers to GL100R002. • When changing a replication set (e.g., adding or removing a replication volume or deleting the replication set), do so from the source system; when aborting, suspending, or resuming a replication, do so from the destination system. • When changing the primary volume of a replication set, do so from the destination system first, then, perform the change on the source system. • When using Windows Dynamic Disk (software RAID) on top of a hardware RAID, cautions must be considered. For more information, see the section "Real World: Dynamic versus Basic Disks" on the topic at http://technet.microsoft.com/en-us/library/dd163558.aspx. • Failover and failback times are affected by the number of system volumes; the more volumes there are on the system, the more time is required for failover and failback to complete. Installation instructions The following sections discuss installing firmware: • "Installation notes and best practices" (page 5) • "Installing firmware using Smart Components in Windows environments" (page 7) • "Installing firmware using Smart Components in Linux environments" (page 8) • "Installing firmware using the Storage Management Utility (SMU)" (page 9) • "Installing firmware using FTP" (page 10) • "Installation troubleshooting" (page 11) Installation notes and best practices WARNING! Do not cycle power or restart devices during a firmware update. If the update is interrupted or there is a power failure, the module could become inoperative. If this occurs, contact technical support. The module may need to be returned to the factory for re-programming. CAUTION: Before upgrading firmware, ensure that the system is stable and is not being re-configured or changed in any way. If changes are in progress, monitor them and wait until they are completed before proceeding with the upgrade. IMPORTANT: In dual-module enclosures, both controllers or both I/O modules must have the same firmware version installed. Running different firmware versions on installed modules may cause unexpected results. Before installing this firmware: • If using a Smart Component, ensure that FTP and telnet are enabled on the arrays being updated. • Create a full backup of system data. (A full backup is strongly recommended.) • Schedule an appropriate time to install the firmware: ◦ For single domain systems, I/O operations must be halted. ◦ For dual domain systems, because the online firmware upgrade is performed while host I/Os are being processed, I/O load can impact the upgrade process. Select a period of low I/O activity to ensure the upgrade completes as quickly as possible and avoid disruptions to hosts and applications due to timeouts. Installation instructions 5

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
•
Some drive firmware Smart Components built before the GL100R002 release may not be
compatible with GL100R002 firmware, causing the Smart Component to stall. HP recommends
checking drive module firmware versions and upgrading them before upgrading controllers to
GL100R002.
•
When changing a replication set (e.g., adding or removing a replication volume or deleting the
replication set), do so from the source system; when aborting, suspending, or resuming a
replication, do so from the destination system.
•
When changing the primary volume of a replication set, do so from the destination system first,
then, perform the change on the source system.
•
When using Windows Dynamic Disk (software RAID) on top of a hardware RAID, cautions must
be considered. For more information, see the section "Real World: Dynamic versus Basic Disks"
on the topic at
h
t
tp://t
ec
hne
t
.mi
c
r
o
s
o
f
t
.co
m/e
n
-u
s/libr
ar
y/dd1
6
3
5
5
8.a
s
p
x
.
•
Failover and failback times are affected by the number of system volumes; the more volumes there
are on the system, the more time is required for failover and failback to complete.
Installation instructions
The following sections discuss installing firmware:
•
“Installation notes and best practices” (page 5)
•
“Installing firmware using Smart Components in Windows environments” (page 7)
•
“Installing firmware using Smart Components in Linux environments” (page 8)
•
“Installing firmware using the Storage Management Utility (SMU)” (page 9)
•
“Installing firmware using FTP” (page 10)
•
“Installation troubleshooting” (page 11)
Installation notes and best practices
WARNING!
Do not cycle power or restart devices during a firmware update. If the update is
interrupted or there is a power failure, the module could become inoperative. If this occurs, contact
technical support. The module may need to be returned to the factory for re-programming.
CAUTION:
Before upgrading firmware, ensure that the system is stable and is not being re-configured
or changed in any way. If changes are in progress, monitor them and wait until they are completed
before proceeding with the upgrade.
IMPORTANT:
In dual-module enclosures, both controllers or both I/O modules must have the same
firmware version installed. Running different firmware versions on installed modules may cause
unexpected results.
Before installing this firmware:
•
If using a Smart Component, ensure that FTP and telnet are enabled on the arrays being updated.
•
Create a full backup of system data. (A full backup is strongly recommended.)
•
Schedule an appropriate time to install the firmware:
For single domain systems, I/O operations must be halted.
◦
◦
For dual domain systems, because the online firmware upgrade is performed while host I/Os
are being processed, I/O load can impact the upgrade process. Select a period of low I/O
activity to ensure the upgrade completes as quickly as possible and avoid disruptions to hosts
and applications due to timeouts.
Installation instructions
5