Alright, got an interesting issue here. I have an environment that I had up and running for over a month in ESX 3.5 U4 with iSCSI connected to several luns on a Netapp 270 running OnTap 126.96.36.199. I have reloaded those same servers with ESX 4. When trying to get iscsi working, I am having absolutely no luck. My problem is similar to this issue, but I don’t even have paths listed out.
I can have them in the same igroup on the filer, but not matter what, the vsphere server will not connect. This happened on both vSphere installs (until I reloaded the one with 3.5 an hour ago, now it’s fine)
I can ping and vmkping 10.1.1.40 from the esx host, and I can ping both the console ip and the vmkernel from the filer. Firewall expetions were added of course, and even allowed all incoming and outgoing traffic.
I have had 2 other people look at it as well for several hours today, so I am quite sure the basics were covered.
I am convinced it is an issue with ESX 4. I have reloaded both machines several times today from scratch, and each time I can configure esx 3.5 no problem with iscsi and nfs, but it won't work no matter what I do with ESX 4. I don't have an explanation. It seems like ESX 4 hates a FAS 270. It is still on the hardware compatibility list for ESX 4 as well.
I implemented an ESX 4 and EMC Storage solution with NO problems. I have now come to do the exact same project but on a FAS2020. I have read a lot of the posts regarding this and wondered if this had been escalated within NetApp for a resolution..