VMware {code}

Friday 17 October 2014

Virtual Networking

MAC Address Change

When set to Allowed,
  1. Virtual Switch will allow the Guest OS to change the MAC address of the Virtual Network Adaptor.
  2. In short, if ‘Effective MAC’ is different from the ‘Initial MAC’, the traffic will still be allowed.
  3. The flow of network traffic is from Virtual Switch to VM.
When set to Rejected,

  1. Initial and Effective MAC addresses must be same else no traffic flow.


Forged Transmit


When set to Allowed,
  1. Compares the Source (Initial) MAC with the Effective MAC for outbound frames.
  2. If Source and Effective MACs are not same, packet drop.
  3. The flow of network traffic is from VM to Virtual Switch.


Beacon Probing

1.

Data is flowing from Uplink 1. Connection between Switch 1 and 4 breaks down.

 2.

Beacons are being sent and returned on the Uplink2 and 3. But are not returned on Uplink1.

3.

Data is now routed to Uplink 3.

Netflow
  1. It is a feature of Distributed Virtual Switch used for monitoring the traffic.
  2. It collects the IP traffic information and sends it over to the ‘Collector’ for traffic flow analysis.
  3. The traffic goes through the Physical Switch.
  4. It can be used for Intra-Host VM traffic (VMs on same host)
  5. Inter-Host traffic (VMs on different hosts)
  6. As well as the VM to physical infrastructure traffic.


Route Based on Original Virtual Port ID

  1. This is the default Load Balancing Policy.
  2. Only one pNIC can be used per vNIC.
  3. Example, if there are four 1Gb pNICs in team, a VM with single vNIC can only utilize 1Gbps speed.
  4. The traffic is sent and received on the same pNIC always in this policy unless that pNIC goes down in a team.
  5. Capable of Link-Status and Beacon probing failover detections.

3 comments: