<div>
Thanks Hancock ... I am not setting up the iSCSI NIC's in a nic team policy I am using the active / unassigned setup .... :-)<br />
<br />
I am team them on the windows server side though..
</div>


Thanks Hancock ... I am not setting up the iSCSI NIC's in a nic team policy I am using the active / unassigned setup .... :-)

I am team them on the windows server side though..

<div>
<div class="content wysiwyg-content">
I am redoing our lab environment at work and setting up a Windows 2012 R2 server to present storage to my three ESXI 5.1 host using storage spaces. I know it is recommended to isolate iscsi traffic to its own subnet? For example my host would have an IP of 10.10.10.1 and separate teamed ISCSI NIC using 1.1.1.1. In VMware would this be a problem since an iSCSI port is another Vmkerel port and cause problems with routing?
</div>
</div>


I am redoing our lab environment at work and setting up a Windows 2012 R2 server to present storage to my three ESXI 5.1 host using storage spaces. I know it is recommended to isolate iscsi traffic to its own subnet? For example my host would have an IP of 10.10.10.1 and separate teamed ISCSI NIC using 1.1.1.1. In VMware would this be a problem since an iSCSI port is another Vmkerel port and cause problems with routing?

ESXi 5.1 Update 3 and Winodws 2012 R2 Storage Spaces

VMware, a software company founded in 1998,  was one of the first commercially successful companies to offer x86 virtualization. The storage company EMC purchased VMware in 1994. Dell Technologies acquired EMC in 2016. VMware’s parent company is now Dell Technologies.

VMware has many software products that run on desktops, Microsoft Windows, Linux, and macOS, which allows the virtualizing of the x86 architecture.  Its enterprise software hypervisor for servers, VMware vSphere Hypervisor (ESXi), is a bare-metal hypervisor that runs directly on the server hardware and does not require an additional underlying operating system.