Configuring ISCSI in VCSA 6.7.0
Trying out Starwind (free version). Did some very basic configuration for it and it appears to be running.
In the web UI host configuration, I have an ISCSI Software Adapter running (vmhba64), status Online, with a server defined at 10.0.0.10:3260 (which is the IP address of the Windows 10gb nic cards). But it also shows Under Targets/devices/paths 0 0 0 for all 3.
Selecting that adapter, there is nothing under the Devices tab below, nor Paths, Dynamic Discovery has the 10.0.0.10:3260 listed.
Network Port Binding shows VMkernael (vSwitch2) as the port group, vmk0 as the VMkernal Adapter, and Compliant as the port group policy. The Path Status is <>Not used, and points to vmnic2 for the Physical Network Adapter.
Pretty sure I haven't finished the configuration on this properly yet. ?
--Ben
In the web UI host configuration, I have an ISCSI Software Adapter running (vmhba64), status Online, with a server defined at 10.0.0.10:3260 (which is the IP address of the Windows 10gb nic cards). But it also shows Under Targets/devices/paths 0 0 0 for all 3.
Selecting that adapter, there is nothing under the Devices tab below, nor Paths, Dynamic Discovery has the 10.0.0.10:3260 listed.
Network Port Binding shows VMkernael (vSwitch2) as the port group, vmk0 as the VMkernal Adapter, and Compliant as the port group policy. The Path Status is <>Not used, and points to vmnic2 for the Physical Network Adapter.
Pretty sure I haven't finished the configuration on this properly yet. ?
--Ben
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
iSCSI has got nothing to do with vCenter Server.
iSCSI is configured per ESXi host. (either via Host HTML client or via vCenter Server if applicable).
You only need to do bindings, with mulitpath....
The first thing you want to do is use ping and vmkping 10.0.0.10 which will test if you can send packets to the SAN (iSCSI)
You can use -I vmk0 to send actual vmkping packets through this interface, this confirms communications.
NEXT, you've got to configure iSCSI LUNs, and add the IQN of the hba, to grant access to the LUN, before the LUN will be connected ?
iSCSI is configured per ESXi host. (either via Host HTML client or via vCenter Server if applicable).
You only need to do bindings, with mulitpath....
The first thing you want to do is use ping and vmkping 10.0.0.10 which will test if you can send packets to the SAN (iSCSI)
You can use -I vmk0 to send actual vmkping packets through this interface, this confirms communications.
NEXT, you've got to configure iSCSI LUNs, and add the IQN of the hba, to grant access to the LUN, before the LUN will be connected ?
Ping and vmkping to 10.0.0.10 work fine.
Defined a vswitch3 with a vmkernal adapter pointing to a dedicated 10gb adapter bound to it.
Under Storage, the ISCSI Storage Adapter is defined and points to vswitch3.
Properties for this adapter has 10.0.0.10:3260 under dynamic discovery.
Under Storage Devices the ISCSI entry does not appear. Something I'm missing?
--Ben
Defined a vswitch3 with a vmkernal adapter pointing to a dedicated 10gb adapter bound to it.
Under Storage, the ISCSI Storage Adapter is defined and points to vswitch3.
Properties for this adapter has 10.0.0.10:3260 under dynamic discovery.
Under Storage Devices the ISCSI entry does not appear. Something I'm missing?
--Ben
Okay, so communications looks good from VMKernel portgroup to the iSCSI SAN. (from ESXi end)
One thing done and out of the way.
If the IP Address of 10.0.0.10:3260 is in place under Dynamic Discovery....
A rescan of the adaptor (hba) should be enough for it to reach out to the SAN and try a connection.....
BUT, if there is no LUN defined, or access control (IQN) defined for the IQN of the ESXi IQN HBA, it will not map, also if chap is defined on the SAN it will reject....
Can you check on the SAN, if it detects and observes a connection ?
One thing done and out of the way.
If the IP Address of 10.0.0.10:3260 is in place under Dynamic Discovery....
A rescan of the adaptor (hba) should be enough for it to reach out to the SAN and try a connection.....
BUT, if there is no LUN defined, or access control (IQN) defined for the IQN of the ESXi IQN HBA, it will not map, also if chap is defined on the SAN it will reject....
Can you check on the SAN, if it detects and observes a connection ?
I set it up w/o authentication in Windows.
The Storage Adapter Properties tab has the following :
Name vmhba64
Model iSCSI Software Adapter
iSCSI Name iqn.1998-01.com.vmware:5bc
iSCSI Alias LUN1
Target Discovery Send Targets, Static Targets
Where do I define a LUN? IQN? Not sure how to query Windows 2012 to determine if it sees a connection.
The Storage Adapter Properties tab has the following :
Name vmhba64
Model iSCSI Software Adapter
iSCSI Name iqn.1998-01.com.vmware:5bc
iSCSI Alias LUN1
Target Discovery Send Targets, Static Targets
Where do I define a LUN? IQN? Not sure how to query Windows 2012 to determine if it sees a connection.
I don't believe I have created a LUN. Where do I do that?
In the Windows server, I see the IQN value as:
iqn.1991-05.com.microsoft:
Where do I add this?
In the Windows server, I see the IQN value as:
iqn.1991-05.com.microsoft:
Where do I add this?
Have a look at this walkthrough...
http://vcloud-lab.com/entries/windows-2012-r2/microsfot-windows-2012-r2-iscsi-target-storage-server-for-esxi-and-hyperv
http://vcloud-lab.com/entries/windows-2012-r2/microsfot-windows-2012-r2-iscsi-target-storage-server-for-esxi-and-hyperv
Found the issue I was having with vSphere not seeing the MS ISCSI target; I needed to add the host's IQN to the MS side. Once I did that and re-scanned, it showed up. Starwind is also installed. Added it as a Datastore and now will test it for speed, latency, etc.
Thanks much for pointing me in the right direction!
--Ben
Thanks much for pointing me in the right direction!
--Ben
Premium Content
You need an Expert Office subscription to comment.Start Free Trial