HP P2000 HP StorageWorks P2000 G3 10GbE iSCSI MSA System Controller Firmware R - Page 4

Known issues and workarounds, When changing a replication set for example - quickspecs

Page 4 highlights

• When changing a replication set (for example, adding or removing a replication volume, or deleting the replication set), do so from the source system; when aborting, suspending or resuming a replication, do so from the destination system. • When changing the external-view volume of a replication set, do so from the destination system first, then perform the change on the source system. • MSA70 disk enclosures are supported for use with P2000 G3 arrays, but must have firmware 2.18 installed. Please check the MSA70 or P2000 G3 QuickSpecs to confirm which version MSA70 firmware is supported. Known issues and workarounds Issue: In SLES 11 environments, when using the iSCSI initiator tools included in SLES 11, 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 11 host. This can be done by entering the /etc/init.d/ open-iscsi restart command. Issue:SLES 11 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 11 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 11 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 0command 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 will be recorded in the event logs: "An unsupported cable or SFP was inserted". At the same time, the host port will not show a status of "Down". Workaround: Do the following: 1. Verify that the SFP+, Copper Cable, or Direct Attach Cable is a supported component. For support inform- ation, see the P2000 G3 QuickSpecs on the P2000 G3 product page: http://www.hp.com/go/p2000. 2. If the components are indeed listed as supported models, remove and reinsert the SFP+, Copper Cable, or Direct Attach cable. 3. If this does not correct the issue with the SFP+, Copper Cable, or Direct Attach Cable connected to the controller, either remove and reinsert the controller or power down and reapply power to the array. Issue: RHEL 5 Update 5 will not shutdown properly when using the iSCSI initiator utilities shipped in RHEL 5 Update 5 to access the array. Workaround: See issue 583218 on the Red Hat Bugzilla bug-tracking system https://bugzilla.redhat.com/ show_bug.cgi?id=583218 for the current status of the issue and possible workarounds. 4

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8

When changing a replication set (for example, adding or removing a replication volume, or de-
leting the replication set), do so from the source system; when aborting, suspending or resuming
a replication, do so from the destination system.
When changing the external-view volume of a replication set, do so from the destination system
first, then perform the change on the source system.
MSA70 disk enclosures are supported for use with P2000 G3 arrays, but must have firmware
2.18 installed. Please check the MSA70 or P2000 G3 QuickSpecs to confirm which version
MSA70 firmware is supported.
Known issues and workarounds
Issue:
In SLES 11 environments, when using the iSCSI initiator tools included in SLES 11, 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 11 host. This can be done by entering the
/etc/init.d/
open-iscsi restart
command.
Issue:
SLES 11 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 11 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 11 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 will be recorded in the event logs:
An unsupported cable or SFP
was inserted". At the same time, the host port will not show a status of "Down".
Workaround:
Do the following:
1.
Verify that the SFP+, Copper Cable, or Direct Attach Cable is a supported component. For support inform-
ation, see the P2000 G3 QuickSpecs on the P2000 G3 product page:
h
t
tp://w
w
w
.hp
.co
m/go/p2000
.
2.
If the components are indeed listed as supported models, remove and reinsert the SFP+, Copper Cable,
or Direct Attach cable.
3.
If this does not correct the issue with the SFP+, Copper Cable, or Direct Attach Cable connected to the
controller, either remove and reinsert the controller or power down and reapply power to the array.
Issue:
RHEL 5 Update 5 will not shutdown properly when using the iSCSI initiator utilities shipped in RHEL 5
Update 5 to access the array.
Workaround:
See issue 583218 on the Red Hat Bugzilla bug-tracking system
h
t
tp
s://bugzilla
.r
edhat
.co
m/
sh
o
w_bug
.cgi?i
d=5
8
3
218
for the current status of the issue and possible workarounds.
4