...
MINT link is the link between two units, which use MINT as transport protocol between each other.
MINT encapsulates and transports through MINT link (or links) all traffic and all protocols. Thus, MINT is the only one transport protocol for IW R5000 InfiNet Wireless R5000 family products.
MINT operates between DataLink and Network Layers of the OSI Model. Therefore MINT is capable to encapsulate and carry through link Layer 2 traffic (Ethernet switched data) and Layer 3 traffic (IP routed data).
...
- For radio interfaces MINT is enabled by default, only radio parameters should be configured;
- For Ethernet interfaces MINT-over-Ethernet should be enabled manually (disabled by default) for Ethernet interfaces. In case to perform it, Pseudo-radio interface (PRF) should be created. Each BS and CPE supports such interfaces.
...
In case of multiple MINT routes the protocol would always choose one route for single data frame and would have possibility to re-select new route for another data frame in case of any path characteristics change. Path characteristics are described by aggregated parameter MINT cost.
MINT cost is calculated from the following parameters:
...
- Each MINT unit has full MINT map with all MINT neighbors;
- Each MINT neighbor constantly checks MINTcost between each other;
- Each check is to be done Check is performed each 1-3 s;
- MINT path can be predictably changed due to change in link quality (cost drop).
...
Blue path (2nd path) – MINT decides to switch to 2nd path due to congestion between node H and
node G.
Green path (3rd path) – MINT decides to abandon 2nd path too due to excessive traffic load and switch traffic flow to 3rd path.
...
Steps to configure MINT-over-Ethernet are shown below. Only step 1 4 is different for untagged approach (1a4b) and for vlan based approach (1b4a).
CLI based configuration
...
Now, both MINT interfaces are treated by the unit as single entity, hence MINT exchange information using both legs (wireless and wired).
4. In order to allow IP management traffic reach the unit, switch group need to be configured.
4a. In case of a VLAN based management, a VLAN interface is requiered with parent eth0 interface. Created VLAN interface and one of joined interfaces (rf or prf) need to be added to the switch group. We strongly recommend you to set a switch group number same with the VLAN used to avoid confusion.
...
4b. If no VLAN is used for management, it is enough to add eth0 interface and one of joined interfaces (rf or prf) to the switch group.
| Code Block | ||||
|---|---|---|---|---|
| ||||
Master#console>sw group 100 add eth0 rf5.0 OK. Master#console>sw group 100 start OK. |
5. Create management svi interface, add it to the the group and set the IP address to svi interface.
...