Difference between revisions of "Manual:PoE-Out"

From MikroTik Wiki
Jump to: navigation, search
(How it works)
 
(15 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 +
{{Versions | v6.0 +}}
 +
{{Warning|This manual is moved to https://help.mikrotik.com/docs/display/ROS/PoE-Out}}
 
==Summary==
 
==Summary==
 +
<p id="shbox">
 +
<b>Sub-menu:</b> <code>/interface ethernet poe</code><br/>
 +
</p>
  
this page describes how poe-out feature can be used on  ''[http://routerboard.com/RB750UP RB750UP]'' and ''[http://routerboard.com/RBOMNITIKUPA5HnD OmniTik UPA-5HnD]''.  These routers  provided power only over the spare pairs.
 
  
This feature will become available on new device featuring  [[SwOS]] interface that will also provide power only over spare pairs. It will use new PoE-out controller firmware.
+
This page describes how PoE-Out ([https://en.wikipedia.org/wiki/Power_over_Ethernet Power over Ethernet]) feature can be used on MikroTik devices with at least one PoE-Out interface. MikroTik uses
 +
RJ45 mode B pinout for power distribution over [https://en.wikipedia.org/wiki/Power_over_Ethernet#Pinouts spare pairs], where the PoE is passed trough pins 4,5 (+) and 7,8 (-). If a device supports powering other devices using PoE-out, then it is recommended to use '''at least 18V''' as the input voltage, except for devices that support multiple output voltages (e.g. CRS328-24P-4S+, CRS112-8P-4S).
  
{{warning|When updated to newer PoE-Out controller firmware version it is not possible to downgrade it}}
+
==MikroTik supported PoE-Out standards==
  
{{Note| RouterOS is scapable to work with 1.x and 2.x firmware releases}}
+
MikroTik devices can support some or all of the following PoE standards:
  
==Configuration==
+
*'''Passive PoE-Out up to 30 V''' - PoE standard, which does not require negotiation between PSE (Power Sourcing Equipment) and PD (Powered Device). For PoE-out uses the same voltage as supplied to the PSE (Power Sourcing Equipment). PoE-Out Standard for devices which supports input voltage up to 30 V. PD resistance on spare pairs should have range from 3kΩ to 26.5kΩ. (e.g. [https://mikrotik.com/product/RB750UPr2 hEX PoE lite], [https://mikrotik.com/product/RB3011UiAS-RM RB3011UiAS-RM], [https://mikrotik.com/product/RB2011iL-IN RB2011iL-IN].)
 +
 
 +
*'''Passive PoE-Out up to 57 V''' - Works same as low voltage (up to 30 V) PoE-Out, but is also capable to deliver high voltage over PoE ports. The output voltage depends from the power source connected to PSE. Can power up af/at compatible devices, which accepts power over 4,5 (+) and 7,8 (-), and does not require PoE negotiation. PD resistance on spare pairs should have range from 3kΩ to 26.5kΩ. (e.g. [https://mikrotik.com/product/cap_ac cAP ac], [https://mikrotik.com/product/RB962UiGS-5HacT2HnT hAP ac], [https://mikrotik.com/product/wsap_ac_lite wsAP ac lite].)
 +
 
 +
*'''IEEE Standards 802.3af/at''' - Also called PoE Type 1/PoE+ Type 2, are PoE standards Defined by the IEEE. The aim of these standards is to reduce incompatibility between vendors. MikroTik PSE with af/at support is capable of powering both a Type 1 and a Type 2 PD. Valid PD should have PoE-In resistance from 23.75kΩ to 26.25kΩ. MikroTik devices which support af/at standard can also switch to Passive PoE-Out mode. (e.g. [https://mikrotik.com/product/RB960PGS hEX PoE], [https://mikrotik.com/product/crs112_8p_4s_in CRS112-8P-4S-IN], [https://mikrotik.com/product/crs328_24p_4s_rm CRS328-24P-4S+RM].)
 +
 
 +
Each PoE-Out implementation supports overload and short-circuit detection.
 +
 
 +
{{Note| Some MikroTik devices support all of the described standards (e.g. hEX PoE, PowerBOX Pro, CRS112-8P-4S-IN etc...) }}
 +
 
 +
==PoE-Out Configuration==
 +
 
 +
PoE Configuration is supported on all MikroTik devices with PoE-Out interfaces, the configurations can be edited from the RouterOS and SwOS interfaces.
  
 
===RouterOS===
 
===RouterOS===
====Global settings====
 
Global PoE settings (affects all ports) can be configured in ''/interface ethernet poe settings'' menu.
 
  
{| cellpadding="2"
+
====Usage====
!width="300px" style="background:#cccccc; border-bottom:1px solid gray;"| Property
+
 
!width="450px" style="background:#cccccc; border-bottom:1px solid gray;"| Desciption
+
RouterOS provides an option to configure PoE-Out over Winbox, Webfig and CLI, basic commands using the CLI are
|-
+
 
|style="border-bottom:1px solid gray;" valign="top"|'''version'''
+
{{Mr-arg-table-h
|style="border-bottom:1px solid gray;" valign="top"|version of PoE controller firmware. It is independent of RouterOS and bootloader version.  
+
|prop=Property
|-
+
|desc=Description
|style="border-bottom:1px solid gray;" valign="top"|'''ether1-poe-in-long-cable''' (<em>default: ''no''</em>)
+
}}
|style="border-bottom:1px solid gray;" valign="top"|setting to yes will disable short detection on all poe-out ports to enable use of longer ethernet cables. This is potentially dangerous settings and should be used with caution.
+
 
|}
+
{{Mr-arg-ro-table
 +
|arg=print
 +
|type=
 +
|desc=Prints PoE-Out related settings.
 +
}}
 +
 
 +
{{Mr-arg-ro-table
 +
|arg=export
 +
|type=
 +
|desc=export is displayed under <code>/interface ethernet</code> menu.
 +
}}
  
{{Note| Global setting of '''''ether1-poe-in-long-cable''''' is for PoE-in on ether1 interface on the router. Cable length that is used to power the router is important}}
+
{{Mr-arg-ro-table
 +
|arg=monitor
 +
|type=string{{!}} interface
 +
|desc=Shows poe-out-status of a specified port, or all ports with <code>/interface ethernet poe monitor [find]</code> command.
 +
}}
  
====Port settings====
+
{{Mr-arg-table-end
PoE Out can be configured in [[M:Interface/Ethernet | <code>/interface ethernet poe</code>]] menu. Each port can be controlled independently.
+
|arg=power-cycle
 +
|type=time:0..1m {{!}}
 +
|default=5s
 +
|desc=Disables PoE-Out power for a specified period of time.
 +
}}
  
Power on 100MBps interface is provided over spare pairs (blue and brown) where blue pair carries positive and brown - negative.
+
====Global Settings====
  
Starting from RouterOS 6.10 these configuration options are available:
+
Some MikroTik PoE-Out devices support global PoE setting which can be configured under <code>/interface ethernet poe settings</code> menu.
 +
Global setting ether1-poe-in-long-cable feature disables strict input/output current monitoring (short detection) to allow the use of PoE-Out with long ethernet cables and/or avoiding improper short-circuit detection.
  
{| cellpadding="2"
+
{{Mr-arg-table-h
!width="300px" style="background:#cccccc; border-bottom:1px solid gray;"| Property
+
|prop=Property
!width="450px" style="background:#cccccc; border-bottom:1px solid gray;"| Desciption
+
|desc=Description
|-
+
}}
|style="border-bottom:1px solid gray;" valign="top"|'''poe-out''' (<em>default: auto-on</em>)
 
|style="border-bottom:1px solid gray;" valign="top"|
 
*'''''auto-on''''' - board will attempt to detect if power can be applied on the port. For power-on to happen there should be resistance on spare pairs in range from 3kΩ to 26.5kΩ.  It is the default setting;
 
*'''''forced-on''''' - detection range is removed. As a result power over Ethernet will be always on;
 
*'''''off''''' - all detection and power is turned off for this port.
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''poe-priority''' (<em>0&nbsp;..&nbsp;99, default: ''10''</em>)
 
|style="border-bottom:1px solid gray;" valign="top"|set port priority regarding other PoE-Out ports. Highest priority is 0, lowest priority is 99. If there are 2 or more ports with similar priority then port with smallest port number will have higher priority. For example, if ether2 and ether3 are of same priority and over-current is detected then PoE-Out on ether3 will be turned off.  Every 6 seconds ports will be checked for possibility to provide PoE-Out if it was turned off due to port priority.
 
|}
 
  
 +
{{Mr-arg-ro-table-end
 +
|arg=ether1-poe-in-long-cable
 +
|type=yes {{!}} no
 +
|default=no
 +
|desc=Setting it to "yes" will disable short detection on all poe-out ports. This is potentially dangerous settings and should be used with caution
 +
}}
  
====Power-cycle====
+
{{Note| Global setting of '''''ether1-poe-in-long-cable''''' can also affect PoE-Out behaviour on PSE which is powered using a DC connector}}
  
In RouterOS poe-out has power-cycle-ping feature, which pings a host and power-cycles poe-out port, if this host does not respond. Power-cycle-ping settings can be changed in /interface ethernet poe set command.
+
====Port Settings====
  
 +
<p>PoE-Out can be configured under <code>/interface ethernet poe</code> menu. Each port can be controlled independently.</p>
  
{| cellpadding="2"
 
!width="300px" style="background:#cccccc; border-bottom:1px solid gray;"| Property
 
!width="450px" style="background:#cccccc; border-bottom:1px solid gray;"| Desciption
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''power-cycle-ping-enabled''' (<em>default: auto-on</em>)
 
|style="border-bottom:1px solid gray;" valign="top"|Enables ping watchdog, power-cycle port if it does not respond.
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''power-cycle-ping-address''' (<em> IPv4 | IPv6 | MAC </em>)
 
|style="border-bottom:1px solid gray;" valign="top"|Address to ping (icmp for IPv4 and IPv6, arp for IPv4, RouterOS mac-ping for MAC).
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''power-cycle-ping-timeout''' (<em> <integer> </em>)
 
|style="border-bottom:1px solid gray;" valign="top"|If ping fails for <timeout> duration, then 5s power-cycle is done.
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''power-cycle-interval''' (<em> none | <integer> </em>)
 
|style="border-bottom:1px solid gray;" valign="top"|If power is on for specified duration, then 5s power-cycle is done.
 
|}
 
  
 +
{{Mr-arg-table-h
 +
|prop=Property
 +
|desc=Description
 +
}}
  
If power-cycle is enabled, /interface ethernet poe monitor will show:
+
{{Mr-arg-ro-table
 +
|arg=name
 +
|type=
 +
|default=
 +
|desc=Name of an interface
 +
}}
  
*'''''power-cycle-host-alive (<em> yes | no </em>)''''' - shows ping status. Is not shown, if ping is disabled or not done yet.
+
{{Mr-arg-table
*'''''power-cycle-after (<em> time </em>)''''' - shows time, how much is left till next power-cycle (because of ping timeout or power-cycle-interval).
+
|arg=poe-out
 +
|type=auto-on {{!}} forced-on {{!}} off
 +
|default=auto-on
 +
|desc=Specifies PoE-Out state
 +
* <var>auto-on</var> - the board will attempt to detect if power can be applied on the port. For power-on to happen there should be resistance on spare pairs in the range from 3kΩ to 26.5kΩ
 +
* <var>forced-on</var> - detection range is removed. As a result power over Ethernet will be always on
 +
* <var>off</var> - all detection and power is turned off for this port
 +
}}
  
{{Note| '''''power-cycle-ping''''' by default uses ICMP packets to check if host is reachable, if ICMP fails, it will use ARP ping, when both fails power-cycle is applied}}
+
{{Mr-arg-table
 +
|arg=poe-priority
 +
|type=integer:0..99 {{!}} any
 +
|default=10
 +
|desc=poe-priority specifies the importance of PoE-Out ports, in cases when a total PoE-Out limit is reached, interface with the lowest port priority will be powered off first.
  
 +
Highest priority is 0, lowest priority is 99. If there are 2 or more ports with the same priority then port with the smallest port number will have a higher priority. For example, if ether2 and ether3 have the same priority and over-current is detected then PoE-Out on ether3 will be turned off.
  
{| cellpadding="2"
+
Every 6 seconds ports will be checked for a possibility to provide PoE-Out if it was turned off due to port priority.
!width="300px" style="background:#cccccc; border-bottom:1px solid gray;"| Command
+
}}
!width="450px" style="background:#cccccc; border-bottom:1px solid gray;"| Desciption
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''print'''
 
|style="border-bottom:1px solid gray;" valign="top"|prints all the properties in menu
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''export'''
 
|style="border-bottom:1px solid gray;" valign="top"|export setting of the current menu.
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''power-cycle''' (<em>0s&nbsp;..&nbsp;1m, default: ''5s''</em>)
 
|style="border-bottom:1px solid gray;" valign="top"|reset the power for specified '''duration''', to power cycle a connected device
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|'''monitor'''
 
|style="border-bottom:1px solid gray;" valign="top"| shows poe-out-status of specified port
 
|}
 
  
'''Settings in old RouterOS versions'''
+
{{Mr-arg-table-end
 +
|arg=poe-voltage
 +
|type=auto {{!}} low {{!}} high
 +
|default=auto
 +
|desc=Feature which allows to manually switch between two voltage outputs on PoE-Out ports. Will take effect only on PSE with switchable voltage modes ([https://mikrotik.com/product/crs112_8p_4s_in CRS112-8P-4S-IN], [https://mikrotik.com/product/crs328_24p_4s_rm CRS328-24P-4S+RM], [https://mikrotik.com/product/netpower_16p netPower 16P], [https://mikrotik.com/product/crs354_48p_4s_2q_rm CRS354-48P-4S+2Q+RM]).
 +
}}
  
Old firmware supported configuration features:
+
====Power-cycle settings====
  
Configuration options are:
+
RouterOS provides a possibility to monitor PD using a ping, and power-cycle a PoE-Out port when the host does not respond. power-cycle-ping feature can be enabled under <code>/interface ethernet poe</code> menu.
*'''''auto-on''''' - board will attempt to detect if power can be applied on the port. For power-on to happen there should be resistance on spare pairs in range from 3kΩ to 26.5kΩ. It is the default setting;
+
 
*'''''forced-on''''' - detection range is removed. As a result power over Ethernet will be always on;
+
{{Mr-arg-table-h
*'''''off''''' - all detection and power is turned off for this port.
+
|prop=Property
 +
|desc=Description
 +
}}
 +
 
 +
{{Mr-arg-table
 +
|arg=power-cycle-ping-enabled
 +
|type=yes {{!}} no
 +
|default=no
 +
|desc=Enables ping watchdog, power-cycles port if a host does not respond to ICMP or MAC-Telnet packets.  
 +
}}
 +
 
 +
{{Mr-arg-table
 +
|arg=power-cycle-ping-address
 +
|type=IPv4 {{!}} IPv6 {{!}} MAC
 +
|default=
 +
|desc=An address which will be monitored. Since RouterOS 6.46beta16, an active route towards PD is required in case an IP address is configured, so make sure PSE can reach the PD. In case MAC address is specified, PSE will send MAC-Telnet ping requests only from specified ethernet interface. When configuring a [[Manual:Interface/Bridge#Bridge_VLAN_Filtering | bridge vlan-filtering]] or some way of [[Manual:Basic_VLAN_switching| VLAN switching]], it is recommended to use IP address for monitoring your PD.
 +
}}
 +
 
 +
{{Mr-arg-table
 +
|arg=power-cycle-ping-timeout
 +
|type=time:0..1h {{!}}
 +
|default=5s
 +
|desc=If the host does not respond for more than <timeout> period of time, then PoE-Out port is switched off for 5s.
 +
}}
 +
 
 +
{{Mr-arg-table-end
 +
|arg=power-cycle-interval
 +
|type=time{{!}} any
 +
|default=
 +
|desc=Disables PoE-Out power for 5s between specified interval. Not related with power-cycle-ping feature.
 +
}}
 +
 
 +
 
 +
If power-cycle is enabled, <code>/interface ethernet poe monitor</code> will show actual status of the host and time when power cycle will be performed [https://wiki.mikrotik.com/wiki/Manual:PoE-Out#PoE-Out_Monitoring]
  
 
===SwOS===
 
===SwOS===
  
PoE Out feature configuration will be available from [[SwOS#Link_Tab | SwOS Link]] page where one of PoE Out profiles can be for each PoE Out enabled port individually:
+
SwOS interface provides basic PoE-Out configuration options:
  
*'''''auto''''' - detection is done regarding resistance on the spare pairs to check if port has PoE capability. For port to be turned on measured value should be within range from 3kΩ to 26.5kΩ;
+
<ul>
*'''''on''''' - PoE Out is enabled on the port regardless of the resistance on the port. Use this with caution as that can damage connected equipment;
+
<li> PoE Out - Change between [[#Port_Settings|PoE-out]] modes (auto/on/off)
*'''''off''''' - PoE Out is turned off.
+
<li> PoE Priority - Change the [[#Port_Settings|Priority]] of port (0...8)
 +
<li> Voltage Level - Change between two voltage outputs on PoE-Out ports (auto/low/high)
 +
</ul>
  
==Monitoring==
+
==PoE-Out Monitoring==
New PoE Out controller firmware enables monitoring of the PoE Out state
 
  
 
===RouterOS===
 
===RouterOS===
  
It is possible to monitor poe-out current usage in RouterOS via ''/interface ethernet poe'' menu. Monitoring currently will show power usage in watts, current load in amperes and supplied voltage.
+
MikroTik devices with PoE-Out controller (not injector) provides port monitoring option. <code>/interface ethernet poe monitor [find]</code>
 +
 
 +
{{Mr-arg-table-h
 +
|prop=Property
 +
|desc=Description
 +
}}
 +
 
 +
{{Mr-arg-ro-table
 +
|arg=name
 +
|type=
 +
|default=
 +
|desc=Name of an interface
 +
}}
 +
 
 +
{{Mr-arg-ro-table
 +
|arg=poe-out
 +
|type=
 +
|default=
 +
|desc=Shows PoE-Out settings
 +
}}
 +
 
 +
{{Mr-arg-ro-table
 +
|arg=poe-out-status
 +
|type=
 +
|default=
 +
|desc=Shows current PoE-Out status on port
 +
* <var>powered-on</var> - Power is applied to the port, and PoE-Out is operating normally,
 +
* <var>waiting-for-load</var> - PSE attempts to detect if power can be applied to the port. For power-on to happen there should be resistance on spare pairs in the range from 3kΩ to 26.5kΩ;
 +
* <var>short-circuit</var> - Short-circuit is detected on PoE-Out port, power is switched off, the only detection with low voltage takes place.
 +
* <var>overload</var> - The PoE-Out current limit is exceeded, power is switched off on PoE-Out port. For port limits see each model specifications.
 +
* <var>voltage-too-low</var> - PD can not be powered with voltage provided from PSE.
 +
* <var>current-too-low</var> - current-too-low means that PD draws too low current (<10mA) than normal PoE-Out device should, reason for this can be:
 +
Delivered voltage at PD is too low for normal powering (for example Vmin = >30V, but provided 24V);
 +
 
 +
PD uses second power source which has a higher voltage than PSE, so all current is taken from second DC source, not PSE PoE-Out port;
 +
* <var>off</var> - all detection and power is turned off for this port;
 +
}}
 +
 
 +
{{Mr-arg-ro-table
 +
|arg=poe-out-voltage
 +
|type=
 +
|default=
 +
|desc=Displays PoE Voltage which is applied to the PD.
 +
}}
 +
 
 +
{{Mr-arg-ro-table
 +
|arg=poe-out-current
 +
|type=
 +
|default=
 +
|desc=Displays port current (mA) which is drawn by the PD.
 +
}}
 +
 
 +
{{Mr-arg-ro-table-end
 +
|arg=poe-out-power
 +
|type=
 +
|default=
 +
|desc=Displays PD power consumption
 +
}}
 +
 
 +
If <code>power-cycle-ping</code> feature is used, <code>/interface ethernet poe monitor [find]</code> will show additional fields:
 +
<pre>
 +
power-cycle-host-alive: <YES/NO> (Shows if monitored host is reachable)
 +
power-cycle-after:<TIME> (Shows time, after which the port will be power-cycled)
 +
</pre>
 +
 
 +
===SNMP===
 +
 
 +
It is possible to monitor PoE-Out values using SNMP protocol, this requires enabled SNMP on PSE. [https://wiki.mikrotik.com/wiki/Manual:SNMP SNMP Wiki]
  
 
SNMP OID tables:
 
SNMP OID tables:
 +
<ul>
 +
<li> 1.3.6.1.4.1.14988.1.1.15.1.1.1 - interface id
 +
<li> 1.3.6.1.4.1.14988.1.1.15.1.1.2 - interface names
 +
<li> 1.3.6.1.4.1.14988.1.1.15.1.1.4 - voltage in dV (decivolt)
 +
<li> 1.3.6.1.4.1.14988.1.1.15.1.1.5 - current in mA
 +
<li> 1.3.6.1.4.1.14988.1.1.15.1.1.6 - power usage in dW (deviwatt)
 +
</ul>
  
1.3.6.1.4.1.14988.1.1.15.1.1.1 - interface id
+
SNMP values can be requested also from the RouterOS, for example, <code>snmp-walk</code> will print current mA from all available PoE-Out ports:
 +
<pre>
 +
/tool snmp-walk address=10.155.149.252 oid=1.3.6.1.4.1.14988.1.1.15.1.1.5
 +
</pre>
 +
To get very specific OID value, use <code>snmp-get</code> tool (displays current mA on ether3 interface):
 +
<pre>
 +
tool snmp-get address=10.155.149.252 oid=1.3.6.1.4.1.14988.1.1.15.1.1.5.3
 +
</pre>
  
1.3.6.1.4.1.14988.1.1.15.1.1.2 - interface names
+
===SwOS===
  
1.3.6.1.4.1.14988.1.1.15.1.1.4 - voltage in dV (decivolt)
+
A PoE-Out controller will enable certain monitoring features also from SwOS, such as PoE-Out Status, PoE-Out Current, PoE-Out Voltage and PoE-Out Power usage.  
  
1.3.6.1.4.1.14988.1.1.15.1.1.5 - current in mA
+
All PoE-Out configuration and monitoring is located on one page, under PoE tab <code>http://<IP>/index.html#poe</code>:
  
1.3.6.1.4.1.14988.1.1.15.1.1.6 - power usage in dW (deviwatt)
+
[[file:SwOS PoE.png]]
 +
 
 +
 
 +
==PoE-Out notifications==
 +
 
 +
===PoE-Out LEDs===
 +
 
 +
====Models with dependant voltage output====
 +
 
 +
PoE-Out LED behaviour can differ between models, but most of them will indicate PoE-Out state on one additional LED. Devices with one voltage output will light:
 +
 
 +
<ul>
 +
<li> Red colour LED - PoE-Out port state is '''powered-on''' (auto or forced-on mode).
 +
<li> Blinking Red colour LED - PoE-Out port state is '''short-circuit'''
 +
</ul>
 +
 
 +
====Models with selectable voltage output====
 +
 
 +
Models with multiple voltage options can indicate additional information:
 +
 
 +
<ul>
 +
<li> Green colour triangle LED - PoE-Out port state is '''powered-on''' (auto or forced-on mode), PD uses low voltage.
 +
<li> Red colour triangle LED - PoE-Out port state is '''powered-on''' (auto or forced-on mode), PD uses high voltage (af/at or passive).
 +
<li> Blinking Green colour triangle LED - PoE-Out port state is '''short-circuit''' or '''overload'''
 +
<li> Blinking Red colour triangle LED - PoE-Out port state is '''short-circuit''' or '''overload'''
 +
</ul>
 +
 
 +
====Model-specific LED behaviour====
 +
 
 +
<ul>
 +
<li> [https://mikrotik.com/product/crs112_8p_4s_in CRS112-8P-4S-IN] - All PoE LEDs flashing: wrong voltage PSU plugged into one of the ports.
 +
<li> [https://mikrotik.com/product/netpower_16p netPower 16P] -  All PoE LEDs flashing: wrong voltage PSU plugged into one of the ports.
 +
<li> [https://mikrotik.com/product/crs328_24p_4s_rm CRS328-24P-4S+RM] - indicates an exceeded overall max PoE output limit. Port PoE-Out priorities will work in 3 independent sections (8 ports each) and overload will happen in any section that breach 150W consumption.
 +
</ul>
 +
 
 +
 
 +
===PoE-Out Logs===
 +
 
 +
By default PoE-Out event [https://wiki.mikrotik.com/wiki/Manual:System/Log logging] is enabled and uses "warning" and "info" topics to notify the user about PoE-Out state changes. Log entries will be added on each PoE-Out state change. Important logs will be added with "warning" topic, informative logs will be added with "info" topic.
 +
 
 +
To avoid unnecessary logging in cases when PD is not powered because of current-too-low, RouterOS will filter such events, and add one log per every 512 current-too-low events.
 +
 
 +
Logs can be disabled if necessary:
 +
<pre>
 +
/system logging set [find topics~"info"] topics=info,!poe-out
 +
/system logging set [find topics~"warning"] topics=warning,!poe-out
 +
</pre>
 +
 
 +
===PoE-Out Warnings in GUI/CLI===
 +
 
 +
To notify a user about important PoE-Out related problems, messages will be shown in Winbox / Webig and CLI interface fields:
 +
<pre>
 +
    1  RS ;;; poe-out status: overload
 +
      ether1                              ether            1500  1588      9204 64:D1:54:61:D5:E0
 +
</pre>
 +
 
 +
Webfig and Winbox will notify user under interfaces:
 +
 
 +
[[file:WebFIG PoE WRN.png]]
  
===SwOS===
 
  
PoE Out controller with new firmware will enable certain monitoring features such as PoE Out state, current power usage and voltage supplied to the board:
 
*'''''PoE Out state''''' - will enable to see PoE Out state remotely just by logging into the board
 
*'''''Current power usage''''' - measured in Amperes will show current usage on the port
 
*'''''Supplied voltage''''' - as this value directly impacts how much power can be given to the connected devices it is important to know value that is available to the SwOS device itself.
 
  
 
==How it works==
 
==How it works==
 +
 +
 +
===PoE-Out Modes===
  
 
====auto-on mode====
 
====auto-on mode====
If ''auto-on'' is selected then port operates in this strict order:
+
 
*with low voltage it checks for resistance on the connected port. If it is detected that resistance is in range (3kΩ to 26.5kΩ) power is turned on;
+
If auto-on is selected on PoE-Out interface, then port operates in this strict order:  
* when power is given it is continuously checked if overload limit is not reached or short circuit is detected
+
 
*when cable is unplugged port returns in detection state and will remain off until suitable port that could accept PoE is detected
+
<ul>
 +
<li>PSE with low voltage checks for a resistance on the connected port. If detected resistance range is between (3kΩ to 26.5kΩ) power is turned on;
 +
<li>When power is applied, the PSE continuously checks if overload limit is not reached or short circuit detected
 +
<li>If the cable is unplugged, the port returns in detection state and will remain off until suitable PD is detected
 +
</ul>
  
 
====forced-on mode====
 
====forced-on mode====
  
If ''forced-on'' is selected then port operates in this strict order:
+
If forced-on is selected then port operates in this strict order:  
*it is checked if  resistance is in range is 0Ω to ∞Ω, so that even if cable is unplugged power will be given on the port
+
<ul>
*when power is given it is continuously checked if overload limit is not reached or short circuit is detected
+
<li>PSE disables resistance check on the port, and apply power on pins 4,5 (+) and 7,8 (-), even if no cable is attached
*when cable is unplugged port remains with power enabled on the port
+
<li>When power is applied, PSE still continuously checks if an overload or short circuit is not detected
 
+
<li>After the cable is unplugged, the power still remains enabled on the port.
 +
</ul>
  
 
====off mode====
 
====off mode====
  
If ''off'' mode is used, poe-out on the port will be turned off at all times and port on the router will behave as simple Ethernet port.
+
If off mode is used, PoE-Out on the port will be turned off, no detection will take place, and interface will behave as a simple Ethernet port.  
  
{{warning|In order to avoid malfunction, after disconnecting PoE-OUT interface you should wait up to 10 seconds before reconnecting PoE-OUT interface again}}
 
  
==Safety==
+
===PoE-Out limitations===
PoE out feature has the following safety features:
 
  
====Port eligibility detection for poe out ====
+
It is important to check PoE-Out specification to find out hardware limitations because it can differ between models
auto-on mode is considered safe, it will check if resistance on the port is within range and only then enable PoE out on the interface. The range is 3kΩ to 26.5kΩ
 
  
====Overload protection====
+
====PoE-Out port limitation====
when port is on (PoE out is enabled) port is checked for overload, If that is detected to avoid hardware damage of powered device or powering device PoE out is turned of on this port.
 
  
With new firmware after overload is detected starts 120 second countdown after what PoE Out feature will be turned on again to see if environment has changed and device connected can be supplied with power again. That is important for configurations that are not connected to mains (solar installations, equipment running on batteries due to mains failure) so that when voltage drops - overload will be detected and connected devices turned off. After a while when voltage level returns to usual operating value - connected equipment can be powered on again.
+
PoE-Out ports are limited with max amp values which are supported in particular voltage, usually max current will differ for low voltage devices (up to 30 V), and for high voltage devices (31 to 57 V).
  
{{Note| PoE-Out controller firmware version 2.0 allows 1A load on port with 2.2A of total limit on all ports}}
+
====PoE-Out total limitation====
  
====Short circuit detection====
+
PSE has also a total PoE-Out current limitation which can't be exceeded, even if individual port limit allows it.
when port is on (PoE out is enabled) port is checked for short circuit. If it is detected to ensure that there is no additional damage on powered device and no damage on powering device PoE out is turned off on all ports
 
  
==PoE Out polarity==
+
====PoE Out polarity====
By default PoE out polarity on MikroTik manufactured devices on 100MBps ports is standard
 
====Standard====
 
PoE out on RouterBOARD devices is standard - over blue pair - positive and over brown pair - negative voltage
 
  
====Reversed====
+
All MikroTik PSE uses the same PoE-Out pin polarity [https://en.wikipedia.org/wiki/Power_over_Ethernet#Pinouts Mode B] 4,5 (+) and 7,8 (-), however other vendors can use opposite or Mode A pinout on PD, this would require using a special [https://en.wikipedia.org/wiki/Power_over_Ethernet#Pinouts crossover cable].
  
Some devices use different polarity to power their devices that is reverse of the standard: over blue pair - negative and over brown pair - positive voltage
+
{{Note| Passive PD with high input inrush current can result in overcurrent protection on PSE, make sure that PD specification supports powering from PSE (not only from the passive power injector) }}
  
====Any====
+
===Safety===
Device that supports either of 2 possible polarities - standard or reversed
 
  
====Wiring====
+
PSE has following safety features:
If you want to power device that supports only reverse polarity using '[http://routerboard.com/RB750UP RB750UP]'' and ''[http://routerboard.com/RBOMNITIKUPA5HnD OmniTik UPA]'' you have to make special cable that will swap required wires, thus enabling you to power these devices.
 
  
On one end you have to have standard RJ45 T568B wiring (orange striped, orange, green striped, blue, blue striped, green, brown striped, brown) and on other and has to have blue and brown pair swapped resulting in (orange striped, orange, green striped, brown, brown striped, green, blue striped, blue)
+
====PoE-Out compatibility detection====
  
== ''[http://routerboard.com/RB750UP RB750UP]'' and ''[http://routerboard.com/RBOMNITIKUPA5HnD OmniTik UPA-5HnD]'' Powered devices==
+
The auto-on mode is considered safe, it will check if the resistance on the port is within allowed range and only then enable PoE out on the interface. The range is 3kΩ to 26.5kΩ
  
Table contain information on what devices can be powered using  ''[http://routerboard.com/RB750UP RB750UP]'' and ''[http://routerboard.com/RBOMNITIKUPA5HnD OmniTik UPA-5HnD]'' as power source for PoE. Table contains devices that are explicitly tested. Routers from same series or with modifications will also work.
+
====Overload protection====
  
Polarity: standard - blue pair positive, brown pair negative; reversed - blue pair negative , brown pair positive, any - either standard or reversed.
+
When a PoE-Out port is powered-on, it is constantly checked for overload. If overload is detected, PoE-Out is turned off on the port to avoid damage to the PD or PSE.
  
{| cellpadding="2"
+
In seconds the PoE Out feature will be turned on again to see if the environment has changed and PD can be supplied with power again. That is important for configurations that are not connected to mains (solar installations, equipment running on batteries due to mains failure) so that when voltage drops - overload will be detected and connected devices turned off. After a while when voltage level returns to usual operating value - connected equipment can be powered up again.
!width="300px" style="background:#cccccc; border-bottom:1px solid gray;"| Device
 
!width="100px" style="background:#cccccc; border-bottom:1px solid gray;"| forced-on
 
!width="100px" style="background:#cccccc; border-bottom:1px solid gray;"| auto-on
 
!width="100px" style="background:#cccccc; border-bottom:1px solid gray;"| polarity
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB433GL [http://routerboard.com/RB433GL]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|any
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB450G [http://routerboard.com/RB450G]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|any
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|OmniTik UPA-5HnD [http://routerboard.com/RBOMNITIKUPA5HnD]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|OmniTik U-5HnD [http://routerboard.com/OMN5HnD]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB711G-5HnD [http://routerboard.com/RB711G-5HnD]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|any
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB411U [http://routerboard.com/RB411U]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB800 [http://routerboard.com/RB800]
 
|style="border-bottom:1px solid gray;" valign="top"|no
 
|style="border-bottom:1px solid gray;" valign="top"|no
 
|style="border-bottom:1px solid gray;" valign="top"|any
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB450 [http://routerboard.com/RB450]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB433AH [http://routerboard.com/RB433AH]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB750 [http://routerboard.com/RB750]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB750UP [http://routerboard.com/RB750UP]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD SXT[http://routerboard.com/RBSXTG-5HnD]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB435G  [http://routerboard.com/RB435G]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|no
 
|style="border-bottom:1px solid gray;" valign="top"|any
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB493AH [http://routerboard.com/RB493AH]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB493 [http://routerboard.com/RB493]
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB532
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB153
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|RouterBOARD RB112
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Motorolla Canopy
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|reversed
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Ubiquity LOCO900
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Ubiquity Bullet M2
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Ubiquity Bullet M5
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Ubiquity NanoStation 2N
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Ubiquity NanoStation M365
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Ubiquity UniFi AP
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Ubiquity UniFi AP long range
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|yes
 
|style="border-bottom:1px solid gray;" valign="top"|standard
 
|}
 
  
==Upgrade PoE Out firmware==
+
====Short circuit detection====
  
PoE-Out controller firmware is not provided separately from RouterOS. For newer PoE-Out firmware it is required to install newer RouterOS release.
+
When power is enabled on PoE-Out port, PSE continuously checks for a short circuit. If it is detected to ensure that there is no additional damage on PD and PSE, the power is turned off on all ports. PSE will continue to check PoE-Out port until environment returns to normal.  
  
{{Note| Firmware upgrade is possible since RouterOS 5.20}}
+
{{warning| Make sure that non-standard incompatible PD which does not have the resistance range 3kΩ to 26.5kΩ are not attached, so the PSE would not try to apply power on them}}
  
{{Note| RouterOS 6.x does not have upgrade command and the upgrade/downgrade is done automatically as you are upgrading or downgrading RouterOS.}}
+
===Model-specific features===
  
Upgrade procedure is as follows:
+
PSE with independent 8-port sections ([https://mikrotik.com/product/crs112_8p_4s_in CRS112-8P-4S-IN], [https://mikrotik.com/product/crs328_24p_4s_rm CRS328-24P-4S+RM], [https://mikrotik.com/product/netpower_16p netPower 16P], [https://mikrotik.com/product/crs354_48p_4s_2q_rm CRS354-48P-4S+2Q+RM]) allows PoE-Out to work independantly from the RouterOS, this means that you can reboot/upgrade your RouterOS and the PD will not be rebooted.  
* upgrade router with newest RouterOS release.  
+
* check current firmware using ''/interface ethernet poe settings print'' command
+
==PoE Out examples==
* to upgrade issue ''/interface ethernet poe settings upgrade''  command
+
 
* when prompted with this message follow instructions as required
+
RouterOS allows to define priorities on PoE-Out ports, so if your installation is going over power budget, the PSE will disable less important PD with the lowest priority.
  Do you really want to upgrade PoE firmware? [y/n]  
 
*you have to reboot the router for changes to take place
 
Please reboot to finish PoE firmware upgrade.
 
*reboot the router
 
===Troubleshooting===
 
If for some reason POE-Out controller firmware update fails you have to follow these steps and firmware upgrade should succede:
 
* Downgrade RouterOS to 5.21
 
* Do ''/interface ethernet poe settings upgrade''
 
* Upgrade back to 5.24 and issue command again ''/interface ethernet poe settings upgrade''
 
  
This should result in newest PoE-Out controller firmware.
+
Priority of ''0'' is the highest priority, ''99'' - lowest
  
==PoE Out examples==
+
{{Note| [https://mikrotik.com/product/crs328_24p_4s_rm CRS328-24P-4S+RM], [https://mikrotik.com/product/netpower_16p netPower 16P], netPower 16P Poe-Out priorities work independently on each 8 port section! }}
PoE-Out firmware starting from 2.0 allows to set port priority. Priority of ''0'' is the highest priority there is, so if your installation is going over power budged port with the lowest priority is going to be turned off first.
 
  
===setting up priority===
+
===Setting up priority===
here is example on how priorities look
+
Example of how to set priorities from CLI:
  
setting up priorities:
+
<pre>
 
  /interface ethernet poe set ether2 poe-priority=10
 
  /interface ethernet poe set ether2 poe-priority=10
 
  /interface ethernet poe set ether3 poe-priority=13
 
  /interface ethernet poe set ether3 poe-priority=13
 
  /interface ethernet poe set ether4 poe-priority=11
 
  /interface ethernet poe set ether4 poe-priority=11
 
  /interface ethernet poe set ether5 poe-priority=14
 
  /interface ethernet poe set ether5 poe-priority=14
 +
</pre>
  
what will happen when power budget will go over set total limit - first, if over-load is detected ether5 will be turned off, then recheck is done and if still total limit over-load is detected next port in priority will be turned off, in this example, ether3 will have its poe-out turned off. Both of these ports will be reched every 6 seconds is it possible to turn poe-out on for these ports. Power up will happen in reverse order as the power was cut.
+
What will happen when power budget will go over total PoE-Out limit - first, if overload is detected, ether5 will be turned off (lowest priority), then recheck is done and if still total limit overload is detected next port in priority will be turned off, in this example, ether3 will be turned off. Both of these ports will be reached every few seconds to check if it is possible to turn PoE-Out on for these ports. Power up will happen in reverse order as the power was cut.
  
===same priority===
+
===Same priority===
 
 
if all, or some ports will have same poe-priority than port with lower port number will have higher priority
 
  
 +
if all, or some ports will have the same poe-priority, then port with the lowest port number will have higher priority
 +
<pre>
 
  /interface ethernet poe set ether2 poe-priority=10
 
  /interface ethernet poe set ether2 poe-priority=10
 
  /interface ethernet poe set ether3 poe-priority=10
 
  /interface ethernet poe set ether3 poe-priority=10
 
  /interface ethernet poe set ether4 poe-priority=10
 
  /interface ethernet poe set ether4 poe-priority=10
 
  /interface ethernet poe set ether5 poe-priority=10
 
  /interface ethernet poe set ether5 poe-priority=10
 +
</pre>
  
in this example, if over-load total limit is reached ether5 will be turned off first, then ether4 then ether3 as all of these ports have same poe priority.
+
In this example, if the total PoE-Out limit is reached ether5 will be turned off first, then ether4 then ether3 as all of these ports have same poe priority.
  
===monitoring poe-out===
+
===Monitoring PoE-Out===
  
all the monitoring of poe-out can be done via ''/interface ethernet poe monitor <interface>'' menu
+
PoE-Out ports can be monitored using a command <code>/interface ethernet poe monitor <interface></code>
  
 
  [admin@MikroTik] > interface ethernet poe monitor [find]
 
  [admin@MikroTik] > interface ethernet poe monitor [find]
Line 399: Line 450:
 
       poe-out-power: 5.1W  2.6W  1.4W  
 
       poe-out-power: 5.1W  2.6W  1.4W  
  
here RB750UP is powering up 3 devices on ports ether2, ether3 and ether4
 
  
==Changes between 1.x and 2.0 PoE-Out controller firmware==
+
===Power-cycle ping ===
 +
 
 +
Monitor connected PD with power-cycle-ping feature:
 +
 
 +
<pre>
 +
/interface ethernet poe set ether1 power-cycle-ping-enabled=yes power-cycle-ping-address=192.168.88.10 power-cycle-ping-timeout=30s
 +
</pre>
 +
 
 +
In this example, PD attached to ether1 will be continuously monitored using a power-cycle-ping feature, which will send ICMP ping requests and wait for a reply. If PD with IP address 192.168.88.10 will not respond for more than 30s, the PoE-Out port will be switched off for 5s.
 +
 
 +
==Troubleshooting==
 +
 
 +
In cases where a PD does not power-up or reboots unexpectedly when powered from your PSE, it's suggested to first check:
 +
<ul>
 +
<li>'''PD supported input voltage''' - PSE output voltage must be in the range supported by the PD. Otherwise the PD is incompatible with the PSE, and will not be able to power-up. Check the PD datasheet.
 +
<li>'''PD supported input PoE-in standard''' - Some PDs do not support af/at standard even if it has PoE-in support up to 57 V, check PD datasheet.
 +
<li>'''PD is rebooted from PSE'''
 +
        <ul>
 +
            <li>Check if PD does not exceed PoE-Out port limit and Total-PoE-Out port limit of the PSE, check PSE datasheet.
 +
            <li>Check if Voltage limit does not drop bellow supported (Can be caused by voltage drop on the wires).
 +
            <li>Check if you are using a proper power supply, the output power of PSU should be calculated from:
 +
                <pre>(MAX power consumption of PSE) + (MAX power consumption of all PD) + 10%)</pre>
 +
            <li>Check if you are using good quality ethernet cables, it's important especially in cases if PoE is used.
 +
        </ul>
 +
<li>'''Chech RouterOS version''' - it's possible, that some PoE related features will be updated with RouterOS, make sure that you are running the latest [https://mikrotik.com/download RouterOS version].
 +
<li>'''PD Does not power up'''
 +
    <ul>
 +
      <li> There can be cases where a PD does not power up, even though it supports passive PoE, and does not consume more power than the specified PSE port limit. This can be caused by inrush current triggering overcurrent protection on the PSE. Make sure that PD specification supports powering from PSE (not only from passive power injector)
 +
      <li> Polarity - Devices with opposite or different pinout can be unable to powerup from all PSE. Check PD datasheet.
 +
      <li> Incompatible resistance - PD resistance on spare pairs should have range from 3kΩ to 26.5kΩ (For Passive-PoE) and from 23.75kΩ to 26.25kΩ on af/at.
 +
    </ul>
 +
</ul>
 +
 
 +
==Legacy==
 +
 
 +
===PoE-Out Controller upgrade===
 +
 
 +
PoE-Out devices which are running RouterOS 5.x can also hold old PoE-Out controller firmware, upgrade to RouterOS 6.x will automatically update the PoE-Out firmware.
 +
Changes between 1.x and 2.x PoE-Out controller firmware will result in higher Max-port limits (0.5A to 1A) in case if it's supported by the hardware, also will provide some additional data which can be monitored, and allow to use PoE-Out priorities.
  
{| cellpadding="2"
+
All MikroTik devices which come with RouterOS 6.x already support the latest PoE-Out firmware.
!width="300px" style="background:#cccccc; border-bottom:1px solid gray;"| feature
 
!width="200px" style="background:#cccccc; border-bottom:1px solid gray;"| version 1.x
 
!width="200px" style="background:#cccccc; border-bottom:1px solid gray;"| version 2.0
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|max limit on port
 
|style="border-bottom:1px solid gray;" valign="top"|500mA
 
|style="border-bottom:1px solid gray;" valign="top"|1A
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|total limit
 
|style="border-bottom:1px solid gray;" valign="top"|2A
 
|style="border-bottom:1px solid gray;" valign="top"|2.2A
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|poe-priority
 
|style="border-bottom:1px solid gray;" valign="top"|not available
 
|style="border-bottom:1px solid gray;" valign="top"|per port priority adjustable
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|monitoring
 
|style="border-bottom:1px solid gray;" valign="top"|not available
 
|style="border-bottom:1px solid gray;" valign="top"|information about each port
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|PoE in long cable mode
 
|style="border-bottom:1px solid gray;" valign="top"|not available
 
|style="border-bottom:1px solid gray;" valign="top"|available
 
|-
 
|style="border-bottom:1px solid gray;" valign="top"|Check PoE controller FW version
 
|style="border-bottom:1px solid gray;" valign="top"|newer RouterOS
 
|style="border-bottom:1px solid gray;" valign="top"|available
 
|}
 
  
 +
==FAQ==
  
 
[[Category:Manual|PoE]]
 
[[Category:Manual|PoE]]

Latest revision as of 12:00, 3 June 2020

Version.png

Applies to RouterOS: v6.0 +

Icon-warn.png

Warning: This manual is moved to https://help.mikrotik.com/docs/display/ROS/PoE-Out


Summary

Sub-menu: /interface ethernet poe


This page describes how PoE-Out (Power over Ethernet) feature can be used on MikroTik devices with at least one PoE-Out interface. MikroTik uses RJ45 mode B pinout for power distribution over spare pairs, where the PoE is passed trough pins 4,5 (+) and 7,8 (-). If a device supports powering other devices using PoE-out, then it is recommended to use at least 18V as the input voltage, except for devices that support multiple output voltages (e.g. CRS328-24P-4S+, CRS112-8P-4S).

MikroTik supported PoE-Out standards

MikroTik devices can support some or all of the following PoE standards:

  • Passive PoE-Out up to 30 V - PoE standard, which does not require negotiation between PSE (Power Sourcing Equipment) and PD (Powered Device). For PoE-out uses the same voltage as supplied to the PSE (Power Sourcing Equipment). PoE-Out Standard for devices which supports input voltage up to 30 V. PD resistance on spare pairs should have range from 3kΩ to 26.5kΩ. (e.g. hEX PoE lite, RB3011UiAS-RM, RB2011iL-IN.)
  • Passive PoE-Out up to 57 V - Works same as low voltage (up to 30 V) PoE-Out, but is also capable to deliver high voltage over PoE ports. The output voltage depends from the power source connected to PSE. Can power up af/at compatible devices, which accepts power over 4,5 (+) and 7,8 (-), and does not require PoE negotiation. PD resistance on spare pairs should have range from 3kΩ to 26.5kΩ. (e.g. cAP ac, hAP ac, wsAP ac lite.)
  • IEEE Standards 802.3af/at - Also called PoE Type 1/PoE+ Type 2, are PoE standards Defined by the IEEE. The aim of these standards is to reduce incompatibility between vendors. MikroTik PSE with af/at support is capable of powering both a Type 1 and a Type 2 PD. Valid PD should have PoE-In resistance from 23.75kΩ to 26.25kΩ. MikroTik devices which support af/at standard can also switch to Passive PoE-Out mode. (e.g. hEX PoE, CRS112-8P-4S-IN, CRS328-24P-4S+RM.)

Each PoE-Out implementation supports overload and short-circuit detection.

Icon-note.png

Note: Some MikroTik devices support all of the described standards (e.g. hEX PoE, PowerBOX Pro, CRS112-8P-4S-IN etc...)


PoE-Out Configuration

PoE Configuration is supported on all MikroTik devices with PoE-Out interfaces, the configurations can be edited from the RouterOS and SwOS interfaces.

RouterOS

Usage

RouterOS provides an option to configure PoE-Out over Winbox, Webfig and CLI, basic commands using the CLI are

Property Description
print () Prints PoE-Out related settings.
export () export is displayed under /interface ethernet menu.
monitor (string| interface) Shows poe-out-status of a specified port, or all ports with /interface ethernet poe monitor [find] command.
power-cycle (time:0..1m |; Default: 5s) Disables PoE-Out power for a specified period of time.

Global Settings

Some MikroTik PoE-Out devices support global PoE setting which can be configured under /interface ethernet poe settings menu. Global setting ether1-poe-in-long-cable feature disables strict input/output current monitoring (short detection) to allow the use of PoE-Out with long ethernet cables and/or avoiding improper short-circuit detection.

Property Description
ether1-poe-in-long-cable (yes | no) Setting it to "yes" will disable short detection on all poe-out ports. This is potentially dangerous settings and should be used with caution
Icon-note.png

Note: Global setting of ether1-poe-in-long-cable can also affect PoE-Out behaviour on PSE which is powered using a DC connector


Port Settings

PoE-Out can be configured under /interface ethernet poe menu. Each port can be controlled independently.


Property Description
name () Name of an interface
poe-out (auto-on | forced-on | off; Default: auto-on) Specifies PoE-Out state
  • auto-on - the board will attempt to detect if power can be applied on the port. For power-on to happen there should be resistance on spare pairs in the range from 3kΩ to 26.5kΩ
  • forced-on - detection range is removed. As a result power over Ethernet will be always on
  • off - all detection and power is turned off for this port
poe-priority (integer:0..99 | any; Default: 10) poe-priority specifies the importance of PoE-Out ports, in cases when a total PoE-Out limit is reached, interface with the lowest port priority will be powered off first.

Highest priority is 0, lowest priority is 99. If there are 2 or more ports with the same priority then port with the smallest port number will have a higher priority. For example, if ether2 and ether3 have the same priority and over-current is detected then PoE-Out on ether3 will be turned off.

Every 6 seconds ports will be checked for a possibility to provide PoE-Out if it was turned off due to port priority.
poe-voltage (auto | low | high; Default: auto) Feature which allows to manually switch between two voltage outputs on PoE-Out ports. Will take effect only on PSE with switchable voltage modes (CRS112-8P-4S-IN, CRS328-24P-4S+RM, netPower 16P, CRS354-48P-4S+2Q+RM).

Power-cycle settings

RouterOS provides a possibility to monitor PD using a ping, and power-cycle a PoE-Out port when the host does not respond. power-cycle-ping feature can be enabled under /interface ethernet poe menu.

Property Description
power-cycle-ping-enabled (yes | no; Default: no) Enables ping watchdog, power-cycles port if a host does not respond to ICMP or MAC-Telnet packets.
power-cycle-ping-address (IPv4 | IPv6 | MAC; Default: ) An address which will be monitored. Since RouterOS 6.46beta16, an active route towards PD is required in case an IP address is configured, so make sure PSE can reach the PD. In case MAC address is specified, PSE will send MAC-Telnet ping requests only from specified ethernet interface. When configuring a bridge vlan-filtering or some way of VLAN switching, it is recommended to use IP address for monitoring your PD.
power-cycle-ping-timeout (time:0..1h |; Default: 5s) If the host does not respond for more than <timeout> period of time, then PoE-Out port is switched off for 5s.
power-cycle-interval (time| any; Default: ) Disables PoE-Out power for 5s between specified interval. Not related with power-cycle-ping feature.


If power-cycle is enabled, /interface ethernet poe monitor will show actual status of the host and time when power cycle will be performed [1]

SwOS

SwOS interface provides basic PoE-Out configuration options:

  • PoE Out - Change between PoE-out modes (auto/on/off)
  • PoE Priority - Change the Priority of port (0...8)
  • Voltage Level - Change between two voltage outputs on PoE-Out ports (auto/low/high)

PoE-Out Monitoring

RouterOS

MikroTik devices with PoE-Out controller (not injector) provides port monitoring option. /interface ethernet poe monitor [find]

Property Description
name () Name of an interface
poe-out () Shows PoE-Out settings
poe-out-status () Shows current PoE-Out status on port
  • powered-on - Power is applied to the port, and PoE-Out is operating normally,
  • waiting-for-load - PSE attempts to detect if power can be applied to the port. For power-on to happen there should be resistance on spare pairs in the range from 3kΩ to 26.5kΩ;
  • short-circuit - Short-circuit is detected on PoE-Out port, power is switched off, the only detection with low voltage takes place.
  • overload - The PoE-Out current limit is exceeded, power is switched off on PoE-Out port. For port limits see each model specifications.
  • voltage-too-low - PD can not be powered with voltage provided from PSE.
  • current-too-low - current-too-low means that PD draws too low current (<10mA) than normal PoE-Out device should, reason for this can be:

Delivered voltage at PD is too low for normal powering (for example Vmin = >30V, but provided 24V);

PD uses second power source which has a higher voltage than PSE, so all current is taken from second DC source, not PSE PoE-Out port;

  • off - all detection and power is turned off for this port;
poe-out-voltage () Displays PoE Voltage which is applied to the PD.
poe-out-current () Displays port current (mA) which is drawn by the PD.
poe-out-power () Displays PD power consumption

If power-cycle-ping feature is used, /interface ethernet poe monitor [find] will show additional fields:

power-cycle-host-alive: <YES/NO> (Shows if monitored host is reachable)
power-cycle-after:<TIME> (Shows time, after which the port will be power-cycled)

SNMP

It is possible to monitor PoE-Out values using SNMP protocol, this requires enabled SNMP on PSE. SNMP Wiki

SNMP OID tables:

  • 1.3.6.1.4.1.14988.1.1.15.1.1.1 - interface id
  • 1.3.6.1.4.1.14988.1.1.15.1.1.2 - interface names
  • 1.3.6.1.4.1.14988.1.1.15.1.1.4 - voltage in dV (decivolt)
  • 1.3.6.1.4.1.14988.1.1.15.1.1.5 - current in mA
  • 1.3.6.1.4.1.14988.1.1.15.1.1.6 - power usage in dW (deviwatt)

SNMP values can be requested also from the RouterOS, for example, snmp-walk will print current mA from all available PoE-Out ports:

/tool snmp-walk address=10.155.149.252 oid=1.3.6.1.4.1.14988.1.1.15.1.1.5

To get very specific OID value, use snmp-get tool (displays current mA on ether3 interface):

tool snmp-get address=10.155.149.252 oid=1.3.6.1.4.1.14988.1.1.15.1.1.5.3

SwOS

A PoE-Out controller will enable certain monitoring features also from SwOS, such as PoE-Out Status, PoE-Out Current, PoE-Out Voltage and PoE-Out Power usage.

All PoE-Out configuration and monitoring is located on one page, under PoE tab http://<IP>/index.html#poe:

SwOS PoE.png


PoE-Out notifications

PoE-Out LEDs

Models with dependant voltage output

PoE-Out LED behaviour can differ between models, but most of them will indicate PoE-Out state on one additional LED. Devices with one voltage output will light:

  • Red colour LED - PoE-Out port state is powered-on (auto or forced-on mode).
  • Blinking Red colour LED - PoE-Out port state is short-circuit

Models with selectable voltage output

Models with multiple voltage options can indicate additional information:

  • Green colour triangle LED - PoE-Out port state is powered-on (auto or forced-on mode), PD uses low voltage.
  • Red colour triangle LED - PoE-Out port state is powered-on (auto or forced-on mode), PD uses high voltage (af/at or passive).
  • Blinking Green colour triangle LED - PoE-Out port state is short-circuit or overload
  • Blinking Red colour triangle LED - PoE-Out port state is short-circuit or overload

Model-specific LED behaviour

  • CRS112-8P-4S-IN - All PoE LEDs flashing: wrong voltage PSU plugged into one of the ports.
  • netPower 16P - All PoE LEDs flashing: wrong voltage PSU plugged into one of the ports.
  • CRS328-24P-4S+RM - indicates an exceeded overall max PoE output limit. Port PoE-Out priorities will work in 3 independent sections (8 ports each) and overload will happen in any section that breach 150W consumption.


PoE-Out Logs

By default PoE-Out event logging is enabled and uses "warning" and "info" topics to notify the user about PoE-Out state changes. Log entries will be added on each PoE-Out state change. Important logs will be added with "warning" topic, informative logs will be added with "info" topic.

To avoid unnecessary logging in cases when PD is not powered because of current-too-low, RouterOS will filter such events, and add one log per every 512 current-too-low events.

Logs can be disabled if necessary:

/system logging set [find topics~"info"] topics=info,!poe-out 
/system logging set [find topics~"warning"] topics=warning,!poe-out 

PoE-Out Warnings in GUI/CLI

To notify a user about important PoE-Out related problems, messages will be shown in Winbox / Webig and CLI interface fields:

     1  RS ;;; poe-out status: overload
       ether1                              ether            1500  1588       9204 64:D1:54:61:D5:E0

Webfig and Winbox will notify user under interfaces:

WebFIG PoE WRN.png


How it works

PoE-Out Modes

auto-on mode

If auto-on is selected on PoE-Out interface, then port operates in this strict order:

  • PSE with low voltage checks for a resistance on the connected port. If detected resistance range is between (3kΩ to 26.5kΩ) power is turned on;
  • When power is applied, the PSE continuously checks if overload limit is not reached or short circuit detected
  • If the cable is unplugged, the port returns in detection state and will remain off until suitable PD is detected

forced-on mode

If forced-on is selected then port operates in this strict order:

  • PSE disables resistance check on the port, and apply power on pins 4,5 (+) and 7,8 (-), even if no cable is attached
  • When power is applied, PSE still continuously checks if an overload or short circuit is not detected
  • After the cable is unplugged, the power still remains enabled on the port.

off mode

If off mode is used, PoE-Out on the port will be turned off, no detection will take place, and interface will behave as a simple Ethernet port.


PoE-Out limitations

It is important to check PoE-Out specification to find out hardware limitations because it can differ between models

PoE-Out port limitation

PoE-Out ports are limited with max amp values which are supported in particular voltage, usually max current will differ for low voltage devices (up to 30 V), and for high voltage devices (31 to 57 V).

PoE-Out total limitation

PSE has also a total PoE-Out current limitation which can't be exceeded, even if individual port limit allows it.

PoE Out polarity

All MikroTik PSE uses the same PoE-Out pin polarity Mode B 4,5 (+) and 7,8 (-), however other vendors can use opposite or Mode A pinout on PD, this would require using a special crossover cable.

Icon-note.png

Note: Passive PD with high input inrush current can result in overcurrent protection on PSE, make sure that PD specification supports powering from PSE (not only from the passive power injector)


Safety

PSE has following safety features:

PoE-Out compatibility detection

The auto-on mode is considered safe, it will check if the resistance on the port is within allowed range and only then enable PoE out on the interface. The range is 3kΩ to 26.5kΩ

Overload protection

When a PoE-Out port is powered-on, it is constantly checked for overload. If overload is detected, PoE-Out is turned off on the port to avoid damage to the PD or PSE.

In seconds the PoE Out feature will be turned on again to see if the environment has changed and PD can be supplied with power again. That is important for configurations that are not connected to mains (solar installations, equipment running on batteries due to mains failure) so that when voltage drops - overload will be detected and connected devices turned off. After a while when voltage level returns to usual operating value - connected equipment can be powered up again.

Short circuit detection

When power is enabled on PoE-Out port, PSE continuously checks for a short circuit. If it is detected to ensure that there is no additional damage on PD and PSE, the power is turned off on all ports. PSE will continue to check PoE-Out port until environment returns to normal.

Icon-warn.png

Warning: Make sure that non-standard incompatible PD which does not have the resistance range 3kΩ to 26.5kΩ are not attached, so the PSE would not try to apply power on them


Model-specific features

PSE with independent 8-port sections (CRS112-8P-4S-IN, CRS328-24P-4S+RM, netPower 16P, CRS354-48P-4S+2Q+RM) allows PoE-Out to work independantly from the RouterOS, this means that you can reboot/upgrade your RouterOS and the PD will not be rebooted.

PoE Out examples

RouterOS allows to define priorities on PoE-Out ports, so if your installation is going over power budget, the PSE will disable less important PD with the lowest priority.

Priority of 0 is the highest priority, 99 - lowest

Icon-note.png

Note: CRS328-24P-4S+RM, netPower 16P, netPower 16P Poe-Out priorities work independently on each 8 port section!


Setting up priority

Example of how to set priorities from CLI:

 /interface ethernet poe set ether2 poe-priority=10
 /interface ethernet poe set ether3 poe-priority=13
 /interface ethernet poe set ether4 poe-priority=11
 /interface ethernet poe set ether5 poe-priority=14

What will happen when power budget will go over total PoE-Out limit - first, if overload is detected, ether5 will be turned off (lowest priority), then recheck is done and if still total limit overload is detected next port in priority will be turned off, in this example, ether3 will be turned off. Both of these ports will be reached every few seconds to check if it is possible to turn PoE-Out on for these ports. Power up will happen in reverse order as the power was cut.

Same priority

if all, or some ports will have the same poe-priority, then port with the lowest port number will have higher priority

 /interface ethernet poe set ether2 poe-priority=10
 /interface ethernet poe set ether3 poe-priority=10
 /interface ethernet poe set ether4 poe-priority=10
 /interface ethernet poe set ether5 poe-priority=10

In this example, if the total PoE-Out limit is reached ether5 will be turned off first, then ether4 then ether3 as all of these ports have same poe priority.

Monitoring PoE-Out

PoE-Out ports can be monitored using a command /interface ethernet poe monitor <interface>

[admin@MikroTik] > interface ethernet poe monitor [find]
              name: ether2 ether3 ether4 ether5
   poe-out-voltage: 23.2V  23.2V  23.2V  
   poe-out-current: 224mA  116mA  64mA   
     poe-out-power: 5.1W   2.6W   1.4W 


Power-cycle ping

Monitor connected PD with power-cycle-ping feature:

/interface ethernet poe set ether1 power-cycle-ping-enabled=yes power-cycle-ping-address=192.168.88.10 power-cycle-ping-timeout=30s

In this example, PD attached to ether1 will be continuously monitored using a power-cycle-ping feature, which will send ICMP ping requests and wait for a reply. If PD with IP address 192.168.88.10 will not respond for more than 30s, the PoE-Out port will be switched off for 5s.

Troubleshooting

In cases where a PD does not power-up or reboots unexpectedly when powered from your PSE, it's suggested to first check:

  • PD supported input voltage - PSE output voltage must be in the range supported by the PD. Otherwise the PD is incompatible with the PSE, and will not be able to power-up. Check the PD datasheet.
  • PD supported input PoE-in standard - Some PDs do not support af/at standard even if it has PoE-in support up to 57 V, check PD datasheet.
  • PD is rebooted from PSE
    • Check if PD does not exceed PoE-Out port limit and Total-PoE-Out port limit of the PSE, check PSE datasheet.
    • Check if Voltage limit does not drop bellow supported (Can be caused by voltage drop on the wires).
    • Check if you are using a proper power supply, the output power of PSU should be calculated from:
      (MAX power consumption of PSE) + (MAX power consumption of all PD) + 10%)
    • Check if you are using good quality ethernet cables, it's important especially in cases if PoE is used.
  • Chech RouterOS version - it's possible, that some PoE related features will be updated with RouterOS, make sure that you are running the latest RouterOS version.
  • PD Does not power up
    • There can be cases where a PD does not power up, even though it supports passive PoE, and does not consume more power than the specified PSE port limit. This can be caused by inrush current triggering overcurrent protection on the PSE. Make sure that PD specification supports powering from PSE (not only from passive power injector)
    • Polarity - Devices with opposite or different pinout can be unable to powerup from all PSE. Check PD datasheet.
    • Incompatible resistance - PD resistance on spare pairs should have range from 3kΩ to 26.5kΩ (For Passive-PoE) and from 23.75kΩ to 26.25kΩ on af/at.

Legacy

PoE-Out Controller upgrade

PoE-Out devices which are running RouterOS 5.x can also hold old PoE-Out controller firmware, upgrade to RouterOS 6.x will automatically update the PoE-Out firmware. Changes between 1.x and 2.x PoE-Out controller firmware will result in higher Max-port limits (0.5A to 1A) in case if it's supported by the hardware, also will provide some additional data which can be monitored, and allow to use PoE-Out priorities.

All MikroTik devices which come with RouterOS 6.x already support the latest PoE-Out firmware.

FAQ