LACP configuration is always a tricky business for every administrator and network engineer and enabling and verifying the configuration of LACP on NX Nodes should not send chills down your spine.
First, let’s understand why we need LACP
What are the advantages of LACP?
- A single user VM with multiple TCP streams could use up to 20 Gbps of bandwidth in an AHV node with two 10 GB adapters.
- A traffic-hashing algorithm such as balance-TCP can split traffic between multiple links in an active-active fashion. Because the uplinks appear as a single L2 link, the algorithm can balance the traffic among bond members without any regard for switch MAC address tables.
- With LACP, multiple links to separate physical switches appear as a single layer-2 link.
Note: To use multiple upstream switches, you must configure MLAG or vPC on the physical switch
Points to seriously consider before jumping towards configuring LACP
- Read the following a guide to understand AHV Networking better
- It is strongly recommended to perform changes on a single node at the time after making sure that cluster can tolerate node failure. Refer to KB 2852 that describes how to check if the cluster can tolerate node failure.
- The use of "allssh manage_ovs update_uplinks" command may lead to a cluster outage. Only use it if the cluster is not in production and has no user VMs running.
WARNING: Updating uplinks using "manage_ovs" will delete and recreate the bond with the default configuration.
To understand about LACP configuration and how to enable and verify it
Give the following KB a read
Have some questions regarding AHV Networking?
Drop a comment and let’s start a discussion