HP MSA 1040 HP MSA 1040/2040 Controller GL 105 Firmware Release Notes - Page 21

Configuration > Advanced Settings > Microsoft Windows Server 2008 R2 > System Utilities - serial number

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

Page 21 highlights

Issue: A serial number was not generated for SMART drive Event 55. Workaround: Identify the drive by using the enclosure and slot number. Issue: In the CLI, the show master-volumes command includes a volume that has been converted to a standard volume. Workaround: Log out, and log in again to the CLI. Issue: Global spares have a status of Up in the SMU, even if they are spun down using the drive spin-down feature. Workaround: None. Issue: On the Configuration > Advanced Settings > Microsoft Windows Server 2008 R2 > System Utilities page, changing the Vdisk Scrub and Managed Logs settings at the same time might result in an error. Workaround: Make these changes one at a time. Issue: When you create a volume set with the volumes mapped to LUNs, if there is a LUN conflict, the array stops mapping volumes to LUNs but creates the volumes as requested. Workaround: Ensure that there are no LUN conflicts before creating the volume set with mapping, or map the remaining volumes to LUNs after the conflict. Issue: SLES 11 might require multiple minutes (15+/-) to create all multipath devices during boot. This typically involves a system with a large number of LUNs and multiple LUN paths. Workaround: None. Wait for the system to complete LUN and path discovery. Issue: Under rare circumstances, some events from one controller are not seen on the other controller. Workaround: Review the events from both controllers. Issue: The USB CLI becomes unusable after a Management Controller reboot in Windows environments. Workaround: 1. Close down the terminal application (e.g., HyperTerminal). 2. Open Device Manager, and disable the Disk Array USB Port under Ports (COM and LPT). 3. Re-enable the Disk Array USB Port. If the problem persists, reboot the host. Issue: The mini-USB CLI port on the array controller does not work. Workaround: Install a device driver for the mini-USB CLI port. This driver is packaged as a Smart Component and is available for download on the MSA 2040 support page. Issue: There is no indication that a LUN has failed-over to the other controller. Workaround: Using the Storage Manage Utility (SMU), open system events and scan for failover events. When using the CLI, use the show events command. Issue: A replication is initiated, but only a snapshot on the primary volume occurs, or the replication is queued. Workaround: Ensure that all systems involved have valid replication licenses installed. Ensure that all volumes and vdisks involved in the replication have started, are attached, and are in good health, including vdisks that contain the snap pools for the volumes involved. A replication normally queues when a previous replication involving the same volumes is active. Issue: A replication set was deleted but is later shown with the primary volume status of Offline and the status-reason is record-missing. Workaround: This generally occurs when you detach the secondary volume, delete the replication set (which stops the vdisk), and restart the vdisk of the secondary volume. To correct this issue, reattach the secondary volume, set it as the primary volume, and delete the replication set. Issue: A Controller Busy error message occurs while you create a replication set. Workaround: Creating replication sets immediately one after the other might result in Controller Busy. This is expected behavior. Wait and try the operation again at a later time. Issue: In the SMU, the Vdisk > Provisioning > Create Multiple Snapshots task allows a secondary volume to be selected but fails the operation. Workaround: User-initiated snapshots are not allowed on secondary volumes. Do not select a secondary volume. Known issues and workarounds 21

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
Issue:
A serial number was not generated for SMART drive
Event 55
.
Workaround:
Identify the drive by using the enclosure and slot number.
Issue:
In the CLI, the
show master-volumes
command includes a volume that has been converted to a standard volume.
Workaround:
Log out, and log in again to the CLI.
Issue:
Global spares have a status of
Up
in the SMU, even if they are spun down using the drive spin-down feature.
Workaround:
None.
Issue:
On the
Configuration > Advanced Settings > Microsoft Windows Server 2008 R2 > System Utilities
page, changing
the
Vdisk Scrub
and
Managed Logs
settings at the same time might result in an error.
Workaround:
Make these changes one at a time.
Issue:
When you create a volume set with the volumes mapped to LUNs, if there is a LUN conflict, the array stops mapping
volumes to LUNs but creates the volumes as requested.
Workaround:
Ensure that there are no LUN conflicts before creating the volume set with mapping, or map the remaining
volumes to LUNs after the conflict.
Issue:
SLES 11 might require multiple minutes (15+/-) to create all multipath devices during boot. This typically involves a
system with a large number of LUNs and multiple LUN paths.
Workaround:
None. Wait for the system to complete LUN and path discovery.
Issue:
Under rare circumstances, some events from one controller are not seen on the other controller.
Workaround:
Review the events from both controllers.
Issue:
The USB CLI becomes unusable after a Management Controller reboot in Windows environments.
Workaround:
1.
Close down the terminal application (e.g., HyperTerminal).
2.
Open Device Manager, and disable the
Disk Array USB Port
under
Ports
(COM and LPT).
3.
Re-enable the
Disk Array USB Port
. If the problem persists, reboot the host.
Issue:
The mini-USB CLI port on the array controller does not work.
Workaround:
Install a device driver for the mini-USB CLI port. This driver is packaged as a Smart Component and is
available for download on the MSA 2040 support page.
Issue:
There is no indication that a LUN has failed-over to the other controller.
Workaround:
Using the Storage Manage Utility (SMU), open system events and scan for failover events. When using the
CLI, use the
show events
command.
Issue:
A replication is initiated, but only a snapshot on the primary volume occurs, or the replication is queued.
Workaround:
Ensure that all systems involved have valid replication licenses installed. Ensure that all volumes and vdisks
involved in the replication have started, are attached, and are in good health, including vdisks that contain the snap pools
for the volumes involved. A replication normally queues when a previous replication involving the same volumes is active.
Issue:
A replication set was deleted but is later shown with the primary volume status of
Offline
and the status-reason is
record-missing.
Workaround:
This generally occurs when you detach the secondary volume, delete the replication set (which stops the
vdisk), and restart the vdisk of the secondary volume. To correct this issue, reattach the secondary volume, set it as the
primary volume, and delete the replication set.
Issue:
A
Controller Busy
error message occurs while you create a replication set.
Workaround:
Creating replication sets immediately one after the other might result in
Controller Busy
. This is expected
behavior. Wait and try the operation again at a later time.
Issue:
In the SMU, the
Vdisk > Provisioning > Create Multiple Snapshots
task allows a secondary volume to be selected but
fails the operation.
Workaround:
User-initiated snapshots are not allowed on secondary volumes. Do not select a secondary volume.
Known issues and workarounds
21