01-08-2023 08:12 PM - edited 01-10-2023 02:39 PM
We are getting "LACP interface ethernet1/24 moved out of AE-group ae1" through syslog (emailed) multiple times in a day on PA 3410 running on PAN OS 10.2.3 in HA active/passive. The switch in use is Aruba 8320
Interesting the same msg is received from the passive device too (whereas its interface is in shutdown mode)
l2ctrld.log has no error message and there is no other error msgs on the system logs. The ports seem to be working fine too.
Below is the last msg from the l2ctrld.log
The ehmon brdagent logs have no errors related to this port 1/24.
Only thing is that this FW was replaced recently. (although the error started to come only after a month or so from migration). The Switch seems to be populating no errors too.
The only other error msgs i see is of "Hardware session Offloading disabled" (Although, I believe this has nothing to do with this LACP port moving out of the group)
Interesting the alerts also do not get disabled: (configuring below has no change in the alert- I am wondering if this msg is from FW although the alert msg says it's coming from the FW)
02-03-2023 09:58 AM
If you aren't seeing the associated log on the device itself, it sounds like something with the log-receiver process is just continually stuck processing. You can try restarting that process itself via the 'debug software restart process log-receiver' and seeing if that clears things up if you haven't tried that already.
I've assumed that you've tried restarting both units to see if it clears things, but if not that would be my next step. If neither of those things work I'd definitely pass this to TAC to help troubleshoot. You shouldn't be getting email notices if you don't have an associated system log, so something is definitely not being processed properly.
01-11-2023 02:00 AM - edited 01-11-2023 02:02 AM
Hi @paragkarki143 ,
Can you check the LACP logs ? Please check if the links are leaving (changing states in) the LAG because of missed LACPDUs from the peer.
This could be a result of the transmission rate mismatch between the peers. Fast mode is very sensitive to the network churn and if no LACPDUs are received for 3 seconds, LACP will go down.
You can set the LACP transmission rate to Slow as to not miss PDUs or LACP updates which is set to a fairly sensitive setting in Fast Mode.
Hope this helps.
01-11-2023 01:59 PM - edited 01-11-2023 02:03 PM
Thanks for the reply.
There are no missed LACPDU's and the LACP Tx rate is slow. Peer is an Aruba switch.
We receive "
LACP interface ethernet1/24 moved out of AE-group ae1. Selection state Unselected(Link down)
constantly" and strangely there are no logs generated in the Firewall (System/monitor logs)
l2ctrld log has below(the whole pattern in curly bracket is repeats with no other errors in-between), and I wonder if this this is the syncing msg to the passive device.
Interestingly, the passive FW is also throwing the same error where as to the ports (ethernet ports) are not even up. I do not see any bugs of such kind reported either.
Any help will be much appreciated.
01-11-2023 02:11 PM
The alert filter that you have setup under your 'system-critical' entry should definitely be preventing the firewall from sending you alerts about these lacp-up/link-down events.
Was their a period that the 3410 was functioning without these messages properly, or did they show up as soon as you installed the 3410?
01-11-2023 02:16 PM
Thanks for the reply. These were installed on early Dec and were working fine until the start of Jan when the msgs started popping out. I m very surprised that the filters are not blocking the msgs and the errors are coming from the passive FW too (eth ports are not even up).
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!