In the instructions for setting up
netiron-6300a-switchingguide.pdf and netiron-05900a-switchingguide.pdf
It is written to make LAG do the following:
Configuring the primary port for a LAG
In previous versions of the Multi-Service IronWare software, the lowest number port was assigned as
the primary port in a LAG or LACP configuration. In version 03.7.00 and later, the primary port must be
explicitly assigned using the primary-port command.
To designate the primary port for the static LAG "blue", use the following command.
device(config)# lag blue static
device(config-lag-blue)# primary-port 3/2
Syntax: [no] primary-port slot/port
Once a primary port has been configured for a LAG, all configurations that apply to the primary port
are applied to the other ports in the LAG.
Configuring load sharing type
Individual LAGs can be configured to perform load sharing over the ports in the LAG using either a
hash based or per packet method, as shown in the following.
device(config)# lag blue static
device(config-lag-blue)# trunk-type hash-based
Syntax: [no] trunk-type hash-based | per-packet
my config:
lag "BRASDownlink" dynamic id 7
ports ethernet 1/41 to 1/42
primary-port 1/41
deploy
port-name "BRAStoP09" ethernet 1/41
port-name "BRAStoP10" ethernet 1/42
!
I do not have such teams. Who knows why?
Only these:
SSH@NetIron CER 2048FX(config-lag-BRASDownlink)
acl-mirror-port
clear
cls
deploy
disable
enable
end
exit
force-primary-port-mac-use
lacp-port-priority
lacp-timeout
monitor
no
physical-port
port-name
ports
primary-port
quit
sflow-forwarding
sflow-subsampling
show
trunk-threshold
update-lag-name
write