09-22-2017 12:25 AM
we are using a large number of FCX648 (running FCXS07400) and some new ICX 7450 (running SPR08030).
On the FCX we have some server attached using the TRUNK command.
trunk ethe 1/1/9 to 1/1/10 port-name "ServerXY_Trunk1" ethernet 1/1/9
How can I configure this on the ICX ? Is it something like:
lag SERVERXZ static id 7 ports ethernet 2/1/41 ethernet 3/1/41 primary-port 2/1/41
Where are some example showing the advantage using static or dynamic "lag" ? Also for some OS would be very helpful.
Thanks a lot!
10-05-2017 09:06 AM - edited 10-05-2017 09:07 AM
Inside the lag configuration on the ICX you need to enter a deploy statement:
lag SERVERXZ static id 7
A dynamic LAG uses control frames (LACP) to establish a relationship to a neighbor. The member port will only come up, when both sides run LACP and agree about an aggregated relationship.
Therefore traffic wont be lost, if you accidentally misconfigure a port or patch on a wrong device. In a static lag the switch is a little bit dumber and just blasts out on every possible interface.
10-06-2017 08:24 AM - edited 10-06-2017 08:31 AM
The latest ICX Firmware 08.0.61 and later changes this again but for better:
There is no more "deploy" command or primary-ports, either.
lag NAME dynamic id 1 ports ethe 1/1/3 ethe 2/1/3 !
vlan 222 name SOME-Data by port tagged lag 1 router-interface ve 222 !
=== LAG "NAME" ID 1 (dynamic Deployed) === LAG Configuration: Ports: e 1/1/3 e 2/1/3 Port Count: 2 Lag Interface: lg1 Trunk Type: hash-based LACP Key: 20001 Deployment: HW Trunk ID 8 Port Link State Dupl Speed Trunk Tag Pvid Pri MAC Name 1/1/3 Up Forward Full 1G 1 Yes 1 0 609c.9fc7.3550 2/1/3 Up Forward Full 1G 1 Yes 1 0 609c.9fc7.3550 Port [Sys P] [Port P] [ Key ] [Act][Tio][Agg][Syn][Col][Dis][Def][Exp][Ope] 1/1/3 1 1 20001 Yes L Agg Syn Col Dis No No Ope 2/1/3 1 1 20001 Yes L Agg Syn Col Dis No No Ope Partner Info and PDU Statistics Port Partner Partner LACP LACP System ID Key Rx Count Tx Count 1/1/3 1-609c.9fea.8b18 20001 202836 202323 2/1/3 1-609c.9fea.8b18 20001 202828 202327
LAGS are NOW actual virtual interfaces:
vlan 222 name SOME-Data by port tagged lag 3 router-interface ve 222 !
interface lag 12 dual-mode trust dscp !
They even track the aggregate speed correctly:
#sh int lag 1 Lag lg1 is up, line protocol is up Configured speed 2G, actual 2G, configured duplex fdx, actual fdx Member of 3 L2 VLANs, port is dual mode in Vlan 1, port state is Forward BPDU guard is Disabled, ROOT protect is Disabled, Designated protect is Disabled STP configured to ON, priority is level0, mac-learning is enabled Openflow is Disabled, Openflow Hybrid mode is Disabled Mirror disabled, Monitor disabled Mac-notification is disabled Member of active trunk ports 1/1/3,2/1/3,lg1, Lag Interface is lg1 Member of configured trunk ports 1/1/3,2/1/3,lg1, Lag Interface is lg1 No port name 300 second input rate: 2711464 bits/sec, 1237 packets/sec, 0.13% utilization 300 second output rate: 8261520 bits/sec, 1263 packets/sec, 0.41% utilization 1348347414 packets input, 421919821330 bytes, 0 no buffer Received 30608210 broadcasts, 12717840 multicasts, 1298919661 unicasts 0 input errors, 0 CRC, 0 frame, 0 ignored 0 runts, 0 giants 1459147537 packets output, 1297618747807 bytes, 0 underruns Transmitted 8567065 broadcasts, 7064948 multicasts, 1443515195 unicasts 0 output errors, 0 collisions Relay Agent Information option: Disabled
It is also smart enough to switch you to the LAG interface. For example:
SSH@Aggregation_Stack(config)#int e 1/1/27 SSH@Aggregation_Stack(config-lag-if-lg4)#