Manual:Interface/Ethernet: Difference between revisions

From MikroTik Wiki
Jump to navigation Jump to search
← Older edit
 
(66 intermediate revisions by 6 users not shown)
Line 1: Line 1:
{{Versions|v3, v4+}}
{{Versions|v3, v4+}}
{{Warning|This manual is moved to https://help.mikrotik.com/docs/display/ROS/Ethernet}}


<div class=manual>
<div class=manual>
Line 9: Line 11:
<br />
<br />
<p>
<p>
MikroTik RouterOS supports various types of Ethernet interfaces.  
MikroTik RouterOS supports various types of Ethernet interfaces - ranging from 10Mbps to 10Gbps Ethernet over copper twisted pair, 1Gbps and 10Gbps SFP/SFP+ interfaces and 40Gbps QSFP interface. Certain RouterBoard devices are equipped with a combo interface that simultaneously contains two interface types (e.g. 1Gbps Ethernet over twisted pair and SFP interface) allowing to select the most suitable option or creating a physical link failover. Through RouterOS, it is possible to control different Ethernet related properties like link speed, auto-negotiation, duplex mode, etc, monitor a transceiver diagnostic information and see a wide range of Ethernet related statistics.
</p>
</p>


==Properties==
==Properties==


<br />
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
 
{{Mr-arg-table
|arg=advertise
|type=10M-full {{!}} 10M-half {{!}} 100M-full {{!}} 100M-half {{!}} 1000M-full {{!}} 1000M-half {{!}} 2500M-full {{!}} 5000M-full {{!}} 10000M-full
|default=
|desc=Advertised speed and duplex modes for Ethernet interfaces over twisted pair, only applies when <var>auto-negotiation</var> is enabled. Advertising higher speeds than the actual interface supported speed will have no effect, multiple options are allowed.
}}
 
{{Mr-arg-table
|arg=arp
|type=disabled {{!}} enabled {{!}} local-proxy-arp {{!}} proxy-arp {{!}} reply-only
|default=enabled
|desc=Address Resolution Protocol mode:
* <var>disabled</var> - the interface will not use ARP
* <var>enabled</var> - the interface will use ARP
* <var>local-proxy-arp</var> - the router performs proxy ARP on the interface and sends replies to the same interface
* <var>proxy-arp</var> - the router performs proxy ARP on the interface and sends replies to other interfaces
* <var>reply-only</var> - the interface will only reply to requests originated from matching IP address/MAC address combinations which are entered as static entries in the [[M:IP/ARP | ARP]] table. No dynamic entries will be automatically stored in the ARP table. Therefore for communications to be successful, a valid static entry must already exist.
}}
 
{{Mr-arg-table
|arg=auto-negotiation
|type=yes {{!}} no
|default=yes
|desc=When enabled, the interface "advertises" its maximum capabilities to achieve the best connection possible.
* '''Note1:''' Auto-negotiation should not be disabled on one end only, otherwise Ethernet Interfaces may not work properly.
* '''Note2:''' Gigabit Ethernet and NBASE-T Ethernet links cannot work with auto-negotiation disabled.
}}
 
{{Mr-arg-table
|arg=bandwidth
|type=integer/integer
|default=unlimited/unlimited
|desc=Sets max rx/tx bandwidth in kbps that will be handled by an interface. TX limit is supported on all Atheros [[M:Switch_Chip_Features | switch-chip]] ports. RX limit is supported only on Atheros8327/QCA8337 switch-chip ports.
}}
 
{{Mr-arg-table
|arg=cable-setting
|type=default {{!}} short {{!}} standard
|default=default
|desc=Changes the cable length setting (only applicable to NS DP83815/6 cards)
}}
 
{{Mr-arg-table
|arg=combo-mode
|type=auto {{!}} copper {{!}} sfp
|default=auto
|desc=When <var>auto</var> mode is selected, the port that was first connected will establish the link. In case this link fails, the other port will try to establish a new link. In case of a reboot, any of the two ports can be running, it depends on which port will successfully establish the link first. When <var>sfp</var> mode is selected, the interface will only work through SFP/SFP+ cage. When <var>copper</var> mode is selected, the interface will only work through RJ45 Ethernet port.
}}
 
{{Mr-arg-table
|arg=comment
|type=string
|default=
|desc=Descriptive name of an item
}}
 
{{Mr-arg-table
|arg=disable-running-check
|type=yes {{!}} no
|default=yes
|desc=Disable running check. If this value is set to 'no', the router automatically detects whether the NIC is connected with a device in the network or not. Default value is 'yes' because older NICs do not support it. (only applicable to x86)
}}
 
{{Mr-arg-table
|arg=tx-flow-control
|type=on {{!}} off {{!}} auto
|default=off
|desc=When set to on, the port will generate pause frames to the upstream device to temporarily stop the packet transmission. Pause frames are only generated when some routers output interface is congested and packets cannot be transmitted anymore. '''auto''' is the same as '''on''' except when auto-negotiation=yes flow control status is resolved by taking into account what other end advertises.
}}
 
{{Mr-arg-table
|arg=rx-flow-control
|type=on {{!}} off {{!}} auto
|default=off
|desc=When set to on, the port will process received pause frames and suspend transmission if required. '''auto''' is the same as '''on''' except when auto-negotiation=yes flow control status is resolved by taking into account what other end advertises.
}}
 
{{Mr-arg-table
|arg=full-duplex
|type=yes {{!}} no
|default=yes
|desc=Defines whether the transmission of data appears in two directions simultaneously, only applies when <var>auto-negotiation</var> is disabled.
}}
 
{{Mr-arg-table
|arg=l2mtu
|type=integer [0..65536]
|default=
|desc=Layer2 Maximum transmission unit. [[ Maximum_Transmission_Unit_on_RouterBoards | Read more>> ]]
}}
 
{{Mr-arg-table
|arg=mac-address
|type=MAC
|default=
|desc=Media Access Control number of an interface.
}}
 
{{Mr-arg-table
|arg=master-port
|type=name | none
|default=none
|desc=Outdated property, more details about this property can be found in the [[Manual:Master-port | Master-port]] page.
}}
 
{{Mr-arg-table
|arg=mdix-enable
|type=yes {{!}} no
|default=yes
|desc=Whether the MDI/X auto cross over cable correction feature is enabled for the port (Hardware specific, e.g. ether1 on RB500 can be set to yes/no. Fixed to 'yes' on other hardware.)
}}
 
{{Mr-arg-table
|arg=mtu
|type=integer [0..65536]
|default=1500
|desc=Layer3 Maximum transmission unit
}}
 
{{Mr-arg-table
|arg=name
|type=string
|default=
|desc=Name of an interface
}}
 
{{Mr-arg-table
|arg=orig-mac-address
|type=read-only: MAC
|default=
|desc=Original Media Access Control number of an interface.
}}
 
{{Mr-arg-table
|arg=poe-out
|type=auto-on {{!}} forced-on {{!}} off
|default=off
|desc=Poe Out settings. [[M:PoE-Out | <code>Read more >></code>]]
}}
 
{{Mr-arg-table
|arg=poe-priority
|type=integer [0..99]
|default=
|desc=Poe Out settings. [[M:PoE-Out | <code>Read more >></code>]]
}}
 
{{Mr-arg-table
|arg=sfp-shutdown-temperature
|type=integer
|default=95
|desc=Temperature at which interface will be temporarily turned off due to too high detected SFP module temperature (introduced v6.48).
}}
 
{{Mr-arg-table
|arg=sfp-rate-select
|type=high {{!}} low
|default=high
|desc=Allows to control rate select pin for SFP ports.
}}
 
{{Mr-arg-table-end
|arg=speed
|type=10Mbps {{!}} 10Gbps {{!}} 100Mbps {{!}} 1Gbps
|default=
|desc=Sets interface data transmission speed which takes effect only when <var>auto-negotiation</var> is disabled.
}}
 
 
'''Read-only properties'''
 
<table class="styled_table">
<table class="styled_table">
<tr>
<tr>
Line 21: Line 198:
</tr>
</tr>
<tr>
<tr>
     <td><var><b>arp</b></var> (<em>disabled | enabled | proxy-arp | reply-only</em>; Default: <b>enabled</b>)</td>
     <td><var><b>running</b></var> (<em>yes | no</em>)</td>
     <td>Address Resolution Protocol mode
     <td>Whether interface is running. Note that some interface does not have running check and they are always reported as "running"</td>
    <ul class="bullets">
</tr>
        <li> <var>disabled</var> - the interface will not use ARP
<tr>
        <li> <var>enabled</var> - the interface will use ARP
    <td><var><b>slave</b></var> (<em>yes | no</em>)</td>
        <li> <var>proxy-arp</var> - the interface will use the ARP proxy feature
     <td>Whether interface is configured as a slave of another interface (for example [[Bonding]])</td>
        <li> <var>reply-only</var> - the interface will only reply to requests originated from matching IP address/MAC address combinations which are entered as static entries in the "/ip arp" table. No dynamic entries will be automatically stored in the "/ip arp" table. Therefore for communications to be successful, a valid static entry must already exist.
     </ul>
</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>auto-negotiation</b></var> (<em>yes | no</em>; Default: <b>yes</b>)</td>
     <td><var><b>switch</b></var> (<em>integer</em>)</td>
     <td>When enabled, the interface "advertises" its maximum capabilities to achieve the best connection possible. <br /> <b>Note1:</b> Auto-negotiation should not be disabled on one end only, otherwise Ethernet Interfaces may not work properly. <br /> <b>Note2:</b> Gigabit link cannot work with auto-negotiation disabled.</td>
     <td>ID to which switch chip interface belongs to.</td>
</tr>
</tr>
</table>
==Menu specific commands==
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
{{Mr-arg-ro-table
|arg=blink
|type=[id, name]
|desc=Blink Ethernet leds
}}
{{Mr-arg-ro-table
|arg=monitor
|type=[id, name]
|desc=Monitor ethernet status. [[#Monitor | Read more>>]]
}}
{{Mr-arg-ro-table
|arg=reset-counters
|type=[id, name]
|desc=Reset stats counters. [[#Stats | Read more>>]]
}}
{{Mr-arg-ro-table
|arg=reset-mac-address
|type=[id, name]
|desc=Reset MAC address to manufacturers default.
}}
{{Mr-arg-ro-table-end
|arg=cable-test
|type=string
|desc=Shows detected problems with cable pairs. [[#Detect Cable Problems | <code>Read More >></code>]]
}}
==Monitor==
To print out a current link rate, duplex mode, and other Ethernet related properties or to see detailed diagnostics information for transceivers, use <code>/interface ethernet monitor</code> command. The provided information can differ for different interface types (e.g. Ethernet over twisted pair or SFP interface) or for different transceivers (e.g. SFP and QSFP).
'''Properties'''
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
{{Mr-arg-ro-table
|arg=advertising
|type=10M-full {{!}} 10M-half {{!}} 100M-full {{!}} 100M-half {{!}} 1000M-full {{!}} 1000M-half {{!}} 2500M-full {{!}} 5000M-full {{!}} 10000M-full
|desc=Advertised speeds and duplex modes for Ethernet interfaces over twisted pair, only applies when <var>auto-negotiation</var> is enabled
}}
{{Mr-arg-ro-table
|arg=auto-negotiation
|type=disabled {{!}} done {{!}} failed {{!}} incomplete
|desc=Current auto negotiation status:
* <var>disabled</var> - negotiation disabled
* <var>done</var> - negotiation completed
* <var>failed</var> - negotiation failed
* <var>incomplete</var> - negotiation not completed yet
}}
{{Mr-arg-ro-table
|arg=default-cable-settings
|type=short {{!}} standard
|desc=Default cable length setting (only applicable to NS DP83815/6 cards)
* <var>short</var> - support short cables
* <var>standard</var> - support standard cables
}}
{{Mr-arg-ro-table
|arg=full-duplex
|type=yes {{!}} no
|desc=Whether transmission of data occurs in two directions simultaneously
}}
{{Mr-arg-ro-table
|arg=link-partner-advertising
|type=10M-full {{!}} 10M-half {{!}} 100M-full {{!}} 100M-half {{!}} 1000M-full {{!}} 1000M-half {{!}} 2500M-full {{!}} 5000M-full {{!}} 10000M-full
|desc=Link partner advertised speeds and duplex modes for Ethernet interfaces over twisted pair, only applies when <var>auto-negotiation</var> is enabled
}}
{{Mr-arg-ro-table
|arg=rate
|type=10Mbps {{!}} 100Mbps {{!}} 1Gbps {{!}} 2.5Gbps {{!}} 5Gbps {{!}} 10Gbps {{!}} 40Gbps {{!}}
|desc=Actual data rate of the connection.
}}
{{Mr-arg-ro-table
|arg=status
|type=link-ok {{!}} no-link {{!}} unknown
|desc=Current link status of an interface
* <var>link-ok</var> - the card is connected to the network
* <var>no-link</var> - the card is not connected to the network
* <var>unknown</var> - the connection is not recognized (if the card does not report connection status)
}}
{{Mr-arg-ro-table
|arg=tx-flow-control
|type=yes {{!}} no
|desc=Whether TX flow control is used
}}
{{Mr-arg-ro-table
|arg=rx-flow-control
|type=yes {{!}} no
|desc=Whether RX flow control is used
}}
{{Mr-arg-ro-table
|arg=combo-state
|type=copper {{!}} sfp
|desc=Used combo-mode for combo interfaces
}}
{{Mr-arg-ro-table
|arg=sfp-module-present
|type=yes {{!}} no
|desc=Whether a transceiver is in cage
}}
{{Mr-arg-ro-table
|arg=sfp-rx-lose
|type=yes {{!}} no
|desc=Whether a receiver signal is lost
}}
{{Mr-arg-ro-table
|arg=sfp-tx-fault
|type=yes {{!}} no
|desc=Whether a transceiver transmitter is in fault state
}}
{{Mr-arg-ro-table
|arg=sfp-type
|type=SFP-or-SFP+ {{!}} DWDM-SFP {{!}} QSFP+
|desc=Used transceiver type
}}
{{Mr-arg-ro-table
|arg=sfp-connector-type
|type=SC {{!}} LC {{!}} optical-pigtail {{!}} copper-pigtail {{!}} multifiber-parallel-optic-1x12 {{!}} no-separable-connector {{!}} RJ45
|desc=Used transceiver connector type
}}
{{Mr-arg-ro-table
|arg=sfp-link-length-9um
|type=m
|desc=Transceiver supported link length for single mode 9/125um fiber
}}
{{Mr-arg-ro-table
|arg=sfp-link-length-50um
|type=m
|desc=Transceiver supported link length for multi mode 50/125um fiber (OM2)
}}
{{Mr-arg-ro-table
|arg=sfp-link-length-62um
|type=m
|desc=Transceiver supported link length for multi mode 62.5/125um fiber (OM1)
}}
{{Mr-arg-ro-table
|arg=sfp-link-length-copper
|type=m
|desc=Supported link length of copper transceiver
}}
{{Mr-arg-ro-table
|arg=sfp-vendor-name
|type=string
|desc=Transceiver manufacturer
}}
{{Mr-arg-ro-table
|arg=sfp-vendor-part-number
|type=string
|desc=Transceiver part number
}}
{{Mr-arg-ro-table
|arg=sfp-vendor-revision
|type=string
|desc=Transceiver revision number
}}
{{Mr-arg-ro-table
|arg=sfp-vendor-serial
|type=string
|desc=Transceiver serial number
}}
{{Mr-arg-ro-table
|arg=sfp-manufacturing-date
|type=date
|desc=Transceiver manufacturing date
}}
{{Mr-arg-ro-table
|arg=sfp-wavelength
|type=nm
|desc=Transceiver transmitter optical signal wavelength
}}
{{Mr-arg-ro-table
|arg=sfp-temperature
|type=C
|desc=Transceiver temperature
}}
{{Mr-arg-ro-table
|arg=sfp-supply-voltage
|type=V
|desc=Transceiver supply voltage
}}
{{Mr-arg-ro-table
|arg=sfp-tx-bias-current
|type=mA
|desc=Transceiver Tx bias current
}}
{{Mr-arg-ro-table
|arg=sfp-tx-power
|type=dBm
|desc=Transceiver transmitted optical power
}}
{{Mr-arg-ro-table
|arg=sfp-rx-power
|type=dBm
|desc=Transceiver received optical power
}}
{{Mr-arg-ro-table
|arg=eeprom-checksum
|type=good {{!}} bad
|desc=Whether EEPROM checksum is correct
}}
{{Mr-arg-ro-table-end
|arg=eeprom
|type=hex dump
|desc=Raw EEPROM of the transceiver
}}
Example output of an Ethernet status:
<pre>
[admin@MikroTik] > /interface ethernet monitor ether1
                      name: ether1
                    status: link-ok
          auto-negotiation: done
                      rate: 1Gbps
              full-duplex: yes
          tx-flow-control: no
          rx-flow-control: no
              advertising: 10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full
  link-partner-advertising: 10M-half,10M-full,100M-half,100M-full,1000M-full
</pre>
Example output of a SFP status:
<pre>
[admin@MikroTik] > /interface ethernet monitor sfp-sfpplus24
                      name: sfp-sfpplus24
                    status: link-ok
          auto-negotiation: done
                      rate: 10Gbps
              full-duplex: yes
          tx-flow-control: no
          rx-flow-control: no
              advertising:
  link-partner-advertising:
        sfp-module-present: yes
              sfp-rx-loss: no
              sfp-tx-fault: no
                  sfp-type: SFP-or-SFP+
        sfp-connector-type: LC
      sfp-link-length-50um: 80m
      sfp-link-length-62um: 30m
          sfp-vendor-name: Mikrotik
    sfp-vendor-part-number: S+85DLC03D
      sfp-vendor-revision: A
        sfp-vendor-serial: STST85S84700155
    sfp-manufacturing-date: 18-12-07
            sfp-wavelength: 850nm
          sfp-temperature: 33C
        sfp-supply-voltage: 3.251V
      sfp-tx-bias-current: 6mA
              sfp-tx-power: -2.843dBm
              sfp-rx-power: -1.203dBm
          eeprom-checksum: good
                    eeprom: 0000: 03 04 07 10 00 00 00 20  40 0c c0 06 67 00 00 00  .......  @...g...
                            0010: 08 03 00 1e 4d 69 6b 72  6f 74 69 6b 20 20 20 20  ....Mikr otik   
                            0020: 20 20 20 20 00 00 00 00  53 2b 38 35 44 4c 43 30      .... S+85DLC0
                            0030: 33 44 20 20 20 20 20 20  41 20 20 20 03 52 00 45  3D      A  .R.E
                            0040: 00 1a 00 00 53 54 53 54  38 35 53 38 34 37 30 30  ....STST 85S84700
                            0050: 31 35 35 20 31 38 31 32  30 37 20 20 68 f0 05 b6  155 1812 07  h...
                            0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........
                            0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........
                            0080: 64 00 d8 00 5f 00 dd 00  8c a0 6d 60 88 b8 71 48  d..._... ..m`..qH
                            0090: 1d 4c 00 fa 17 70 01 f4  31 2d 04 ea 27 10 06 30  .L...p.. 1-..'..0
                            00a0: 31 2d 01 3c 27 10 01 8e  00 00 00 00 00 00 00 00  1-.<'... ........
                            00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........
                            00c0: 00 00 00 00 3f 80 00 00  00 00 00 00 01 00 00 00  ....?... ........
                            00d0: 01 00 00 00 01 00 00 00  01 00 00 00 00 00 00 26  ........ .......&
                            00e0: 21 8a 7f 00 0c cd 14 4c  1d 9c 00 00 00 00 00 00  !......L ........
                            00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........
</pre>
==Detect Cable Problems==
Cable test can detect problems or measure the approximate cable length if the cable is unplugged on the other end and there is therefore, "no-link".
RouterOS will show:
* which cable pair is damaged
* the distance to the problem
* how exactly the cable is broken - short-circuited or open-circuited
This also works if the other end is simply unplugged - in that case, the total cable length will be shown.
Here is example output:
<pre>
[admin@CCR] > interface ethernet cable-test ether2
        name: ether2
      status: no-link
  cable-pairs: open:4,open:4,open:4,open:4
</pre>
In the above example, the cable is not shorted but “open” at 4 meters distance, all cable pairs equally faulty at the same distance from the switch chip.
Currently <code>cable-test</code> is implemented on the following devices:
* CCR series devices
* CRS1xx series devices
* CRS2xx series devices
* OmniTIK series devices
* RB450G series devices
* RB951 series devices
* RB2011 series devices
* RB4011 series devices
* RB750Gr2
* RB750UPr2
* RB751U-2HnD
* RB850Gx2
* RB931-2nD
* RB941-2nD
* RB952Ui-5ac2nD
* RB962UiGS-5HacT2HnT
* RB1100AHx2
* RB1100x4
* RBD52G-5HacD2HnD
* RBcAPGi-5acD2nD
* RBmAP2n
* RBmAP2nD
* RBwsAP-5Hac2nD
* RB3011UiAS-RM
* RBMetal 2SHPn
* RBDynaDishG-5HacD
* RBLDFG-5acD
* RBLHGG-5acD
{{ Note | Currently <code>cable-test</code> is not supported on Combo ports. }}
==Stats==
Using <code>/interface ethernet print stats</code> command, it is possible to see a wide range of Ethernet related statistics. The list of statistics can differ between RouterBoard devices due to different Ethernet drivers. The list below contains all available counters across all RouterBoard devices. Most of the Ethernet statistics can be remotely monitored using [[Manual:SNMP | SNMP]] and MIKROTIK-MIB.
<br />
<table class="styled_table">
<tr>
<tr>
    <td><var><b>bandwidth</b></var> (<em>integer/integer</em>; Default: <b>unlimited/unlimited</b>)</td>
  <th width="40%">Property</th>
    <td>Sets max rx/tx bandwidth in kbps that will be handled by an interface.</td>
  <th >Description</th>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>cable-setting</b></var> (<em>default | short | standard</em>; Default: <b>default</b>)</td>
     <td><var><b>driver-rx-byte</b></var> (<em>integer</em>)</td>
     <td>changes the cable length setting (only applicable to NS DP83815/6 cards)</td>
     <td>Total count of received bytes on device CPU</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>disable-running-check</b></var> (<em>yes | no</em>; Default: <b>yes</b>)</td>
     <td><var><b>driver-rx-packet</b></var> (<em>integer</em>)</td>
     <td>Disable running check. If this value is set to 'no', the router automatically detects whether the NIC is connected with a device in the network or not. Default value is 'yes' because older NICs do not support it. (only applicable to x86)</td>
     <td>Total count of received packets on device CPU</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>flow-control-auto</b></var> (<em>yes | no</em>; Default: <b></b>)</td>
     <td><var><b>driver-tx-byte</b></var> (<em>integer</em>)</td>
     <td></td>
     <td>Total count of transmitted bytes by device CPU</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>flow-control-rx</b></var> (<em>yes | no</em>; Default: <b></b>)</td>
     <td><var><b>driver-tx-packet</b></var> (<em>integer</em>)</td>
     <td></td>
     <td>Total count of transmitted packets by device CPU</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>flow-control-tx</b></var> (<em>yes | no</em>; Default: <b></b>)</td>
     <td><var><b>rx-64</b></var> (<em>integer</em>)</td>
     <td></td>
     <td>Total count of received 64 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>full-duplex</b></var> (<em>yes | no</em>; Default: <b>yes</b>)</td>
     <td><var><b>rx-65-127</b></var> (<em>integer</em>)</td>
     <td>Defines whether the transmission of data appears in two directions simultaneously</td>
     <td>Total count of received 65 to 127 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>l2mtu</b></var> (<em>integer</em>; Default: <b></b>)</td>
     <td><var><b>rx-128-255</b></var> (<em>integer</em>)</td>
     <td>Layer2 Maximum transmission unit. [[ Maximum_Transmission_Unit_on_RouterBoards | Read more>> ]]</td>
     <td>Total count of received 128 to 255 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>mac-address</b></var> (<em>MAC</em>; Default: <b></b>)</td>
     <td><var><b>rx-256-511</b></var> (<em>integer</em>)</td>
     <td>Media Access Control number of an interface.</td>
     <td>Total count of received 256 to 511 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>master-port</b></var> (<em>name | none</em>; Default: <b>none</b>)</td>
     <td><var><b>rx-512-1023</b></var> (<em>integer</em>)</td>
     <td>Sets interface to be a slave of this named switch group master interface</td>
     <td>Total count of received 512 to 1023 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>mdix-enable</b></var> (<em>yes | no</em>; Default: yes<b></b>)</td>
     <td><var><b>rx-1024-1518</b></var> (<em>integer</em>)</td>
     <td>Whether the MDI/X auto cross over cable correction feature is enabled for the port (Hardware specific, e.g. ether1 on RB500 can be set to yes/no. Fixed to 'yes' on other hardware.)</td>
     <td>Total count of received 1024 to 1518 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>mtu</b></var> (<em>integer</em>; Default: <b>1500</b>)</td>
     <td><var><b>rx-1519-max</b></var> (<em>integer</em>)</td>
     <td>Layer3 Maximum transmission unit</td>
     <td>Total count of received frames larger than 1519 bytes</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>name</b></var> (<em>string</em>; Default: <b></b>)</td>
     <td><var><b>rx-align-error</b></var> (<em>integer</em>)</td>
     <td>Name of an interface</td>
     <td>Total count of received align error events - packets where bits are not aligned along octet boundaries</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>orig-mac-address</b></var> (<em>string</em>; Default: <b></b>)</td>
     <td><var><b>rx-broadcast</b></var> (<em>integer</em>)</td>
     <td>Name of an interface</td>
     <td>Total count of received broadcast frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>poe-out</b></var> (<em>auto-on | forced-on | off</em>; Default: <b>off</b>)</td>
     <td><var><b>rx-bytes</b></var> (<em>integer</em>)</td>
     <td>Poe Out settings. [[M:PoE-Out | <code>Read more >></code>]]</td>
     <td>Total count of received bytes</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>poe-priority</b></var> (<em></em>; Default: <b></b>)</td>
     <td><var><b>rx-carrier-error</b></var> (<em>integer</em>)</td>
     <td>Poe Out settings. [[M:PoE-Out | <code>Read more >></code>]]</td>
     <td>Total count of events when carrier sense error occurred</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>sfp-rate-select</b></var> (<em>high | low</em>; Default:<b>high</b>)</td>
     <td><var><b>rx-code-error</b></var> (<em>integer</em>)</td>
     <td></td>
     <td>Total count of received frames with code error</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>speed</b></var> (<em>10Mbps | 100Mbps | 1Gbps</em>; Default: <b>max available</b>)</td>
     <td><var><b>rx-control</b></var> (<em>integer</em>)</td>
     <td>Sets the data transmission speed of the interface. By default, this value is the maximal data rate supported by the interface</td>
     <td>Total count of received control or pause frames</td>
</tr>
</tr>
</table>
<h3>Read-only properties</h3>
<table class="styled_table">
<tr>
<tr>
  <th width="40%">Property</th>
    <td><var><b>rx-error-events</b></var> (<em>integer</em>)</td>
  <th >Description</th>
    <td>Total count of received frames with active error event</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>running</b></var> (<em>yes | no</em>)</td>
     <td><var><b>rx-fcs-error</b></var> (<em>integer</em>)</td>
     <td>Whether interface is running. Note that some interface does not have running check and they are always reported as "running"</td>
     <td>Total count of received frames with incorrect checksum</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-1024-1518</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-fragment</b></var> (<em>integer</em>)</td>
     <td>Total count of received 1024 to 1518 byte packets</td>
     <td>Total count of received fragmented frames (not related to IP fragmentation)</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-128-255</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-ip-header-checksum-error</b></var> (<em>integer</em>)</td>
     <td>Total count of received 128 to 255 byte packets</td>
     <td>Total count of received frames with IP header checksum error</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-1519-max</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-jabber</b></var> (<em>integer</em>)</td>
     <td>Total count of received packets larger than 1519 bytes</td>
     <td>Total count of received jabbed packets - packet that is transmitted longer than the maximum packet length</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-256-511</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-length-error</b></var> (<em>integer</em>)</td>
     <td>Total count of received 256 to 511 byte packets</td>
     <td>Total count of received frames with frame length error</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-512-1023</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-multicast</b></var> (<em>integer</em>)</td>
     <td>Total count of received 512 to 1023 byte packets</td>
     <td>Total count of received multicast frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-64</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-overflow</b></var> (<em>integer</em>)</td>
     <td>Total count of received 64 byte packets</td>
     <td>Total count of received overflowed frames, can be caused when device resources are insufficient to receive a certain frame</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-65-127</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-pause</b></var> (<em>integer</em>)</td>
     <td>Total count of received 65 to 127 byte packets</td>
     <td>Total count of received pause frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-align-error</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-runt</b></var> (<em>integer</em>)</td>
     <td>Total count of received align error messages</td>
     <td>Total count of received frames shorter than the minimum 64 bytes, usually caused by collisions</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-broadcast</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-tcp-checksum-error</b></var> (<em>integer</em>)</td>
     <td>Total count of received broadcast packets</td>
     <td>Total count of received frames with TCP header checksum error</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-bytes</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-too-long</b></var> (<em>integer</em>)</td>
     <td>Total count of received bytes</td>
     <td>Total count of received frames that were larger than the maximum supported frame size by the network device, see the <var>max-l2mtu</var> property</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-fcs-error</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-too-short</b></var> (<em>integer</em>)</td>
     <td>Total count of received frames with incorrect checksum</td>
     <td>Total count of received frame shorter than the minimum 64 bytes</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-fragment</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-udp-checksum-error</b></var> (<em>integer</em>)</td>
     <td>Total count of received fragmented frames</td>
     <td>Total count of received frames with UDP header checksum error</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-multicast</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-unicast</b></var> (<em>integer</em>)</td>
     <td>Total count of received multicast packets</td>
     <td>Total count of received unicast frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-overflow</b></var> (<em>integer</em>)</td>
     <td><var><b>rx-unknown-op</b></var> (<em>integer</em>)</td>
     <td>Total count of received overflowed packets</td>
     <td>Total count of received frames with unknown Ethernet protocol</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-pause</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-64</b></var> (<em>integer</em>)</td>
     <td>Total count of received pause frames</td>
     <td>Total count of transmitted 64 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-runt</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-65-127</b></var> (<em>integer</em>)</td>
     <td>Total count of received frames shorter than the minimum 64 bytes
     <td>Total count of transmitted 65 to 127 byte frames</td>
but with a valid CRC</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>rx-too-long</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-128-255</b></var> (<em>integer</em>)</td>
     <td>Total count of received packets that were larger than the maximum packet size</td>
     <td>Total count of transmitted 128 to 255 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>slave</b></var> (<em>yes | no</em>)</td>
     <td><var><b>tx-256-511</b></var> (<em>integer</em>)</td>
     <td>Whether interface is configured as a slave of another interface (for example [[Bonding]])</td>
     <td>Total count of transmitted 256 to 511 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>switch</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-512-1023</b></var> (<em>integer</em>)</td>
     <td>ID to which switch chip interface belongs to.</td>
     <td>Total count of transmitted 512 to 1023 byte frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-1024-1518</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-1024-1518</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted 1024 to 1518 byte packets</td>
     <td>Total count of transmitted 1024 to 1518 byte frames</td>
</tr>
<tr>
    <td><var><b>tx-1519-max</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted frames larger than 1519 bytes</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-128-255</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-align-error</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted 128 to 255 byte packets</td>
     <td>Total count of transmitted align error events - packets where bits are not aligned along octet boundaries</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-1519-max</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-broadcast</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted packets larger than 1519 bytes</td>
     <td>Total count of transmitted broadcast frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-256-511</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-bytes</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted 256 to 511 byte packets</td>
     <td>Total count of transmitted bytes</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-512-1023</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-collision</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted 512 to 1023 byte packets</td>
     <td>Total count of transmitted frames that made collisions</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-64</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-control</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted 64 byte packets</td>
     <td>Total count of transmitted control or pause frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-65-127</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-deferred</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted 65 to 127 byte packets</td>
     <td>Total count of transmitted frames that were delayed on its first transmit attempt due to already busy medium</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-align-error</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-drop</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted align error messages</td>
     <td>Total count of transmitted frames that were dropped due to already full output queue</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-broadcast</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-excessive-collision</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted broadcast packets</td>
     <td>Total count of transmitted frames that already made multiple collisions and never got successfully transmitted</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-bytes</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-excessive-deferred</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted bytes</td>
     <td>Total count of transmitted frames that were deferred for an excessive period of time due to already busy medium</td>
</tr>
</tr>
<tr>
<tr>
Line 246: Line 788:
<tr>
<tr>
     <td><var><b>tx-fragment</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-fragment</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted fragmented frames</td>
     <td>Total count of transmitted fragmented frames (not related to IP fragmentation)</td>
</tr>
<tr>
    <td><var><b>tx-carrier-sense-error</b></var> (<em>integer</em>)</td>
    <td>Total count of events when carrier sense error occured</td>
</tr>
<tr>
    <td><var><b>tx-late-collision</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted frames that made collision after being already halfway transmitted</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-multicast</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-multicast</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted multicast packets</td>
     <td>Total count of transmitted multicast frames</td>
</tr>
<tr>
    <td><var><b>tx-multiple-collision</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted frames that made more than one collision and subsequently transmitted successfully</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-overflow</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-overflow</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted overflowed packets</td>
     <td>Total count of transmitted overflowed frames</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-pause</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-pause</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted pause frames</td>
     <td>Total count of transmitted pause frames</td>
</tr>
<tr>
    <td><var><b>tx-all-queue-drop-byte</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted bytes dropped by all output queues</td>
</tr>
<tr>
    <td><var><b>tx-all-queue-drop-packet</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted packets dropped by all output queues</td>
</tr>
<tr>
    <td><var><b>tx-queueX-byte</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted bytes on a certain queue, the '''X''' should be replaced with a queue number</td>
</tr>
<tr>
    <td><var><b>tx-queueX-packet</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted frames on a certain queue, the '''X''' should be replaced with a queue number</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-runt</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-runt</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted frames shorter than the minimum 64 bytes
     <td>Total count of transmitted frames shorter than the minimum 64 bytes, usually caused by collisions</td>
but with a valid CRC</td>
</tr>
<tr>
    <td><var><b>tx-too-short</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted frames shorter than the minimum 64 bytes</td>
</tr>
<tr>
    <td><var><b>tx-rx-64</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted and received 64 byte frames</td>
</tr>
<tr>
    <td><var><b>tx-rx-64-127</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted and received 64 to 127 byte frames</td>
</tr>
<tr>
    <td><var><b>tx-rx-128-255</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted and received 128 to 255 byte frames</td>
</tr>
<tr>
    <td><var><b>tx-rx-256-511</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted and received 256 to 511 byte frames</td>
</tr>
<tr>
    <td><var><b>tx-rx-512-1023</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted and received 512 to 1023 byte frames</td>
</tr>
<tr>
    <td><var><b>tx-rx-1024-max</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted and received frames larger than 1024 bytes</td>
</tr>
<tr>
    <td><var><b>tx-single-collision</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted frames that made only a single collision and subsequently transmitted successfully</td>
</tr>
</tr>
<tr>
<tr>
     <td><var><b>tx-too-long</b></var> (<em>integer</em>)</td>
     <td><var><b>tx-too-long</b></var> (<em>integer</em>)</td>
     <td>Total count of transmitted packets that were larger than the maximum packet size</td>
     <td>Total count of transmitted packets that were larger than the maximum packet size</td>
</tr>
<tr>
    <td><var><b>tx-underrun</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted underrun packets</td>
</tr>
<tr>
    <td><var><b>tx-unicast</b></var> (<em>integer</em>)</td>
    <td>Total count of transmitted unicast frames</td>
</tr>
</tr>


</table>
</table>


==Menu specific commands==
For example, output of Ethernet stats on hAP ac2 device:
 
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
 
{{Mr-arg-ro-table
|arg=blink
|type=[id, name]
|desc=Blink Ethernet leds
}}
 
{{Mr-arg-ro-table
|arg=monitor
|type=[id, name]
|desc=Monitor ethernet status. [[#Monitor | Read more>>]]
}}
 
{{Mr-arg-ro-table
|arg=reset-counters
|type=[id, name]
|desc=Reset stats counters. [[#Stats | Read more>>]]
}}
 
{{Mr-arg-ro-table
|arg=reset-mac-address
|type=[id, name]
|desc=Reset MAC address to manufacturers default.
}}
 
{{Mr-arg-ro-table-end
|arg=cable-test
|type=string
|desc=Shows detected problems with cable pairs. [[#Detect Cable Problems | <code>Read More >></code>]]
}}
 
==Monitor==
 
<code>/interface ethernet monitor</code> command prints out current link, rate and duplex status of an interface.
 
 
'''Properties:'''
 
{{Mr-arg-table-h
|prop=Property
|desc=Description
}}
 
{{Mr-arg-ro-table
|arg=auto-negotiation
|type=done {{!}} incomplete
|desc=Current auto negotiation status:
* <var>done</var> - negotiation completed
* <var>incomplete</var> - negotiation failed or not yet completed
}}
 
{{Mr-arg-ro-table
|arg=default-cable-settings
|type=short {{!}} standard
|desc=Default cable length setting (only applicable to NS DP83815/6 cards)
* <var>short</var> - support short cables
* <var>standard</var> - support standard cables
}}
 
{{Mr-arg-ro-table
|arg=full-duplex
|type=yes {{!}} no
|desc=Whether transmission of data occurs in two directions simultaneously
}}
 
{{Mr-arg-ro-table
|arg=rate
|type=10Mbps {{!}} 100Mbps {{!}} 1Gbps
|desc=Actual data rate of the connection.
}}
 
{{Mr-arg-ro-table
|arg=status
|type=link-ok {{!}} no-link {{!}} unknown
|desc=Current link status of an interface
* <var>link-ok</var> - the card is connected to the network
* <var>no-link</var> - the card is not connected to the network
* <var>unknown</var> - the connection is not recognized (if the card does not report connection status)
}}
 
{{Mr-arg-ro-table-end
|arg=phy-regs
|type=
|desc=List of Ethernet PHY registers
}}
 
 
Example output of ethernet status:
<pre>
<pre>
[admin@MikroTik] /interface ethernet> monitor ether1
[admin@MikroTik] > /interface ethernet print stats
            status: link-ok
                       name:           ether1 ether2         ether3       ether4 ether5
  auto-negotiation: done
            driver-rx-byte: 182 334 805 898      0 5 836 927 820    24 895 692      0
              rate: 1Gbps
           driver-rx-packet:   4 449 562 546      0  4 320 155 362      259 449      0
      full-duplex: yes
            driver-tx-byte:   15 881 099 971      0 70 502 669 211    60 498 056    53
 
           driver-tx-packet:       52 724 428      0     54 231 229      106 498      1
</pre>
                  rx-bytes: 178 663 398 808      0 5 983 590 739 1 358 140 795      0
 
              rx-too-short:                0     0             0            0      0
 
                     rx-64:       12 749 144      0       362 459      125 917      0
==Detect Cable Problems==
                 rx-65-127:        9 612 406      0    20 366 513      292 189      0
 
                 rx-128-255:       6 259 883      0     1 672 588      261 013      0
In RouterOS v6rc4 and newer releases there is the ability to detect problems with connected cables.
                 rx-256-511:       2 950 578      0        211 380      278 147      0
Cable test can detect problems or measure the approximate cable length if the cable is unplugged on the other end and there is therefore, "no-link".
               rx-512-1023:        3 992 258      0        185 666       163 241      0
RouterOS will tell:
               rx-1024-1518:     119 034 611      0     2 796 559      696 254      0
 
               rx-1519-max:                0     0              0             0     0
* which cable pair is damaged
               rx-too-long:                0     0              0             0     0
* the distance to the problem
              rx-broadcast:      12 025 189      0      1 006 377        64 178      0
* how exactly the cable is broken - short-circuited or open-circuited
                  rx-pause:                0     0             0             0      0
 
              rx-multicast:       4 687 869      0        36 188      220 136     0
This also works if the other end is simply unplugged - in that case, the total cable length will be shown.
               rx-fcs-error:                0      0              0            0      0
 
            rx-align-error:                0     0             0             0      0
This works on '''SXT-G''', '''SXT Lite''', '''RB711G''', '''RB2011''', '''RB750''' series and other devices with the same switch chips, and also the '''Cloud Core''' series devices.
              rx-fragment:                0      0              0            0      0
 
               rx-overflow:                0     0             0             0      0
Here is example output:
                  tx-bytes:  16 098 535 973      0 72 066 425 886  225 001 772      0
<pre>
                     tx-64:       1 063 375      0       924 855        37 877      0
[admin@CCR] > interface ethernet cable-test ether2
                 tx-65-127:       26 924 514      0      2 442 200      959 209      0
        name: ether2
                 tx-128-255:       14 588 113      0       924 746      295 961      0
      status: no-link
                 tx-256-511:       1 323 733      0     1 036 515        33 252      0
  cable-pairs: open:4,open:4,open:4,open:4
               tx-512-1023:       1 287 464      0     2 281 554        3 625      0
</pre>
               tx-1024-1518:       7 537 154      0     48 212 304        64 659      0
 
               tx-1519-max:                0     0             0             0      0
In the above example, cable is not shorted but “open” at 4 meters distance, all cable pairs equally faulty at the same distance from the switch chip.
               tx-too-long:                0     0              0             0     0
 
              tx-broadcast:              590      0        145 800      823 038      0
==Stats==
                  tx-pause:                0      0              0            0      0
RouterOS v3.22 introduces a new command:
              tx-multicast:                0      0      1 039 243        41 716      0
<pre>
              tx-underrun:                0      0              0            0      0
/interface ethernet print stats
               tx-collision:                0     0              0             0     0
</pre>
     tx-excessive-collision:                0     0             0             0      0
This command will display all kinds of other statistics if the interface is supporting them (currently only RB450G ether2-ether5, RB750 ether2-ether5, RB750G ether1-ether5 and also RB1100 ether1-ether10). Complete list of properties can be found in [[#Read-only_properties | section above]]<br />
     tx-multiple-collision:                0     0              0             0     0
<br />
       tx-single-collision:                0     0             0             0      0
For example, output of ethernet stats on RB450G:
     tx-excessive-deferred:                0     0             0             0      0
<pre>
               tx-deferred:                0     0              0             0     0
[admin@MikroTik] /interface ethernet> print stats  
         tx-late-collision:                0     0             0             0      0
                       name: ether1-gateway ether2-local ether3-local ether4-local ether5-local
              rx-broadcast:                22          31          3666        11         
                  rx-pause:               0           0            0            0           
              rx-multicast:               4           7            1423        5         
              rx-fcs-error:               0            0            2            0           
            rx-align-error:               0           0            0            0         
                  rx-runt:               0           0           0            0         
              rx-fragment:                0           0           1            0          
                     rx-64:               0           0           0            0         
                 rx-65-127:               8            14          21598       10         
                 rx-128-255:               0           0            0            0          
                 rx-256-511:               18          24          2245        6         
               rx-512-1023:               28926       7649        371938      24476        
               rx-1024-1518:               0           0           0            0         
               rx-1519-max:                0           0           0           0          
               rx-too-long:                0           0           0           0          
              rx-overflow:                0           0           0           0          
                  rx-bytes:               15337844    4063737     199738064    12975401   
               tx-broadcast:                13          13          1496        8         
                  tx-pause:                0           0           0           0          
              tx-multicast:                13          13          1496        8         
               tx-underrun:                0           0           0           0          
                     tx-64:               0           0            0            0          
                 tx-65-127:               26           26          2992        16         
                 tx-128-255:               0           0            0           0         
                 tx-256-511:               0           0            0            0          
               tx-512-1023:               0           0            0            0          
               tx-1024-1518:               0           0           0            0         
               tx-1519-max:                0           0           0           0
               tx-too-long:                0           0           0           0
               tx-collision:                0           0           0           0
     tx-excessive-collision:                0           0           0           0
     tx-multiple-collision:                0           0           0           0
       tx-single-collision:                0           0           0           0
     tx-excessive-deferred:                0           0           0           0
               tx-deferred:                0           0           0           0
         tx-late-collision:                0           0           0           0
                  tx-bytes:                2561        2561        294712      1576
 
</pre>
</pre>


Line 459: Line 936:


==PoE out==
==PoE out==
PoE out settings are only available on RouterBOARD devices that have this hardware feature present.  
<p id="shbox"><b>Sub-menu:</b> <code>/interface ethernet poe</code></p>
 
PoE out settings are only available on RouterBOARD devices that have this hardware feature present. See more here: [[PoE-Out]]
See more here: [[PoE-Out]]


{{cont}}
{{cont}}

Latest revision as of 12:39, 14 August 2023

Applies to RouterOS: v3, v4+

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


Summary

Sub-menu: /interface ethernet
Standards: IEEE 802.3


MikroTik RouterOS supports various types of Ethernet interfaces - ranging from 10Mbps to 10Gbps Ethernet over copper twisted pair, 1Gbps and 10Gbps SFP/SFP+ interfaces and 40Gbps QSFP interface. Certain RouterBoard devices are equipped with a combo interface that simultaneously contains two interface types (e.g. 1Gbps Ethernet over twisted pair and SFP interface) allowing to select the most suitable option or creating a physical link failover. Through RouterOS, it is possible to control different Ethernet related properties like link speed, auto-negotiation, duplex mode, etc, monitor a transceiver diagnostic information and see a wide range of Ethernet related statistics.

Properties

Property Description
advertise (10M-full | 10M-half | 100M-full | 100M-half | 1000M-full | 1000M-half | 2500M-full | 5000M-full | 10000M-full; Default: ) Advertised speed and duplex modes for Ethernet interfaces over twisted pair, only applies when auto-negotiation is enabled. Advertising higher speeds than the actual interface supported speed will have no effect, multiple options are allowed.
arp (disabled | enabled | local-proxy-arp | proxy-arp | reply-only; Default: enabled) Address Resolution Protocol mode:
  • disabled - the interface will not use ARP
  • enabled - the interface will use ARP
  • local-proxy-arp - the router performs proxy ARP on the interface and sends replies to the same interface
  • proxy-arp - the router performs proxy ARP on the interface and sends replies to other interfaces
  • reply-only - the interface will only reply to requests originated from matching IP address/MAC address combinations which are entered as static entries in the ARP table. No dynamic entries will be automatically stored in the ARP table. Therefore for communications to be successful, a valid static entry must already exist.
auto-negotiation (yes | no; Default: yes) When enabled, the interface "advertises" its maximum capabilities to achieve the best connection possible.
  • Note1: Auto-negotiation should not be disabled on one end only, otherwise Ethernet Interfaces may not work properly.
  • Note2: Gigabit Ethernet and NBASE-T Ethernet links cannot work with auto-negotiation disabled.
bandwidth (integer/integer; Default: unlimited/unlimited) Sets max rx/tx bandwidth in kbps that will be handled by an interface. TX limit is supported on all Atheros switch-chip ports. RX limit is supported only on Atheros8327/QCA8337 switch-chip ports.
cable-setting (default | short | standard; Default: default) Changes the cable length setting (only applicable to NS DP83815/6 cards)
combo-mode (auto | copper | sfp; Default: auto) When auto mode is selected, the port that was first connected will establish the link. In case this link fails, the other port will try to establish a new link. In case of a reboot, any of the two ports can be running, it depends on which port will successfully establish the link first. When sfp mode is selected, the interface will only work through SFP/SFP+ cage. When copper mode is selected, the interface will only work through RJ45 Ethernet port.
comment (string; Default: ) Descriptive name of an item
disable-running-check (yes | no; Default: yes) Disable running check. If this value is set to 'no', the router automatically detects whether the NIC is connected with a device in the network or not. Default value is 'yes' because older NICs do not support it. (only applicable to x86)
tx-flow-control (on | off | auto; Default: off) When set to on, the port will generate pause frames to the upstream device to temporarily stop the packet transmission. Pause frames are only generated when some routers output interface is congested and packets cannot be transmitted anymore. auto is the same as on except when auto-negotiation=yes flow control status is resolved by taking into account what other end advertises.
rx-flow-control (on | off | auto; Default: off) When set to on, the port will process received pause frames and suspend transmission if required. auto is the same as on except when auto-negotiation=yes flow control status is resolved by taking into account what other end advertises.
full-duplex (yes | no; Default: yes) Defines whether the transmission of data appears in two directions simultaneously, only applies when auto-negotiation is disabled.
l2mtu (integer [0..65536]; Default: ) Layer2 Maximum transmission unit. Read more>>
mac-address (MAC; Default: ) Media Access Control number of an interface.
master-port (name; Default: none) Outdated property, more details about this property can be found in the Master-port page.
mdix-enable (yes | no; Default: yes) Whether the MDI/X auto cross over cable correction feature is enabled for the port (Hardware specific, e.g. ether1 on RB500 can be set to yes/no. Fixed to 'yes' on other hardware.)
mtu (integer [0..65536]; Default: 1500) Layer3 Maximum transmission unit
name (string; Default: ) Name of an interface
orig-mac-address (read-only: MAC; Default: ) Original Media Access Control number of an interface.
poe-out (auto-on | forced-on | off; Default: off) Poe Out settings. Read more >>
poe-priority (integer [0..99]; Default: ) Poe Out settings. Read more >>
sfp-shutdown-temperature (integer; Default: 95) Temperature at which interface will be temporarily turned off due to too high detected SFP module temperature (introduced v6.48).
sfp-rate-select (high | low; Default: high) Allows to control rate select pin for SFP ports.
speed (10Mbps | 10Gbps | 100Mbps | 1Gbps; Default: ) Sets interface data transmission speed which takes effect only when auto-negotiation is disabled.


Read-only properties

Property Description
running (yes | no) Whether interface is running. Note that some interface does not have running check and they are always reported as "running"
slave (yes | no) Whether interface is configured as a slave of another interface (for example Bonding)
switch (integer) ID to which switch chip interface belongs to.

Menu specific commands

Property Description
blink ([id, name]) Blink Ethernet leds
monitor ([id, name]) Monitor ethernet status. Read more>>
reset-counters ([id, name]) Reset stats counters. Read more>>
reset-mac-address ([id, name]) Reset MAC address to manufacturers default.
cable-test (string) Shows detected problems with cable pairs. Read More >>

Monitor

To print out a current link rate, duplex mode, and other Ethernet related properties or to see detailed diagnostics information for transceivers, use /interface ethernet monitor command. The provided information can differ for different interface types (e.g. Ethernet over twisted pair or SFP interface) or for different transceivers (e.g. SFP and QSFP).

Properties

Property Description
advertising (10M-full | 10M-half | 100M-full | 100M-half | 1000M-full | 1000M-half | 2500M-full | 5000M-full | 10000M-full) Advertised speeds and duplex modes for Ethernet interfaces over twisted pair, only applies when auto-negotiation is enabled
auto-negotiation (disabled | done | failed | incomplete) Current auto negotiation status:
  • disabled - negotiation disabled
  • done - negotiation completed
  • failed - negotiation failed
  • incomplete - negotiation not completed yet
default-cable-settings (short | standard) Default cable length setting (only applicable to NS DP83815/6 cards)
  • short - support short cables
  • standard - support standard cables
full-duplex (yes | no) Whether transmission of data occurs in two directions simultaneously
link-partner-advertising (10M-full | 10M-half | 100M-full | 100M-half | 1000M-full | 1000M-half | 2500M-full | 5000M-full | 10000M-full) Link partner advertised speeds and duplex modes for Ethernet interfaces over twisted pair, only applies when auto-negotiation is enabled
rate (10Mbps | 100Mbps | 1Gbps | 2.5Gbps | 5Gbps | 10Gbps | 40Gbps |) Actual data rate of the connection.
status (link-ok | no-link | unknown) Current link status of an interface
  • link-ok - the card is connected to the network
  • no-link - the card is not connected to the network
  • unknown - the connection is not recognized (if the card does not report connection status)
tx-flow-control (yes | no) Whether TX flow control is used
rx-flow-control (yes | no) Whether RX flow control is used
combo-state (copper | sfp) Used combo-mode for combo interfaces
sfp-module-present (yes | no) Whether a transceiver is in cage
sfp-rx-lose (yes | no) Whether a receiver signal is lost
sfp-tx-fault (yes | no) Whether a transceiver transmitter is in fault state
sfp-type (SFP-or-SFP+ | DWDM-SFP | QSFP+) Used transceiver type
sfp-connector-type (SC | LC | optical-pigtail | copper-pigtail | multifiber-parallel-optic-1x12 | no-separable-connector | RJ45) Used transceiver connector type
sfp-link-length-9um (m) Transceiver supported link length for single mode 9/125um fiber
sfp-link-length-50um (m) Transceiver supported link length for multi mode 50/125um fiber (OM2)
sfp-link-length-62um (m) Transceiver supported link length for multi mode 62.5/125um fiber (OM1)
sfp-link-length-copper (m) Supported link length of copper transceiver
sfp-vendor-name (string) Transceiver manufacturer
sfp-vendor-part-number (string) Transceiver part number
sfp-vendor-revision (string) Transceiver revision number
sfp-vendor-serial (string) Transceiver serial number
sfp-manufacturing-date (date) Transceiver manufacturing date
sfp-wavelength (nm) Transceiver transmitter optical signal wavelength
sfp-temperature (C) Transceiver temperature
sfp-supply-voltage (V) Transceiver supply voltage
sfp-tx-bias-current (mA) Transceiver Tx bias current
sfp-tx-power (dBm) Transceiver transmitted optical power
sfp-rx-power (dBm) Transceiver received optical power
eeprom-checksum (good | bad) Whether EEPROM checksum is correct
eeprom (hex dump) Raw EEPROM of the transceiver

Example output of an Ethernet status: 

[admin@MikroTik] > /interface ethernet monitor ether1
                      name: ether1
                    status: link-ok
          auto-negotiation: done
                      rate: 1Gbps
               full-duplex: yes
           tx-flow-control: no
           rx-flow-control: no
               advertising: 10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full
  link-partner-advertising: 10M-half,10M-full,100M-half,100M-full,1000M-full

Example output of a SFP status: 

[admin@MikroTik] > /interface ethernet monitor sfp-sfpplus24
                      name: sfp-sfpplus24
                    status: link-ok
          auto-negotiation: done
                      rate: 10Gbps
               full-duplex: yes
           tx-flow-control: no
           rx-flow-control: no
               advertising: 
  link-partner-advertising: 
        sfp-module-present: yes
               sfp-rx-loss: no
              sfp-tx-fault: no
                  sfp-type: SFP-or-SFP+
        sfp-connector-type: LC
      sfp-link-length-50um: 80m
      sfp-link-length-62um: 30m
           sfp-vendor-name: Mikrotik
    sfp-vendor-part-number: S+85DLC03D
       sfp-vendor-revision: A
         sfp-vendor-serial: STST85S84700155
    sfp-manufacturing-date: 18-12-07
            sfp-wavelength: 850nm
           sfp-temperature: 33C
        sfp-supply-voltage: 3.251V
       sfp-tx-bias-current: 6mA
              sfp-tx-power: -2.843dBm
              sfp-rx-power: -1.203dBm
           eeprom-checksum: good
                    eeprom: 0000: 03 04 07 10 00 00 00 20  40 0c c0 06 67 00 00 00  .......  @...g...
                            0010: 08 03 00 1e 4d 69 6b 72  6f 74 69 6b 20 20 20 20  ....Mikr otik    
                            0020: 20 20 20 20 00 00 00 00  53 2b 38 35 44 4c 43 30      .... S+85DLC0
                            0030: 33 44 20 20 20 20 20 20  41 20 20 20 03 52 00 45  3D       A   .R.E
                            0040: 00 1a 00 00 53 54 53 54  38 35 53 38 34 37 30 30  ....STST 85S84700
                            0050: 31 35 35 20 31 38 31 32  30 37 20 20 68 f0 05 b6  155 1812 07  h...
                            0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........
                            0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........
                            0080: 64 00 d8 00 5f 00 dd 00  8c a0 6d 60 88 b8 71 48  d..._... ..m`..qH
                            0090: 1d 4c 00 fa 17 70 01 f4  31 2d 04 ea 27 10 06 30  .L...p.. 1-..'..0
                            00a0: 31 2d 01 3c 27 10 01 8e  00 00 00 00 00 00 00 00  1-.<'... ........
                            00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........
                            00c0: 00 00 00 00 3f 80 00 00  00 00 00 00 01 00 00 00  ....?... ........
                            00d0: 01 00 00 00 01 00 00 00  01 00 00 00 00 00 00 26  ........ .......&
                            00e0: 21 8a 7f 00 0c cd 14 4c  1d 9c 00 00 00 00 00 00  !......L ........
                            00f0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ........ ........

Detect Cable Problems

Cable test can detect problems or measure the approximate cable length if the cable is unplugged on the other end and there is therefore, "no-link". RouterOS will show:

  • which cable pair is damaged
  • the distance to the problem
  • how exactly the cable is broken - short-circuited or open-circuited

This also works if the other end is simply unplugged - in that case, the total cable length will be shown.

Here is example output: 

[admin@CCR] > interface ethernet cable-test ether2
         name: ether2
       status: no-link
  cable-pairs: open:4,open:4,open:4,open:4

In the above example, the cable is not shorted but “open” at 4 meters distance, all cable pairs equally faulty at the same distance from the switch chip.

Currently cable-test is implemented on the following devices:

  • CCR series devices
  • CRS1xx series devices
  • CRS2xx series devices
  • OmniTIK series devices
  • RB450G series devices
  • RB951 series devices
  • RB2011 series devices
  • RB4011 series devices
  • RB750Gr2
  • RB750UPr2
  • RB751U-2HnD
  • RB850Gx2
  • RB931-2nD
  • RB941-2nD
  • RB952Ui-5ac2nD
  • RB962UiGS-5HacT2HnT
  • RB1100AHx2
  • RB1100x4
  • RBD52G-5HacD2HnD
  • RBcAPGi-5acD2nD
  • RBmAP2n
  • RBmAP2nD
  • RBwsAP-5Hac2nD
  • RB3011UiAS-RM
  • RBMetal 2SHPn
  • RBDynaDishG-5HacD
  • RBLDFG-5acD
  • RBLHGG-5acD

Note: Currently cable-test is not supported on Combo ports.


Stats

Using /interface ethernet print stats command, it is possible to see a wide range of Ethernet related statistics. The list of statistics can differ between RouterBoard devices due to different Ethernet drivers. The list below contains all available counters across all RouterBoard devices. Most of the Ethernet statistics can be remotely monitored using SNMP and MIKROTIK-MIB.


Property Description
driver-rx-byte (integer) Total count of received bytes on device CPU
driver-rx-packet (integer) Total count of received packets on device CPU
driver-tx-byte (integer) Total count of transmitted bytes by device CPU
driver-tx-packet (integer) Total count of transmitted packets by device CPU
rx-64 (integer) Total count of received 64 byte frames
rx-65-127 (integer) Total count of received 65 to 127 byte frames
rx-128-255 (integer) Total count of received 128 to 255 byte frames
rx-256-511 (integer) Total count of received 256 to 511 byte frames
rx-512-1023 (integer) Total count of received 512 to 1023 byte frames
rx-1024-1518 (integer) Total count of received 1024 to 1518 byte frames
rx-1519-max (integer) Total count of received frames larger than 1519 bytes
rx-align-error (integer) Total count of received align error events - packets where bits are not aligned along octet boundaries
rx-broadcast (integer) Total count of received broadcast frames
rx-bytes (integer) Total count of received bytes
rx-carrier-error (integer) Total count of events when carrier sense error occurred
rx-code-error (integer) Total count of received frames with code error
rx-control (integer) Total count of received control or pause frames
rx-error-events (integer) Total count of received frames with active error event
rx-fcs-error (integer) Total count of received frames with incorrect checksum
rx-fragment (integer) Total count of received fragmented frames (not related to IP fragmentation)
rx-ip-header-checksum-error (integer) Total count of received frames with IP header checksum error
rx-jabber (integer) Total count of received jabbed packets - packet that is transmitted longer than the maximum packet length
rx-length-error (integer) Total count of received frames with frame length error
rx-multicast (integer) Total count of received multicast frames
rx-overflow (integer) Total count of received overflowed frames, can be caused when device resources are insufficient to receive a certain frame
rx-pause (integer) Total count of received pause frames
rx-runt (integer) Total count of received frames shorter than the minimum 64 bytes, usually caused by collisions
rx-tcp-checksum-error (integer) Total count of received frames with TCP header checksum error
rx-too-long (integer) Total count of received frames that were larger than the maximum supported frame size by the network device, see the max-l2mtu property
rx-too-short (integer) Total count of received frame shorter than the minimum 64 bytes
rx-udp-checksum-error (integer) Total count of received frames with UDP header checksum error
rx-unicast (integer) Total count of received unicast frames
rx-unknown-op (integer) Total count of received frames with unknown Ethernet protocol
tx-64 (integer) Total count of transmitted 64 byte frames
tx-65-127 (integer) Total count of transmitted 65 to 127 byte frames
tx-128-255 (integer) Total count of transmitted 128 to 255 byte frames
tx-256-511 (integer) Total count of transmitted 256 to 511 byte frames
tx-512-1023 (integer) Total count of transmitted 512 to 1023 byte frames
tx-1024-1518 (integer) Total count of transmitted 1024 to 1518 byte frames
tx-1519-max (integer) Total count of transmitted frames larger than 1519 bytes
tx-align-error (integer) Total count of transmitted align error events - packets where bits are not aligned along octet boundaries
tx-broadcast (integer) Total count of transmitted broadcast frames
tx-bytes (integer) Total count of transmitted bytes
tx-collision (integer) Total count of transmitted frames that made collisions
tx-control (integer) Total count of transmitted control or pause frames
tx-deferred (integer) Total count of transmitted frames that were delayed on its first transmit attempt due to already busy medium
tx-drop (integer) Total count of transmitted frames that were dropped due to already full output queue
tx-excessive-collision (integer) Total count of transmitted frames that already made multiple collisions and never got successfully transmitted
tx-excessive-deferred (integer) Total count of transmitted frames that were deferred for an excessive period of time due to already busy medium
tx-fcs-error (integer) Total count of transmitted frames with incorrect checksum
tx-fragment (integer) Total count of transmitted fragmented frames (not related to IP fragmentation)
tx-carrier-sense-error (integer) Total count of events when carrier sense error occured
tx-late-collision (integer) Total count of transmitted frames that made collision after being already halfway transmitted
tx-multicast (integer) Total count of transmitted multicast frames
tx-multiple-collision (integer) Total count of transmitted frames that made more than one collision and subsequently transmitted successfully
tx-overflow (integer) Total count of transmitted overflowed frames
tx-pause (integer) Total count of transmitted pause frames
tx-all-queue-drop-byte (integer) Total count of transmitted bytes dropped by all output queues
tx-all-queue-drop-packet (integer) Total count of transmitted packets dropped by all output queues
tx-queueX-byte (integer) Total count of transmitted bytes on a certain queue, the X should be replaced with a queue number
tx-queueX-packet (integer) Total count of transmitted frames on a certain queue, the X should be replaced with a queue number
tx-runt (integer) Total count of transmitted frames shorter than the minimum 64 bytes, usually caused by collisions
tx-too-short (integer) Total count of transmitted frames shorter than the minimum 64 bytes
tx-rx-64 (integer) Total count of transmitted and received 64 byte frames
tx-rx-64-127 (integer) Total count of transmitted and received 64 to 127 byte frames
tx-rx-128-255 (integer) Total count of transmitted and received 128 to 255 byte frames
tx-rx-256-511 (integer) Total count of transmitted and received 256 to 511 byte frames
tx-rx-512-1023 (integer) Total count of transmitted and received 512 to 1023 byte frames
tx-rx-1024-max (integer) Total count of transmitted and received frames larger than 1024 bytes
tx-single-collision (integer) Total count of transmitted frames that made only a single collision and subsequently transmitted successfully
tx-too-long (integer) Total count of transmitted packets that were larger than the maximum packet size
tx-underrun (integer) Total count of transmitted underrun packets
tx-unicast (integer) Total count of transmitted unicast frames

For example, output of Ethernet stats on hAP ac2 device: 

[admin@MikroTik] > /interface ethernet print stats
                      name:           ether1 ether2         ether3        ether4 ether5
            driver-rx-byte:  182 334 805 898      0  5 836 927 820    24 895 692      0
          driver-rx-packet:    4 449 562 546      0  4 320 155 362       259 449      0
            driver-tx-byte:   15 881 099 971      0 70 502 669 211    60 498 056     53
          driver-tx-packet:       52 724 428      0     54 231 229       106 498      1
                  rx-bytes:  178 663 398 808      0  5 983 590 739 1 358 140 795      0
              rx-too-short:                0      0              0             0      0
                     rx-64:       12 749 144      0        362 459       125 917      0
                 rx-65-127:        9 612 406      0     20 366 513       292 189      0
                rx-128-255:        6 259 883      0      1 672 588       261 013      0
                rx-256-511:        2 950 578      0        211 380       278 147      0
               rx-512-1023:        3 992 258      0        185 666       163 241      0
              rx-1024-1518:      119 034 611      0      2 796 559       696 254      0
               rx-1519-max:                0      0              0             0      0
               rx-too-long:                0      0              0             0      0
              rx-broadcast:       12 025 189      0      1 006 377        64 178      0
                  rx-pause:                0      0              0             0      0
              rx-multicast:        4 687 869      0         36 188       220 136      0
              rx-fcs-error:                0      0              0             0      0
            rx-align-error:                0      0              0             0      0
               rx-fragment:                0      0              0             0      0
               rx-overflow:                0      0              0             0      0
                  tx-bytes:   16 098 535 973      0 72 066 425 886   225 001 772      0
                     tx-64:        1 063 375      0        924 855        37 877      0
                 tx-65-127:       26 924 514      0      2 442 200       959 209      0
                tx-128-255:       14 588 113      0        924 746       295 961      0
                tx-256-511:        1 323 733      0      1 036 515        33 252      0
               tx-512-1023:        1 287 464      0      2 281 554         3 625      0
              tx-1024-1518:        7 537 154      0     48 212 304        64 659      0
               tx-1519-max:                0      0              0             0      0
               tx-too-long:                0      0              0             0      0
              tx-broadcast:              590      0        145 800       823 038      0
                  tx-pause:                0      0              0             0      0
              tx-multicast:                0      0      1 039 243        41 716      0
               tx-underrun:                0      0              0             0      0
              tx-collision:                0      0              0             0      0
    tx-excessive-collision:                0      0              0             0      0
     tx-multiple-collision:                0      0              0             0      0
       tx-single-collision:                0      0              0             0      0
     tx-excessive-deferred:                0      0              0             0      0
               tx-deferred:                0      0              0             0      0
         tx-late-collision:                0      0              0             0      0

Switch

Sub-menu: /interface ethernet switch

This submenu allows configuration of certain RouterBoard switch chip features. Read more >>.

PoE out

Sub-menu: /interface ethernet poe

PoE out settings are only available on RouterBOARD devices that have this hardware feature present. See more here: PoE-Out

[ Top | Back to Content ]

Retrieved from "https://wiki.mikrotik.com/index.php?title=Manual:Interface/Ethernet&oldid=34598"