HP P2000 Release Note page 13

Issue: In the Command Line Interface, the array will incorrectly accept a DNS name for the address for the SMNP, SMTP,
and NTP servers. The array does not use DNS, and will not be able to connect to the server correctly.
Workaround: Instead of network names, enter the IP addresses for the servers.
Issue: In Windows configurations, the IQN shown by the NC551 card during POST may not match the IQN seen in the
array controller. This occurs when the NC551 was set up in a boot-from-storage configuration. After an operating system
is installed, the POST message will show the IQN that is supplied by the iSCSI Software Initiator, but the NC551 BIOS will
continue to use the IQN setup to boot the OS.
Workaround: Using the NC551 BIOS Utility, remove the boot settings and then log back into the array with the new IQN.
If the volume used for mapping was explicitly mapped to the host, recreate the mapping for the new IQN.
Issue: When accessing more than 128 LUNs using a Qlogic iSCSI HBA in boot-from-storage configurations, the system my
hang when a reset is issued on the array.
Workaround: Access 128 LUNs or less via the Qlogic iSCSI HBA when using the card in boot-from-storage configurations.
Issue: RHEL 4.8 may not discover all multipath devices and partitions during boot or reboot.
Workaround: This issue is addressed by applying the updated device-mapper-multipath package described in RedHat Bug
Fix Advisory RHBA-2009:1524- 1 , available at
Issue: RHEL 5.4 may not discover all multipath devices and partitions during boot or reboot.
Workaround: This issue is addressed by applying the updated device-mapper-multipath packages described in RedHat
Bug Fix Advisory RHBA-2010:0255- 1 , available at https://rhn.redhat.com/errata/RHBA-2010-0255.html.
Issue: Under rare circumstances, some events from one controller are not seen on the other controller.
Workaround: Review the events from both controllers.
Issue: During a firmware upgrade, the firmware bundle version may show incorrectly.
Workaround: Wait until the firmware upgrade process is complete before checking the firmware bundle version.
Issue: Java script issues are seen when using Microsoft Internet Explorer in multi-byte language locales, resulting in truncated
messaging and hung pop-up windows. These issues will be resolved in future a firmware release.
Workaround: This is a display problem only. When a pop-up window remains on screen with no update for a prolonged
period, close and then re-open the browser. The Internet Explorer English locale and the Firefox browser will not exhibit
the issues.
Issue: In SLES 1 1 environments, when using the iSCSI initiator tools included in SLES 1 1, the host will occasionally not
correctly log into the iSCSI array on reboot, even when set to automatically connect.
Workaround: Restart the iSCSI service on the SLES 1 1 host. This can be done by entering the following command:
/etc/init.d/open-iscsi restart
Issue: SLES 1 1 may 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: SLES 1 1 SP1 may not create all devices during boot. This typically involves a system with a large number of LUNs,
multiple LUN paths, and the SLES 1 1 SP1 open-iscsi utilities.
Workaround: Do one of the following:
Install the following Novell patches:
◦
kpartx-0.4.8-40.23.1.x86_64.rpm
◦ libvolume_id1-128-13.11.4.x86_64.rpm
◦ multipath-tools-0.4.8-40.23.1.x86_64.rpm
◦ open-iscsi-2.0.871-0.22.1.x86_64.rpm
◦ udev-128-13.11.4.x86_64.rpm
Run the /sbin/multipath -v 0 command to force multipathd to rescan all LUNs and paths and create any devices
that were not correctly created before.
Issue: In rare conditions, the array controller may report that a supported 10 GbE SFP+, 10GbE Copper Cable, or 10GbE
Direct Attach Cable is unsupported. This condition is most likely to occur when a SFP+, Copper Cable, or Direct Attach
Cable is hot plugged into the controller while the controller is running. When this occurs, the following Warning message
http://rhn.redhat.com/errata/RHBA-2009- 1 524.html.
Known issues and workarounds 13