Differences between revisions 9 and 10
Revision 9 as of 2012-06-02 16:04:30
Size: 1389
Editor: PieterSmit
Comment:
Revision 10 as of 2012-06-02 16:05:16
Size: 1389
Editor: PieterSmit
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
 * See [[cisco\Nexus]]  * See [[cisco/Nexus]]

VMware notes

Multi Interface load-balancing and fail-over

  • You must enable beacon probing when downstream link failures may impact availability and there is no Link State Tracking on the physical switch.

    • ESX periodically broadcast beacon packets out of all uplinks in a team.
    • If an uplink fails to receive any beacon packets (actually missing 3 consecutive packets), we mark it bad.
    • If a team has two uplinks, any link failure will result in all packets being sent to both uplinks.

TLA's

  • Flow
    • [VM]-vNIC-on VM-FEX-10Gto-Nexus2K/5k-vEth port.
    • floating vEthernet interface - can migrate with vm
  • VM-FEX - Cisco Virtual Machine Fabric Extender - on UCS system with Palo chipset in the server blades
  • VMXNET3 paravirtualized device driver
  • VMDirectPath - Virtual and Physical Nic matches, vm can talk directly to HW.
  • vSphere 5 introduced support for vMotion with VMDirectPath for VM-FEX NICs
  • VEM - Virtual ethernet module

...


CategoryNetwork

VMware (last edited 2012-06-02 16:05:16 by PieterSmit)