Received our first UPA a couple days ago. It took a while to get started, and we found some issues that really ought to be resolved (hopefully in software!); here are our observations:

Netinstall

• Unlike the RB750UP, holding down the OmniTik UPA's reset button does not cause any of the LEDs to light up or go out, so I had to guess how long to hold it down before releasing it. On the 750UP, you hold it down ~10 seconds until the "ACT" LED starts blinking, continue holding it down another ~15 seconds until it stops blinking, then release it. So I held down the button on the UPA for ~30 seconds before it would go to netinstall. Once there, it behaved as expected.
• The remainder of the observations apply to ROS 5.14.

LEDs

• The correct LED blinks to show activity when a device is plugged in, but a different LED lights up red when PoE is in use. (PoE on Ether2 blinks LED#2, but turns LED#5 red; PoE on Ether3 blinks LED#3, but turns LED#4 red; etc.)
• LEDs often remain red even when the corresponding device is disconnected from the UPA--even after rebooting the UPA!

PoE

• Upon first boot, all the Ethernet ports had PoE-out disabled. But whether I set them to auto-on or forced-on, I couldn't get them to power any of the RBs in my lab. Only after I rebooted the UPA (after upgrading the boot firmware from 2.37 to 2.38, if that makes a difference), did the ports start supplying PoE.
• Hot-plugging a device into Ether2 or Ether3 will cycle power to the devices in Ether4 and Ether5, regardless of their types.

SXT

• Our newly-delivered SXTs experience multiple "false starts" powering up when connected via Ether4 or Ether5, regardless of what (if anything) is powered via Ether2 and Ether3.
• Our RB711-2HnDs do not have this problem when plugged into any port. And it isn't a matter of load: With the same four devices (two SXTs & two 711-2HnDs) plugged into different ports, the SXTs in Ether2 and Ether3 start up fine, as do the 711-2HnDs in Ether4 and Ether5.
• Could be related to the power-cycling behavior of Ether4 and Ether5 noted above.

Winbox & Command

• /interface ethernet export does not include poe-out states.
• Upon reboot, Winbox indicates that all five Ether ports have PoE disabled, regardless of their actual states.
• PoE cannot be turned off--neither via winbox nor the command interface.
• As a suggestion, when PoE is set to auto, it would be helpful to have an indication as to whether PoE is actually being used on that port.

Please contact support with the supout.rif file from this device, we will check if this is software or hardware related. I am sorry you had such experience with your first device.

Please contact support with the supout.rif file from this device, we will check if this is software or hardware related. I am sorry you had such experience with your first device.

I just sent it. FWIW once everything is plugged in and stable, power and connectivity are consistent thus far.

We have the same problems

problems here:
1) a sextant plugged in port 2 is not getting power anymore, even rebooting omnitik
2) !!!!! omnitik ethernet negotiates only 10mbit !!!!!!!!

setup:

sextant --- omnitik --- rb751 --- omnitik --- sextant

of course omnitik models are with poe out and 751 is not, so we are using 3 power supplies here. 10mbit makes all this 802.11n useless, please fix this!!

need supout?

Please contact support with the supout.rif file from this device, we will check if this is software or hardware related. I am sorry you had such experience with your first device.

Ticket#2012041266000486

We have the same problems.

5.15 - the problem is not solved

I had the same problem originally with my new Omnitik UPA, with PoE out not working at all, despite rebooting.

As the OP suggested, upgrading the RouterBoard firmware to 2.38 fixes the PoE out issue, and it's now powering a Bullet 2HP happily (finally!)

Exact same problems as described here also.

Has anyone found a fix?

Any idea when there will be an update to fix these?

Frustrating to buy something for a specific application then have it not work when you put it in the field.

Anybody already know what this red led is all about?
Indeed very frustrating when you buy something and it start behaving weird and there is no proper manual!

Anybody already know what this red led is all about?

A red LED signifies that a port is being used to supply PoE. The only problem is, the wrong LED lights up red! #2 and #5 are interchanged, and #3 and #4 are interchanged.

Suppose you plug only one device into the RB750UP; for example, an RB411 into ether2. LED #2 will light up green to indicate port activity, and LED #5 will light up red to indicate that PoE is being provided (via ether2). After you experiment with it a bit, it will make sense. But I do hope they come up with a fix for it--preferably at the firmware/driver level rather than in hardware.

So this is an issue already around for a while and MT did not even respond to it?
I'll open a ticket for that, wake these guys up a bit....

Anybody already know what this red led is all about?

A red LED signifies that a port is being used to supply PoE. The only problem is, the wrong LED lights up red! #2 and #5 are interchanged, and #3 and #4 are interchanged.

Suppose you plug only one device into the RB750UP; for example, an RB411 into ether2. LED #2 will light up green to indicate port activity, and LED #5 will light up red to indicate that PoE is being provided (via ether2). After you experiment with it a bit, it will make sense. But I do hope they come up with a fix for it--preferably at the firmware/driver level rather than in hardware.

RB750UP LEDs are fine. OmniTIK UPA power out LEDs are reversed, just like you described.

Anybody already know what this red led is all about?

A red LED signifies that a port is being used to supply PoE. The only problem is, the wrong LED lights up red! #2 and #5 are interchanged, and #3 and #4 are interchanged.

Suppose you plug only one device into the RB750UP; for example, an RB411 into ether2. LED #2 will light up green to indicate port activity, and LED #5 will light up red to indicate that PoE is being provided (via ether2). After you experiment with it a bit, it will make sense. But I do hope they come up with a fix for it--preferably at the firmware/driver level rather than in hardware.

RB750UP LEDs are fine. OmniTIK UPA power out LEDs are reversed, just like you described.

Is this going to fixed or do we just have to live with it? Is it going to be mentioned in the manual?
The manual doesn't even speak about a red light! So, like me, most users seeing this for the fist time are worried about it. If you don't know you might think the unit malfunctions!

We have updated the "Quick Guide" documents as per your suggestion

How many concurrent connections can the Omnitik handle?

RB750UP LEDs are fine. OmniTIK UPA power out LEDs are reversed, just like you described.

Is this going to fixed or do we just have to live with it? Is it going to be mentioned in the manual? The manual doesn't even speak about a red light! So, like me, most users seeing this for the fist time are worried about it. If you don't know you might think the unit malfunctions!

We have updated the "Quick Guide" documents as per your suggestion

But... is the fact that the power-indication lights are reversed on the OmniTik UPA going to be fixed? If so, will the fix apply to existing units (e.g., via firmware), or will only newly-manufactured units be corrected?

LED order on Omnitik UPA-5HnD cannot be fixed. That is a hardware problem and LEDs are actually wired through PCB in wrong order. Only "workaround" for this is when PoE controller firmware will be capable of showing port PoE out actual state in /interface ethernet print, so that LEDs can be ignored completely. However that feature is not ready yet.

LED order on Omnitik UPA-5HnD cannot be fixed. That is a hardware problem and LEDs are actually wired through PCB in wrong order. Only "workaround" for this is when PoE controller firmware will be capable of showing port PoE out actual state in /interface ethernet print, so that LEDs can be ignored completely. However that feature is not ready yet.

It could be fixed in firmware if each red LED could be configured in ROS to indicate PoE for any given port; then the owners of reverse-LED OmniTiks could just (re)configure them accordingly.

A visual indication of status that does not require additional equipment is useful. Just because Winbox is able to show the status, does not make the LED output worthless; otherwise there would be no reason to have the green LEDs either.

This also begs the question: will there be a hardware revision in which the LEDs are wired correctly?

It could be fixed in firmware if each red LED could be configured in ROS to indicate PoE for any given port; then the owners of reverse-LED OmniTiks could just (re)configure them accordingly.

if it could be fixed it would have been fixed already. Me saying it cannot mean just that.

A visual indication of status that does not require additional equipment is useful. Just because Winbox is able to show the status, does not make the LED output worthless; otherwise there would be no reason to have the green LEDs either.

it is very useful if device is on the table, later on when it is installed outdoors - it is not that handy any more, is it?

This also begs the question: will there be a hardware revision in which the LEDs are wired correctly?

you have to ask sales.

It could be fixed in firmware if each red LED could be configured in ROS to indicate PoE for any given port; then the owners of reverse-LED OmniTiks could just (re)configure them accordingly.

if it could be fixed it would have been fixed already. Me saying it cannot mean just that.

So the line to the power-indication LED must be wired directly to the power circuitry, then. I was hoping it was via a driver, as the green indicators are handled.

it is very useful if device is on the table, later on when it is installed outdoors - it is not that handy any more, is it?

Most of my outdoor work is on buildings just 2-4 stories up. During installation/maintenance, it's still helpful to know that the devices connected to it are powered and active before climbing back down, without having to bring up a laptop.

true, that is why it is considered to be an issue that has to be fixed in future. In the mean time, you will have to remember the led order.

on the other hand it is possible to change default configuration to this:

ros code

/system leds
set 0 disabled=no interface=ether1 leds=led1 type=interface-activity
add disabled=no interface=ether5 leds=led2 type=interface-activity
add disabled=no interface=ether4 leds=led3 type=interface-activity
add disabled=no interface=ether3 leds=led4 type=interface-activity
add disabled=no interface=ether2 leds=led5 type=interface-activity

this will match greed led activity with red led poe-out indicator.

Considering testing some Omnitik UPA. Other than the LED issue, have the other issues from the original post been addressed with firmware? It appears that many things were changed in 5.20.

there definitely should be improvement. But still consider that physics cannot be cheated. Taking that into consideration - most problems that where noted have been addressed and can be attempted to be worked around.

I picked up an Omnitik UPA, it's upgraded to latest 5.20 w/ 2.41 firmware. The command to monitor power output isn't working, it just shows no output:
Which is different than what it shows in the wiki:
* http://wiki.mikrotik.com/wiki/Manual:Po ... ng_poe-out

I've also tried to monitor with each interface number instead of [find], no difference.

Do you upgrade PoE-Out firmware?

Ah, I missed that. That indeed did the trick, thanks.

Do you upgrade PoE-Out firmware?

Code: Select all

/interface ethernet poe settings upgrade

I did that twice, restart each time after and I have still poe-out version 1.0.
(Omnitik u5hnd, ROS 5.21)

Is there a file that could be uploaded and installed during restart with new poe-out version? What is the latest poe-out version I could/should have?

Now I have installed RouterOS v. 5.22, did twice the poe upgrade, restarted each time and still the poe version is 1.0. How to enable the poe-out function??

I just upgraded RB750UP to ROS 5.22 and upgraded poe-out to 2.1. I have not any issue.
Maybe try reset to default device and then upgrade poe-out. If this not help try netinstall.

Now I have installed RouterOS v. 5.22, did twice the poe upgrade, restarted each time and still the poe version is 1.0. How to enable the poe-out function??

POE out, is only on http://routerboard.com/RBOMNITIKUPA-5HnD

Omnitik UPA5HND. I have this model. So what to do if standard POE out upgrade from v1.0 does not work?

Omnitik UPA5HND. I have this model. So what to do if standard POE out upgrade from v1.0 does not work?

please clarify what doesn't work exactly

Exactly: Does not upgrade from version 1.0. therefore POE-Out function could not be set and used in any way.

As I already wrote here, I gave command to upgrade poe, confirmed "Y" and after "successfull upgrade" did restart. Then check the POE version - still 1.0. I did this several times with version 5.21 and 5.22. Nothing happen.

I have exactly the same problem with RouterOS 5.22 running on RB2011UAS. Did the POE upgrade from CLI, then rebooted and it's still stuck at version 1.0:

Is there a solution to this, I have just taken omnitik out of box and poe worked for a while until I plugged in groove2hp, then it cycled off/on.

So checked out firmware and it ver 1.

upgraded ros to v5.24

Have downloaded latest fw from web page for the poe out, stuck it into the files directory and went back to terminal >>>>int poe settings etc etc

And told it to upgrade, rebooted etc etc..

Still says ver1

I manged to see it with netinstall.

How to upgrade poe firmware from netinstall.

Any ideas,

PS I have to install it in the morning!

install 5.21, then upgrade poe firmware (now it should read 2 beta or something). Then upgrade to 5.24 and upgrade the poe fw again.

I had to do that to mine omnitik upas atleast.

Nope, not working on mine. Did exactly as suggested, a couple of times, POE just won't upgrade from 1.0

Nope, not working on mine. Did exactly as suggested, a couple of times, POE just won't upgrade from 1.0

Gerhard, the RB2011 doesn't have PoE out functionality. This upgrade is not for your router. It is only for OmniTik UPA and RB750UP

Hmm, interesting. I thought that's what the POE markings above ETH1 meant. If it doesn't have POE out, what does that POE refer to?

PoE input. You can power this board from PoE

Well, would be a good time to stop trying to POE my access point then : ). Thank you!

ps: any chance of taking a quick look at this? http://forum.mikrotik.com/viewtopic.php?f=2&t=71097

I've just buy OmniTik UPA. I was hope that led order is fixed but isn't.
After more than year you're don't fix this issue. Why?

I've just buy OmniTik UPA. I was hope that led order is fixed but isn't.
After more than year you're don't fix this issue. Why?

It is probably from the same production batch as your first one. Software can't fix it. New hardware is needed.

When will be new hardware?

Normis - please answer on my question
When will be new hardware?
Will be?

Sorry but we don't comment on unreleased product availability.

I asked when will be OmniTIK UPA-5HnD with fixed hardware (led order).
I don't ask about new product?
Will be OmniTIK UPA-5HnD with fixed hardware or not?

I asked when will be OmniTIK UPA-5HnD with fixed hardware (led order). I don't ask about new product? Will be OmniTIK UPA-5HnD with fixed hardware or not?

If they were working on a hardware revision that fixes this problem, and it were to become public knowledge, some people would delay their purchases--reducing the demand for, and value of, existing stock.

Hi There,

+1 for me re: not being able to upgrade the poe firmware from 1.0 to 2.1.

RouterOS : v5.25
Firmware : 3.07

Anyone got any solutions to this ?

POE seems very flakey.

Sometimes works sometimes does not.

Cheers
D

What is the answer to the command: ?

I have an Omnitik that also will not upgrade POE firmware from 1.0 to 2.0. What is going on... this problem has been reported over a year now and still no resolution? Not only have MTK support not fixed this problem, but they also have FAILED to provide a work around .

Also, what is the latest POE Firmware, I have some 750up that are 2.0 and some at 2.1 with the same rev of ROS.

I have an Omnitik that also will not upgrade POE firmware from 1.0 to 2.0. What is going on... this problem has been reported over a year now and still no resolution? Not only have MTK support not fixed this problem, but they also have FAILED to provide a work around .

Also, what is the latest POE Firmware, I have some 750up that are 2.0 and some at 2.1 with the same rev of ROS.

Try this it worked for me.

http://wiki.mikrotik.com/wiki/Manual:Po ... leshooting

I realised that poe out works without any problems only and only if I take the non-poe out device and solder the wires on pcb myself. Of course an appropriate power adapter is necessary to power more devices.

Odesláno z mého N1 pomocí Tapatalk

I realised that poe out works without any problems only and only if I take the non-poe out device and solder the wires on pcb myself. Of course an appropriate power adapter is necessary to power more devices.

Odesláno z mého N1 pomocí Tapatalk

We also use the not POE omnitik and a soldering iron, over 100 omnitiks deployed now ...

I did a test with the POE version and also ended with the soldering irion

Small improvements are always necessary (if possible). And soldering poe-out is one of them.
I wonder, why are there such rumours about poe-out devices when every device can be poe-out right from manufacturing.

Small improvements are always necessary (if possible). And soldering poe-out is one of them.
I wonder, why are there such rumours about poe-out devices when every device can be poe-out right from manufacturing.

The ability to distribute power to other devices is good; the abilities to:

• turn power on & off remotely for individual ports;
• disable PoE for devices that are damaged by it; and
• isolate devices so that one shorted line doesn't cause a voltage drop that takes down all the other devices; all while
• maintaining product warranty

are sometimes useful too.

That said, when should we expect a detailed photo of the best way to connect the necessary pins?

Unfortunatelly, simple stupid wire soldering would not provide the ability to control the poe on ports. Anyway, I would appreciate also such device that would provide full control on powering the ports. Hope that Mirkotikls will work on it and provide such devices to us.

That said, when should we expect a detailed photo of the best way to connect the necessary pins?

Of course this is not the best way, but it works:

Small improvements are always necessary (if possible). And soldering poe-out is one of them.
I wonder, why are there such rumours about poe-out devices when every device can be poe-out right from manufacturing.

The ability to distribute power to other devices is good; the abilities to:

• turn power on & off remotely for individual ports;
• disable PoE for devices that are damaged by it; and
• isolate devices so that one shorted line doesn't cause a voltage drop that takes down all the other devices; all while
• maintaining product warranty

are sometimes useful too.

http://forum.mikrotik.com/viewtopic.php ... 78#p408078
Its nice when an Omnitik can all do this, but sometimes it is the omnitik itself that needs a powercycle. Off course this would also count for a rb750UP but usually the omnitik plays a more important role in a network than a rb750UP would. An omnitik usually sits in top of a mast or tower where the 750 can be in a more reachable position. An Omnitik in need of a power cycle because it crashed or stalled would be more a network nightmare (since it probably has wireless clients associated, access-list, wireless settings etc.) than a simple remote powercycle of a rb750UP. I use these 750's only to power devices and pass traffic to them. No wireless, no client lists etc. If the 750 has gone, its simple to replace, even a basic configured unit can be used. Where the omnitik most probably needs a full mirror config from the one it has to replace. (Who is actually keeping a fully up-to-date backup copy of each AP to use in case of an emergency.... ? I thougth so.)
I'll bet, in most network setups, a malfuncioning Omnitik is more a distaster than a malfunctioning 750. And the latter is probably faster to replace too.

I usually use a separate backhaul antenna to connect uplink and than the AP's and other units. If now the omnitik would supply power to the backhaul antenna, and the omnitik develops a problem, my backhaul probably is also going down and I need to go to the tower myself to do a power cycle. Not a desirable option....
In using a 750UP performing the power supply the change a malfuntioning omnitik bringing down the link towards that tower is gone. As long as the rb750 is up I can still remote power cycle the Omnitik and any other units. I can even have a fully automated powercycle script to manage the backhaul unit! (You can't have a script make the omnitik powercycle itself. Thats impossible. It just switches itself off. Total disaster!)
And because the 750UP has simpler tasks to perform the change it goes down is also smaller. (What about interferences or 'radio attacks' on the omnitik to disrupt it? The rb750 has no problems with that.)

Second big advantage of using a 750UP over an Omnitik for a 'do-it-all' solution; - Dual power input.... Use both the power plug and the PoE-in port for power supply. Use one as main and the other with an emergency backup powersource, and the change the 750UP goes down due a power supply issue is 50% less thant the single power intake option of the omnitik.

The use of a rb750UP (or better rb780UP with better voltage and overall consumption monitoring) would make it a much more versatile device than the omnitik for the same purpose...

That said, when should we expect a detailed photo of the best way to connect the necessary pins?

Of course this is not the best way, but it works:

IMG_0501_cr_res.jpg

There are much simpler solutions .....

I know that. But I think that shorter way is better way.

Sent from Android by Tapatalk.

Hello all

Id like to ask you for help. I bought new Omnitik UPA-5HnD and POE out is not working too. There is poe firmware 2.13

I wanted to connect to one port SXT 5Ghz but power was not working. There I hear any sound from device as electronic fuse. But SXT consume about 2-3W less then 500mA.

BUT if I connect to same port for example RB911Ui-2HnD is was working and behind this RB951 to port 5 - STX its working too.
It means RB951 + STX connected to one port to OmniTIK is working , but alone SXT not.

There must be any construction problem, problem of detection device...

Do you have any tip what to try?

Thanks Jiri

What happens if you set power manual on ?

Hello

Nothink. Still the same sound from device. Auto, Force nothink help.

Sometime help if I a lot time disconnect cable to SXT in very short time, device starting. But after reboot omnitik the same problem

Im going to send it back to distributor.

I could recommend to manufacturer to stop sale this devices. Development of MK must solve this issue.

Jiri

Small update to my soldering poe. I have found that most of my wires soledered on ethernet ports are not necessary. The ground is already connected and the two positive wires of each port are also connected between. So only such simple connection is necessary:

interesting stuff, would this also work with an RB4xx series board?

interesting stuff, would this also work with an RB4xx series board?

i use it for the 493 series ...