Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
11 Cards in this Set
- Front
- Back
|
VMware NIC Teaming Policies: Load Balancing
|
Networking, pages 46 - 51
Load balancing determines how OUTGOING traffic is distributed among the network adapters assigned to a vSwitch. |
|
|
Load Balancing: Route based on the originating port ID
|
Networking, pages 46 - 51
Route based on the originating port ID - chooses an uplink based on the virtual port where the traffic entered the virtual switch. |
|
|
Load Balancing: Route based on IP hash
|
Networking, pages 46 - 51
Route based on the IP hash - chooses an uplink based on a hash of the source and destination IP address or each packet. Requires ETHERCHANNEL. REMEBER ETHERCHANNEL |
|
|
Load Balancing: Route based on source MAC hash
|
Networking, pages 46 - 51
Route based on source MAC hash - chooses an uplink based on the hash of the source Ethernet |
|
|
Load Balancing: Use explicit failover order
|
Networking, pages 46 - 51
Use explicit failover order - always uses the highest order from the list of Active adapters which pass failover detection criteria |
|
|
VMware NIC Teaming Policies: Network Failover Detection
|
Networking, pages 46 - 51
Network Failover Detection controls the link status and beacon probing . Beaconing is not supported with guest VLAN tagging. |
|
|
Network Failover Detection: Link status only
|
Networking, pages 46 - 51
Link Status Only - relies solely on the link status that the network adapter provides. This option detects failures, such as cable pulls and physical switch power failures, but not configuration errors (such as a physical switch port being blocked by spanning tree, a physical switch port that is misconfigured to the wrong VLAN, or cable pulls on the other side of a physical switch). |
|
|
Network Failover Detection: Beacon Probing
|
Networking, pages 46 - 51
Beacon probing - sends out and listens for beacon probes on all NICs in the team and uses this information, in addition to link status, to determine link failure. Requires 3 NICs. |
|
|
VMware NIC Teaming Policies: Notify Switches
|
Networking, pages 46 - 51
Select Yes (default) or No to notify switches in the case of failover. If you select Yes, a notification to update the lookup tables on the physical switches is sent whenever: -a virtual NIC is connected to the vSwitch -whenever that virtual NICs traffic would be routed over a different physical network In almost all cases this process is desirable for the lowest latency of failover occurrences and migrations with vMotion. |
|
|
VMware NIC Teaming Policies: Failback
|
Networking, pages 46 - 51
Select Yes (default) or No to enable or disable failback (respectively). This option determines how a physical adapter is returned to active duty after recovering from a failure. |
|
|
VMware NIC Teaming Policies: Failover Order
|
Specify how to distribute the workload for uplinks
Active Uplinks - Continue to use the uplink when the network adapter connectivity is up and active. Standby Uplinks - Use this uplink if one of the active adapter's connectivity is down. Unused Uplinks - Do not use this uplink. |
