Hey all,
Let's take look at creating LAGs (LACP and static). LACP (802.3ad) is the most common link-aggregation method. We also offer static LAGs.
To create an LACP LAG named 'testlag' with an auto-generated id, you would issue the following:
ICX#conf t
ICX(config)#lag testlag dynamic id auto
In this example, let's assign ports 1/3/1 and 1/3/3 to this LAG:
ICX(config-lag-testlag)#ports eth 1/3/1 e 1/3/3
LAG testlag deployed successfully!
The resulting configuration from 'show run':
lag lagname dynamic id 1
ports ethe 1/3/1 ethe 1/3/3
!
<output omitted>
!
interface lag 1
We can see the LAG was assigned id 1 and there is also an 'intferace lag 1' in the running configuration. We can use this to define various configurations at the interface level. We will not define anything in our example, but I will show the the interface configuration mode for a lag for the sake of completeness.
ICX(config)#interface lag 1
ICX(config-lag-if-lg1)#
To ensure our LAG is working properly, you can issue 'show lag':
The most important part of this output is the [Ope] column on the far right. A LAG that is up and working will show ‘Ope’ for all ports in this column. If you see ‘Ina’ (inactive) here, you may want to confirm VLAN tagging, Layer 1 port statuses and the partner side LAG configuration.
Configurating a static LAG will be very similar. Using the same ports from our last example, the configuration would like this:
ICX(config)#lag teststaticlag static id auto
ICX(config-lag-teststaticlag)#ports eth 1/3/1 e 1/3/3
LAG teststaticlag deployed successfully!
Resulting configuration in ‘show run’:
lag teststaticlag static id 1
ports ethe 1/3/1 ethe 1/3/3
!
<output omitted>
!
interface lag 1
The ‘show lag’ for a static LAG will look like this:
Hopefully the above two examples will give you confidence to deploy both dynamic (LACP) and static LAGs. We do have some additional LAG options. To see all available configuration options for LAGs, please see our FastIron Layer 2 Switching Configuration Guide:
HTML Version
PDF Version (requires login)
Let us know if you have any questions!
