LACP/STP error logs

Post Reply
asouthcombe
Member
Posts: 4
Joined: 11 Dec 2023 08:36

LACP/STP error logs

Post by asouthcombe »

Hello, I have an omniswitch stack of two OS6900-V72 hardware revision R02 and software 8.5.255.R02 GA.
There are some fairly worrying messages showing in switch 1's log, something like this:

2025 Apr 15 02:35:05.323 [SWITCH NAME REDACTED] swlogd linkAggNi main ERR: [1:1] -> [la_ni_hw_lacp_frame_trt.cpp:263] la_ni_lacp_decode_frame_f: Not my chas, Qdisp_mod/port: 4/0 in_chas: 2 my_chas: 1
repeated many many times.

there is also this:

2025 Apr 15 02:35:04.520 [SWITCH NAME REDACTED] swlogd stpNi _BINt ERR: STPNI stpni_decodeFrame@310 This seems to be the packet which I sent

We have no idea what may be the problem. We have a case open with ALU but they aren't particularly quick and member 1 went down overnight.
We have LACP linkaggs, but none really new and no changes for almost a month. I'm not sure when this log started appearing.
Does anyone have any ideas?
silvio
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 2076
Joined: 01 Jul 2008 10:51
Location: Germany

Re: LACP/STP error logs

Post by silvio »

Strange messages... I haven't seen them.
To find out when it startet you have two possibilities:
- Maybe there is an external trap receiver (like Omnivista) or syslogserver attached. Then you can check, if you see any associated messages at the same time and can check when they have started.
- in the flash of the switch is a swlog_archive folder. Copy the gz-file to your computer and unzip it. There are the older swlog files. Together with the 8 actual files you can search f.e. with notepad++ within all files (all in one search) for the messages.
But you have a very old release (7 years). It will be good idea to do an update and check after it for the message again.
BR Silvio
Post Reply

Return to “OmniSwitch 6900”