Hi guys
I am more than fed up with the issue of RB433ah nework port getting burnt
On the same mast where I have so many radios (Motorola canopy, tranzeo and Mikrotik), in the past two years I have changed the RB433ah about three times due to network port failure whereas other radios are doing fine.
At first I thought it was due to lighting but Why is it not affecting others.
I have also noticed this at many other locations.
The network port on 433ah are failing like never before + kernel failure.

By my own rating, out of every ten 433ah boards, 3 will have network port failure and 4 will have kernel failure within the first few mounts in outdoor enviroment.

Can someone explain this.

Hi , can you make some photo like outdoor case inside, mast installation, grounding. I believe we can help eliminate this problem.Else lightening damage and kernel failure is not related. When your PHY is dead it's simple show no link, or no BIOS start/no booting.

I'm seeing similar issues on the RB433UAH, sporadically dropping wireless and/or lan interfaces :-/
sometimes a restart or reseating of the card makes it work again but it doesn't make any sense why a simple reboot would cause the cards to suddenly no longer be recognised.

It also seems to go into a debug mode when the ethernet ports disappear, showing random messages like:

BUFS: b_a 1, b_f 0, f_a 1, f_f 0

Note however the issue doesn't seem to be permanent.. rebooting a couple of times and reseating can completely fix the failure :-/

We've a lot of problems with 4xx-Boards around a region where there
are many lightnings. Ethernetports are dying while POE is working.
Sometimes it helps to unplug the Power, wait for a while and then
plug it in again. Other Equipment plugged to the same outlet strip
has no problems. It seems 4xx-Ethernetports are very sensible to
powerevents.

We're looking into using Ethernet Lightning-Protection in this region.

I've seen expensive equipment (e.g. MOTO PTP) comes with Ethernet
lightning protection. One near the Equipment and one where Ethernet
enters the Building.

Stefan

These problems I'm having are just on our testbench thou, and not a cloud in the sky

Tried downgrading all the boards to routerboot 2.19 with no difference, another one just stopped responding on ethernet interfaces after a reboot.

Should have read the boards before buying a RB433 with this same issue

BABOW.
1 out of 4 I got for a job had this issue.

No bios updates or firmware changes could fix it, the problem was pretty random as far as I could see.

Yeah, tried a bunch of wifi cards, every time I enabled the wireless it'd kernel panic and lose the wifi interfaces. Fiddling around would get them back again and then it'd panic again etc.

So now I'm using a little RB133C instead.

Out of interest, what wireless cards were you using? Mine were SR5's
and did you have problems with any other wireless cards?

I'm away from home atm but will be testing mine with a couple of other spare cards I have laying around to see if it does the same with Mikrotik cards.

R52 and R52-350

Why not try to use the POE surge protector...
We have applied over 300 unit POE surge protector..

Before we buy we facing a lot of ethernet port burned issue, but after applied that, no more ethernet burned occur...

But, when there is ready strong lightning, the POE surge protector will burned but not the equipment ethernet.

If you interest, can email to me and i will share with u.

These problems I'm having are just on our testbench thou, and not a cloud in the sky

Tried downgrading all the boards to routerboot 2.19 with no difference, another one just stopped responding on ethernet interfaces after a reboot.

The problem was occuring on these boards before they even got outside my office.

regarding the problems with lightning - please answer the question asked by 'aaa' we can't help you otherwise. we must know the details about the installation.

regarding strange kernel messages - post screenshots and more information.

I can't answer if there is no information. Read the article in my signature!