StarWind Software

Team

I am trying to configure an instance of vsan using the CVM virtual machine approach. I have successfully configured the vm and attached passthur disks to the vm and setup the storage pool / volume and successfully created the iscsi luns using powershell scripts.

I have 2x sync and 2x iscsi nic directly connected at 10gb between the hosts.

I have a separate management network in a set team for hyperv and management traffic.

My issue is when it comes to connecting the host machines to the iscsi targets there is no network path as such from the host machine to the iscsi target network.

One of the guides alludes to needing an extra internal switch but I am not sure how to configure. When i read the esxi setup there is a port group setup to expose the iscsi network to the host machines.

This document https://www.starwindsoftware.com/resour ... shell-cli/ contains this bit of information.

An additional internal switch is required for iSCSI Connection. Contact support for additional details.

What is the trick on hyperv to allow the host machines access to this iscsi network?

Extra Pics

Try pinging the Host iSCSI IP addresses from VMs.
It looks like there is something funny between Linux and Windows.

I can ping the IP address of the management of the VM which is connected via the switched network and have access the web interface

I am trying to connect my host to the iscsi network address and as they are on separate virtual switches and are direct connected without switching. So there is no path to the iscsi network network.

There is section in your documentation that says you need an additional internal virtual switch. Trying to understand what that means.

Using this ps command i was able to expose the virtual switch to the host machine. is this the approved method.

Add-VMNetworkAdapter -ManagementOS -Name "P4 ISCSI" -SwitchName "P4 ISCSI"

We normally use UI.
Can you ping iSCSI IPs on the host from the VM? You need to assign IP addresses on iSCSI Hyper-V switch and ping it from both local and partner VMs

You've got a solid setup going! It sounds like the missing piece is configuring an internal virtual switch in Hyper-V to bridge the iSCSI network to the host. Have you tried setting up an **Internal Virtual Switch** in the Virtual Switch Manager and assigning it an IP in the iSCSI subnet? That should allow the host to communicate with the targets. Also, double-check the NIC bindings to make sure iSCSI traffic is properly routed.
Let me know if you need more details!

Thanks for your hint.

I solved my problem through your tutorial, thanks a lot!