...
So, here we have network where almost each unit has at least two connections via MINT protocol. Therefore, it is possible to balance traffic via one or second path (or even load balance using both). In case of one link failure, traffic will flow through the another one. Eventually, under certain circumstances the units can always stay connected because both links down situation is very unlikely to happen. It doesn’t really matter what type of physical connection is used (wired or wireless), MINT use any connection. The , the only difference is MINT cost value for each link. So the MINT area main purpose is to create the network there all nodes are familiar with link cost values between all nodes, it can garantee fastest calculation of the best route by taking in account the radio parameters.
| Note | ||
|---|---|---|
| ||
For more information about traffic balancing proceed to article Link aggregation, balancing and redundancy. |
...
Force reboot on remote MINT neighbor
| |||||||
Set new IP address and Default Gateway on remote MINT neighbor
|
| Note | ||
|---|---|---|
| ||
Full syntax of MINT remote commands with different options is described in WANFleX command reference guide Layer 2 commands set -PHY and MAC. |
MINT area prerequisites
In default configuration MINT protocol is enabled and used only between wireless radio interfaces. However, in order to create interconnected MINT area MINT-over-Ethernet interfaces (PRF) are required.
...