Term
| What do load balancing policies on vSS and vDS do? |
|
Definition
| Load balancing policies are used to determine how outbound traffic is spread across multiple physical adapters (vmnics) |
|
|
Term
| How is inbound load balancing handled? |
|
Definition
| Inbound load balancing is handled by the physical switch the physical uplinks are connected to |
|
|
Term
| Where do you start to configure load balancing and failover policies on vSS? |
|
Definition
| Start in Configuration tab, and click 'properties' next to the vSS you want to modify. Edit properties and configure in NIC Teaming tab |
|
|
Term
| Where do you configure load balancing and failover policies on vDS? |
|
Definition
| Go to the Networking view through the inventory menu. Edit settings on the dvPort group and select 'teaming and failover' under 'policies' |
|
|
Term
| Name the 5 options under the Load Balancing Policy Exception. Identify which option is unique to vDS. |
|
Definition
| Route based on the originating port ID, Route based on IP hash, Route based on source MAC hash, Use explicit failover order, Route based on Physical NIC load (vDS only) |
|
|
Term
| Define the Route based on the originating port ID option for the Load Balancing policy exception |
|
Definition
| Traffic will exit through the same port it was sent in on |
|
|
Term
| Which option is the default for Load Balancing? |
|
Definition
| Route based on originating port ID |
|
|
Term
| Define the Route based on IP hash option for Load Balancing |
|
Definition
| A hash is produced using the source and destination IP Addresses and used to determine which nic is used. All ports on the physical switch must be part of an etherchannel group. This is one of the most true load balancing options as it will utilize all links, however not recommended if most traffic is just coming from the same IP as the hash would always be the same. All port groups using the same physical uplinks should use IP hash load balancing policy. |
|
|
Term
| Define the Route based on source MAC hash load balancing policy |
|
Definition
| This is similar to IP hash but uses hashing based on the source MAC address and does not require additional configuration on the physical switch. i.e. ports do not need to be bonded together |
|
|
Term
| Define the Use explicit failover order policy for Load Balancing |
|
Definition
| This setting uses the physical uplink that is listed first under 'Active Adapters'. You can set your own desired failover order for your NICs |
|
|
Term
| Define the Route based on physical Nic Load option for Load Balancing policy |
|
Definition
Note: only available on a dvswitch
Monitors the load on the physical NICs and will reconfigure VMs to use different NICs in order to distribute the load across all of the NICs |
|
|
Term
| Name the 4 options available for Network Failover Detection |
|
Definition
| Link Status only, Beacon Probing, Notify Switches, Failback |
|
|
Term
| Define the Link Status only option for Network Failover Detection |
|
Definition
| Only monitors the status of the physical link to detect a network failure. Thus, only helps if the port on the physical switch fails or is unplugged. I.e. Does not detect misconfigurations such as vLAN pruning or spanning tree. |
|
|
Term
| Define the Beacon Probing option for Network Failover Detection |
|
Definition
| Sends a probe down the line and will listen to the beacon probes on all physical NICs that are part of the team. Will typically be able to detect misconfigurations. Do not use with IP hash load balancing |
|
|
Term
| Define the Notify Switches Policy in the Network Failover Detection Policy options |
|
Definition
| Choosing Yes will notify the physical switch to update its lookup tables whenever a failover event occurs or whenever a virtual NIC is connected. |
|
|
Term
| Define the Failback policy in the Network Failover Detection Policy options |
|
Definition
Should we fail back ot the original NIC when it becomes operational again?
If you choose No, then the failed physical adapter that becomes operational will only become active if the original standby adapter fails |
|
|
Term
| Name the three groups available for NICs in the Failover Order policy |
|
Definition
| Active, Standby or Unused |
|
|
Term
| What are 'Active Adapters' |
|
Definition
| Physical adapters listed here are active and are being used for inbound/outbound traffic. They will always be used when connected and operational |
|
|
Term
| What are 'Standby Adapters' |
|
Definition
| Physical adapters listed here are on standby and are only used when an active adapter fails or no longer has network connectivity |
|
|
Term
| What are 'Unused Adapters' |
|
Definition
| Physical adapters listed here will not be in use |
|
|
