Hyper-V iSCSI Direct Connect Disk

The host has 4 NICs, two for the SAN and one each for the LAN and the virtual switch.  I created a second virtual switch which I connected to one of the SAN NICS.  I added a second NIC to to the guest, and connected it to the second (iSCSI) virtual switch.  When I open up the iSCSI initiator on the guest OS, I don't see any SAN volumes.

After you create the second virtual switch, give the guest a 2nd virtual nic (to this second virtual switch) and you assign an IP (in the iSCSI subnet) to this virtual NIC, you need to add the group iSCSI IP to the discovery of the iSCSI initiator and set the ACL on the volume to either the iqn or the iSCSI IP of the guest.

However, this is just to get the basic functionality.

To do guest attached iSCSI better, I'd suggest:

- use completely different physical network ports for guest iSCSI versus host iSCSI (if you're using 10Gbit NICs this is probably not as necessary, but wouldn't hurt if you have the ports (on the network cards and switches)

- create 2 virtual switches each with 1 single nic for the virtual network and don't allow management over this (uncheck that checkbox when creating the virtual switch)

- enable jumbo frames and flowcontrol on those physical nics

- give the guest 2 extra virtual network cards and connect each to one of the 2 virtual iSCSI networks

- install the Equallogic hitkit on the guest (and reboot)

- configure the guest for iSCSI access just like you do a host