HP StorageWorks 2000i HP StorageWorks MSA2000 G2 Firmware Release Notes (50884 - Page 14

Issue, Workaround, CTR + F5, Serial Number, Provisioning Wizard, Create Volume Set

Page 14 highlights

• Issue: When an enclosure has a status of OK, the enclosure health reason is displayed as "The enclosure health is not known". • Workaround: The health reason field is only populated when the enclosure is in a degraded or fault status. • Issue: Following a reboot, the device mapper multipath may not detect all MPATH devices correctly. • Workaround: Issue the command multipath -v3 to recover missing devices. • Issue: In a Solaris iSCSI environment, path failover and failback functionality may not work correctly. • Workaround: Refer to SUN CR numbers 6764779 and 6844558. • Issue: Some entries in the SMU and CLI are not localized properly for all languages. • Workaround: HP is continually updating localized content. • Issue: Some configuration changes under heavy I/O may return a communication error. • Workaround: Retry configuration changes during a period of lower I/O. • Issue: Some cached data in the browser may not be updated while navigating through the SMU. • Workaround: Press CTR + F5 to refresh or log out and back into the SMU. • Issue: The tree view for a vdisk in SMU may not function properly. • Workaround: Click the ++ symbol at the top of the tree view. This refreshes the screen and enables the tree view. • Issue: In single controller mode, some event log descriptions can indicate a second controller. • Workaround: These messages can be safely ignored. • Issue: During drive firmware upgrade, all volumes are taken offline to preserve data integrity. • Workaround: Plan drive firmware updates during a maintenance window. • Issue: In a c-Class blade environment, VMWare may fail I/O during failover operations. • Workaround: The VMWare kernel parameter ResetOnFailover must be set to 0 in order for array failover to work properly. • Issue: SMU may display a flashing background or other display issues if left open for an extended amount of time. • Workaround: Do not maintain an open SMU session for more than 24 hours. Log out of the SMU when SMU tasks are complete. • Issue: SMU may lose authentication if the browser refresh button is clicked. • Workaround: Log back in to re-establish authentication. • Issue: In the SMU Enclosure Overview page, the column Serial Number is mislabeled; it should be labeled WWID. • Workaround: This will be resolved in a future release. • Issue: The serial number for a volume returned by the SMU and CLI does not match the serial number returned by VPD data. • Workaround: Serial numbers are shown in different formats. The last 16 digits of the serial number are unique for each volume and match between the CLI, SMU, and VPD data. • Issue: You can not create volumes for OpenVMS using the Provisioning Wizard or Create Volume Set pages of the SMU. • Workaround: Volumes for OpenVMS may only be created using the Create Volume page of the SMU. 14

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16

Issue:
When an enclosure has a status of OK, the enclosure health reason is displayed as
The enclosure
health is not known
.
Workaround:
The health reason field is only populated when the enclosure is in a degraded or fault status.
Issue:
Following a reboot, the device mapper multipath may not detect all MPATH devices correctly.
Workaround:
Issue the command
multipath
v3
to recover missing devices.
Issue:
In a Solaris iSCSI environment, path failover and failback functionality may not work correctly.
Workaround:
Refer to SUN CR numbers 6764779 and 6844558.
Issue:
Some entries in the SMU and CLI are not localized properly for all languages.
Workaround:
HP is continually updating localized content.
Issue:
Some configuration changes under heavy I/O may return a communication error.
Workaround:
Retry configuration changes during a period of lower I/O.
Issue:
Some cached data in the browser may not be updated while navigating through the SMU.
Workaround:
Press
CTR + F5
to refresh or log out and back into the SMU.
Issue:
The tree view for a vdisk in SMU may not function properly.
Workaround:
Click the
++
symbol at the top of the tree view. This refreshes the screen and enables the
tree view.
Issue:
In single controller mode, some event log descriptions can indicate a second controller.
Workaround:
These messages can be safely ignored.
Issue:
During drive firmware upgrade, all volumes are taken offline to preserve data integrity.
Workaround:
Plan drive firmware updates during a maintenance window.
Issue:
In a c-Class blade environment, VMWare may fail I/O during failover operations.
Workaround:
The VMWare kernel parameter
ResetOnFailover
must be set to 0 in order for array
failover to work properly.
Issue:
SMU may display a flashing background or other display issues if left open for an extended amount
of time.
Workaround:
Do not maintain an open SMU session for more than 24 hours. Log out of the SMU when
SMU tasks are complete.
Issue:
SMU may lose authentication if the browser refresh button is clicked.
Workaround:
Log back in to re-establish authentication.
Issue:
In the SMU Enclosure Overview page, the column
Serial Number
is mislabeled; it should be labeled
WWID
.
Workaround:
This will be resolved in a future release.
Issue:
The serial number for a volume returned by the SMU and CLI does not match the serial number returned
by VPD data.
Workaround:
Serial numbers are shown in different formats. The last 16 digits of the serial number are
unique for each volume and match between the CLI, SMU, and VPD data.
Issue:
You can not create volumes for OpenVMS using the
Provisioning Wizard
or
Create Volume Set
pages
of the SMU.
Workaround:
Volumes for OpenVMS may only be created using the
Create Volume
page of the SMU.
14