VMware
1 Replies Last post: May 18, 2007 6:53 AM by Dave.Mishchen…  

Not getting iscsi connection to work with 3.01.. posted: May 18, 2007 6:34 AM

Click to view TheKingNL's profile Novice 13 posts since
Jul 23, 2006
Hi guys,

I installed a clean ESX 3.01 test box with two physical nics. One is connected to my internal network, and the other one the my SAN network. The "SAN" NIC is connected to a GB-switch and the switch has a connection to an Equallogic SAN.

The first NIC has 10.0.0.100 /255.255.255.0 and is configured with the service console.

The second NIC has 192.168.1.100 /255.255.255.0.

I first enabled the iSCSI client on the FW.

I then used networking to configure the VM Kernel on the second NIC. (So 192.168.1.100)

I then enable the iSCSI Software Adapter and added the SAN (192.168.1.10) to the Dynamic Discovery tab. The system does not discovery anything however. I did a rescan/reboot a few times.

- When I select the iscsi software adapter and check the details it does not list an ip address. The field is empty. Is this OK?

Anybody some help? How can I troubleshoot this isse?

I checked the manual and they explain I should add another service console connection on the "SAN" NIC? This sounds strange to me as this NIC is not connected to my normal network. Should I add a service console? And which IP should I use?
Click to view Dave.Mishchenko's profile Guru 8,876 posts since
Nov 15, 2005

  • I do not see the ESX server connecting to my SAN.
  • I can not ping 192.168.1.10 (SAN) from the ESX
console. I can however ping 192.168.1.100 (ESX) from
another host connected to the SAN network. So maybe
it's normal one can't ping from the console to this
IP?
Try vmkping - but that's not the issue here.

- One I go to "Network Adapters" it list
192.168.1.200 - 192.168.1.207. It should list
192.168.1.1 - 192.168.1.254 I assume? As subnet is
/24.
What's seen here is not usually that accurate

I checked the manual and they explain I should add
another service console connection on the "SAN" NIC?
This sounds strange to me as this NIC is not
connected to my normal network. Should I add a
service console? And which IP should I use?

You'll need to add a service console port on that subnet (with a 192.168.1.x IP). The SC handles the initial connection to the iSCSI server and once the connection is made then the traffic is sent via the vmkernel.

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities