We have a small issue were we have LUNs that are being brought into service as AA rather than ALUA. All our hosts are ESX 4.1u1 with NetApp FC storage. The igroup is ALUA enabled. Some hosts bring in all the LUNs as ALUA and some have a few that get detected as AA. Here are a few messages that I’ve come across that might be related.
From messages log:
Aug 18 08:44:33 esxp007 sfcb-vmware_base[9119]: -#- Serious provider id / provider process mismatch --- (PID=9119, ProcName=vmware_base, ReqProvId=20185095)
Aug 18 08:44:33 esxp007 sfcb-vmware_base[9119]: Provider is not found
Here is another entry as well vmkernel:
Aug 18 09:48:46 esxp007 vmkernel: 34:14:05:02.678 cpu4:24519)WARNING: NMP: nmp_AddPathToDevice: The SATP for physical path "vmhba0:C0:T3:L9" (VMW_SATP_DEFAULT_AA) does not match the SATP and options already associated with NMP device with primary uid "naa.60a98000486e2f422f4a4c6d
Aug 18 09:48:46 esxp007 vmkernel: 34:14:05:02.678 cpu4:24519)WARNING: VMW_SATP_ALUA: satp_alua_getTargetPortInfo: Could not find relative target port ID for path "vmhba0:C0:T3:L9" - Not found (195887107)
Aug 18 09:48:46 esxp007 vmkernel: 34:14:05:02.678 cpu4:24519)WARNING: NMP: nmp_SatpClaimPath: SATP "VMW_SATP_ALUA" could not add path "vmhba0:C0:T3:L9" for device "naa.60a98000486e2f422f4a4c6d30395467". Error Not foundd
Aug 18 09:48:46 esxp007 vmkernel: 34:14:05:02.678 cpu4:24519)WARNING: ScsiPath: 3815: Plugin 'NMP' had an error (Not found) while claiming path 'vmhba0:C0:T3:L9'.Skipping the path.
Aug 18 09:48:46 esxp007 vmkernel: 34:14:05:02.678 cpu4:24519)ScsiClaimrule: 1183: Plugin NMP specified by claimrule 65535 was not able to claim path vmhba0:C0:T3:L9. Busy
Aug 18 09:48:46 esxp007 vmkernel: 34:14:05:02.678 cpu4:24519)ScsiClaimrule: 1405: Error claiming path vmhba0:C0:T3:L9. Busy.
I might have to open a ticket to get to the bottom of this.
Any thoughts here? I inherited these host and am new to NetApp storage as well.
