vmware virtual network

First compare the existing Ethernet and virtual networks:

• Existing Ethernet:
  assembly comprising: a cable card terminal, a physical switch
  scenarios: a plurality of physical blocks to the network adapter connected via a physical switch network medium, and then connected to a router, routing switch connected to the Ethernet through the host

• Virtual Network:
  assembly comprising: a virtual switch physical NIC (Alternatively, if only the internal communication requires the virtual machine, is optional) uplink port physical switch port group (the same physical NIC, optional)
  scene: on one or more esxi esxi between virtual machines can communicate, while the physical network card may be connected by a physical switch implemented with Ethernet communications
  a core concept of virtual network: virtual switch
  
  a virtual connection between the switch provides a unified virtual machines on the host or a different host.
  Virtual switch having a specific connection type:

• Port Group: virtual network adapter is connected to a virtual machine, you can create different ports in different types of business

• VMkernel port: For IP storage, vSphere vMotion, VMware vSphere Fault Tolerance, vSAN, vSphere replication, and network management ESXi

• Connected to the physical NIC: upstream port

The same can be multiple networks simultaneously on virtual switches, networks can also exist on a separate virtual switch
standard virtual switch:

by default creates a virtual switch is created when esxi, if only one, is the standard virtual switch, all of the virtual card, physical NICs are connected to a virtual switch.
Distributed virtual switch

has a plurality of independent virtual switches, each switch corresponding to a different virtual network requirements.
The pros and cons of both

• Standard virtual switch: broadcast domain is too large, but can be resolved by VLAN, single point of failure can be solved physical NIC, for link redundancy, load balancing, according to the conventional load port, data can be transferred out of the shunt
• Distributed Virtual Switch: benefit is to isolate broadcast domains, from the point of view, it is more comfortable, but the link redundancy is more bad angle, a network card problem, the corresponding service will be a problem, resulting link failure, there is no load balancing

We can see a host of standard switch by selecting the virtual switch on vsphere client configure options to configure the

virtual switch also supports vlan

Vlan id allocated in the virtual switch port group

Network switches and ports strategy:
By default, all port groups at the policy level standard switch settings for standard switch.
Available network policy:

• Safety

• traffic shaping

• NIC teaming and failover
  has three modes:

• Promiscuous mode: allows the switch or port group forwards all traffic, no matter where the destination is

• Mac Address Change Mode: When a visitor to change the Mac address, accept or reject incoming traffic

• Forged transfer: When a visitor to change the mac address, accept or reject output flow

Traffic shaping

is a mechanism to limit the network bandwidth consumed by virtual machine available,
Peak bandwidth: peak
average: normally achievable bandwidth (-kbit / S)
Burst size: controlling the duration of the peak
burst size = bandwidth * time

you traffic can be established to form policy for each port group and each distributed port or distributed port group: traffic shaping is disabled by default. Parameters apply to each virtual LAN standard switch. On a standard switch, traffic shaping control only outbound traffic, i.e. from vm to a virtual switch and output to the physical network traffic.
NIC Teaming
administrator can configure specific options for editing by a combination of NIC failover policies


passage before the matter between separate, there has been a channel after teaming, you can achieve load balancing and redundancy traffic

Select a variety of load balancing:

• originating virtual port ID

• 
  Flow out of the virtual machine is load balancing
  virtual machine's NIC is connected to the virtual switch port group specifies the port number of
  traffic will be on the specified port number are routed to a physical NIC

• mac hash
  
  -based load balancing hash mac
  mac address of the virtual machine for the hash calculation, whether the packet from which a physical NIC out traffic from the mac address of the fixed path will go

• source and destination ip hash
  
  based on source and destination ip address hash
  in this way to achieve a true actual load balancing
  detecting a network fault
  VMkernel can use the link status or a beacon, or both are used to detect network problems.
  VMkernel detected by the network failure, which monitors the link status, and performs the beacon probe. VMkernel notification of changes in the physical location of a physical switch MAC address.
  VMkernel failover from the configurable parameters based implementation:

• Recovery: How to return from a physical adapter failure recovery to active status.

• Load balancing options: Use explicit failover order. Always use active adapters list vmnic uplink top

。