Manual:Interface/Ethernet: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 9: | Line 9: | ||
<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> | ||
Revision as of 17:35, 26 March 2020
Applies to RouterOS: v3, v4+
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 | proxy-arp | reply-only; Default: enabled) | Address Resolution Protocol mode:
|
| auto-negotiation (yes | no; Default: yes) | When enabled, the interface "advertises" its maximum capabilities to achieve the best connection possible.
|
| 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. If both ports are connected at the same time (e.g. after reboot), the priority will be the SFP/SFP+ port. 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. Feature is supported on AR724x, AR9xxx, QCA9xxx CPU ports, all CCR ports and all Atheros switch chip ports. |
| 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. Feature is supported on AR724x, AR9xxx, QCA9xxx CPU ports, all CCR ports and all Atheros switch chip ports. |
| 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-rate-select (high | low; Default: high) | |
| 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" |
| rx-1024-1518 (integer) | Total count of received 1024 to 1518 byte packets |
| rx-128-255 (integer) | Total count of received 128 to 255 byte packets |
| rx-1519-max (integer) | Total count of received packets larger than 1519 bytes |
| rx-256-511 (integer) | Total count of received 256 to 511 byte packets |
| rx-512-1023 (integer) | Total count of received 512 to 1023 byte packets |
| rx-64 (integer) | Total count of received 64 byte packets |
| rx-65-127 (integer) | Total count of received 65 to 127 byte packets |
| rx-align-error (integer) | Total count of received align error messages |
| rx-broadcast (integer) | Total count of received broadcast packets |
| rx-bytes (integer) | Total count of received bytes |
| rx-fcs-error (integer) | Total count of received frames with incorrect checksum |
| rx-fragment (integer) | Total count of received fragmented frames |
| rx-multicast (integer) | Total count of received multicast packets |
| rx-overflow (integer) | Total count of received overflowed packets |
| rx-pause (integer) | Total count of received pause frames |
| rx-runt (integer) | Total count of received frames shorter than the minimum 64 bytes but with a valid CRC |
| rx-too-long (integer) | Total count of received packets that were larger than the maximum packet size |
| 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. |
| tx-1024-1518 (integer) | Total count of transmitted 1024 to 1518 byte packets |
| tx-128-255 (integer) | Total count of transmitted 128 to 255 byte packets |
| tx-1519-max (integer) | Total count of transmitted packets larger than 1519 bytes |
| tx-256-511 (integer) | Total count of transmitted 256 to 511 byte packets |
| tx-512-1023 (integer) | Total count of transmitted 512 to 1023 byte packets |
| tx-64 (integer) | Total count of transmitted 64 byte packets |
| tx-65-127 (integer) | Total count of transmitted 65 to 127 byte packets |
| tx-align-error (integer) | Total count of transmitted align error messages |
| tx-broadcast (integer) | Total count of transmitted broadcast packets |
| tx-bytes (integer) | Total count of transmitted bytes |
| tx-fcs-error (integer) | Total count of transmitted frames with incorrect checksum |
| tx-fragment (integer) | Total count of transmitted fragmented frames |
| tx-multicast (integer) | Total count of transmitted multicast packets |
| tx-overflow (integer) | Total count of transmitted overflowed packets |
| tx-pause (integer) | Total count of transmitted pause frames |
| tx-runt (integer) | Total count of transmitted frames shorter than the minimum 64 bytes but with a valid CRC |
| tx-too-long (integer) | Total count of transmitted packets that were larger than the maximum packet size |
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
/interface ethernet monitor command prints out a current link, rate and duplex status of an interface and detailed diagnostics information for transceivers.
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:
|
| default-cable-settings (short | standard) | Default cable length setting (only applicable to NS DP83815/6 cards)
|
| 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
|
| 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 trasnceiver is in cage |
| sfp-rx-lose (yes | no) | Whether a receiver signal is lost |
| sfp-tx-fault (yes | no) | Whether a transceiver laser is in fault state |
| sfp-type (SFP-or-SFP+ | DWDM-SFP | QSFP+) | Used trasnceiver 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) | Detected link length when copper transceiver is used |
| 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 laser 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 ethernet status:
[admin@MikroTik] /interface ethernet> monitor ether1
status: link-ok
auto-negotiation: done
rate: 1Gbps
full-duplex: yes
Example output of an SFP status:
[admin@MikroTik] /interface ethernet> monitor sfp1
name: sfp1
status: link-ok
auto-negotiation: done
rate: 1Gbps
full-duplex: yes
tx-flow-control: no
rx-flow-control: no
sfp-module-present: yes
sfp-rx-lose: no
sfp-tx-fault: no
sfp-connector-type: optical-pigtail
sfp-link-length-copper: 1m
sfp-vendor-name: OEM
sfp-vendor-part-number: SFP-10G-CU1M
sfp-vendor-revision: A0
sfp-vendor-serial: E1309250082
sfp-manufacturing-date: 13-10-10
eeprom: 0000: 03 04 21 00 00 00 00 00 04 00 00 00 67 00 00 >
0010: 00 00 01 00 4f 45 4d 20 20 20 20 20 20 20 20 >
0020: 20 20 20 20 00 00 40 20 53 46 50 2d 31 30 47 >
0030: 43 55 31 4d 20 20 20 20 41 30 20 20 00 00 00 >
0040: 00 00 00 00 45 31 33 30 39 32 35 30 30 38 32 >
0050: 20 20 20 20 31 33 31 30 31 30 20 20 00 00 00 >
Detect Cable Problems
In RouterOS v6rc4 and newer releases there is the ability to detect problems with connected cables. 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 tell:
- 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, 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
RouterOS v3.22 introduces a new command:
/interface ethernet print stats
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 section above
For example, output of ethernet stats on RB450G:
[admin@MikroTik] /interface ethernet> print stats
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
Switch
Sub-menu: /interface ethernet switch
This submenu allows configuration of certain RouterBoard switch chip features. Read more >>.
PoE out
PoE out settings are only available on RouterBOARD devices that have this hardware feature present.
See more here: PoE-Out
[ Top | Back to Content ]