LACP not working

cyberbot · Nov 24, 2020, 12:26 PM

You might have to redeploy it. The ports still show S in the Tio field.

That's not something I've ever tried on this switch.

Thank you Steve,
do you mean to remove the ethernets from the lag or delete the lag completed?
i am getting this error

Error: LAG WAN is deployed, please undeploy it first.

stephenw10 · Nov 24, 2020, 12:47 PM

It's been a while since I had to mess with anything on this switch but I believe, like that error implies, you cannot make changes to the lag while it's deployed. You'll have to 'undeploy' it to switch to long mode timeouts.

You could also try changing the pfSense LACP timeout mode to fast (short) to match which might be easier. In 2.5 that's a GUI setting, I'm not sure I've ever set that in 2.4.5....

stephenw10 · Nov 24, 2020, 1:04 PM

Ah here we go:

[2.4.5-RELEASE][root@7100.stevew.lan]/root: ifconfig lagg0 lacp_fast_timeout
[2.4.5-RELEASE][root@7100.stevew.lan]/root: ifconfig -vv lagg0
lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=500b8<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,VLAN_HWFILTER,VLAN_HWTSO>
        ether 00:e0:ed:86:a6:8c
        inet6 fe80::2e0:edff:fe86:a68c%lagg0 prefixlen 64 scopeid 0x15
        inet 172.21.16.206 netmask 0xffffff00 broadcast 172.21.16.255
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect
        status: active
        groups: lagg
        laggproto lacp lagghash l2,l3,l4
        lagg options:
                flags=90<LACP_STRICT>
                flowid_shift: 16
        lagg statistics:
                active ports: 2
                flapping: 0
        lag id: [(8000,00-E0-ED-86-A6-8C,02B2,0000,0000),
                 (0001,60-9C-9F-54-14-F2,561F,0000,0000)]
        laggport: ixl0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3f<ACTIVITY,TIMEOUT,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING>
                [(8000,00-E0-ED-86-A6-8C,02B2,8000,0001),
                 (0001,60-9C-9F-54-14-F2,561F,0001,0041)]
        laggport: ixl1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING> state=3f<ACTIVITY,TIMEOUT,AGGREGATION,SYNC,COLLECTING,DISTRIBUTING>
                [(8000,00-E0-ED-86-A6-8C,02B2,8000,0002),
                 (0001,60-9C-9F-54-14-F2,561F,0001,0043)]

Though I note it did not cause the lagg to break with pfSense set as short and the switch as long...

cyberbot · Nov 24, 2020, 2:02 PM

@stephenw10 said in LACP not working:

ifconfig lagg0 lacp_fast_timeout

Thank you Steve,

do you mean i have to do it also on the pfsensen side too ?

ifconfig lagg0 lacp_fast_timeout

stephenw10 · Nov 24, 2020, 2:04 PM

It would be better to change that on the switch if you can but, as a test, you can set fast(short) mode in pfSense and that should also match each end.

Steve

cyberbot · Nov 24, 2020, 3:13 PM

@stephenw10 said in LACP not working:

It would be better to change that on the switch if you can but, as a test, you can set fast(short) mode in pfSense and that should also match each end.

Steve

Thank you Steve, ive done hte fast timeout on the pfsense unfortunately it still blocking the ports

on the switch too

=== LAG "wan" ID 5 (dynamic Not Deployed) ===
LAG Configuration:
   Ports:
   Port Count:    0
   Primary Port:  none
   Trunk Type:    hash-based
   LACP Key:      20005
   LACP Timeout:  long

both switches are stacked maybe forgot to mention, maybe its relevant .

stephenw10 · Nov 24, 2020, 3:34 PM

Ah, OK. Yes it could well be, have you configured it for cross-chassis lag?

I have no experience of doing that with Brocade but I imagine it has to be configured for it.

Steve

stephenw10 · Nov 24, 2020, 5:45 PM

Also check the switch logs. There is likely a reason those ports show as blocked and it should be shown there.

cyberbot · Nov 25, 2020, 2:54 PM

@stephenw10 said in LACP not working:

Also check the switch logs. There is likely a reason those ports show as blocked and it should be shown there.

i cannot seems to find the cause yet.
we are still investigating i am affraid the switch and pfsense are not a good friends.
i will try to use a different switch maybe unifi switch L:ayer 3 switch

stephenw10 · Nov 25, 2020, 3:17 PM

Are you able to test a lagg to a single switch rather than cross-chassis?

Or even just connect the ports individually outside of a lagg to be sure they come up as not blocked?

Steve

cyberbot · Nov 25, 2020, 3:24 PM

@stephenw10 said in LACP not working:

Are you able to test a lagg to a single switch rather than cross-chassis?

Or even just connect the ports individually outside of a lagg to be sure they come up as not blocked?

Steve

i havent done that yet, need to drive to the Datacenter to try,

i remeber it working with one cable untill i connect the second cable.,

stephenw10 · Nov 25, 2020, 3:45 PM

It seems like a loop that the switch is blocking then.

I would expect to see something in the switch logs.

cyberbot · Nov 25, 2020, 4:14 PM

@stephenw10 said in LACP not working:

It seems like a loop that the switch is blocking then.

I would expect to see something in the switch logs.

i've been kicking my head down to find the log of the switch.
cannot seems how to see them.
what are the commands for brodcad switches to see the logs?

stephenw10 · Nov 25, 2020, 5:31 PM

On the ICX6450 I have it's show logging at least to get basic logs. I've never tried to get more.

cyberbot · Nov 25, 2020, 6:05 PM

@stephenw10 said in LACP not working:

On the ICX6450 I have it's show logging at least to get basic logs. I've never tried to get more.

Thank you Steve,
i know about the logging but thought i need seperate log check for the LAG only.

Dynamic Log Buffer (50 lines):
Nov 26 02:29:40:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:40:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:40:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:40:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:40:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:40:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:39:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:39:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:33:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:33:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:33:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:33:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:33:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:33:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:32:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:32:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:26:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:26:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:26:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:26:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:26:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:26:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:25:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:25:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:19:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:19:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:19:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:19:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:19:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:19:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:18:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:18:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:12:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:12:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:12:I:Trunk: Group (1/1/1, 2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:12:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:12:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is down.
Nov 26 02:29:12:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:11:I:System: Logical link on dynamic lag interface ethernet 1/1/1 is up.
Nov 26 02:29:11:I:System: Interface ethernet 1/1/1, state up
Nov 26 02:29:11:I:Trunk: Group (1/1/1, 2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:05:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:05:I:Trunk: Group (2/1/1) removed by 802.3ad link-aggregation module.
Nov 26 02:29:05:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is down.
Nov 26 02:29:05:I:System: dynamic lag interface 2/1/1's peer info (priority=3,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:05:I:System: dynamic lag interface 1/1/1's peer info (priority=4,id=e839.3511.faab,key=0) mis-matches with lag's peer info (priority=32768,id=e839.3511.faab,key=715), set to mismatch Error
Nov 26 02:29:04:I:System: Logical link on dynamic lag interface ethernet 2/1/1 is up.
Nov 26 02:29:04:I:System: Interface ethernet 2/1/1, state up
Nov 26 02:29:01:I:Trunk: Group (2/1/1) created by 802.3ad link-aggregation module.
Nov 26 02:29:01:I:System: dynamic lag 1, has new peer info (priority=32768,id=e839.3511.faab,key=715) (N/A)

stephenw10 · Nov 25, 2020, 6:35 PM

Hmm, well I'm not familiar with that peer info mismatch but it doesn't look good!

I would think if you can resolve that it will come up OK.

Looks like this: http://docs.ruckuswireless.com/fastiron/08.0.80/fastiron-08080-l2guide/GUID-6298B5C2-295F-476A-9B99-E465BC0E4B0D.html

You have custom peer info values configured causing the mismatch?

Steve

cyberbot · Nov 25, 2020, 6:41 PM

@stephenw10 said in LACP not working:

You have custom peer info values configured causing the mismatch?

Thank you Steve
what do you mean with You have custom peer info values configured causing the mismatch? on the pfbox or switch?

stephenw10 · Nov 25, 2020, 6:48 PM

On the switch, as shown in that doc.

cyberbot · Nov 25, 2020, 6:53 PM

@stephenw10 said in LACP not working:

On the switch, as shown in that doc.

i always thought it on the switch, i dont understand about the mismatch value thing,
but i need to do some research to see if i can fix it.

stephenw10 · Nov 25, 2020, 6:55 PM

It's possible to set the peer-info value in the switch and that will break the lag if it doesn't match what the peer is actually sending.
Without any peer-info set it accepts the first info it sees as dynamic.

Check the lag config on the switch.

Steve