To create a LACP link (LAGG) via the vSphere Client, select your vDS virtual switch, then go to "Configure -> Settings -> LACP" and click the "NEW" button.
In the “New Link Aggregation Group” window that appears, indicate:
Source : Create a Link Aggregation Group - VMware Docs.
Your LACP (LAG) link has been created.
For this tutorial, we used a Netgear switch that supports LACP.
More precisely, it is the switch: Netgear GS810EMX (Nighthawk SX10).
Note: in business, you will mainly use Cisco switches.
As you can see, for the LACP link (LAG), we will use ports 4 and 6 of our Netgear switch.
The 2 cables are currently connected between the Netgear switch and the VMware ESXi host, hence the "CONNECTED" status visible on the 2 ports (4 and 6).
The LACP link is currently not configured on our Netgear switch.
If you wish, you can rename a port on the Netgear switch by clicking on its number, then on: Edit.
Change the Port Name if desired, then click: Apply.
In our case, we renamed our ports 4 and 6 to: ESXi LACP (LAG1).
To configure the LACP link (LAG) on the Netgear GS810EMX (Nighthawk SX10) switch, go to "Switching -> LAG".
Choose "LAG 1" and configure this:
The message "LAG Mode has been updated" appears.
Once the LACP link (LAG) has been created, in the "Home" tab, you will see that LAG 1 is made up of ports 4 and 6 (in our case).
However, at the moment, the link is not established (Link Down) since the LACP configuration on VMware vSphere is not completed.
When you want to migrate network traffic (in our case, that of our virtual machines) to LACP links, you must do this in 3 steps.
To get started, select your vDS virtual switch where you created your LAG (LACP link) and go to: Configure -> Settings -> LACP.
Next, click on the “Migrating network traffic to LAGs” link displayed.
The vSphere Client displays the 3 steps required for migrating network traffic to your LAGs.
Step 1: Click the “Manage Distributed Port Groups” link.
In the "[vDS switch name] - Manage Distributed Port Groups" wizard that appears, check the "Teaming and Failover" box and click Next.
Select the port group you want to migrate to your LAG (LACP link) and click Next.
Select your LAG (default: lag1) and click on the "up" arrow to move it up to the "Standby uplinks" section.
As requested by the vSphere client, your LAG is now asleep for this distributed port group.
Currently, uplinks "Uplink 1" and "Uplink 2" are active for this distributed port group.
As the vSphere client warns you, this is a supported but temporary configuration.
Click OK.
Plain Text
When migrating physical adapters between a LAG and standalone uplinks, the combination of active standalone uplinks and a standby LAG is only supported as an intermediate configuration.
Click Finish.
Your port group has been successfully migrated to your LAG (lag1 in our case).
In particular, you will see a “Reconfigure the distributed port group” task appear at the bottom of the page.
If you go to the "Configure -> Settings -> Topology" section of your vDS virtual switch and click on the name of the port group you just modified, you will see that VMware vSphere is currently using only uplinks (Uplink X).
This is because only the uplinks "Uplink 1" and "Uplink 2" are active on this port group.
VMware 9/28/2022
VMware 6/10/2022
VMware 7/13/2022
VMware 6/8/2022
Pinned content
Contact
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.
No comment