Upgrading everyday security Commpact Uživatelský manuál Strana 23

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 58
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 22
5 Type the Maximum Transmission Units (MTU) for the virtual distributed switch.
MTU is the maximum amount of data that can be transmitted in one packet before it is divided into
smaller packets. VXLAN traffic frames are slightly larger in size because of encapsulation, so the MTU
for each switch must be set to 1550 or higher.
6 In VMKNic IP Addressing, specify the IP pool to be used for the Management and Edge cluster.
Select To
Use DHCP
Assign an IP address to the VXLAN VTEPs through Dynamic Host
Configuration Protocol (DHCP).
Use IP pool
Assign a static IP address to the VXLAN VTEPs from the selected IP pool,
or create a new IP pool.
7 If you selected Use IP Pool, select an IP pool.
8 Select the VMKNic Teaming Policy for the vSwitch. The NIC teaming policy determines the load
balancing and failover settings of the virtual switch.
It is important to choose the right teaming policy to avoid packet loss. See “Teaming Policy for Virtual
Distributed Switches,” on page 23.
9 Edit the VTEP value, if required.
VTEP (VXLAN Tunnel End Points) is the number of dvUplinks on the switch, which load balances
traffic between multiple PNICs. VMware recommends that you do not edit the default VTEP value.
This field is disabled if the teaming policy you selected does not require multiple VTEPs (ether channel,
failover, LACPv1, or LACPv2).
10 Click OK.
Teaming Policy for Virtual Distributed Switches
You should choose a teaming policy for VXLAN transport based on the topology of your physical switches.
It is recommended that you do not mix teaming policies for different portgroups on a vSphere Distributed
Switch. If uplinks are shared in these different teaming policies, then traffic will be interrupted. For a
Logical Distributed Router, mixed teaming policies may result in routing problems. As a best practice - if
you want to use IP hash based teaming (Ether channel, LACPv1, or LACPv2), use all uplinks on the vSphere
Distributed Switch for the team and do not have portgroups on that vSphere Distributed Switch with
different teaming policies.
For certain teaming modes, VMware software creates multiple VTEPs to load balance traffic among the
physical vNICs.
For information on teaming mode descriptions, refer to the VMware vSphere documentation.
Table 41. Teaming Policy table
Teaming Mode
Multiple VTEPs
Created vDS Version
Ether channel
NOTE If you are using blade chassis, validate that it
supports ether channel before choosing this teaming
mode.
No 5.1 and later
Failover No 5.1 and later
LACPv1 No 5.1
Chapter 4 Installing NSX Components
VMware, Inc. 23
Zobrazit stránku 22
1 2 ... 18 19 20 21 22 23 24 25 26 27 28 ... 57 58

Komentáře k této Příručce

Žádné komentáře