HP P6000 1GbE iSCSI and 10GbE iSCSI/FCoE Firmware Release Notes (5697-3242, March 2014)

• Microsoft Windows 2012 LOGO conformance test failure, where a persistent reservation
generation in the PERSISTENT RESERVE IN SCSI command parameter data field was
not incremented when a Microsoft Windows 2012 iSCSI or FCoE initiator PREEMPTed its own
reservation.
• iSCSI and iSCSI/FCoE Product enhancement support for thin provisioned overcommitted
(TPOC) LUN handling for non-Windows iSCSI and FCoE initiators when combined with
XCS11001000 and later revisions, and P6000 Command View 10 and later revisions:
◦ TPOC LUNs presented to non-Windows initiators are write protected instead of going
offline while the TPOC state persists. TPOC LUNs presented to Windows and Microsoft
Windows 2008 initiators are masked by the iSCSI and iSCSI/FCoE modules. HP P6000
Command View is utilized to resolve the overcommitted state and then to clear the mask
by re-presenting previously overcommitted LUNs presented to the iSCSI MPX HOSTs to
the respective iSCSI and FCoE initiators.
◦ TPOC LUNs presented to Windows and Microsoft Windows 2008 initiators are offline
masked while the overcommitted state persists. This behavior occurs for all iSCSI and
iSCSI/FCoE initiator types with MEZ50-3_0_4_1 and MEZ75-3_2_2_6 firmware.
• iSCSI Product enhancement support of 1024 LUNS by enabling Virtual Port Groups VP2,3,4.
This feature is now enabled by default and is the same as the default setting for the iSCSI/FCoE
modules and for the MPX200 Multifunction Router. This enhancement enables the iSCSI and
iSCSI/FCoE modules to share a common firmware code base. P6000 Command View 10.1
supports this enhancement.
• iSCSI and iSCSI/FCoE modules sometimes fail the Persistent Reserve in the report
capabilities command.
• iSCSI and iSCSI/FCoE modules report unexpected reservation conflict responses after
preemption during clustered servers failover.
• iSCSI/FCoE modules experiencing repeated FCoE port RSCNs might report Task Set Full
resulting from running out of handling resources.
• iSCSI/FCoE modules VPgroups 2,3,4 FCoE-WWN persistence is incorrectly maintained after
controller replacement and full configuration restore.
• iSCSI/FCoE set CHAP sometimes failed to save for virtual (VPgroup) presented targets.
• iSCSI and iSCSI/FCoE modules jumbo frame handling might cause a kernel panic restart.
• iSCSI Initiator left in reconnecting state after iSCSI module code load or reboot.
• iSCSI module GE1 link sometimes down after controller power cycle.
• 10GbE iSCSI initiator causing iSCSI/FCoE module software crash and reboot.
• 10GbE iSNS connectivity causing iSCSI/FCoE module software crash and reboot.
• Microsoft Windows 2008 native MPIO discovery failure for iSCSI/FCoE module presented
targets.
• iSCSI and iSCSI/FCoE module peer-peer communication re-sync failure after a reboot.
• The CLI ->show peers command is enhanced to display real-time peer-peer link status.
• The log file is enhanced to include peer-peer link status changes.
• iSCSI and iSCSI/FCoE module P6000 Command View management of CHAP settings for
VPgroup 3 and 4 API failure.
• iSCSI/FCoE module utilizing the FCoE protocol incorrectly responds with good instead of
queue full status resulting in a lost write data.
6