Configuring Aggregate Ethernet (AE) Interfaces with LACP in Versa Director


Link Aggregation Control Protocol (LACP) allows multiple physical Ethernet links to be bundled together into a logical Aggregate Ethernet (AE) interface, providing higher bandwidth, redundancy, and resiliency. In Versa Networks environments, AE interfaces with LACP can be configured either through a Device Template (recommended) or directly at the Appliance Context level. 


Note: 

AE interfaces cannot be configured using a Workflow Template, as workflows only provision service-oriented configurations and not base networking constructs like link aggregation.


WAN side limitation: 

- AE cannot be attached to the WAN, instead, we can attach the AE to an IRB, and then it can be part of the SD-WAN WAN interface.

-We cannot do adaptive shaping or QoS configuration over IRBs.

This article walks through the methods of LACP configuration and provides additional considerations for network engineers deploying Versa Secure SD-WAN environments.

Why Use AE + LACP?

AE interfaces with LACP offer several operational benefits:

Method 1: Configuring LACP Using a Device Template (Recommended)

The Device Template method is highly recommended because it provides centralized configuration management and scalable deployment across multiple appliances.

Step 1: Create a New Aggregate Ethernet (AE) Interface

  1. In the Director view, navigate to:
    Configuration > Templates > Device Templates

  2. Select the device template to modify.

  3. Go to: Networking > Interfaces > AE

  4. Click + Add to create a new AE interface.

  5. Enter the Aggregate Ethernet interface number (e.g., ae0).

  6. Enable LACP and configure parameters:

    • LACP Mode

      • active: The device actively initiates LACP negotiation.

      • passive: The device waits for an LACP peer before enabling negotiation.

    • System Priority: Value between 1–65535 (default 127). Lower values have higher priority in LACP decisions.

    • Periodicity:

      • fast: Sends LACP PDUs every 1 second.

      • slow: Sends PDUs every 30 seconds.

    • Max Links: Maximum number of physical interfaces that can be bundled (default 16).

  7. Click OK to save.

Step 2: Add Physical LAN Ports (Vni Ports) as AE Members

  1. Go to Networking > Interfaces > Ethernet.

  2. Click Add to configure a physical Ethernet interface.

  3. In the Add Ethernet Interface window, select the Subinterfaces tab.

  4. Click Aggregate Member.

  5. Configure:

    • Interface: Select the AE interface you created (e.g., ae0).

    • LACP Priority: Determines member preference during link selection (default 127).

  6. Click OK.


  7. Repeat for all ports you want in the bundle.

Step 3: Assign AE Interface to Networks and Virtual Routers

  1. Navigate to the Networks tab within the device template.

  2. Add the new AE interface to the relevant LAN network.


  3. Navigate to the Virtual Routers tab.

  4. Add the LAN network (with AE) under the correct Virtual Router.

  5. Commit changes so they propagate to the appliance.

Method 2: Configuring LACP in Appliance Context

For standalone or quick deployments, you can configure LACP directly in the appliance context under Configuration > Networking > Interfaces > AE. This is useful for testing or when applying unique configurations not shared via templates. However, this approach reduces scalability since changes must be performed on each appliance individually.

Verifying LACP Configuration Using VOS CLI: