LINUX AND VMWARE STUFF

• Increased network capacity for the virtual switch hosting the team.
• Passive failover in the event one of the adapters in the team goes down.

• Route based on the originating port ID: Choose an uplink based on the virtual port where the traffic entered the virtual switch.
• Route based on an IP hash: Choose an uplink based on a hash of the source and destination IP addresses of each packet. For non-IP packets, whatever is at those offsets is used to compute the hash.
• Route based on a source MAC hash: Choose an uplink based on a hash of the source Ethernet.
• Use explicit failover order: Always use the highest order uplink from the list of Active adapters which passes failover detection criteria.
• Route based on physical NIC load (Only available on Distributed Switch): Choose an uplink based on the current loads of physical NICs.

• The default load balancing policy is Route based on the originating virtual port ID. If the physical switch is using link aggregation, Route based on IP hash load balancing must be used.
• LACP support has been introduced in vSphere 5.1 on distributed vSwitches and requires additional configuration. 
•  
• Ensure VLAN and link aggregation protocol (if any) are configured correctly on the physical switch ports.

1. Highlight the host and click the Configuration tab.
2. Click the Networking link.
3. Click Properties.
4. Under the Network Adapters tab, click Add.
5. Select the appropriate (unclaimed) network adapter(s) and click Next.
6. Ensure that the selected adapter(s) are under Active Adapters.
7. Click Next > Finish.
8. Under the Ports tab,highlight the name of the port group and click Edit.
9. Click the NIC Teaming tab.
10. Select the correct Teaming policy under the Load Balancing field.
11. Click OK.

1. Under vCenter Home, click Hosts and Clusters.
2. Click on the host.
3. Click Manage > Networking > Virtual Switches.
4. Click on the vSwitch.
5. Click Manage the physical network adapters.
6. Select the appropriate (unclaimed) network adapter(s) and use the arrow to move the adapter(s) to Active Adapters.
7. Click Edit settings.
8. Select the correct Teaming policy under the Load Balancing field.
9. Click OK.

1. From Inventory, go to Networking.
2. Click on the Distributed switch.
3. Click the Configuration tab.
4. Click Manage Hosts. A window pops up.
5. Click the host.
6. From the Select Physical Adapters option, select the correct vmnics.
7. Click Next for the rest of the options.
8. Click Finish.
9. Expand the Distributed switch.
10. Right-click the Distributed Port Group.
11. Click Edit Settings.
12. Click Teaming and Failover.
13. Select the correct Teaming policy under the Load Balancing field.
14. Click OK.

1. Under vCenter Home, click Networking.
2. Click on the Distributed switch.
3. Click the Getting Started tab.
4. Under Basic tasks, click Add and manage hosts. A window pops up.
5. Click Manage host networking.
6. Click Next > Attached hosts.
7. Select the host(s).
8. Click Next.
9. Select Manage physical adapters and deselect the rest.
10. Click Next
11. Select the correct vmnics.
12. Click Assign Uplink > Next.
13. Click Next for the rest of the options.
14. Click Finish.
15. Expand the Distributed Switch.
16. Click Distributed Port Group. > Manage > Settings.
17. Under Properties, click Edit.
18. Click Teaming and failover.
19. Select the correct Teaming policy underthe Load Balancing field.
20. Click OK.

NIC Teaming

Load Balancing

1. Route based on the originating virtual port
2. Route based on IP hash
3. Route based on source MAC hash
4. Use explicit failover order

Network Failure Detection

 
An example where beacon probing finds upstream switch failures

Notify Switches

Failback

Failover Order

• Active adapters: Adapters that are Actively used to pass along traffic.
• Standby adapters: These adapters will only become Active if the defined Active adapters have failed.
• Unused adapters: Adapters that will never be used by the vSwitch, even if all the Active and Standby adapters have failed.

vCenter Service

Inventory Service

Single Sign on

vPostgres Service

vSphere Web Client

VMware System and Hardware Health Manager

Performance Charts