Power-Cycle-Ping-Address turns Red, I do not have any PoE on all Interfaces, this feature is New from Mikrotik, which Address I must add to turn off the Red Text ??
Another bug?
2015-11-09 16-56-23 Š”ŠŗŃŠøŠ½ŃŠ¾Ń ŃŠŗŃŠ°Š½Š°.png
Why does it reboot my PoE device while itās online?
And what about āgrace periodā to NOT reboot while device is starting just after power cycle and before it become ready to ping reply?
PeterDoBrasil - You should try with 6.33 version.
Poe board starts to power-cycle interface if Host doesnāt respond to PING or ARP-ping, can you please try ping manualy with both methods on 6.33 version ?
And āgrace periodā can be set with āpower-cycle-ping-timeoutā parameter
Hello,
I confirm this bug with ROS 6.33 on two devices - PowerBOX and 951Ui-2HnD. Also with ROS 6.34rc5 on 951Ui-2HnD. When you add an ethernet port to bridge or make it Switch slave, then Power Cycle Host Alive is never on. If you leave the port stand alone (not in bridge or switch slave) then it works as expected.
Best regards
Thanks for reporting, I just reproduced this bug. We will try to fix this soon.
I can confirm, all my ports are bridged together, ROS v6.33.1 on RB750UP.
Can ping IP manually, but Power-Cycle-Ping ignores this fact and reboots connected/powered device.
At the moment fix for this bug is available in our RC version, and also will be included in the next bugfix version.
Iāve upgraded bridging RB750UP to 6.33.2, Power-Cycle-Ping is fixed ā THANKS MT!
I wonder how often powered devices are pinged? Power Cycle Ping Timeout value?
What if my device starts to reply ping in 5-10-15 minutes after powered on (f.e. Cambium heater applied when cold weather), but I want to ping test it every 2-3 minutes?
What is the Power Cycle Ping Timeout minimum value? āGrace periodā for certain powered device or more I think?
If the power-cycle-ping is enabled, PSE (PoE out device) will send ping every 10 s. This interval is not changeable. In your case when " device starts to reply ping in 5-10-15 minutes", you should use power-cycle-ping-timeout period greater than 15m.
power-cycle-ping-timeout value range is from 0s to 1h.
I need to Get some into on this one.
Please confirm my Suspicions 
- Power Cycle Pings a Host, but ONLY on the interface it is enabled for, correct?
- it WILL NOT currently ping any routable devices on other interfaces
- This is basically useless if you wish to monitor a device on the other side of a VLAN/PPPoE Session.
Feature Request - make the Power Cycle ping ping on any interface - or at least give us the option to choose either
an interface
checkbox for this interface only
or both.
This may run as intended, but not currently as it should. Currently VLAN is very helpful for my backhaul networks as it also allows me to run a Hotspot from the core, i could go the other way and run the HS over a VLAN, but this means that if anyone does happen to get into my Backhaul, they have access (highly unlikely - but possible), with the HS on the main LAN, adds a layer of authentication. Currently have one device i am trying to patch temporarily, until i can get up to replace - would prefer to not reboot entire router every time, and as the eternet port has no network on it at all - kinda not cool (and having to passthrough on the HS is a dick move)
What ever happened with this bug?
I have a PowerBox Pro with v6.41.1 and it refuses to power-cycle any POE interface, and power-cycle ping does no action whatsoever, as if it is configured incorrectly. It is running from solar + 24V battery, usually about 26V supply.
Can anyone advise?
Still seeing this as a bug no matter what the setting of Force On or Auto On. Mikrotik any fix planned?
I have the same problem, power cyrcle does not work on PowerBox Pro with v6.42.3.
Is it bug?
Yes itās a bug !
Have same problem.
If your pinged IP is not on interface, like on vlan management.
I can confirm on CRS328, both 6.43.16 and 6.44.3 still have this bug (with the shiny new recommended hw-offloaded bridge VLAN setup). Normal ping from command line to the same IP addresses works just fine, but power-cycle-ping reboots the devices periodically as if there was never any response. ARP table shows as if the pings were sent from bridge itself (untagged) instead of the proper tagged VLAN on the bridge. If power-cycle-ping is actually ARP ping (not ICMP), please allow specifying the interface in addition to IP address.
Ticket#2019070322006731
NetPower 16p, RB750Pr2 (powerBox), firmware 6.45.9 still not working!!!. Ping works, but the device on the port is restarting. Will it ever work! ??