Thanks.. Maybe you can help me understand the concept of VMKernel in VMWare.. My VM Host and SAN/NAS Server is connected to the LB4M switch via a 10G link using the Brocade 1020R 10G network card. I have setup ISCSI targets on my SAN Server to be used as VM datastores using the free version of the StarWind software. Below is a screenshot of how I have configure the virtual switch in VMWare. Do I need a VMKernel on Switch 1 since I have an ISCSI adapter configured to connect to the ISCSI datastore target which is used by the 2 VM Guests (GLOVER-GEN, GLOVER-GEN_2). Please advise.
View attachment 144
vSphere Networking
http://pubs.vmware.com/vsphere-55/t...e-esxi-vcenter-server-55-networking-guide.pdf
VMware Virtual Networking Concepts
http://www.vmware.com/files/pdf/virtual_networking_concepts.pdf
In my own words.
A VMware vSwitch is a virtual switch. For each vSwitch you must have dedicated NIC's.
A port group is a set of ports of like configuration.
a VMKernel is All non VM traffic. All kernel traffic NFS, ISCSi, Management, Fault Tolerance, vMotion, must be associated with a VMKernel port. Each of these would have a IP Address.
In Production you would assign each type of traffic with a dedicated VLAN, and map out all hosts and IP's on that vlan ahead of time, and if using 1GB assign more than one NIC's to each vSwitch and then create a vSwitch for each type of traffic. If your using 10GB/40GB, often management, and vMotion, are on one vSwitch, and storage traffic on another.
Often you would then setup a Third vSwitch for all VMware Production traffic, and a VM Network for all associated VLAN's. AKA File Servers VLAN 100. Database Servers VLAN 101.
Now, That's assuming your using ESXi free, and not a version that allows you to use VDS switches, as in that case things get more complicated. That is covered in the linked vSphere Networking PDF.