HP P2000 Release Note page 15

1gbe iscsi msa and 10gbe iscsi msa controller firmware
Hide thumbs Also See for P2000:
Table of Contents

Advertisement

Workaround:
1.
Close down the terminal application. (Example: HyperTerminal)
2.
Open Device Manager and disable the "Disk Array USB Port" under Ports (COM & 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 P2000 G3 support page.
Issue: When using SMI-S, only partial support is provided for iSCSI Target Ports Subprofile.
Workaround: None.
Issue: When using SMI-S, the ExtentStatus property in StorageVolume is always set to "2".
Workaround: None.
Issue: When creating a storage repository with Citrix 5.5 update 2 and attaching it to the server pool while the servers in
the pool are on, the storage repository is only multipathed on the master server. This seems to happen only with the first
storage repository created after rebooting the servers. If a second storage repository is created and attached (without
rebooting the servers), that storage repository is correctly multipathed with all servers in the pool.
Workaround: Detach and reattach the storage repository and the storage repository will be multipathed with all servers in
the pool.
Issue: There is no indication that a LUN has failed over to the other controller.
Workaround: Using the Storage Manage Utility (SMU), open up system events and scan for failover events. When using
the CLI, use the show events command.
Issue: When accessing the Command Line Interface (CLI), output from commands scroll by with no option to page through
the output.
Workaround: Change the window height or scrollback value of the command window to a larger value and use the scroll
bar on the command window to scroll through the CLI output.
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 and 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 the secondary volume is detached and its vdisk stopped when the replication set
was deleted, and then the vdisk of the secondary volume restarted. To correct this issue, reattach the secondary volume,
set it as the primary volume, and delete the replication set.
Issue: An error message indicating "controller busy" occurs while creating a replication set.
Workaround: Creating a replication set immediately following another replication set creation may 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.
Issue: A scheduled replication is missing or replications are queued, but don't complete.
Workaround: A best practice is to schedule no more than four volumes to start replicating at the same time and for those
replications to recur no less than 30 minutes apart. If you schedule more replications to start at the same time or schedule
replications to start more frequently, some scheduled replications may not have time to complete.
Issue: Unable to perform a local replication (a replication where the external view volume and the destination volume reside
on the same system) with a single vdisk.
Workaround: Create a second vdisk for the destination volume.
Issue: Deleting the replication-set from the destination system fails.
Known issues and workarounds
15

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents