MikroTik RouterOS Device Driver Management

Mikrotik Load Interface Driver 5

Most of the cheap cards do not support this mode. If balance-rr and balance-xor modes are set, then the switch should be configured to evenly distribute packets across all links. On some switches you need to set correct link aggregation protocol, to make balancing work in both directions.

Incoming traffic is not balanced and is received by the current slave.

Used to determine whether link is up or other changes have occurred in the network. This mode provides load balancing and fault tolerance. It is critical that one of the available link monitoring options is enabled. Interface bonding creates a virtual interface that can load balance traffic over multiple interfaces.

Manual Interface/Bonding - MikroTik Wiki

Example connects two ethernet interfaces on a router to the Edimax switch as a single, kodicom security drivers load balanced and fault tolerant link. Provides fault tolerance and load balancing. This mode does not provide load balancing. Provides load balancing and fault tolerance.

Manual Interface

This mode balances outgoing traffic by peer. This mode uses only one active slave to transmit packets. If only one target is set, the target itself may go down. Quick setup guide demonstrates use of the balance-rr bonding mode.

Balance-rr is also useful for bonding several wireless links, however it requires equal bandwidth for all bonded links. First link has more bandwidth so we set it as primary link. Maximum Transmit Unit in bytes.

If bandwidth of one bonded link drops, then total bandwidth of bond will be equal to the bandwidth of the slowest bonded link. Only one slave can be active at a time. Image above illustrates how balance-alb mode works. If switch is used to aggregate links together, then appropriate switch port configuration is required, however many switches do not support balance-rr.

Since frame ordering is mandatory on Ethernet links then any traffic between two devices always flows over the same physical link limiting the maximum speed to that of one interface. Link status determination relies on the device driver. It is not possible to use both methods at the same time due to restrictions in the bonding driver. If device driver does not support this option then link will appear as always up. In the above example, if one of the bonded links were to fail, the bonding driver will still continue to send packets over the failed link which will lead to network degradation.

Mikrotik load interface driver 5

Interface is used as primary output interface. In this mode, the interfaces are aggregated in a group where each slave shares the same speed.

More interfaces can be added to increase throughput and fault tolerance. It includes automatic configuration of the aggregates, so minimal configuration of the switch is needed. Device drivers are included in the system software package and in the additional feature packages.

Slaves in bonding interface will transmit and receive data in sequential order. If a link has been brought up, bonding interface is disabled for up-delay time and after this time it is enabled. When ports are configured with broadcast mode, all slave ports transmit the same packets to the destination to provide fault tolerance. This provides fault tolerance but slows down traffic throughput on some slow machines. But as you already know, balance-tlb is not balancing incoming traffic.

Navigation menu

MikroTik RouterOS Device Driver Management

Address Resolution Protocol for the interface. This mode balances outgoing traffic across the active ports based on the hashed protocol header information and accepts incoming traffic from any active port.

Meaning of each option is described later in this article. Compared to balance-tlb mode, traffic from clients can also use the secondary link to communicate with the router. Each link can be a different speed and duplex mode and no specific switch configuration is required as for the other modes.

Image above illustrates how balance-tlb mode works. If this mode is set, packets are transmitted in sequential order from the first available slave to the last. Another slave only becomes active, if first one fails. Mode is basically the same as balance-tlb but incoming traffic is also balanced. No additional configuration is required for the switch.

Interface bonding does not create a interface with a larger link speed. The transmit algorithm attempts to use as much information as it can to distinguish different traffic flows and balance across the available interfaces. As you can see, it is quite simple to set up. If primary interface fails, only then are other slaves used.

This algorithm will place all traffic to a particular network peer on the same slave. This allows for traffic to a particular network peer to span multiple slaves, although a single connection will not span multiple slaves. This standard also mandates that frames will be delivered in order and connections should not see mis-ordering of packets.

Unplug one of the cables to test if the link monitoring works correctly, you will notice some ping timeouts until arp monitoring detects link failure. The additional slave only becomes active if the primary slave fails.

Upload the required software package containing the required drivers and reboot the router. If a link failure has been detected, bonding interface is disabled for down-delay time.

The same as balance-tlb but received traffic is also balanced. Therefore for communications to be successful, a valid static entry must already exist. Obtain the required software license to enable the functionality of the interface. This also gives assurance that traffic is actually flowing over the links. Active-backup is the best choice in high availability setups with multiple switches that are interconnected.

Device Driver Management

Value should be a multiple of mii-interval. Namespaces Manual Discussion. This value works only with active-backup mode.

MikroTik RouterOS Device Driver Management