Thanks for the link. I got it to work - I implemented the linked VMWare configuration, and then after plugging in the Debug Port's serial cable on the MD3600i, I was able to see more output and I realized I had accidentally enabled "disallow unnamed discovery" in the iSCSI config on the MD3600i.  As well, the initiator's auto-generated host port identifier was over 40 characters long - I found a link indicating some of Dell's implementations don't like anything over 31 characters, which appeared to also be causing me problems (it still didn't work after removing the "disallow unnamed discovery").  I shorted the initiator's identifier below that, rescanned from VMWare, and it all works now. Thanks again.
Hi, I am attempting to configure an MD3600i using iSCSI, with 3 x VMWare ESXi 4.1 U 1 servers connecting to it.  So far I'm still trying to get 1 x server connected to the SAN :( I have followed Dell's MD32xx/MD36xx deployment guide with ESX 4.1 ([URL] ).  The MD3600i has virtual drives and host group configured, and it even saw VMWare's host port identifier before configuring the Host Group, and let me associate the identifier directly to the Host Group when prompted.   However, I am then unable to rescan from the iSCSI initiator in VMWare and see any drives.  The ESXi server says "In Progress" for a while and then times out.  While connecting, the MD3600i event log lists "Login failure" (Event 1808). I have tried configuring both the MD3600i's target authentication and the ESXi iSCSI initiator to CHAP (made sure I was entering the correct password) as well as no authentication, and it still throws that error.  I am unable to find this error in the above doc, the MD3600i deployment guide or owner's manual, or in any searching I've done so far. Any ideas?   Thanks in advance.
MD3600i - VMWare iSCSI initiator causing "login failure" error, won't see iSCSI 
target