LACP via MLAG config check

Ian_Broadway — Fri, 18 Aug 2017 13:59:00 GMT

Hi All,

First time configuring a server with LACP via two switches with MLAG configuration.

Can someone just confirm this is correct?

I have read the XOS guide and have not done anything extra with regards to configuring a LACP MAC or setting priorities?

The two switches are x460-g2s running 21.1.3.7 patch 1-7. Currently seems to be working.

see the configuration below;

MCR-SVR-SW3.24 # sh mlag peer Multi-switch Link Aggregation Peers: MLAG Peer : MCR-SVR-SW4 VLAN : ISC-3 Virtual Router : VR-Default Local IP Address : 1.1.1.17 Peer IP Address : 1.1.1.18 MLAG ports : 1 Tx-Interval : 1000 ms Checkpoint Status : Up Peer Tx-Interval : 1000 ms Rx-Hellos : 1455 Tx-Hellos : 1509 Rx-Checkpoint Msgs: 1213 Tx-Checkpoint Msgs: 1345 Rx-Hello Errors : 0 Tx-Hello Errors : 0 Hello Timeouts : 0 Checkpoint Errors : 0 Up Time : 0d:0h:23m:43s Peer Conn.Failures: 0 Local MAC : 00:04:96:99:02:e1 Peer MAC : 00:04:96:99:06:98 Config'd LACP MAC : None Current LACP MAC : 00:04:96:99:06:98 Authentication : None
MCR-SVR-SW4.31 # sh mlag peer Multi-switch Link Aggregation Peers: MLAG Peer : MCR-SVR-SW3 VLAN : ISC-3 Virtual Router : VR-Default Local IP Address : 1.1.1.18 Peer IP Address : 1.1.1.17 MLAG ports : 1 Tx-Interval : 1000 ms Checkpoint Status : Up Peer Tx-Interval : 1000 ms Rx-Hellos : 1441 Tx-Hellos : 1441 Rx-Checkpoint Msgs: 1333 Tx-Checkpoint Msgs: 1199 Rx-Hello Errors : 0 Tx-Hello Errors : 0 Hello Timeouts : 0 Checkpoint Errors : 0 Up Time : 0d:0h:23m:29s Peer Conn.Failures: 0 Local MAC : 00:04:96:99:06:98 Peer MAC : 00:04:96:99:02:e1 Config'd LACP MAC : None Current LACP MAC : 00:04:96:99:06:98 Authentication : None
MCR-SVR-SW3.25 # sh mlag ports Local Local Remote MLAG Local Link Remote Peer Fail Fail Id Port State Link Peer Status Count Count ================================================================================ 1 1 A Up MCR-SVR-SW4 Up 0 0 ================================================================================ Local Link State: A - Active, D - Disabled, R - Ready, NP - Port not present Remote Link : Up - One or more links are active on the remote switch, Down - No links are active on the remote switch, N/A - The peer has not communicated link state for this MLAG port Number of Multi-switch Link Aggregation Groups : 1 Convergence control : Conserve Access Lists Reload Delay Interval : 30 seconds Reload Delay : Disabled
MCR-SVR-SW4.32 # sh mlag ports Local Local Remote MLAG Local Link Remote Peer Fail Fail Id Port State Link Peer Status Count Count ================================================================================ 1 1 A Up MCR-SVR-SW3 Up 0 0 ================================================================================ Local Link State: A - Active, D - Disabled, R - Ready, NP - Port not present Remote Link : Up - One or more links are active on the remote switch, Down - No links are active on the remote switch, N/A - The peer has not communicated link state for this MLAG port Number of Multi-switch Link Aggregation Groups : 1 Convergence control : Conserve Access Lists Reload Delay Interval : 30 seconds Reload Delay : Disabled
MCR-SVR-SW3.26 # sh sharing Load Sharing Monitor Config Current Agg Min Ld Share Dist Ld Share Agg Link Link Up Master Master Control Active Algorithm Flags Group Mbr State Transitions ================================================================================ 1 1 LACP 1 L2 A 1 Y A 2 ================================================================================ Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback Minimum Active: (<) Group is down. # active links less than configured minimum Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based (L3_L4) Layer 3 address and Layer 4 port based (custom) User-selected address-based configuration Custom Algorithm Configuration: ipv4 L3-and-L4, xor Distribution Flags: A - All: Distribute to all members, L - Local Slot: Distribute to members local to ingress slot, P - Port Lists: Distribute to per-slot configurable subset of members, R - Resilient Hashing enabled. Number of load sharing trunks: 1
MCR-SVR-SW4.33 # sh sharing Load Sharing Monitor Config Current Agg Min Ld Share Dist Ld Share Agg Link Link Up Master Master Control Active Algorithm Flags Group Mbr State Transitions ================================================================================ 1 1 LACP 1 L2 A 1 Y A 2 ================================================================================ Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback Minimum Active: (<) Group is down. # active links less than configured minimum Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based (L3_L4) Layer 3 address and Layer 4 port based (custom) User-selected address-based configuration Custom Algorithm Configuration: ipv4 L3-and-L4, xor Distribution Flags: A - All: Distribute to all members, L - Local Slot: Distribute to members local to ingress slot, P - Port Lists: Distribute to per-slot configurable subset of members, R - Resilient Hashing enabled. Number of load sharing trunks: 1

I've highlighted the config from one of the switches in bold to differentiate.

Do i need to worry about this?
http://documentation.extremenetworks.com/exos/EXOS_21_1/Slots_and_Ports/c_LACPDU-transmision-on-MLAG...

Thanks
Ian

RE: LACP via MLAG config check

Ian_Broadway — Fri, 18 Aug 2017 14:09:00 GMT

the commands i used;

MCR-SVR-SW3
create vlan ISC-3
CONF "ISC-3" T 1502
conf isc-3 add po 50 t
conf "isc-3" ipaddress 1.1.1.17/30
create mlag peer MCR-SVR-SW4
conf mlag peer "MCR-SVR-SW4" ipaddress 1.1.1.18
enable sharing 1 grouping 1 algorithm address-based L2 lacp
enable mlag port 1 peer "MCR-SVR-SW4" id 1

MCR-SVR-SW4
create vlan ISC-3
conf vlan "isc-3" t 1502
conf "isc-3" ipaddress 1.1.1.18/30
conf "isc-3" add po 49 t
create mlag peer MCR-SVR-SW3
conf mlag peer "MCR-SVR-SW3" ipaddress 1.1.1.17
enable sharing 1 grouping 1 algorithm address-based L2 lacp
enable mlag port 1 peer "MCR-SVR-SW3" id 1

RE: LACP via MLAG config check

Stephane_Grosj1 — Fri, 18 Aug 2017 14:09:00 GMT

Hi,

one thing that you might want to do, is also to configure the LACP Mac, instead of leaving it automatic. This is not critical, but I consider it a best practice. In case of a reboot of the MLAG switches, it helps to not have a flap of that Mac address, impacting the traffic that just restarted to flow.

RE: LACP via MLAG config check

Ian_Broadway — Fri, 18 Aug 2017 14:09:00 GMT

I assume I can just configure the current auto mac as the configured one?

RE: LACP via MLAG config check

Stephane_Grosj1 — Fri, 18 Aug 2017 14:09:00 GMT

yes, the lacp-mac is one of the two MLAG peer's mac.

RE: LACP via MLAG config check

dflouret — Fri, 18 Aug 2017 19:41:00 GMT

Ian,

One of the hidden goodies of v21.1.x is that you have an application in the GUI to automate the configuration of MLAG.

It is documented in the Chalet User Guide
http://documentation.extremenetworks.com/chalet/index.html

You may want to play with it and tell us what you think about it.

topic RE: LACP via MLAG config check in ExtremeSwitching (EXOS/Switch Engine)

LACP via MLAG config check

RE: LACP via MLAG config check

RE: LACP via MLAG config check

RE: LACP via MLAG config check

RE: LACP via MLAG config check

RE: LACP via MLAG config check