Network components include:
1,vsphere Standard Switch , responsible for managing the virtual machine traffic. Must be managed separately on each ESXi host.
2.vsphere Distributed Switch , which manages the traffic of virtual machines and Vmkernel, is shared and managed by ESXi hosts and clusters in a data center. The distributed switch abbreviation is VDS.
3, Port/port group , is a logical object of Vswintch, a virtual switch can contain either a Vmkernel port or a virtual machine port group. Distributed switches are distributed port groups.
4,Vmkernel Port , is a special type of Virtual Switch port, configured with an IP address to support hypervisor management traffic, vMotion, ISCs storage access, VMware virtual San traffic, network attached storage (NAS ) or network File system (NFS) Access or vsphere FT logging. When used as a VMware NSX network virtualization and security platform, you also create Vmkernel ports for the Vxlan Tunnel Terminal (VTEP). Use the Vxlan TCP/IP stack instead of the default stack to create the Vmkernel port. The Vmkernel port is also known as vmknic.
5. The virtual machine Port Group is a set of virtual switch ports that share a set of identical configurations that allow virtual machines to access other virtual machines configured on the same port group, accessible Pvlan, or on a physical network.
6, virtual LAN, virtual or physical switch configured on the logical LAN, can provide efficient traffic segmentation, broadcast control and security, only for specific VLAN configuration port transport traffic.
7, Trunk Port , is the physical switch port, is responsible for monitoring and execution of multiple VLAN traffic transmission. The virtual Switch supports VLANs and uses VLAN trunking to enable free connection of VLANs to virtual switches.
8, Access Port , the port on the physical switch, only responsible for the traffic of one VLAN.
9,vmxnet, virtual network adapter located in the guest operating system. 1gb/s
10,vlance adapter , virtual network adapter located on the guest operating system. 100m/s
11,e1000 Adapter , simulates the virtual machine network adapter of the Intel® e1000 network adapter.
Problems with virtual network design considerations:
1, whether there is or need a dedicated traffic management network.
2. Whether there is or need a network dedicated to transmitting vmotion traffic.
3. Is there an IP storage network? Does this IP storage network have a private network? Running iSCSI or Nas/nfs? Do you want to implement VMware virtual SAN?
4, ESXi host design How many standard NIC?
5, the host NIC running 1GB or 1GB network.
6. Do I need to implement ultra-advanced fault tolerant mechanisms for virtual machines?
7. Does the existing physical network contain VLANs?
8. Do you want to extend the VLAN application to the virtual Switch?
9. Do you want to introduce Vxlan in your environment by using NSX?
This article is from the "Yu Zhang" blog, make sure to keep this source http://zhangyu89.blog.51cto.com/5175945/1981668
VMware Virtualization Network Learning (i)