Summary
While running agent base virtualization job on vCenter 5, it failed because the iSCSI initiator of vCenter could not establish a network connection to the target of FAS, if initiator and target are not in the same subnet.
Symptoms
1. Virtualization job log has error message similar to "java.lang.Exception: Failed to find lun iqn.1992-08.com.netapp:sn.84186047 lun number 0on SCSI adapter vmhba34";
2. The hostd.log from ESXi server showed error message similar to "[2D249B90 info 'ha-eventmgr'] Event 846 : Login to iSCSI target iqn.1992-08.com.netapp:sn.84309427 on vmhba34 @ vmk1 failed. The iSCSI initiator could not establish a network connection to the target."
Resolution
VMware vCenter 5 introduces a new 'Network Configuration' tab in the Sotware iSCSI Adapter properties window. It's used for binding ports to the iSCSI adapter.
After selecting the VMkernel adapters for use with the Software iSCSI Adapter, the Port Group Policy tab will tell you whether or not these adapters are compliant or not for binding. If you have more than one active uplink on a vSwitch that has multiple vmnic uplinks, the vmk interfaces will not show up as compliant. Only one uplink should be active, all other uplinks should be placed into an unused state.
From VMware KB: Cannot reach iSCSI target after enabling iSCSI port binding on ESX/ESXi 4.x and ESXi 5.0 (see the link in Reference Document), iSCSI port binding in ESXi 5.x does not support routing.
To resolve this issue and still use iSCSI port binding, you must place the iSCSI initiator and the iSCSI target on the same subnet.
Or resolve this issue by disabling iSCSI port binding.
To disable iSCSI port binding, remove the selected VMkernel adapters from 'Network Configuration' tab in the Sotware iSCSI Adapter properties window.