X620 error messages: "adj 0.0.0.0: # L3 hash table entries already 0"

[FredrikB]

Hi!

We see a LOT of these on an X620-16x running 22.5.1.7 patch1-9) that is an MLAG peer with another identical switch:

09/30/2019 12:44:53.03 adj 0.0.0.0: # L3 hash table entries already 0.
09/30/2019 13:15:02.14 Previous message repeated 1844 additional times in the last 1809 second(s)

The other MLAG peer has no logs of this kind. The only other switch where we see this is an old X450a-24x with some VLANs that are the same as on this X620. There are, however, lots of switches with these same VLANs that do not log anything similar.

I found a couple of posts and KBs that state it's cosmetic, but this is on 22.5, not 15.x as the articles talk about:

https://community.extremenetworks.com/extremeswitching-exos-223284/adj-0-0-0-0-l3-hash-table-entries-already-0-6780841

https://extremeportal.force.com/ExtrArticleDetail?an=000090797

Should we raise a case for this in 22.5 or just filter out the logs?

Best regards,

/Fredrik

[FredrikB]

HI! Thanks for the reply. We see this in other switches ad well (non-stacked) and it seems the counters in the switch get out of sync from time to time causing this. Rebooting or creating an ACL to stop the messages has been proposed, but the ACL solution may cause other messages to be suppressed, so we don’t quite like that workaround. I guess we’ll live with it until the next reboot.

[davidj_cogliane]

I think that looks like the peers are out of sync, might be worth opening a case.