Manual:Interface: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
<div class=manual> | <div class=manual> | ||
<h2>Sub Categories</h2> | <h2>Sub Categories</h2> | ||
| Line 41: | Line 34: | ||
}} | }} | ||
<h2>Summary</h2> | |||
<p><b>Sub-menu:</b> <code>/interface</code></p> | |||
<br /> | |||
<p> | |||
MikroTik RouterOS supports a variety of Network Interface Cards as well as virtual interfaces (like Bonding, Bridge, VLAN etc.). Each of them has its own submenu, but common properties of all interfaces can be configured and read in general interface menu. | |||
</p> | |||
<h2>Properties</h2> | <h2>Properties</h2> | ||
Revision as of 12:07, 16 March 2010
Applies to RouterOS: v3, v4
Sub Categories
|
List of reference sub-pages |
Case studies |
List of examples |
Summary
Sub-menu: /interface
MikroTik RouterOS supports a variety of Network Interface Cards as well as virtual interfaces (like Bonding, Bridge, VLAN etc.). Each of them has its own submenu, but common properties of all interfaces can be configured and read in general interface menu.
Properties
| Property | Description |
|---|---|
| l2mtu (integer; Default: ) | Layer2 Maximum transmission unit. Note that this property can not be configured on all interfaces. Read more>> |
| mtu (integer; Default: ) | Layer3 Maximum transmission unit |
| name (string; Default: ) | Name of an interface |
Read-only properties
| Property | Description |
|---|---|
| bytes (integer/integer) | Total received and transmitted bytes by interface since startup. Read more>> |
| drops (integer/integer) | packets not sent/received because interface queue is full (no free descriptors), dma engine overrun/underrun. Read more>> |
| dynamic (yes|no) | Whether interface is dynamically created |
| errors (integer/integer) | Packets received with some kind of error or not transimitted because of some error. Read more>> |
| packets (integer/integer) | Total count of packets on interface since startup. Read more>> |
| 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) |
| dynamic (yes|no) | Whether interface is dynamically created |
| type (string) | Type of an interface (ethernet, wireless, etc.) |
Traffic monitor
The traffic passing through any interface can be monitored using following command:
/interface monitor-traffic [id | name]
For example monitor ether2 and aggregate traffic. Aggregate is used to monitor total ammount of traffic handled by the router:
[maris@maris_main] > /interface monitor-traffic ether2,aggregate
rx-packets-per-second: 9 14
rx-drops-per-second: 0 0
rx-errors-per-second: 0 0
rx-bits-per-second: 6.6kbps 10.2kbps
tx-packets-per-second: 9 12
tx-drops-per-second: 0 0
tx-errors-per-second: 0 0
tx-bits-per-second: 13.6kbps 15.8kbps
Stats
RouterOS v3.22 introduces a new command:
/interface print stats
This command prints total packets, bytes, drops and errors.
All interfaces that support this feature will be displayed. Some interfaces are not supporting Error and Drop counters at the moment (RB4XX except RB450G ether 2-5), these devices will not display these counters.
Traffic monitor now also displays errors per second, in addition to the usual stats:
/interface monitor-traffic
/interface ethernet print stats will display all kinds of other statistics if the interface is supporting them (currently only RB450G ether2-ether5 and also RB750 ether2-ether5).
[ Top | Back to Content ]