HP P2000 HP P2000 G3 1GbE iSCSI MSA and 10GbE iSCSI MSA Controller Firmware TS - Page 12

Known issues and workarounds, When creating a volume set with the volumes mapped to LUNs - manual

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

Page 12 highlights

Known issues and workarounds Issue: When installing a firmware update using the Smart Component, the installation routine may incorrectly report that the upgrade was unsuccessful. Workaround: If the Smart Component installation routine states that a firmware load was unsuccessful, verify which version of firmware is installed using an array management utility, such as the SMU or CLI. If the version listed is the old version, run the Smart Component again. Issue: When creating a user or modifying user information in the SMU, there is no option to enable the SMI-S interface for the user. Workaround: Add the SMI-S interfaces to the user using the set user interfaces CLI command, making sure to include all appropriate interfaces. Issue: If the iSCSI IQN name is longer than 55 characters, the enumeration of CIM_StorageHardwareID fails. Workaround: Modify the IQN name to be shorter than 55 characters Issue: Manually creating a replication-prepared (secondary) volume and associating it with a primary volume originally created with pre-TS230 firmware can fail. Automatically created secondary volumes do not have this problem. Workaround: • In the SMU, use the Replication Setup Wizard or the Replicate Volume task or, in the CLI, use the create replication set command to automatically create the secondary volume. (Preferred workaround)) • Issue the following commands in the CLI to specify the block size of the manually created secondary volume, ensuring that it is exactly the same size as the source volume (Alternative workaround): 1. In CLI API format, use the show volumes command to determine the size of the pre-T230 volume in blocks. This will be displayed by the "size-numeric" property. 2. Use the create volume command and specify the size in blocks (obtained in step 1) -to create the replication-prepared volume. 3. Create a replication set that associates the two volumes. Issue: During path failover events on systems with large LUN counts, Red Hat Enterprise Linux 4 iSCSI clients may report issues accessing devices. Workaround: Increase the disk timeout to a minimum of 60 seconds. Issue: When using both the primary and secondary paths on both ports of the Qlogic iSCSI HBAs, failover does not work correctly on cable pulls. Workaround: When setting up the Qlogic iSCSI HBAs, set up only the primary path for both ports. Issue: When creating a volume set with the volumes mapped to LUNs, if there is a LUN conflict, the array will stop mapping volumes to LUNs, but will create 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: In dual-controller systems, accessing the SMU of a controller does not display vdisks owned by the other controller. Workaround: Restart the other controller. Issue: In the CLI, the TakeSnapshot task returns the message: "Unable to validate retention limits. - The user is not recognized on this system." Workaround: Restart the controller accessed. Issue: In the SMU, the Japanese version of some pages and some error messages displays English text. Workaround: None. Issue: A failed drive becomes available when the vdisk that it was a member of is deleted. Workaround: Do not use the drive. Issue: The array will incorrectly accept a DNS name for the address of the NTP server in the Storage Management Utility. The array does not use DNS, and will translate the name into an invalid "255.255.255.255" IP address. Workaround: Instead of a network name, enter the NTP server IP address. 12 Known issues and workarounds

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
Known issues and workarounds
Issue:
When installing a firmware update using the Smart Component, the installation routine may incorrectly report that
the upgrade was unsuccessful.
Workaround:
If the Smart Component installation routine states that a firmware load was unsuccessful, verify which version
of firmware is installed using an array management utility, such as the SMU or CLI. If the version listed is the old version,
run the Smart Component again.
Issue:
When creating a user or modifying user information in the SMU, there is no option to enable the SMI-S interface for
the user.
Workaround:
Add the SMI-S interfaces to the user using the
set user interfaces
CLI command, making sure to
include all appropriate interfaces.
Issue:
If the iSCSI IQN name is longer than 55 characters, the enumeration of CIM_StorageHardwareID fails.
Workaround:
Modify the IQN name to be shorter than 55 characters
Issue:
Manually creating a replication-prepared (secondary) volume and associating it with a primary volume originally
created with pre-TS230 firmware can fail. Automatically created secondary volumes do not have this problem.
Workaround:
•
In the SMU, use the Replication Setup Wizard or the Replicate Volume task or, in the CLI, use the
create replication
set
command to automatically create the secondary volume. (Preferred workaround))
•
Issue the following commands in the CLI to specify the block size of the manually created secondary volume, ensuring
that it is exactly the same size as the source volume (Alternative workaround):
1.
In CLI API format, use the
show volumes <volume-name>
command to determine the size of the pre-T230 volume
in blocks. This will be displayed by the "size-numeric" property.
2.
Use the
create volume
command and specify the size in blocks (obtained in step 1) -to create the
replication-prepared volume.
3.
Create a replication set that associates the two volumes.
Issue:
During path failover events on systems with large LUN counts, Red Hat Enterprise Linux 4 iSCSI clients may report
issues accessing devices.
Workaround:
Increase the disk timeout to a minimum of 60 seconds.
Issue:
When using both the primary and secondary paths on both ports of the Qlogic iSCSI HBAs, failover does not work
correctly on cable pulls.
Workaround:
When setting up the Qlogic iSCSI HBAs, set up only the primary path for both ports.
Issue:
When creating a volume set with the volumes mapped to LUNs, if there is a LUN conflict, the array will stop mapping
volumes to LUNs, but will create 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:
In dual-controller systems, accessing the SMU of a controller does not display vdisks owned by the other controller.
Workaround:
Restart the other controller.
Issue:
In the CLI, the
TakeSnapshot
task returns the message: “Unable to validate retention limits. – The user is not
recognized on this system.”
Workaround:
Restart the controller accessed.
Issue:
In the SMU, the Japanese version of some pages and some error messages displays English text.
Workaround:
None.
Issue:
A failed drive becomes available when the vdisk that it was a member of is deleted.
Workaround:
Do not use the drive.
Issue:
The array will incorrectly accept a DNS name for the address of the NTP server in the Storage Management Utility.
The array does not use DNS, and will translate the name into an invalid “255.255.255.255” IP address.
Workaround:
Instead of a network name, enter the NTP server IP address.
12
Known issues and workarounds