Unsolved
This post is more than 5 years old
4 Posts
0
5854
May 8th, 2009 11:00
MD3000i / ESXi Networking Problem
First time iSCSI user.
I setup MD3000i and ESXi host on internal LAN (10.0.0.x) for testing. Left ESXi eth1 unused. Was able to enable iSCSI, set send targets, config host access, create host-to-virt disk map, etc. and rescanned HBA.
That worked ok, after scan completed, I was able to see the LUNs in ESXi.
Next, I wanted to move the iSCSI traffic off to dedicated, isolated, switches.
So I physically moved iSCSI cables to 2 standalone switches, edited MD Host Ports setting them back to the defaults (192.168.130.x & 131.x).
Enabled ESXi ETH1 as VMkernel and set to IP in same range as one of the segments (192.168.130.103). I'll be adding more eth ports soon for the second subnet.
I left the two MD mgmnt ports in the LAN (10.0.0.18 & 140).
On ESXi, I removed the old send targets and entered the new IPs (192.168.130.101 & 102).
Rebooted everything for good measure. Rescanned HBA, but the LUNS do NOT show up in ESXi.
What am I doing wrong?
Thanks in advance for your help!
I setup MD3000i and ESXi host on internal LAN (10.0.0.x) for testing. Left ESXi eth1 unused. Was able to enable iSCSI, set send targets, config host access, create host-to-virt disk map, etc. and rescanned HBA.
That worked ok, after scan completed, I was able to see the LUNs in ESXi.
Next, I wanted to move the iSCSI traffic off to dedicated, isolated, switches.
So I physically moved iSCSI cables to 2 standalone switches, edited MD Host Ports setting them back to the defaults (192.168.130.x & 131.x).
Enabled ESXi ETH1 as VMkernel and set to IP in same range as one of the segments (192.168.130.103). I'll be adding more eth ports soon for the second subnet.
I left the two MD mgmnt ports in the LAN (10.0.0.18 & 140).
On ESXi, I removed the old send targets and entered the new IPs (192.168.130.101 & 102).
Rebooted everything for good measure. Rescanned HBA, but the LUNS do NOT show up in ESXi.
What am I doing wrong?
Thanks in advance for your help!
No Events found!
ronniereid
4 Posts
0
May 8th, 2009 11:00
MD Host Ports:
Mgmt1: 10.0.0.18, 255.255.255.0
Mgmt2: 10.0.0.140, 255.255.255.0
0:0, 192.168.130.101, 255.255.255.0, 192.168.130.0 is gateway, but the switch is isolated
0:1, 192.168.131.101, 255.255.255.0, 192.168.131.0 is gateway, but the switch is isolated
1:0, 192.168.130.102, 255.255.255.0, 192.168.130.0 is gateway, but the switch is isolated
1:1, 192.168.131.102, 255.255.255.0, 192.168.131.0 is gateway, but the switch is isolated
ESXi vSwitch0
VM Network, VMKernel: 10.0.0.63
ESXi vSwitch1
VMkernel: 192.168.130.103
ronniereid
4 Posts
0
May 8th, 2009 13:00
http://communities.vmware.com/message/1247343
Any ideas?
ronniereid
4 Posts
0
May 8th, 2009 14:00
Apparently, the ESXi iSCSI Initiator needs to be (re)enabled AFTER adding the vSwitch on the isolated network. My theory is that it was using the 1st VMkernel switch for discovery.
After adding the second VMkernel switch for the isolated iSCSI network, I disabled iSCSI in ESXi, rebooted, then re-enabled it. After rescanning HBA, the LUNs appeared.
Scott Hanson
342 Posts
0
May 8th, 2009 22:00