Loading...
Loading...
Revision TableVersionDateDetails327 February 2014Added two paragraphs regarding P2000 to the bottom of the Note in the Workaround section. Revised the name of HP P2000 G3 SAS MSA in the Scope section.24 October 2013Added notes regarding SCSI-2 to the Workaround section.111 February 2013Original document release.A compatibility issue between the HP Smart Array P711m, P712m and P721m Controllers and the P2000G3 VAAI plugin Atomic Test and Set (ATS) primitive on HP P2000 G3 SAS MSA Dual Controller LFF Array Systems and HP P2000 G3 SAS MSA Dual Controller SFF Array Systems may cause boot from storage and datastore creation failures when using VMware ESXi5.x or ESX/ESXi4.1.When this issue occurs, messages similar to the following will be logged in the VMkernel log file of the ESX server:2012-10-25T15:22:34.347Z cpu28:8220)WARNING: NMP: nmp_DeviceRetryCommand:133:Device2012-10-25T15:22:35.249Z cpu24:8839)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.600c0ff0001344cecd99725001000000" - issuing command 0x4124419f01002012-10-25T15:22:35.249Z cpu4:8196)<4>hpsa 0000:0c:00.0: Device:C1:B0:T2:L1 Command:0xc2 Command Invalid.2012-10-25T15:22:35.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:348:Retry cmd 0xc2 (0x4124419f0100) to dev "naa.600c0ff0001344cecd99725001000000" failed on path "vmhba8:C0:T2:L1" H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2012-10-25T15:22:35.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:378:Logical device "naa.600c0ff0001344cecd99725001000000": awaiting fast path state update before retrying failed command again...2012-10-25T15:22:36.249Z cpu7:10340)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.600c0ff0001344cecd99725001000000" - issuing command 0x4124419f01002012-10-25T15:22:36.249Z cpu4:8196)<4>hpsa 0000:0c:00.0: Device:C1:B0:T2:L1 Command:0xc2 Command Invalid.2012-10-25T15:22:36.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:348:Retry cmd 0xc2 (0x4124419f0100) to dev "naa.600c0ff0001344cecd99725001000000" failed on path "vmhba8:C0:T2:L1" H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2012-10-25T15:22:36.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:378:Logical device "naa.600c0ff0001344cecd99725001000000": awaiting fast path state update before retrying failed command again...2012-10-25T15:22:37.249Z cpu24:8839)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.600c0ff0001344cecd99725001000000" - issuing command 0x4124419f01002012-10-25T15:22:37.249Z cpu4:8196)<4>hpsa 0000:0c:00.0: Device:C1:B0:T2:L1 Command:0xc2 Command Invalid.2012-10-25T15:22:37.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:348:Retry cmd 0xc2 (0x4124419f0100) to dev "naa.600c0ff0001344cecd99725001000000" failed on path "vmhba8:C0:T2:L1" H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2012-10-25T15:22:37.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:378:Logical device "naa.600c0ff0001344cecd99725001000000": awaiting fast path state update before retrying failed command again...2012-10-25T15:22:38.249Z cpu7:10340)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device "naa.600c0ff0001344cecd99725001000000" - issuing command 0x4124419f01002012-10-25T15:22:38.249Z cpu4:8668)<4>hpsa 0000:0c:00.0: Device:C1:B0:T2:L1 Command:0xc2 Command Invalid.2012-10-25T15:22:38.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:348:Retry cmd 0xc2 (0x4124419f0100) to dev "naa.600c0ff0001344cecd99725001000000" failed on path "vmhba8:C0:T2:L1" H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.2012-10-25T15:22:38.249Z cpu28:8220)WARNING: NMP: nmpCompleteRetryForPath:378:Logical device"naa.600c0ff0001344cecd99725001000000": awaiting fast path state update before retrying failed command again...2012-10-25T15:22:39.249Z cpu24:8839)WARNING: NMP: nmpDeviceAttemptFailover:599:Retry world failover device"naa.600c0ff0001344cecd99725001000000" - issuing command 0x4124419f01002012-10-25T15:22:39.249Z cpu4:8668)<4>hpsa 0000:0c:00.0: Device:C1:B0:T2:L1 Command:0xc2 Command Invalid.Messages may not be available for boot from storage failures. Because of this issue, booting from the SAN operation in the configuration above is currently unsupported.The HP Custom ISO Images for VMware ESXi began including the P2000G3 VAAI plugin in June 2012 for both ESX/ESXi4.1 and ESXi5.x releases. If one of these custom images is used, the P2000G3 VAAI plugin will be installed by default. For additional information on HP Custom ISO Image contents, refer to the following link:http://h18004.www1.hp.com/products/servers/software/vmware-esxi/driver_version.html
This issue only impacts configurations that useallof the following components unless specified otherwise:Hypervisor:VMware ESXi5.1, VMware ESXi5.0, and VMware ESX/ESXi4.1, including all supported updates.Host Bus Adapter: Any of the following:HP Smart Array P711m ControllerHP Smart Array P712m ControllerHP Smart Array P721m ControllerHost bus Adapter driver/firmware:AnyProLiant servers:ProLiant blade server configurations using P711m, P712m and P721m controllers connected to the HP P2000 G3 SAS MSA Array System ControllerStorage Array:HP P2000 G3 SAS MSA Array System ControllerStorage Array firmware: Any of the following:TS230TS240Software:P2000 VAAI plugin version1 or version 2Rack mount ProLiant servers using the HP H221 Host Bus Adapter connected to the HP P2000 G3 SAS MSA Dual Controller LFF Array Systems and HP P2000 G3 SAS MSA Dual Controller SFF Array Systems are not affected by this issue.
Refer to the Workaround section.WorkaroundThe following workaround will effectively address this issue for configurations where ESX is booted locally:Disable the Atomic Test and Set (ATS) primitive.VMware ESX VAAI features are controlled by a set of global parameters also referred to as primitives. One of these primitives is the Atomic Test and Set (ATS) primitive used on VMFS datastore. Disabling this global primitive at the ESX level will disable the ability of ESX to invoke this command and resolve the datastore creation issue. To disable this primitive, you must use the ESX CLI, vCLI or vMA and issue the command:Example, ESX CLI for ESXi5.x:To disable:esxcli system settings advanced set –I 0 –o /VMFS3/HardwareAcceleratedLockingCheck the value:esxcli system settings advanced list–o /VMFS3/HardwareAcceleratedLockingExample, ESX CLI for ESX/ESXi4.1:To disable:esxcfg-advcfg–s 0 /VMFS3/HardwareAcceleratedLockingCheck the value:esxcfg-advcfg–g /VMFS3/HardwareAcceleratedLockingDisabling the VAAI ATS primitive will cause ESX to revert back to using SCSI-2 reservation instead of the SCSI Compare-Write (ATS) commands for datastore resource arbitration. The use of SCSI-2 reservation yields more resource contention and lower scalability for the datastore than ATS.Customers running the affected configuration described above who experience SCSI-2 reservation conflict issues after disabling the ATS primitive, should not re-enable the ATS primitive to address the reservation conflict issues. This would put the configuration right back into the scenario described in this advisory.Until a fix is released for this issue, customers should address the the SCSI-2 reservation conflict issues directly. The following VMware KB article is a good start at identifying and resolving such reservation conflict issues.KB Article 1005009:http://kb.vmware.comBoot from storage configurationsmustrevert to a local boot configuration, and this workaround must be applied.The P2000 VAAI VIB,hp_vaaip_p2000 - Version 2.1.0-2, was removed from the September 2013 ESXi5.5, ESXi5.1U1 and ESXi5.0U2 HP images.Customers using Fibre Channel and/or iSCSI P2000 arrays wishing to use the VAAI plugin with these ESXi versions, will need to manually install the plugin.
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.