jjohnsoncantell Posted March 31, 2016 Posted March 31, 2016 Greetings, Since a controller rebuild on my mc3200 I have been getting frequent messages in the syslog such as this "kernel: protocol 0081 is buggy, dev eth0" It repeats constantly and in large numbers such as in the excerpt from the syslog below. I've tried using the other ethernet port and I'm getting the same message just with eth1 instead so I'm guessing it cannot be the nic itself. A few weeks after this started we have noticed all the clients being dropped from the controller at the same time at random times throughout the day, it may have been happening for longer but it's only recently I've been aware of it. Any suggestions as to a solution would be appreciated [TABLE=width: 1810] [TR] [TD=align: right]24/03/2016 00:06[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]kernel: protocol 0081 is buggy, dev eth0[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:06[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 14 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:07[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 8 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:08[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 47 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:10[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 21 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:11[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 6 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:12[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 12 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:13[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 14 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:15[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 13 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:16[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 46 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:17[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 5 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:18[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 37 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:19[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 21 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:20[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 19 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:22[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 11 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:23[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 25 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:24[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 9 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:25[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 19 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:26[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 14 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:28[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 21 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:29[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]last message repeated 11 times[/TD] [/TR] [TR] [TD=align: right]24/03/2016 00:29[/TD] [TD]Kernel.Critical[/TD] [TD]10.0.0.15[/TD] [TD]kernel: protocol 0081 is buggy, dev eth0[/TD] [/TR] [/TABLE]
njc235 Posted April 1, 2016 Posted April 1, 2016 Have you logged a call with Fortinet support? If you are 'in' support it is your best option.
twin--turbo Posted April 1, 2016 Posted April 1, 2016 Our first MC3200 was very flakey, turned out to be faulty. TT
jjohnsoncantell Posted April 1, 2016 Author Posted April 1, 2016 I wish it was still in support but its not. Its was reflashed back to factory and re-configured which is when i started to get this problem. Going try and get a factory image incase the one on the controller was corrupted.
njc235 Posted April 1, 2016 Posted April 1, 2016 Depending on how long it's been out of support, you might like to try to get it back on again. There will be a backdate fee but it may not go all the way back.
jjohnsoncantell Posted April 11, 2016 Author Posted April 11, 2016 Looks like ours was a faulty controller too @TT thankfully its been swapped out for a working model. Today is the first time it will be used in anger so I'm hoping it will be ok.
jjohnsoncantell Posted April 11, 2016 Author Posted April 11, 2016 @njc235 The company whos engineer flashed it before the problem occurred. Still an outdated controller but at least its now working
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now