Switch Link Aggregations Configuration

Dashboard Location: Switching > Configure > Link Aggregation

Network Link Aggregation and LACP Management

Switch Link Aggregations configuration in Meraki networks provides administrators with comprehensive port bonding and link aggregation capabilities, enabling increased bandwidth, redundancy, and load distribution across multiple physical connections. This functionality supports enterprise network resilience, bandwidth optimization, high availability requirements, and traffic load balancing through Link Aggregation Control Protocol (LACP) and static link bundling for enhanced network performance and fault tolerance.

Diagram

Classes

switch (meraki.domains.organizations.networks)

Name	Type	Constraint	Mandatory	Default Value
link_aggregations	List	`[link_aggregations]`	No

link_aggregations (meraki.domains.organizations.networks.switch)

Name	Type	Constraint	Mandatory
switch_ports	List	`[switch_ports]`	No
switch_profile_ports	List	`[switch_profile_ports]`	No
link_aggregation_name	String	min: `1`, max: `127`	Yes

switch_ports (meraki.domains.organizations.networks.switch.link_aggregations)

Name	Type	Constraint	Mandatory	Default Value
port_id	Any	Integer[min: `1`, max: `48`] or String[matches: `(\d{1,3})`]	Yes
device	String	min: `1`, max: `127`	Yes

switch_profile_ports (meraki.domains.organizations.networks.switch.link_aggregations)

Name	Type	Constraint	Mandatory	Default Value
profile	String	min: `1`, max: `127`	Yes
port_id	Any	Integer[min: `1`, max: `48`] or String[matches: `(\d{1,3})`]	Yes

Examples

Example-1: The example below demonstrates link aggregation configuration.

This configuration creates bundled network connections for increased bandwidth and redundancy. The example includes LACP settings, load balancing algorithms, and port grouping for high-availability network links.

This configuration establishes link aggregation using “switch_ports” arrays containing “device” identifiers and “port_id” numbers (8, 9) to define which physical ports participate in the bundle, and “link_aggregation_name” to label each link aggregation group. link_aggregation_name must be unique within a network — every LAG (even those on different switches in the same network) must have a distinct name (e.g. core_switch_01_LAG1, core_switch_02_LAG1). Reusing the same name across LAGs in the same network will cause configuration conflicts and apply failures.

Note: Updating the ports of an existing LAG is performed by editing the configuration of the physical port members (their port-level attributes such as VLAN, trunk/allowed VLANs, RSTP, STP guard, PoE, etc.). The Meraki Dashboard API does not expose an updatable virtual aggregation/master port — LAG-wide settings are derived from the lowest-numbered physical member. To change LAG membership itself, update the switch_ports list under the corresponding link_aggregations entry; to change forwarding behaviour, update the underlying switch.ports entries for each physical port that belongs to the LAG.

meraki:
  domains:
    - name: !env domain
      administrator:
        name: !env org_admin
      organizations:
        - name: !env org
          networks:
            - name: !env network_name
              product_types:
                - appliance
                - switch
                - wireless
                - camera
                - sensor
                - cellularGateway
              switch:
                link_aggregations:
                  - switch_ports:
                      - device: !env core_switch_01
                        port_id: 8
                      - device: !env core_switch_01
                        port_id: 9
                    link_aggregation_name: "core_switch_01_LAG1"
                    # switch_profile_ports:
                    #   - profile: "1"
                    #     port_id: 1
                    #   - profile: "1"
                    #     port_id: 2
                  - switch_ports:
                      - device: !env core_switch_02
                        port_id: 8
                      - device: !env core_switch_02
                        port_id: 9
                    link_aggregation_name: "core_switch_02_LAG1"
                    # switch_profile_ports:
                    #   - profile: "2"
                    #     port_id: 3
                    #   - profile: "2"
                    #     port_id: 4