From 9448fd522a3a7ec012d7b9ae7e16d10f91e05205 Mon Sep 17 00:00:00 2001 From: Jim McCarron Date: Mon, 11 Nov 2024 08:50:57 -0500 Subject: [PATCH] mgmt lag order --- ...initial_setup_of_velos_system_controllers.rst | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/initial_setup_of_velos_system_controllers.rst b/docs/initial_setup_of_velos_system_controllers.rst index 1376913..6ddbb68 100644 --- a/docs/initial_setup_of_velos_system_controllers.rst +++ b/docs/initial_setup_of_velos_system_controllers.rst @@ -237,15 +237,9 @@ As seen in previous diagrams, each system controller has its own independent out To enable this feature, you would need to enable link aggregation on the system controllers via the CLI, webUI or API, and then make changes to your upstream layer2 switching infrastructure to ensure the two ports are put into the same LAG. To configure the management ports of both system controllers to run in a LAG, configure as follows: -On the active controller, create a management LACP interface: - -.. code-block:: bash - lacp interfaces interface mgmt-aggr - config name mgmt-aggr - ! -Next, create a management aggregate interface and set the **config type** to **ieee8023adLag**, and set the **lag-type** to **LACP**. +Create a management aggregate interface and set the **config type** to **ieee8023adLag**, and set the **lag-type** to **LACP**. .. code-block:: bash @@ -255,6 +249,14 @@ Next, create a management aggregate interface and set the **config type** to **i aggregation config lag-type LACP ! +On the active controller, create a management LACP interface: + +.. code-block:: bash + + lacp interfaces interface mgmt-aggr + config name mgmt-aggr + ! + Finally, add the aggregate that you created by name to each of the management interfaces on the two controllers: .. code-block:: bash