<div>
Looks like it!<br />
<br />
or add another interface if possible!
</div>


<div>
Hancock, thank you for your reply. I was trying to create a new vlan for our iSCSI traffic but with on vswitch and only two active pNIC it does look like it will be an option. Should I reuse the existing vmkernel used for NFS or create a new one on the same vlan?<br />
<br />
Thanks for the confirmation.<br />
<br />
P.S: I have setup block storage before but never software iscsi in ESXi believe it or not....
</div>


compdigit44

<div>
If my NFS and soon to be iSCSI will be on the same vLAN couldn't I used the existing vmkernel interface? My concern is if I add another vmk on the same vlan as NFS NFS traffic might try to go down the path of the ISCSI vmk who's IP is not listed on the NFS export policy.<br />
<br />
P.S: This is not idea by a constraint I have to work with.
</div>


<div>
I would use different IP Address ranges for NFS and iSCSI!<br />
<br />
So technically traffic is segregated by IP Address, although using the same VLAN.<br />
<br />
and then &nbsp;you create VMKernel Portgroups 2 x NFS on IP Network A, and 2 x iSCSI on IOP Network B all using VLAN C.<br />
<br />
this separates traffic
</div>


<div>
this is my problem though, only have one fiber card with 2 ports and VM and storage traffic uses those ports.
</div>


<div>
I even thought about using one one pnic per vmk which I know is horrible
</div>


<div>
if you have two physical nics connected to a vSwitch, what is the issue ?<br />
<br />
you can have many VMKernel Portgroups on a vSwitch......(they are virtual nics)
</div>


<div>
but how will the current nfs traffi know to use the correct vmkernel if two vmk's are on the same vlan
</div>


<div>
because the VMKernel Portgroups have different IP Addresses on different sub networks<br />
<br />
and usually your NFS NAS will have an IP address on the same network as your VMKernel IP Address.<br />
<br />
e.g.<br />
<br />
NFS - 10.10.1.1 NFS VMKernel Portgroup - NAS (NFS) 10.10.1.250<br />
<br />
iSCSI 192.168.1.1 iSCSI VMKernel Portgroup - iSCSI SAN 192.168.1.250
</div>


<div>
I am going to have to look at this more tomorrow, I know I am missing what you are saying
</div>


<div>
try it and use vmkping to send traffic (e.g. a ping) out of the correct VMKernel, and see if it reaches it's destination!
</div>


<div>
I am going to create a new question since I already accepted this one..<br />
<br />
Thanks Again
</div>


<div>
<div class="content wysiwyg-content">
Here is our current setup which is not ideal and built long before I started.<br />
<br />
8 ESXi 6.5 hosts<br />
1x 2 port fiber<br />
1x 1GB management port<br />
<br />
Right now all Vm guest and NFS traffic are on one vswitch and use the same physical interfaces. Here is my question / problem. We have a new iSCSI SAN. I have created a software iscsi interface but cannot bind any pNIC's because they are all in use. Is my only option to have the iSCSI traffic use the same vswitch and vlan as well?
</div>
</div>


Here is our current setup which is not ideal and built long before I started.

8 ESXi 6.5 hosts
1x 2 port fiber
1x 1GB management port

Right now all Vm guest and NFS traffic are on one vswitch and use the same physical interfaces. Here is my question / problem. We have a new iSCSI SAN. I have created a software iscsi interface but cannot bind any pNIC's because they are all in use. Is my only option to have the iSCSI traffic use the same vswitch and vlan as well?

Software iSCSI and limited pNIC's

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.