ether1-poe-in-long-cable went away?

RouterOS General
1

I just got in a shipment of PowerBox Pros to replace the PowerBoxes on several of my towers.

I exported the config on one of the original PowerBoxes, and tried importing it into the PowerBox Pro. It puked on this sequence:
/interface ethernet poe settings
set ether1-poe-in-long-cable=yesHere’s what the CLI offers for options on the PowerBox:
[admin@SK.GABB] /interface ethernet poe> ?

.. – go up to ethernet
edit –
export – Print or save an export script that can be used to restore configuration
find – Find items by value
get – Gets value of item’s property
monitor – Monitor interface status
power-cycle –
print – Print values of item properties
set – Change item properties
settings –
unset --Here’s what it offers for options on the PowerBox Pro:
[admin@MikroTik] /interface ethernet poe> ?

.. – go up to ethernet
edit –
export – Print or save an export script that can be used to restore configuration
find – Find items by value
get – Gets value of item’s property
monitor – Monitor interface status
power-cycle –
print – Print values of item properties
set – Change item properties
unset --Both devices are running precisely the same release (6.38.7). I can’t find anything about this issue in release notes, hardware notes for the new device, or the wiki.

My problem is, I don’t want to prep all these boxes, then go out to set them up on the towers and discover they don’t work because this setting isn’t active. I’ve done that dance before and it wasn’t pleasant.

Do I not have to worry about this setting on the new devices anymore, or what? Is the old limitation removed by the new 802.3at/af support on the Pros?

2

I just stumbled upon this problem too. is the /interface ethernet poe settings set ether1-poe-in-long-cable=yes command not necessary now? did the powerbox worked well to you?

3

Apparently, the new gigabit-capable units of this type are also 802.3af capable, and whatever changes were made to the POE-in circuitry removed the “long cable input” limitation. Unfortunately, scripts written for one PowerBox variant now won’t work for the other without the addition or removal of that particular script line.

My first OmniTik POE ac unit will arrive tomorrow, and I fully expect the same behavior from it in this regard.

4

I’m interested too in this topic. I plan to buy powerbox pro, And I wanna be sure it be able to powerup the other devices.

I’m using linkedpro cat 5e cable 80 ft, and need to power 1 mantbox, 1 basebox and 1 sxt 5.

previously, i tried with powerbox and omnitik 5 poe and I don’t have sucess working.

5

I purchased 20 PowerBox Pro’s and on my taller towers I am having problems with POE output on them when I get above 2 ports powered by the box.

Why has Mikrotik not commented on this?

6

Sorry, I didn’t see this earlier…

I have verified that if you are going to power multiple higher-current devices from a PowerBox Pro, it’s best to supply the current to the PBP over the barrel plug and not via POE to port 1. I had a PBP that was powering four devices from power supplied to port 1, and after a year or so the last device started to get powered down by the PBP. I replaced the POE-in with 24VDC supplied over thick “parking deck” cable directly to the barrel connector, and the PBP is now happy as a clam.

The PBP has a per-port power-out limitation and a total power-out limitation that is well described in the literature, so make sure you are staying within this. If you are using POE-in, sometimes your CAT-5 cable simply can’t carry the max current that your PBP would otherwise be willing to ship out.