Setting and Clearing a 802.3ad Static LAG, on various products

FAQ_User — Tue, 06 May 2014 01:41:00 GMT

Article ID: 6769

Products
DFE
Matrix C1
Matrix C2

Cause
The

code:

lacp static lag

command set, used for creating and removing Static Link Aggregation Groups, auto-generates a series of commands which then appear in the device configuration if they override factory defaults.

This document specifies the subcommands used for each product and operation.

Solution
Matrix DFE

How to create a Static LAG (example): Matrix N3(rw)->set lacp static lag.0.2 key 2000 ge.1.1-2

Issuing :
clear port lacp port ge.1.1-2 aadminstate all
clear port lacp port ge.1.1-2 padminstate all
clear port lacp port ge.1.1-2 aadminstate lacpactive
set lacp aadminkey lag.0.2 2000
set port lacp port ge.1.1-2 aadminkey 2000
set port lacp port ge.1.1-2 padminkey 2000
clear port lacp port ge.1.1-2 padminsysid
set port lacp port ge.1.1-2 disable

Matrix N3(rw)->

Lags are numbered lag.0.1 through lag.0.48.
Keys are numbered 0 through 65535.
Key specification is optional. If unspecified, a key will be assigned based on the referenced lag port. That is, keys 1-48 will be used, respectively, for lag.0.1 through lag.0.48.
The key value must be unique, on the local/actor device. If ports other than the desired underlying physical ports share the same admin key value, aggregation will fail or undesired aggregations will form.

How to remove a Static LAG (example): Matrix N3(rw)->clear lacp static lag.0.2 ge.1.1-2

Issuing :
set port lacp port ge.1.1-2 disable
clear port lacp port ge.1.1-2 padminkey
clear port lacp port ge.1.1-2 aadminkey
clear port lacp port ge.1.1-2 aadminstate all
clear port lacp port ge.1.1-2 padminstate all
set port lacp port ge.1.1-2 enable

Matrix N3(rw)->clear lacp aadminkey lag.0.2
Matrix N3(rw)->The last command is necessary due to a bug in the '

code:

clear lacp static

' command, which does not fully reverse the commands issued by the '

code:

set lacp static

' command.

How to 802.1Q-trunk a LAG: 5038.
Further details are available in the Matrix DFE Configuration Guide.

Matrix C1

How to create a Static LAG (example): Matrix C1(rw)->set lacp static lag.1.2 key 1000 ge.1.8-9

Issuing :
clear port lacp port ge.1.8-9 aadminstate all
clear port lacp port ge.1.8-9 padminstate all
clear port lacp port ge.1.8-9 aadminstate lacpactive
set port lacp port ge.1.8-9 padminstate lacpagg
set lacp aadminkey lag.1.2 1000
set port lacp port ge.1.8-9 aadminkey 1000
set port lacp port ge.1.8-9 padminkey 1000
clear port lacp port ge.1.8-9 padminsysid
Matrix C1(rw)->

Lags are numbered lag.1.1 and lag.1.2.
Keys are numbered 0 through 65535.
The key value must be unique, on the local/actor device. If ports other than the desired underlying physical ports share the same admin key value, aggregation will fail or undesired aggregations will form.
At least two ports need to be assigned to a LAG port for a Link Aggregation Group to form and attach to the specified LAG port.

How to remove a Static LAG (example): Matrix C1(rw)->clear lacp static lag.1.2 ge.1.8-9

Issuing :
set port lacp port ge.1.8-9 disable
clear port lacp port ge.1.8-9 padminkey
clear port lacp port ge.1.8-9 aadminkey
clear port lacp port ge.1.8-9 aadminstate all
clear port lacp port ge.1.8-9 padminstate all
set port lacp port ge.1.8-9 enable
clear lacp aadminkey lag.1.2
Matrix C1(su)->
Matrix C2

How to create a Static LAG (example): Matrix C2(rw)->set lacp aadminkey lag.0.5 422
Matrix C2(rw)->set port lacp port ge.1.8-9 aadminkey 422
Matrix C2(rw)->Note1: Though the '

code:

set lacp static

' command exists, it tends to lock up the cli (firmware 2.01.24, at least) and should not be used.
Note2: Because

code:

lag.0.5

's aadminkey has a default value of

code:

(recommended for use), the '

code:

set lacp

' command shown above is only necessary if a differing aadminkey value had been selected. It will only appear in the output of a '

code:

show configuration

' command if it differs from the default value.

Lags

Keys are numbered 0 through 65535.
The default Key values for lag.0.1 through lag.0.6 are 418-423, respectively.
The key value must be unique, on the local/actor device. If ports other than the desired underlying physical ports share the same admin key value, aggregation will fail or undesired aggregations will form.
At least two ports need to be assigned to a LAG port for a Link Aggregation Group to form and attach to the specified LAG port.

How to remove a Static LAG (example): Matrix C1(su)->set lacp aadminkey lag.0.5 422
Matrix C1(su)->clear port lacp port ge.1.8-9 aadminkey
Matrix C1(su)->Note1: Though the '

code:

clear lacp static

' command exists, it tends to lock up the cli (firmware 2.01.24, at least) and should not be used.
Note2: Because

code:

lag.0.5

's aadminkey already has a value of

code:

, the '

code:

set lacp

' command shown above will not be necessary.

See also: 5531.
Further details are available in the Matrix C2 Configuration Guide.

topic Setting and Clearing a 802.3ad Static LAG, on various products in FAQs

Setting and Clearing a 802.3ad Static LAG, on various products