Successfully pass the free certification exam at IW Academy and become an Infinet Certified Engineer.
Description
CAUTION
This description of "mint" command is not applicable to WANFleX software RMA version. Before upgrading from RMA to MINT read the documentation carefully and test in the lab.
This document describes the "mint" command in version of the WANFleX software without the TDMA technology support.
The MINT (Mesh Interconnection Networking Technology) architecture gives a functionality to present a radio interface of a unit (as well as a network connected to it) as a traditional Ethernet in a bus topology. Therefore a unit can have several Ethernet interfaces and several pseudo-interfaces (tun, ppp, null etc). Any of Ethernet interfaces can be united in bridging groups which consist of two or more interfaces to increase link capacity. Moreover, routing mode can also be used.
Syntax:
mint IFNAME -type {master | slave} mint IFNAME -mode {mobile | nomadic | fixed} mint IFNAME -nodeid NUMBERID mint IFNAME -name NAME mint IFNAME -netid NUMBER mint IFNAME -key SECRETKEY mint IFNAME -authmode {public | static | remote} mint IFNAME -[no]scrambling mint IFNAME -[no]authrelay -[no]snmprelay -[no]syslog mint IFNAME -[no]replicate [$ACL] mint IFNAME -[no]swborder mint IFNAME -tpcmin {dBm|default} -tpcmax {dBm|default} -tpcadj {+/-dBm|default} mint IFNAME -ratefall 0..8 [0] mint IFNAME -[no]idfs mint IFNAME -[no]autobitrate [+/-DB] | -fixedbitrate mint IFNAME -minbitrate N mint IFNAME -extracost N -fixedcost N -joincost N -meshextracost N mint IFNAME -maxlinks N mint IFNAME -mulcast [0..5] mint IFNAME -loamp N -hiamp N mint IFNAME -maxamp N [-lockdown T] mint IFNAME -hierr N (default 15) mint IFNAME -[no]log [detail] mint IFNAME [-]failover {MAC|auto} mint IFNAME -roaming {leader | enable [multiBS] [global] | disable} mint IFNAME profile N|all [-freq X[,Y,N-M,...] | auto] [-sid X[,Y,..]] [-band NN] [-bitr NN|max] [-miso | -mimo [greenfield | legacy]] [-type {master|mesh|slave}] [-key XXX] [-nodeid N] [{-minbitr XXX [-autobitr [+/-dB]] | -fixedbitr}] [enable | disable | delete] mint IFNAME addnode [-defgw X.X.X.X] [-defmask X.X.X.X] mint IFNAME addnode -mac X:X:X:X:X:X [-key STR] [-note STR] [-maxrate N | -maxmcs N] [-lip X.X.X.X] [-tip X.X.X.X] [-mask X.X.X.X] [-lgw X.X.X.X] [-tgw {X.X.X.X | none}] [-lcost N] [-tcost N] [{-setpri | -addpri} NN | -1] [-mimo | -miso] [-disable | -enable | -delete] mint IFNAME delnode -mac X:X:X:X:X:X mint IFNAME rcmd {-n[t] ADDR | -l[t] | -all | -swg N [-t]} [-self[2]] [-key KEY [-q] [-mask 1,2..16] {"Command" | -file URL} mint rcmdserver -guestKey STRING -fullKey STRING [-mask 1,2..16] mint IFNAME -odr hub mint IFNAME -odr spoke [[-]connected [$ACL]] [[-]kernel [$ACL]] mint IFNAME -odr disable | show mint join IFNAME1 IFNAME2 ... mint disjoin mint IFNAME poll {start [[-]qos ][[-]log] | stop | stat [clear]} mint IFNAME monitor [-s] [-i SEC] [MAC [MAC ...]] mint IFNAME -airupdate {disable | {[active|passive]|force}} [-f ftp://user:pass@host/path/file] mint [IFNAME] map [routes | full | swg] [detail] [-a] [-m] mint [IFNAME] snap[shot] [N] [list | save ["Comment"] | diff [cost|hops|name]] [fix MAC [MAC ...] | del] mint -[no]colormap mint IFNAME ping [-n MAC] ... [-s LEN] [-swg N] [-p PRIO] [-i] mint [IFNAME] info MAC mint [IFNAME] -cluster N NAME mint IFNAME start | stop | restart | clear
Parameters
Parameter | Description |
---|---|
IFNAME | The network interface to which commands are referred. |
-type {mesh | master | slave} | Sets the node type. Three node types are available: "master", "mesh" or "slave".
|
-mode {mobile | nomadic | fixed} | Sets a mode of the node. A mode is defined by the application of the node for the network
|
-nodeid NUMBERID | Sets a node identifier. By default, it is set equal to the device’s serial number. NOTE The "XXX.YYY" format is displayed only if the device's own identifier is also specified in this format. Thus, if you set an identification number in the “XXX.YYY” format at the base station, then the neighbors identifiers will also be shown in this format (no matter how they are defined on the neighboring devices). |
-name NAME | Sets a name for the node. This node name will be displayed in the "mint map" set of commands. A node name should not exceed 16 characters. Spaces in the node name are accepted if placed in quotes. |
-netid NUMBER | Sets a network system identifier (up to 8-digit HEX figure). It must be the same at both ends of the link. |
-key SECRETKEY | Sets a secret key for the current node. The key can be up to 64 characters long and should not contain spaces (or should be placed in quotes). Authentication modes are described by parameters below. |
-authmode {public | static | remote} | Sets the type of nodes authentication.There are three types of nodes authentication available.
|
-[no]authrelay | By this parameter a node having a local database of its neighbors or having an access to a remote authentication server can be configured as an authentication relay. The information about authentication relay will be automatically distributed throughout the MINT network. Nodes which use remote mode of authentication but both do not have access to the "remote" server and do not have the information in their local database will use authentication relay in order to obtain the keys of potential neighbors. |
-[no]snmprelay | A node becomes an SNMP relay. The information about SNMP relay will be automatically distributed throughout the MINT network. |
-[no]syslog | A node become a syslog server. All devices in MINT network will send notification about incidents in own system log to local device. Those incidents will be displayed in syslog of local node. The device keep the syslog server functions until a reboot, after which the command must be re-entered. The information about syslog server will be automatically distributed throughout the MINT network. |
-[no]scrambling | Enables/disables the data scrambling to improve the connection stability. By default is enable. |
-[no]replicate [$ACL] | Allows to make "isolation" of wireless subscriber stations from direct exchange of information with each other in switching mode. NOTE This feature applies only to traffic entering a wireless network from the wired segment of a subscriber station. Inside a wireless network nodes are all accessible to each other at all times. |
-[no]swborder | Enables/disables the "Switch border" regime. In this mode a node becomes "border" between MINT domains, it stops the exchange of information about switching groups and whole data exchange between these domains, but all capabilities of MINT protocol can still be used (obtaining information about the whole MINT network, remote command implementation and so on). |
-tpcmin {dBm|default} -tpcmax {dBm|default} -tpcadj {+/-dBm|default} | Allow to manage ATPC (Automatic Transmit Power Control) function behavior. ATPC function is enabled/disabled by the "rfconfig <interface> pwrctl" command.
|
-hierr N | Sets the percentage of retries after which the system will change the modulation to the lower value. By default is 15. |
-[no]autobitrate [+/-DB] | -fixedbitrate |
|
-minbitrate N | Sets minimal transmitting speed for "autobitrate" mode. |
-ratefall 0..8 [0] | Allows to influence autobitrate mechanism in the following way: it sets upper bitrate index threshold below which errors and retries checks are not performed, just energetic ability to upper bitrate is taken into consideration. Bitrate indexes are from 1 to 8 and correspond with bitrates available on the device’s radio interface (to see bitrate list use the "rf rfX cap" command). "0" ratefall’s value cancels the command. |
-[no]idfs | Enables/disables the Instant DFS function. |
[-meshextracost N] [-extracost N] [-fixedcost N] [-joincost N] |
|
-maxlinks N | Sets the maximum allowed number of simultaneously connected CPEs (radio connections). When this value is reached, other attempts to connect to the base station will be rejected. |
-mulcast [0..5] | Makes the transformation of multicast traffic to unicast. If two or more clients are subscribed to the same multicast stream, a copy of the original stream will be sent to each of them in unicast mode. NOTE Transformation into unicast requires copy of data by the memory, it increases the CPU load of the device. Furthermore, for each of the new unicast streams a certain percentage of attempts may be required that increases traffic even more.
|
[-]failover MAC|auto | Allows to backup the main communication channel, which can be organized on third party manufacturers equipment. Communication is established between Master and Slave devices via the radio and at the same time using the pseudo-radio interface, through the main communication channel. The Master device with enabled "failover" function checks the availability of the MAC address of the remote device through the primary channel. If the address is available, an operation of the backup channel (radio) is blocked. If the address of the Slave device disappears in the primary channel, the backup channel is unlocked and traffic starts to flow over it, until the MAC address of the remote node is available through the primary channel again. If the primary channel is created by InfiNet devices, same as backup, then not only the presence / absence of an alternative link with the monitored node will be taked into account but also the cost of this connection. In this case, the device that provides the lowest cost of communication (best quality) through the radio will become the main one, the second device will turn off its transmitter and go into standby mode. More information about settings of this function is in the paragraph "Examples". |
[-loamp N] [-hiamp N] |
|
-maxamp N [-lockdown T] | Limits the maximum "N" signal level, preventing devices connection. If the SNR level of an already connected neighbor is exceeded, the connection will be terminated.
|
monitor [-s] [-i SEC] [MAC [MAC ...]] | If a MAC address is not specified then all neighbors and candidates of this node will be monitored. The "nodeid" and name of node are permitted to use instead of MAC addresses.
|
start | stop | restart | clear | Starts/stops/restarts/clears the MINT configuration for the specified interface. |
-[no]log [detail] | Allows to control logging settings for MINT protocol. Three different modes are available:
|
Frequency roaming | |
-roaming {leader | enable [multiBS] [global] | disable} | For a flexible management of frequency resource, higher noise immunity and throughput optimization InfiNet Wireless equipment supports frequency roaming capability based on MINT protocol. Roaming is turned off by default – that means that the unit works using fixed radio interface configuration.
|
profile N|all [-freq X[,Y,N-M,...] | auto] [-sid X[,Y,..]] [-band NN] [-bitr NN|max] [-miso | -mimo [greenfield | legacy]] [-type {master|mesh|slave}] [-key XXX] [-nodeid N] [{-minbitr XXX [-autobitr [+/-dB]] | -fixedbitr}] [enable | disable | delete] | Managing roaming profiles.
|
Local Nodes Database | |
addnode [-defgw X.X.X.X] [-defmask X.X.X.X] | Allows to create a local devices database with which this node can establish connections.
|
addnode -mac X:X:X:X:X:X [-key STRING] [-note STRING] [-maxrate N| -maxmcs N] [-lip X.X.X.X] [-tip X.X.X.X] [-mask X.X.X.X] [-lgw X.X.X.X] [-tgw {X.X.X.X | none}] [-lcost N] [-tcost N] [{-setpri | -addpri} NN | -1] [-mimo | -miso] [-disable | -enable | -delete] |
|
delnode -mac X:X:X:X:X:X |
|
Remote Command Management | |
rcmd {-n[t] ADDR | -all | -l[t] -swg N [-t]} [-self[2]] [-key KEY] [-t] [-q] [-mask 1,2..16] {"Command" | -file URL} | Remote command management allows one MINT node to perform commands on one other or all MINT nodes in the network.
ВНИМАНИЕ The maximum "Command" lenght is 60000 characters, but via SSH/Telnet only 512 is available. If your command lenght is longer please use "Command line" mode in the device's web-interface.
|
-rcmdserver [-guestKey STRING] [-fullKey STRING] [-mask 1,2..16] | Disables/enables remote control management mode (enabled by default).
|
Routing in the network with the "hub-and-spoke" topologyOn-Demand Routing (ODR) protocol – is an add-ons over the MINT protocol that allows routing in networks with the "hub" topology without the use of any special routing protocol. The main ODR using advantage is the available network bandwidth increasement by eliminating the service traffic of a separate routing protocol whilst still maintaining dynamic routing functionality. The ODR protocol propagates IP prefixes on the Layer 2 using MINT protocol. ODR is applicable only for the networks with the "hub-and-spoke" topology, when all nodes (spokes) are connected only to a hub node. A "hub-and-spoke" network example is a simple "Point-to-Multipoint" topology where each subscriber terminal has the only wireless connection to the base station. | |
-odr hub | Sets the device as a hub. |
-odr spoke [[-]connected [$ACL]] [[-]kernel [$ACL]] | Sets the device as a spoke. Allows to specify a list of IP addresses/networks using the Access Control List.
|
-odr disable | show |
|
Marker access mode (polling)Polling mode is a method of accessing common radio channel under master station control, which consists in centralized distribution of transmission authorization markers by a master station to slaves. This mode greatly improves operational stability and throughput of master stations under conditions of heavy load and signal level misbalance between different slave units. It is particularly useful when slaves units are at long range from a base station and not in the direct visibility of each other, so that they cannot avoid mutual collisions in the radio channel by listening each other's transmission. The polling regime makes it possible to establish reliable communication between subscribers when the ordinary CSMA/CA wireless access method does not work at all. Despite a slight decrease in the maximum transmission speed, the polling mode substantially increases the total throughput of a base station and provides for its fair distribution between client units. The polling algorithm is so designed as to minimize the protocol overhead while maintaining high efficiency and reliability. The marker access disadvantages in the radio environment are a relatively large initial delay and variation in response time on short packets, which affects critical services, such as online games and telemetry. In addition, two base station sectors with marker access, which are situated closely and operate at the same frequencies, almost completely suppress each other's. | |
poll {start [[-]qos] [[-]log] | stop | stat [clear]} |
Restrictions on the enabling of this mode depend on types of devices in the MINT architecture. |
Over-the-air updateThe "air update" system allows to facilitate the task of the firmware mass upgrade in the MINT network, which includes a large number of similar devices. It is enough to update the firmware manually (or via the task scheduler) only on one device (of each type), the other devices will be updated automatically. | |
-airupdate {disable | {[active|passive]|force}} [-f ftp://user:pass@host/path/file] | Each device can be configured to use either active or passive update mode. Active devices periodically (every half an hour) announce to the MINT network information about the firmware they have, its version and the time of continuous (without reboots) work with this version. All MINT network devices (both active and passive) accept and store information from active devices, selecting the sources that offer the most recent version and work with it for the longest time. After a period of information accumulation, the devices send their requests for a new version to the most appropriate source. Active devices collect requests, group them and send a new version simultaneously to all subscribers using a special protocol of MINT-MTP multicast distribution.
If the firmware is sent to a group of subscribers and the transmission fails, or the connection between the source and the subscriber is lost, the subscriber will stop receiving the update and will repeat the request when receiving the next announcements until the update is successfully completed. |
Setting of "join" connections type | |
join IFNAME1 IFNAME2 ... | The capability to join two or more interfaces of one device in one "mesh" network is an important function of MINT architecture. There is no differences in the settings of these interfaces and protocols which can limit association. This way radio and pseudo radio interfaces can be associated. By reasonably combining join bridges and pseudo-radio interfaces, can be ensured a sufficient number of reliable alternative paths on the network and optimal traffic distribution which allows to eliminate bottlenecks. NOTE If several interfaces are combined by the "join" function, only one of them (any) need to be included in the switching group. |
disjoin | Disjoins interfaces and make them independent. |
Current Connections Information | |
info MAC | Displays information about the "MAC" node status and the traffic route to this node. |
ping [-n MAC] ... [-s LEN] [-swg N] [-p PRIO] [-i] | Sends test packets from the network interface. The the command result is reflected in the system log. If the network node MAC address is not specified, the test packet will be sent to all network nodes in "reliable multicast" mode.
|
map [routes | full | swg] [detail] [-a] [-m] | The parameter is used to get information about the current links of this node. Without arguments, displays information about the MINT network neighbor nodes.
|
snap[shot] [N] [list | save ["Comment"] | diff [cost|hops|name]] | Allows to save data about MINT network neighbor nodes to the device memory that allows to compare it state in future.
|
-[no]colormap | Displays information about the current connections of this node in the same way as the "map" parameter, applying to the neighbors the color indication depending on the signal level between the current device and the neighbor node, as well as the number of retries and transmission errors. |
-cluster N NAME | Allows to combine devices that are in close proximity to each other to the single cluster for easy display on the map.
|
Examples
Display information about the wireless links state using the "mint rf5.0 map detail" command: mint rf5.0 map detail ============================================================================== Interface rf5.0 Node 00043523FA96 "Slave", Id 60758, Nid 0, (Slave) Freq 5550, Band 40, Sid 10101010, autoBitrate 300000 (min 30000), Noise -88 ------- ---------------------------- ------------ ----- ------- ----- ------- Id Name Node SNR Bitrate Retry Options ------------------------------------ ------------ rx/tx rx/tx rx/tx ------- 13659 LINAR 00043514C93B 46/45 300/300 0/0 /M/F load 5/2, pps 3/0, cost 51 pwr 10/10, thr 23/23 dist 2, H08v1.90.46, up 18:20, IP=192.168.103.82 ------- ---------------------------- ------------ ----- ------- ----- ------- 1 active neighbors Total load: 5/2 (rx/tx), 7 (sum) Kbps Total nodes in area: 2 Indicators in the "Options" column can have the following values:
A "?" mark in front of the remote device name indicates that there is no password set on this device. Pay attention to the "*" symbol, which can mean the following:
|
Nodes А and B use the same key and can connect to each other in "public" mode. Node А: mint rf5.0 –key SECRETKEY mint rf5.0 –authmode public Node B: mint rf5.0 –key SECRETKEY mint rf5.0 –authmode public |
Nodes А and B use different access keys, but can connect to each other in "public" mode using local databases. Node А: mint rf5.0 –key SECRETKEY mint rf5.0 –authmode public mint rf5.0 addnode -mac B:B:B:B:B:B -key KEY2 Node B: mint rf5.0 –key KEY2 mint rf5.0 –authmode public mint rf5.0 addnode -mac A:A:A:A:A:A -key SECRETKEY In this case, each node can additionally establish links with other nodes operating in the "public" mode, if their keys match the node's own key. |
Node A uses a local database and acts as an authentication gateway. Node B does not have its own database and uses authentication gateway services in "remote" mode. Node А: mint rf5.0 –key KEY1 mint rf5.0 –authmode static mint rf5.0 –authrelay mint rf5.0 addnode -mac B:B:B:B:B:B -key KEY2 mint rf5.0 addnode -mac С:С:С:С:С:С -key KEY3 Node B: mint rf5.0 –key KEY2 mint rf5.0 –authmode remote Node B will receive neighbor information through the authentication gateway (node A). |
In order to simplify the base station sector configuration in the static description of the subscribers, the command "mint addnode" will add with two parameters "-defgw X.X.X.X" and "-defmask X.X.X.X". mint rf5.0 addnode –mac 000028BAF234 –lip 1.1.1.1 –tip 1.1.1.2 –mask 255.255.255.252 –lcost 120 If the description of the particular subscriber does not specify the exact gateway address or network mask, the default values set in these parameters will be used. Thus, for each subscriber it is enough to specify only dynamically assigned IP address and access key. mint rf5.0 addnode -mac 000435567322 -tip 10.1.1.1 -key SecretKey1 If no access key is specified, it is assumed that it matches the base station key. If no IP address is specified, no action is taken on the addresses. CAUTION Information about the default gateway (which is defined by the "addnode-tgw / addnode –defgw" commands) is not passed to the host unless it has specified an address and a network mask. |
The command removes the network node with the MAC address "00:00:28:BA:F2:34" from the local database. mint rf5.0 delnode –mac 000028BAF234 |
The command sends remote commands to all devices on the MINT network: display device configuration (in the first case), upload command file from ftp (in the second case). mint rf5.0 rcmd -n all -cmd "co sh" mint rf5.0 rcmd -n all -file ftp_name:ftp_pswd@192.168.100.21/1.txt |
Enable polling. mint rf5.0 poll start Display polling statistic by using "stat" parameter. mint rf5.0 poll stat MI=9, MP=60, MT=120, started md=143234, ma=123212, mt=36 pd=312762, pa=22343, pt=11 В выводе отображаются значения следующих параметров:
|
The command displays data for monitoring signal levels. mint rf5.0 monitor The input/output signal levels are displayed relative to the minimum rate for receiving/transmitting. |
The operator decides to replace the firmware on the network with a new, obviously proven one. mint rf5.0 –airupdate force This device does not participate in the automatic update system, does not generate and does not listen to announcements. mint rf5.0 –airupdate disable The operator specifies the path to the ftp server from where the device will download updates. mint rf5.0 -f ftp://user:pass@host/path/file |
Let's make a link reservation. To do this, create a pseudo-radio interface on each device via Ethernet (or vlan). In this case, both devices will communicate with each other via "prf" interfaces using the main link. ifconfig prf0 up prf 0 parent eth0 mint prf0 start On both devices join the "rf5.0" and "prf0" interfaces with the "join" parameter. mint join rf5.0 prf0 Both devices must have at least one switching group between ETH and RF interfaces, which will provide L2 traffic transmission for the time of the main link absence. switch group 1 add eth0 rf5.0 switch group 1 start switch start CAUTION In case the InfiNet Wireless devices are used for the redundant link, it is recommended to use own switching group on each link. In case it is necessary to use one switching group, "rf5.0" and "prf0" interfaces can not be joined with the "join" parameter. Also, it is necessary to explicitly specify the MAC address of the remote device, since the "auto" option will not work. The "failover" function is enabled on the Master radio interface. mint rf5.0 -failover auto As soon as the Master detects that the monitored MAC address is accessible via the "prf0" interface, it will immediately turn off its radio transmitter and put the radio interface into the DOWN state, simultaneously stopping the traffic switching. Having lost synchronization on the radio with the Master, Slave will stop transmitting and go into a standby mode. If the connection to the MAC address being monitored is lost, for example, if the main link fails, the Master will turn on its transmitter and put the radio interface into the UP state. The Slave detects the presence of a signal from the Master and go into a mode of communication. The client traffic will start to be transmitted over the radio again. |
Upgrading current RMA network to MINT
CAUTION
It is recommended to study MINT technology features and test your basic configuration skills on the test devices before complying this instruction.
It is also recommended to consider principles of new network building in advance: will it be Mesh or "Point-to-Multipoint" network, how and what routing will be used, will it be a switched network.
Perform the following actions on each client device:
- Note down or remember MAC address of radio interface which is used to connect to base station. You can view it using command:
ifc rf5.0
- Save current configuration (it is supposed that client device is connected to base station in the moment) using command:
config save
- Upload MINT firmware using command:
fl get user:password@server/file
- Perform restart of all the client devices (one after another) using command:
restart y
- Upload MINT firmware on the base station and restart base station.
After the restart all devices will start with MINT firmware. Upon discovering the old configuration (RMA) new MINT firmware will start neighbor search protocol on all radio interfaces of the device with default parameters (master, autobitrate, hiamp=4). Radio interface parameters will be delivered from the old configuration (at the time of its last saving). This is enougth for device to connect to MINT Network. The devices will lose IP address assigned by RMA.
- Ensure all devices have connected to base station using "mint map" command.
- Assign appropriate IP address on base station radio interface.
ifc rf5.0 10.0.0.254/24 up
- By using "mint rcmd", assign IP addresses on radio interfaces of all client devices addressing them using MAC address (colon in MAC addresses are not necessary).
mint rf5.0 rcmd -node 17:9a:c2:f4:34 -cmd "ifc rf5.0 10.0.0.1/24 up; co save;" mint rf5.0 rcmd -node 17:9a:c3:ad:46 -cmd "ifc rf5.0 10.0.0.2/24 up; co save;" mint rf5.0 rcmd -node 179ab1f391 -cmd "ifc rf5.0 10.0.0.3/24 up; co save;"
After that all client devices will be accessible from base station by IP (if it wasn’t rejected by configuration options).
- Using telnet perform the rest necessary configuration on each device for smooth network functioning (routing and so on).
If IP access is not obtained, it is always possible to verify or correct configuration of client devices using "mint rcmd" command.
mint rf5.0 rcmd -node 0023113231 -cmd "co show" -reply
With "–reply" parameter the command result will be displayed in a local system log (sys log show).