Hello,
I have an RB433 on 5.17. Eth1 is connected to WAN over PoE injector, Eth2 & Eth3 are connected to separate switches. A bridge is setup on eth2, eth3 and wlan1 with hotspot configured on the bridge. This RB433 is located at a student housing complex that does not currently have any tenants, so there is no one accessing internet, etc.. Every day almost every 24hours, I lose connection to the Mikrotik via Dude. I can't ping it when it happens either. When I go out to the site and connect to eth2 or thru one of the switches, eth1 link goes up and I gain access to the internet. I view the logs but it only tells me that eth1 went down and came back up. Is there some setting that shuts down the eth1 port when there is not a lot of activity or does this sound like a hardware problem? Thanks for the help.
Re: eht1 port shuts down
A sort of port flapping issue? If you have a way of detecting when that is happening (for example some pingable device behind that port) then you can set a Netwatch script to disable/enable that interface, maybe it will save you a trip or two to that location.
Code: Select all
:local Items;
:local Item;
:log info message="The X.Y.Z.W does not ping, we'll flip the ether1.";
:set Items [/int find name="ether1"];
:foreach Item in=$Items do={/int disable $Item};
:delay 5;
:set Items [/int find name="ether1"];
:foreach Item in=$Items do={/int enable $Item};
-
-
walkbyfaith
Frequent Visitor
- Posts: 80
- Joined:
Re: eht1 port shuts down
I have 3 RB433's that this is happening on. I have eht1 connected to WAN over PoE injector. The port just seems to shut down. I go on site and connect to the RB433 via Winbox and I can ping all LAN equipment that is pingable but, I cannot ping anything on the WAN. The LAN clients can ping the default gateway which is the eth2 port on the mikrotik. Here are my firewall rules:
0 ;;; allow all LAN connections
chain=input action=accept src-address-list=MyLAN
1 ;;; accept input new connections
chain=input action=accept connection-state=new
2 ;;; accept input established connections
chain=input action=accept connection-state=established
3 ;;; accept input established connections
chain=input action=accept connection-state=related
4 ;;; allow all LAN connections to pass thru router
chain=forward action=accept src-address-list=MyLAN
5 ;;; accept forward new connections
chain=forward action=accept connection-state=new
6 ;;; accept forward established connections
chain=forward action=accept connection-state=established
7 ;;; accept forward related connections
chain=forward action=accept connection-state=related
8 ;;; drop all other connections
chain=input action=drop
9 ;;; drops all other connections thru router
chain=forward action=drop
10 X ;;; place hotspot rules here
chain=unused-hs-chain action=passthrough
11 ;;; drop invalid forward connections
chain=forward action=drop connection-state=invalid
12 ;;; drop invalid input connections
chain=input action=drop connection-state=invalid
I can see traffic on the LAN side going to the accept rules. I have dude located on a separate subnet and when this happens I cannot ping or winbox to the RB433. Could this be a bad eth1 port? Thanks for any help.
0 ;;; allow all LAN connections
chain=input action=accept src-address-list=MyLAN
1 ;;; accept input new connections
chain=input action=accept connection-state=new
2 ;;; accept input established connections
chain=input action=accept connection-state=established
3 ;;; accept input established connections
chain=input action=accept connection-state=related
4 ;;; allow all LAN connections to pass thru router
chain=forward action=accept src-address-list=MyLAN
5 ;;; accept forward new connections
chain=forward action=accept connection-state=new
6 ;;; accept forward established connections
chain=forward action=accept connection-state=established
7 ;;; accept forward related connections
chain=forward action=accept connection-state=related
8 ;;; drop all other connections
chain=input action=drop
9 ;;; drops all other connections thru router
chain=forward action=drop
10 X ;;; place hotspot rules here
chain=unused-hs-chain action=passthrough
11 ;;; drop invalid forward connections
chain=forward action=drop connection-state=invalid
12 ;;; drop invalid input connections
chain=input action=drop connection-state=invalid
I can see traffic on the LAN side going to the accept rules. I have dude located on a separate subnet and when this happens I cannot ping or winbox to the RB433. Could this be a bad eth1 port? Thanks for any help.
Re: eht1 port shuts down
walkbyfaith, check if problem remains with DC power supply. If it is present only when using PoE injector, try to change to different PoE injector.
Read the topic about similar problem:
http://forum.mikrotik.com/viewtopic.php ... 90#p321499
Read the topic about similar problem:
http://forum.mikrotik.com/viewtopic.php ... 90#p321499
Re: eht1 port shuts down
I have a new RB433 (in service 2 weeks) in almost the same configuration with V5.14 and the same PoE injector that causes some users problems, and it is doing fine. Here are the units I am using:
http://www.titanwirelessonline.com/Pass ... -inj-3.htm
http://www.titanwirelessonline.com/18V- ... e-18vs.htm
Is there a "break-in" time for the start of the failure?
Is it a specific time of day that it fails? Like at night?
What power supply (wall wart) are you using?
http://www.titanwirelessonline.com/Pass ... -inj-3.htm
http://www.titanwirelessonline.com/18V- ... e-18vs.htm
Is there a "break-in" time for the start of the failure?
Is it a specific time of day that it fails? Like at night?
What power supply (wall wart) are you using?
-
-
walkbyfaith
Frequent Visitor
- Posts: 80
- Joined:
Re: eht1 port shuts down
Thanks for all of your help. I replaced the PoE injector with another one. Both are of this type:
http://www.ispsupplies.com/categories/P ... -24-W.html
It usually starts happening in a day, no particular time, pretty much random. But after reading becs article, it is exactly the same port flapping that occurs. I have the RB433 connected from eth2 to a non managed switch and eht3 is connected to an 8 port non managed switch. When this happens, I still get a dhcp ip address from the RB433 and can ping the RB433 LAN port but can get on the internet.
I have not tried using just DC but that will be the next step. Thank you becs and SurferTim for your help. The topics were very helpful.
http://www.ispsupplies.com/categories/P ... -24-W.html
It usually starts happening in a day, no particular time, pretty much random. But after reading becs article, it is exactly the same port flapping that occurs. I have the RB433 connected from eth2 to a non managed switch and eht3 is connected to an 8 port non managed switch. When this happens, I still get a dhcp ip address from the RB433 and can ping the RB433 LAN port but can get on the internet.
I have not tried using just DC but that will be the next step. Thank you becs and SurferTim for your help. The topics were very helpful.
Re: eht1 port shuts down
I have thousands of units out in the field and never see this problem except once. That turned out to be a hi power Fm radio station close by. solved by extra shielding. I just thought i would mention this as it does sound like a cabling interference issue.
Re: eht1 port shuts down
I have had exactly the same problem with an RB750, and a pair of RB751s. I do not use PoE injectors but use the external power supply.
Re: eht1 port shuts down
What external power supply are you using?I have had exactly the same problem with an RB750, and a pair of RB751s. I do not use PoE injectors but use the external power supply.
I have been running a test for a couple years now, monitoring grid tie voltage vs output of an unregulated power supply. This is a 12v 1A unregulated wall wart connected to a RB433AH. I have verified the voltage reading is correct within one tenth of a volt with my meter. This is the last day's report from a three day run.
If this is 12 volt unregulated, then multiply those readings by 2 for a 24v unregulated supply. Bear in mind the maximum input voltage to those devices is 28vdc. How many of those readings would be over 28v?Daily voltage report for test on aug/10/2012
23:00 = 14.7 Line voltage = 124
22:00 = 14.4 Line voltage = 122
21:00 = 14.2 Line voltage = 120
20:00 = 13.9 Line voltage = 118
19:00 = 14.1 Line voltage = 119
18:00 = 14.0 Line voltage = 119
17:00 = 13.9 Line voltage = 118
16:00 = 14.1 Line voltage = 119
15:00 = 14.1 Line voltage = 119
14:00 = 13.9 Line voltage = 118
13:00 = 14.0 Line voltage = 119
12:00 = 14.4 Line voltage = 122
11:00 = 14.0 Line voltage = 119
10:00 = 14.4 Line voltage = 122
09:00 = 14.2 Line voltage = 120
08:00 = 14.4 Line voltage = 122
07:00 = 14.4 Line voltage = 122
06:00 = 14.6 Line voltage = 124
05:00 = 14.9 Line voltage = 126
04:00 = 14.9 Line voltage = 126
03:00 = 14.9 Line voltage = 126
02:00 = 14.8 Line voltage = 125
01:00 = 14.9 Line voltage = 126
00:00 = 14.7 Line voltage = 124
Since voltmonitor started on 04:00:10 aug/07/2012
Maximum = 15.3v at 04:00:10 aug/08/2012
Minimum = 13.6v at 20:00:10 aug/09/2012
edit: My test is to plug in the wall wart while not connected to anything. Measure the output voltage. If it is near or above 28 volts, don't use it!
-
-
walkbyfaith
Frequent Visitor
- Posts: 80
- Joined:
Re: eht1 port shuts down
I have used the ac power supply that is used on the RB433 and got the same result. The eth1 link goes up and down and eventually I can no longer ping the RB433. We have a tool similar to the wall wart that you use SurferTim and we connected to a plug with nothing connected to it so see what the results are. There are 3 RB433 that this problem occurs on. I will post the results when I get them. Thanks again everyone for all of your help.
Re: eht1 port shuts down
You are using an 18 volt wall wart? That is what I am using. I could have sworn you are using this:
http://www.ispsupplies.com/categories/P ... -24-W.html
Isn't that a 24 volt power supply? At $6.95, I would suspect it is unregulated.
Try powering it with a 12 volt unregulated wall wart.
http://www.ispsupplies.com/categories/P ... -24-W.html
Isn't that a 24 volt power supply? At $6.95, I would suspect it is unregulated.
Try powering it with a 12 volt unregulated wall wart.
-
-
walkbyfaith
Frequent Visitor
- Posts: 80
- Joined:
Re: eht1 port shuts down
SurferTim,
You are correct. I am using the 24V power supply in the link. Do you have any 12 volt unregulated power supply suggestions? Thanks again.
You are correct. I am using the 24V power supply in the link. Do you have any 12 volt unregulated power supply suggestions? Thanks again.
Re: eht1 port shuts down
If you have a DVM, you can measure the voltage at the router.
I use the PoE injector and wall wart in the links that I posted above in my first response. It is still working great. If you doubt me, the best way to check is try your router powered by a 12V 1A wall wart in the power jack, just as a test. How does it do then?
I use the PoE injector and wall wart in the links that I posted above in my first response. It is still working great. If you doubt me, the best way to check is try your router powered by a 12V 1A wall wart in the power jack, just as a test. How does it do then?
-
-
walkbyfaith
Frequent Visitor
- Posts: 80
- Joined:
Re: eht1 port shuts down
SurferTIm,
Just so I get the hardware correct.
This link is to the wall wart, correct?
http://www.titanwirelessonline.com/Pass ... -inj-3.htm
and this is to the ac power
http://www.titanwirelessonline.com/18V- ... e-18vs.htm
And you're using these together, correct?
Also, on the RB433 logs, the eth1 link goes up and down and then the last log entry for eth1 is that it is up. I still cannot ping to the RB433 and I cannot ping from the RB433 to any other node either by URL or by IP address. Once I disable and enable the eth1 port everything works fine.
I should have the logs today from the voltage logger. THanks for all your help.
Just so I get the hardware correct.
This link is to the wall wart, correct?
http://www.titanwirelessonline.com/Pass ... -inj-3.htm
and this is to the ac power
http://www.titanwirelessonline.com/18V- ... e-18vs.htm
And you're using these together, correct?
Also, on the RB433 logs, the eth1 link goes up and down and then the last log entry for eth1 is that it is up. I still cannot ping to the RB433 and I cannot ping from the RB433 to any other node either by URL or by IP address. Once I disable and enable the eth1 port everything works fine.
I should have the logs today from the voltage logger. THanks for all your help.
Re: eht1 port shuts down
Those are the ones. The PoE injector does not come with a power supply. That web site offers a 24 volt and an 18 volt power supply for it. I use the 18 volt model because of the problems I had with 24 volt unregulated supplies.