topic RE: Load sharing (lacp) in ExtremeSwitching (EXOS/Switch Engine)

Load sharing (lacp)

Sai_Prasad_Rao_ — Thu, 22 Sep 2016 19:51:00 GMT

If I have load sharing enabled on 1:4,2:4 with 1:4 as master. Do I need to put all vlans as tag on both 1:4 and 2:4 Or should I allow all vlans as tag on only master port 1:4 1:4,2:4 are ports of one core connecting to other core 1:4,2;4.

RE: Load sharing (lacp)

Paul_Russo — Thu, 22 Sep 2016 19:53:00 GMT

Hello Sai

Once you have a Load share enabled you just add the master port to the VLAN. The other ports will not show up.

Hope that helps

P

RE: Load sharing (lacp)

Sai_Prasad_Rao_ — Thu, 22 Sep 2016 19:53:00 GMT

Didnt get that sorry

U mean allow all vlans on master port only , what if master port goes down? I have on one core: all vlans tagged on 1:4,2:4 On other core all vlans are tagged on 1:4 only

RE: Load sharing (lacp)

Paul_Russo — Thu, 22 Sep 2016 19:53:00 GMT

Hey Sai

The Load share will use all links to send traffic from any VLAN on the port. You just use the master port to assign the Load Share to the VLAN.

So if the master port, or any port, goes down the load share will instantly move the traffic that was supposed to go over that port to one of the other ports.

When you add Load share port to a VLAN it will show the master port and have a flag that it is a shared port it will not show all of the other ports in the load share.

I hope that makes sense.

Thanks
P

RE: Load sharing (lacp)

Patrick_Voss — Thu, 22 Sep 2016 19:53:00 GMT

The master port is the only port that needs to be added into any configuration.

RE: Load sharing (lacp)

Kawawa — Thu, 22 Sep 2016 19:53:00 GMT

Any configurations you add to the master port are propagated to all other ports in the LAG, trying to add a VLAN or any other configuration to the secondary ports in the LAG will produce the following error:Error: Port is in load sharing mode. Perform all configuration changes to load share master .

RE: Load sharing (lacp)

Henrique — Thu, 22 Sep 2016 19:53:00 GMT

When you create a LAG (let's say master = 1:4 and group = 1:4, 2:4) the master port represents the group for switch vlan configuration.

That means the switch will consider this LAG as port "1:4g" where "g" means Load Sharing port.

Based on that, when you do "configure vlan add ports 1:4 tagged", all the LAG will be applied/configured to that vlan.

When you do a "show vlan " you will see the following (based on above description):

Tag: 1:4g

If the master port goes down, traffic will be shared to the remaining ports.

RE: Load sharing (lacp)

Sai_Prasad_Rao_ — Thu, 22 Sep 2016 19:53:00 GMT

OK makes sense

But on switch configuration why I am seeing 1:4,2:4 tagged for all vlans on core-a and only 1:4 tagged for all vlans on core-b . I mean config should be same on both cores right. Both core are connecting to each other over 1:4 and 2:4 and are running vrrp

RE: Load sharing (lacp)

Henrique — Thu, 22 Sep 2016 19:53:00 GMT

Could you please share the output for the command below on both core-a and core-b:

show configuration | include sharing
show sharing

RE: Load sharing (lacp)

Sai_Prasad_Rao_ — Thu, 22 Sep 2016 19:53:00 GMT

Core-A:

enable sharing 1:4 grouping 1:4, 2:4 algorithm address-based L2 lacp

Core-B:

enable sharing 1:4 grouping 1:4, 2:4 algorithm address-based L2 lacp

RE: Load sharing (lacp)

Paul_Russo — Thu, 22 Sep 2016 19:53:00 GMT

Hello Sai

Those are the correct commands. can you share the output you saw when it shows 1:4 tagged on one core and 1:4,2:4 on the other switch?

Also can you do a show port 1:4,2:4 info detail on both switches and post it?

Thanks
P

RE: Load sharing (lacp)

Sai_Prasad_Rao_ — Thu, 22 Sep 2016 19:53:00 GMT

Core-A
-> show ports sharing Load Sharing Monitor
Config Current Agg Ld Share Ld Share Agg Link Link Up
Master Master Control Algorithm Group Mbr State Transitions
==============================================================================
1:4 1:4 LACP L2 1:4 Y A 1
L2 2:4 Y A 1
==============================================================================
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based

Core-B
-> show ports sharing Load Sharing Monitor
Config Current Agg Ld Share Ld Share Agg Link Link Up
Master Master Control Algorithm Group Mbr State Transitions
==============================================================================
1:4 1:4 LACP L2 1:4 Y A 1
L2 2:4 Y A 1
==============================================================================
Link State: A-Active, D-Disabled, R-Ready, NP-Port not present, L-Loopback
Load Sharing Algorithm: (L2) Layer 2 address based, (L3) Layer 3 address based

THIS LOOKS good may be I was seeing some other config,

RE: Load sharing (lacp)

Paul_Russo — Thu, 22 Sep 2016 19:53:00 GMT

I agree it looks like a valid config. If you do a show VLAN for the ones tagged on those ports you should just see port 1:4 added as tagged with a little g showing it is shared. If that is the case I think you are fine.

P

RE: Load sharing (lacp)

Balaji_Kumar_Na — Fri, 23 Sep 2016 09:43:00 GMT

You need to associate master port 1:4 alone to all vlans.