These are the following objectives for Section 2.2 of the blueprint.
Section 2 – Create and Manage VMware NSX Virtual Networks
Objective 2.2 – Configure VXLANs
Skills and Abilities
· Prepare cluster for VXLAN - Yellow-Bricks
· Configure VXLAN transport zone parameters - Wahl Network
· Configure the appropriate teaming policy for a given implementation - link
Just a few quick points on VXLAN
A more detailed explanation can be found in NSX Components and Features
VXLAN is a L2 over L3 encapsulation tecnology. The original ethernet frame is encapsulated with external VXLAN, UDP, IP and ethernet headers to ensure it can be transported across the netwrok infrastructure.
Just a few quick points on VXLAN
A more detailed explanation can be found in NSX Components and Features
VXLAN is a L2 over L3 encapsulation tecnology. The original ethernet frame is encapsulated with external VXLAN, UDP, IP and ethernet headers to ensure it can be transported across the netwrok infrastructure.
A VXLAN segment can span multiple L3 networks, with full connectivity of VMs.
VMkernel interface is used to communicate over VXLAN. Everything is tunneled directly via vmkernels.
VXLAN kernel module encapsulates packet in a VXLAN header, sends it out the vmkernel interface (VTEP) - VXLAN tunnel endpoint, to the VTEP on a destination host, which de-encapsulates it and hands it to VM. This process is completely transparant to the VM.
Depending on teaming types hosts may have single or multiple VTEPs
The VXLAN Network Identifier (VNI) is a 24 bit identifier which is associated with each L2 segment created, it is carried inside the VXLAN header and is associated to an IP subnet, like a traditional VLAN. This VNI is the reason VXLAN can scale beyond the 4094 VLAN limitation.
VTEPs are identified by the source and destination IP addresses used in the external IP header.
A minimum of 1600 Bytes for the MTU is the recommendation for VXLAN.
VMkernel interface is used to communicate over VXLAN. Everything is tunneled directly via vmkernels.
VXLAN kernel module encapsulates packet in a VXLAN header, sends it out the vmkernel interface (VTEP) - VXLAN tunnel endpoint, to the VTEP on a destination host, which de-encapsulates it and hands it to VM. This process is completely transparant to the VM.
Depending on teaming types hosts may have single or multiple VTEPs
The VXLAN Network Identifier (VNI) is a 24 bit identifier which is associated with each L2 segment created, it is carried inside the VXLAN header and is associated to an IP subnet, like a traditional VLAN. This VNI is the reason VXLAN can scale beyond the 4094 VLAN limitation.
VTEPs are identified by the source and destination IP addresses used in the external IP header.
A minimum of 1600 Bytes for the MTU is the recommendation for VXLAN.
No comments:
Post a Comment