Tue Dec 06, 2016 7:19 am
I have noticed two occasions of LACP resetting and pause frames errors. The most recent log entries follows:
Dec 5 17:51:33 switch[1370]: got excessive pause frames on port 4 (15116), count = 1
Dec 5 20:13:51 Port: link state changed to 'down' on port 12
Dec 5 20:13:51 STP: set port 12 to discarding
Dec 5 20:13:52 LACP: starting negotiation with partner D4-CA-6D-AC-D4-84
Dec 5 20:13:52 LACP: LACP changed state to Active on port 1 (key 10)
Dec 5 20:13:52 switch[2876]: LACP changed state to Active on port 1 (Port 1-Router) (key 10)
Dec 5 20:13:52 LACP: LACP changed state to Active on port 2 (key 10)
Dec 5 20:13:52 switch[2880]: LACP changed state to Active on port 2 (Port 2-Router) (key 10)
Dec 5 20:13:52 STP: set port 15 to discarding
Dec 5 20:13:52 STP: set port 1 to discarding
Dec 5 20:13:52 STP: set port 2 to discarding
Dec 5 20:13:54 Port: link state changed to 'up' (100M-F) on port 12
Dec 5 20:13:54 STP: set port 12 to discarding
Dec 5 20:13:55 STP: set port 15 to learning
Dec 5 20:13:55 STP: set port 1 to learning
Dec 5 20:13:55 STP: set port 2 to learning
Dec 5 20:13:55 STP: set port 15 to forwarding
Dec 5 20:13:55 STP: set port 1 to forwarding
Dec 5 20:13:55 STP: set port 2 to forwarding
Dec 5 20:13:57 STP: set port 12 to learning
Dec 5 20:13:57 STP: set port 12 to forwarding
Dec 5 20:14:11 Port: link state changed to 'down' on port 12
Dec 5 20:14:11 STP: set port 12 to discarding
Dec 5 20:14:14 Port: link state changed to 'up' (1G) on port 12
Dec 5 20:14:14 STP: set port 12 to discarding
Dec 5 20:14:16 STP: set port 12 to learning
Dec 5 20:14:16 STP: set port 12 to forwarding
Dec 5 20:14:16 STP: set port 12 to discarding
Dec 5 20:14:31 STP: set port 12 to learning
Dec 5 20:14:46 STP: set port 12 to forwarding
Dec 5 20:16:44 Port: link state changed to 'down' on port 12
Dec 5 20:16:44 STP: set port 12 to discarding
Dec 5 20:16:44 LACP: starting negotiation with partner D4-CA-6D-AC-D4-84
Dec 5 20:16:44 LACP: LACP changed state to Active on port 2 (key 10)
Dec 5 20:16:44 switch[3184]: LACP changed state to Active on port 2 (Port 2-Router) (key 10)
Dec 5 20:16:44 LACP: LACP changed state to Active on port 1 (key 10)
Dec 5 20:16:45 switch[3188]: LACP changed state to Active on port 1 (Port 1-Router) (key 10)
Dec 5 20:16:45 STP: set port 15 to discarding
Dec 5 20:16:45 STP: set port 1 to discarding
Dec 5 20:16:45 STP: set port 2 to discarding
Dec 5 20:16:46 Port: link state changed to 'up' (100M-F) on port 12
Dec 5 20:16:46 STP: set port 12 to discarding
Dec 5 20:16:47 STP: set port 15 to learning
Dec 5 20:16:47 STP: set port 1 to learning
Dec 5 20:16:47 STP: set port 2 to learning
Dec 5 20:16:47 STP: set port 15 to forwarding
Dec 5 20:16:47 STP: set port 1 to forwarding
Dec 5 20:16:47 STP: set port 2 to forwarding
Dec 5 20:16:49 STP: set port 12 to learning
Dec 5 20:16:49 STP: set port 12 to forwarding
Dec 5 20:17:03 Port: link state changed to 'down' on port 12
Dec 5 20:17:03 STP: set port 12 to discarding
Dec 5 20:17:06 Port: link state changed to 'up' (1G) on port 12
Dec 5 20:17:06 STP: set port 12 to discarding
Dec 5 20:17:41 STP: set port 12 to learning
Dec 5 20:17:56 STP: set port 12 to forwarding
Dec 5 20:55:46 switch[1370]: got excessive pause frames on port 4 (15004), count = 1
Dec 5 21:00:28 switch[1370]: got excessive pause frames on port 4 (17541), count = 1
Dec 5 21:07:56 switch[1370]: got excessive pause frames on port 4 (16455), count = 1
Dec 5 21:09:34 switch[1370]: got excessive pause frames on port 4 (15936), count = 1
Dec 5 21:12:15 switch[1370]: got excessive pause frames on port 4 (15483), count = 1
Dec 5 21:34:25 switch[1370]: got excessive pause frames on port 4 (15279), count = 1
I am running 1.4.6 and have noticed the LACP problem on more recent versions of firmware. Port 4 and 12 are UBNT AC Rocket radios with flow control active. This is a WS-12-50A so I have no idea what port 15 is. This switch only has 14 ports. According to the logs the problems start with port 12; maybe an RSTP issue? I have no log entries on the attached Mikrotik CCR. It appears to be oblivious to all of the hate and discontent in the switch. I have not noticed any problems prior to a version of 1.4.5 RC when I received my first problem similar to this. I upgraded to 1.4.6 last week and I just received the problem again.
Any recommendations are appreciated.