Objective 5.2: Configure VXLAN

  • Physical Req Consideration
    • MTU is at least 50 bytes mode than MTU of the vm vNIC
    • DHCP is available on VXLAN transport VLANs if youa re using DHCP for IP assignment for VMKNics (VTEP)
    • 5-tuple hash disto should be enabled for LACP
    • VXLAN traffic should be placed in separate VLAN from other traffic (MGMT, vmo)

 

  • Prepare Cluster for VXLAN
    • Chapter 10 p53 of Install Guide
    • For each cluster click install in the installation status column
    • monitor install until the status column shows a green tick
    • 3 vmware install bundles are installed and registered with all hosts within the prepared cluster
      • VXLAN
      • DFW
      • Logical routing
    • DHCP available on VXLAN transport vlan

 

  • Teaming Policy
    • Teaming policy for hosts is major design point
      • available bandwidth
      • reliability/robustness
      • VTEP config
      • Supported
      • not recommended to mix teaming policies for different port groups on same dist switch
    • As best practice if you want to use IP hash, lacpV1 or lacpV2
      • use all uplinks on the VDS for teaming
    • consider lacp on compute cluster only and not edge
    • route based and mac based support multi vtep

 

  • Config and Modify Transport Zone Options
    • Edit settings icon in transport zone
    • you can migrate existing logical switches to new control plane
    • all logical switches in a TZ will be available and visible to all vms within clusters in the TZ

 

  • VXLAN Tunnel Endpoints (VTEP)
    • plan IP addresing scheme for VXLAN VTEPs
    • See VMware Docs
    • DHCP or manually configured
      • If you want a specific IP address assigned to a VTEP you can use DHCP or reservation that maps a MAC address to a specific IP address in the DHCP server
      • use an IP pool then manually edit the VTEP IP address assigned to the VM kernel MNIC under Manage > Networking > Virtual Switches

<VCP6-NV6.2

plasebikan