Hi BAAAASS,
I have tried both a 600GB and a 4GB partition.
Main Topics
Browse All TopicsI've spent about 6 hours on the phone with Dell to no avail. We cannot get my Dell R710 ESXi 3.5 184236 to connect to a new MD3000i. The R710 has the onboard Broadcom's connected to the general network, and then 2 Intel GB NIC's connected to the iSCSI network (10.0.2.xx and 10.0.3.xx). The MD3000i has dual controllers connected to 2 switches. 2 Windows 2003 servers are successfully connected to the MD3000i. Here's a rundown of what we have done:
1. Tried connecting by having only one of the network iSCSI connections enabled.
2. Associated the virtual disks to both the ESX group and the ESXi_1 server.
3. Shortened the iSCSI host name of the ESXi server.
4. Configured a VM to be on the iSCSI network subnet, ensuring the VM could ping the MD3000i host.
5. Rebooted the ESXi_1 server multiple times.
I am able to ping the ESXi server from a Windows machine on the same iSCSI network. I have worked with both the Enterprise Server and the MD3000i support groups. The next solution is to have a person in my remote office access the ESXi server, go to the unsupported mode, and trying pinging port 3260 on the ESXi. I am hesitant to do this though in case anything goes awry.
Are there any ideas on what might be going wrong?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Keeping in mind that VMWare is not my area of expertise.
But based on the following:
* Other Servers are currently connecting fine to the SAN
* In essence the ESXi Server is running fine on its own Set of Local HDD - Please confirm
I can only guess that there are settings discrepancies between the iSCSI settings - can you double check this?
Yes, the R710 has a bunch of local disks in a RAID 10 array. My goal is to migrate the storage to the MD3000i. It does have the DRAC installed, but it is only the Express version so it doesn't have a console option.
I've gone through the settings on the MD3000i group and the ESXi settings with the Dell Enterprise people. The setup on ESXi seems very straightforward there are only a handful of things to do:
1. Add the storage adaptor and VMKernels
2. Enable iSCSI
3. Reboot
4. Add the host to the MD3000i
5. Setup a virtual disk and LUN
6. Have the ESXi server scan for changes
Thanks for the info. Do you mean that I need to have a VMWare Inf Client running on the iSCSI network? If so, I can give that a try. My primary Windows host has the VM Client on it. Do I just try and access the host on the iSCSI ip address (of the ESXi box)?
I have been able to setup a Ubuntu VM on the iSCSI network and it can access the MD3000i after some googling on how to do it.
I just got an update from Dell. The ESXi logs are showing that the MD3000i is rejecting discovery. This is an entry from the MD3000i log:
Date/Time: 10/21/09 3:21:50 PM
Sequence number: 982
Event type: 1808
Description: Login failure
Event specific codes: 0/0/0
Event category: Error
Component type: RAID Controller Module
Component location: iqn.1998-01.com.vmware:esx
Logged by: RAID Controller Module in slot 1
Did you open the firewall port on your ESX server for ISCSI.
after doing this enable the iscsi iniator on vmware and type the ip of one of the MD3000i controllers.
Then on the md3000i, you should see this new connection(WWN). Created a server group for this ISCSI connection. Then assign a virtual disk to this new server group.
Also do you have CHAP enabled on the MD3000i or some other authentication?
most likely zoning on the MD3000 if it's not accepting discovery. I remember in the ESX 3.5 I had an issue with setting up an ESX/ESXi host with capital letters which would mess up the iSCSI IQN. If you're using capitals for the host try to redo it with lowercase letters and redo the IQN. Make sure you configure it as an iSCSI initiator on the MD3000 and check the zoning.
Business Accounts
Answer for Membership
by: BAAAASSPosted on 2009-10-21 at 07:56:18ID: 25624575
How big is the LUN on the 3000i you are trying to allocate for the ESXi server?