Astra Wireless Documentation
  • Technical documentation
    • Astra Quanta⁣ Technical User Manual
      • Introduction⁣⁣⁣⁣⁣⁣⁣
        • Key Features⁣⁣⁣⁣⁣
        • Hardware Platform⁣⁣⁣⁣⁣
        • Power Supply⁣⁣⁣⁣⁣⁣
        • Lightning⁣ ⁣protection unit⁣⁣⁣⁣⁣
        • Packing list⁣⁣⁣⁣⁣⁣⁣
      • Planning considerations⁣⁣⁣⁣⁣⁣⁣
      • Link pre-configuration in the lab⁣⁣⁣⁣⁣
      • Installation
      • Operation & Administration⁣⁣⁣⁣⁣
        • Web GUI access⁣⁣⁣⁣
        • Dashboard⁣⁣⁣⁣
        • General settings⁣⁣⁣⁣⁣
        • Security settings⁣⁣⁣⁣
        • Radio settings⁣⁣⁣⁣
        • Network settings⁣⁣⁣⁣⁣
        • Switch Settings
        • SNMP settings⁣⁣⁣⁣
        • Spectrum Analyzer⁣⁣⁣⁣⁣
        • Antenna Alignment Tool⁣⁣⁣⁣⁣
        • Maintenance⁣⁣⁣
        • Instant DFS⁣⁣⁣⁣
        • Graphs⁣⁣⁣⁣
      • Troubleshooting⁣⁣⁣⁣⁣⁣⁣⁣⁣
    • Astra Evolution Technical User Manual
      • Introduction⁣⁣⁣⁣⁣⁣
        • Key Features⁣⁣⁣⁣⁣⁣⁣
        • Hardware Platform⁣⁣⁣⁣⁣⁣⁣⁣
        • Power supply⁣⁣⁣⁣⁣⁣⁣
        • Lightning protection unit⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣
        • Synchronization unit⁣⁣⁣⁣⁣⁣⁣
        • ⁣⁣⁣Packing List
      • Planning considerations⁣⁣⁣⁣⁣⁣⁣⁣⁣
      • Link Pre-configuration in the lab⁣⁣⁣⁣⁣⁣⁣⁣⁣
      • Installation⁣⁣⁣⁣⁣
      • Operation & Administration⁣⁣⁣⁣⁣⁣⁣
        • Web GUI access⁣⁣⁣⁣⁣⁣
        • Device Status⁣⁣
        • Basic Settings⁣⁣⁣⁣⁣
          • System Settings⁣⁣⁣⁣⁣⁣
          • Network Settings⁣⁣⁣⁣⁣⁣⁣
          • Link Settings⁣⁣⁣⁣⁣⁣
          • Static Links⁣⁣⁣⁣⁣
          • MAC Switch⁣ ⁣
          • IP Firewall
          • SNMP
          • QoS Options⁣⁣⁣⁣⁣⁣
          • Traffic Shaping⁣⁣⁣⁣⁣⁣⁣
          • Extra Commands⁣⁣⁣⁣⁣⁣
        • Maintenance
        • Spectrum Analyzer
        • DFS
        • Command Line
      • Troubleshooting⁣⁣⁣⁣⁣⁣
        • No access to the local unit⁣⁣⁣⁣⁣
        • The wireless link cannot be established⁣⁣⁣⁣⁣
        • The wireless link is established, but there is no access to the remote device⁣⁣⁣
        • The wireless link throughput is lower than expected⁣⁣⁣
        • Common errors in configuration⁣⁣⁣⁣
        • Emergence Repair Console⁣⁣
        • Unicast-flood detection⁣⁣⁣⁣
    • AstraFleX⁣ Technical User Manual
      • Getting started with AstraFleX User Manual
      • ⁣⁣IP-address format
      • General Purpose Command Set
      • Layer 2 commands set -PHY and MAC
        • ⁣prf ⁣command
        • ⁣⁣lag command (Link Aggregation )
        • ⁣⁣svi command
        • ⁣⁣ltest (radio link test)
        • macf command (addresses mapping)
        • ⁣⁣arp command (ARP protocol)
        • ⁣⁣switch command
        • ⁣⁣dfs (Dynamic Frequency Selection)
        • ⁣⁣lldp command
        • ⁣⁣mint command
        • ⁣⁣rfconfig command
      • ⁣⁣Layer 3 Command set – IP Networking
        • ⁣⁣Ifconfig command (interfaces configuration)
        • tun command (tunnels building)
        • qm command (QoS configuration)
        • ⁣⁣route command (static routes configuration)
        • ⁣⁣arip command
        • ⁣⁣OSPF command
        • ARDA (Aqua Router DAemon)
        • ⁣⁣netstat command (Network statistics)
        • ⁣⁣ipfw command (IP Firewall)
          • ⁣⁣PCAP-filters
        • ⁣⁣loadm command (load meter)
        • ⁣⁣rpcapd command (Remote Packet Capture)
        • ⁣⁣snmpd command (SNMP daemon)
        • ⁣⁣td command (Telnet daemon)
        • ⁣⁣nat command (Network Address Translation)
        • ⁣⁣trapd command (SNMP Traps support)
        • dhcpd command (DHCP Server)
        • ⁣⁣dhcpr command (DHCP relay)
        • dhcpc command (DHCP Client)
        • ⁣⁣vrrp command (VRRP server)
      • ⁣⁣Other commands
    • ⁣NEXT Monitoring System Technical User Manual
      • Description⁣ and operational principles
      • Installation
      • Configuration⁣⁣ ⁣and⁣ management⁣
        • Wireless⁣ ⁣⁣devices preparation
        • Accounts⁣ and user groups
        • Devices⁣ ⁣and links
        • Incident⁣ ⁣⁣management
        • System⁣⁣ ⁣configuration
      • Monitoring⁣ ⁣and management
        • R⁣ep⁣o⁣⁣rts
        • Devices
        • ⁣⁣Incidents
        • MAP
      • Technical support
  • White⁣ papers
    • MINT ⁣⁣⁣technology
    • Dynamic ⁣⁣Frequency ⁣⁣Selection
    • ⁣⁣RADIUS authentication for admin users
    • Security in Astra Wireless Devices
    • ⁣⁣Performance of the Astra Wireless devices
      • Astra Quanta
        • ⁣⁣Thr⁣⁣⁣oughpu⁣t⁣⁣⁣⁣⁣⁣
        • ⁣Packet ⁣⁣performanc⁣e⁣⁣⁣⁣⁣
      • Astra Evolution
        • H22 platform
          • Packet ⁣⁣⁣perfor⁣mance⁣⁣
          • Throug⁣hput⁣⁣⁣⁣⁣⁣
        • H16 platform
          • Packet⁣⁣ ⁣perfor⁣mance⁣⁣
          • ⁣⁣⁣⁣⁣⁣Throug⁣hput⁣⁣⁣⁣⁣⁣⁣
    • ⁣⁣⁣Link ⁣⁣⁣aggregation, balancing and redundancy
      • Astra Evolution
        • Redundancy ⁣⁣⁣with Failover option
        • Redundancy w/o aggregation and AstraMUX
        • Redundancy⁣⁣⁣ ⁣with aggregation and w/o AstraMUX
        • Redundancy ⁣⁣with AstraMUX
        • Full⁣ Duplex
      • Astra Quanta
        • Aggregation ⁣with redundancy ⁣based on⁣ LACP
        • Redundancy⁣⁣⁣ ⁣based ⁣on STP
        • ⁣Redundancy⁣⁣ based on⁣ OSPF
        • ⁣Redundancy with Evolution
    • Beamforming⁣ ⁣technology
    • ⁣⁣⁣Remote ⁣⁣⁣L2 management of Evolution via CLI
    • ⁣⁣⁣Remote ⁣⁣⁣L2 management of Evolution via Web GUI
    • Connectivity with mobile objects⁣⁣⁣⁣
      • Mining industry⁣⁣⁣
      • Railway transport⁣⁣⁣
      • Transport over the water⁣⁣⁣
      • Configuration example⁣⁣⁣
Powered by GitBook

Astra Wireless Technology © 2024. All rights reserved. For more information about available models, sales and technical support, please proceed to https://astrawireless.net/

On this page
  • "rf6.0" subsection
  • Radio link settings
  • Frequency limitation
  • Setting channel type mode
  • "prf" subsection
  • "Join" subsection
  1. Technical documentation
  2. Astra Evolution Technical User Manual
  3. Operation & Administration⁣⁣⁣⁣⁣⁣⁣
  4. Basic Settings⁣⁣⁣⁣⁣

Link Settings⁣⁣⁣⁣⁣⁣

PreviousNetwork Settings⁣⁣⁣⁣⁣⁣⁣NextStatic Links⁣⁣⁣⁣⁣

Last updated 9 months ago

In the "Link Settings" section you can configure the parameters for the Radio interface, for the Pseudo Radio interface and for the Join function.

"rf6.0" subsection

Radio link settings

"rf6.0" subsection is divided in two zones:

  • The panel that describes global link settings, in the left side of the page

  • The panel that describes the radio channel settings which are currently in use, in the right side of the page.

In Master mode:

In Slave mode:

In a point-to-multipoint topology, several profiles can be configured on the Slave device (with parameters for connecting to each base station sector). A subscriber terminal can connect to more than one base station, both in nomadic or mobile mode and in a fixed mode for redundancy purposes (a separate profile for each base station). When trying to establish a wireless connection, the subscriber terminal selects a base station with parameters that provide the best connection quality (RSSI, signal-to-noise ratio, bitrate, errors number, retries, etc.) If connection with the base station is lost, the subscriber terminal will not try to reconnect to it, but will evaluate the signal parameters of all available base stations sectors.

The "Frequency roaming" function is enabled by default (the "auto" option of the Frequency parameter), and allows the subscriber terminal with automatic frequency selection (if it has appropriate radio profiles):

  • Automatically switch from the main base station (roamingleader) to the backup.

  • Automatically switch between different base stations while moving.

  • Automatically switch to a new base station frequency if the current base station frequency has changed.

During frequency roaming process the traffic transmission does not stop.The radio link parameters are described in the table below.

General Settings

Parameter
Description

Enable link

Enable/disable wireless link (enabled by default)

Type

Set the node type to Master or Slave

  • Master: can establish connections with one or more slave type nodes. A master node is used in the configuration of the BS for the PtMP links.

  • Slave: can only connect to one master type node. A slave node is usually used in the configuration of the CPE.

MultiBS

(Slave)

Enabled: when the link parameters deteriorate, the CPE will disconnect from the current base station and try to find the sector with the best parameters values.

Disabled: the CPE will keep the connection with a current base station until the signal is completely lost.

Available for Slave node only.

Mode

This setting determines the operating mode of the device. The operating mode is determined by the application of this node in the network.

  • Fixed - the node has a fixed position in the network, it is constantly on. It is a core node of the network. Recalculation of the MINT connections cost in this mode will occur every 3 seconds.

  • Nomadic - the node can change its geographic location, but data exchange within the network, as a rule, occurs when the node does not move. The cost of MINT connections will be recalculated every 1.5 seconds.

  • Mobile - the node often moves. Data exchange take place during the movement. Recalculation of the cost of MINT connections will occur every second.

  • Drive - mode used for AstraDrive devices.

Compatibility mode

Enable/disable compatibility with previous generation family device. Available for Slave node only.

VBR

(Slave)

The mode at which the service information is carried out at above a minimum bitrate (if possible).

Radar Detection

(Slave)

Enable/disable "Radar Detection" features (a special license with the country code is necessary).

The DFS system performs radar detection and if a radar signal is detected, that frequency is marked as occupied and it can be used again only after a hold-down interval (the link is switched automatically to another frequency).

Max Links

(Master)

Maximum allowed number of connected CPEs ( in the case of radio connection ) . When this value is reached, other attempts to connect to the base station will be rejected.

Use AUX-ODU-SYNC

(Master)

Enable/disable external synchronization unit, in seconds.

Information about AUX-ODU-SYNC connection is described in the section "Synchronization unit".

Sync Hold Time

(Master)

Standalone downtime in case of external synchronization unit disable. Value "0" (zero) disables this parameter control, command to work always is set.

In case of external synchronization unit disable, the devices can synchronously work for some time using own clock signal generator. However, eventually, because of generators frequencies mismatch, the time discrepancy can reach unacceptable values and devices will begin to interfere with each other. In this case, through fixed time the device will stop the transmitter and will stop operation of TDMA until synchronization unit enable.

Frame Size

(Master)

Set the time slot duration (in milliseconds).

  • Consists of transfer time, reception time and guard intervals

  • The range is from 2 to 10 ms in increments of 0.1 ms

  • The recommended values for links PtP at the balanced channel depending on channel width: 2-2,5 ms for 40 and 80 MHz, 2-4 ms for 20 MHz, 3-5 ms for 10 MHz

  • The recommended values for links PtMP depending on channel width: 5 ms for 20, 40 and 80MHz

Auto

(Master)

This option works only for links "PtP" and allows to reduce the window size and a delay at absence or a small amount of traffic. Automatically selects the frame size.

Turbo

(Master)

Increase the throughput in case of link degradation due to errors in the radio. The sliding window of the ARQ algorithm are extended from three to five frames, which increases its efficiency.

DL/UL ratio (%)

(Master)

Set the DL percentage of the time slot:

  • The range is from 20 to 80% in increments of 1%.

  • The empty field enables the mode of flexible DL/UL ratio adjustment depending on traffic load.

Real accepted values depend on the used bandwidth, the frame size and the used modulations. To determine the established value acceptability it is necessary to control parameters (Tx Time Limit/Rx Time Limit) in radio interface statistics. Any of these parameters shall not be less than zero. In the PtMP system with a large number of clients, the ratio of real throughput in this or other way does not match the established DL/UL value. Uplink performance will always be less, because of big overheads of the uplink traffic servicing. In case of a large number of clients value more than 65% practically do not lead to throughput increase in Downlink. Rated speed in Uplink and Downlink (Rx Cap/Tx Cap) is reached only in case of sector full and balanced load by all clients.

Max Distance (Km)

(Master)

Set the maximum operational distance (in kilometers).

Has an impact on guard intervals duration.

The range is from 1 to 100 km in increments of 1 km.

It allows the system to calculate signal propagation time to the furthest subscriber and value of the guard interval between transmission and receiving phases. It is recommended to set 3-5 km more than really measured distance. In case of LOS condition violation or with a large number of reflections larger value as 10-20 km can be required.

STA RSSI (dBm)

(Master)

Set the target power of received radio signal from Slave node at the input of Master node.

  • The range is from -90 to -20 dBm in increments of 1

It allows to reduce the radiation influence from the subscriber units to the neighbor sector due to insufficient suppression of the antenna pattern back lobe.

To achieve maximum TDMA network performance it is important to obtain the highest possible signal level and modulation (bitrates), so transmitter power reducing is a necessary measure. If possible, it is better to try to reduce the impact of clients on neighbor sector (and vice versa), organizational measures (shielding, antennas diversity, etc.).

Regulatory Domain

Allows to limit frequencies available for use on the device, in accordance with the requirements of local legislation.

In some regulatory domains DFS modes are restricted to use.

The list of available regulatory domains is determined by the license.

DFS

(Master)

Enable/disable DFS.

If “DFS only” is set, the DFS system monitors interferences but does not perform radar detection.

If "DFS with Radar Detection" is set, the DFS system monitors interferences and performs radar detection.

For the two radios base stations, the “Instant DFS” option is available (one of the two radios is used for DFS scanning, Radar detection and Spectrum analyzing).

Please note that, in some countries, switching “DFS off” and/or failing to detect public service radar signals are against the regulations and may result in legal action.

Tx Power

Set the output power of the radio interface.

Acts as a top limit for the output power control if the ATPC mechanism is turned on.

Two operating ranges of Tx power are available:

  • “-10...10” (if chosen top limit is 10 dBm or less)

  • “0...27” (if chosen top limit is from 10.5 dBm to 27 dBm)

By default, it is turned on (it is strongly recommended to remains “on”).

The offset parameter is used to adjust the thresholds.

Node Name

Set the name for this node in the network.

By default, it is the "Unknown" node.

This node name will appear on the neighbor lists.

Scrambling

Enable/disable the data scrambling to improve the connection stability (enabled by default).

Trap gateway

Enable/disable gateway for SNMP-traps.

Switch border

Enable/disable the switch border mode. In this mode the unit operates as a "borderline" between the MINT domains, i.e. prevents the distribution of information about the switch groups and data transfer between these domains, while retaining all the capabilities of the MINT protocol (obtaining information about the whole MINT network, sending remote commands etc.).

Use Global Leader option

  • When enabled on the Master, sets it as the global leader node of the MINT network.

  • If enable on Slave, device should search and connect only to a network which has one or more global roaming leaders.

It helps to prevent the creation of locally closed segments that are separated from the main network.

Any MINT device (including AstraMUX) that has direct access from the control center or has access to the Internet can be assigned as a leader.

Network Entry SNR (dB)

  • "low" - this option sets the minimal signal level for the neighbor. Signal level is measured in dB above the noise threshold for the current bitrate. If the level gets lower than specified value the connection with a neighbor will be lost.

  • "high" - this option sets the minimal SNR for a new neighbor. Signal level is measured in dB above the noise threshold for the current bitrate. If neighbor’s signal level is equal or higher than a specified value the node will consider this neighbor to be a candidate

Network Entry EVM (-dB)

  • "high" - minimum EVM value required to establish a radio link between two devices. Value by defaut - 8.

  • "low" - minimum EVM value at which the radio link between devices will not be broken. Value by default -0.

Max SNR (dB)

Limits the maximum signal level, preventing devices connection. If the SNR level of an already connected neighbor is exceeded, the connection will be terminated.

  • Lockdown – blocks attempts to connect from a device whose signal level has exceeded the limit for a specified time in seconds.

Non-decreasing MCS

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 (bitrate list is available in the "Current settings" part).

  • The "0" value cancels the limitation.

RX Attenuation

The noise level measured by the radio module is calculated as the minimum received signal level (RSSI) in a certain period.

The "RX Attenuation" parameter allows manually raise noise threshold on several dB. In this case the radio module won't react to signals below the established threshold. In certain cases it gives the ability to be protected from the low signals interferences which disrupt the radio module as a result of capture effect. This effect is expressed in the fact that the radio module having captured the low signal from the foreign source, tries to strengthen it and to accept completely ignoring a strong signal from the client which has appeared later.

This parameter allows to protect the receiver from the powerful signal source overload.

Multicast Mode

(Master)

Traffic transmission mode:

  • "Multicast" - conventional mode that uses modulation one step lower than the lowest modulation among the traffic receivers when transmitting the "multicast/broadcast" frames. In the case of "multicast" streams information from "IGMP Snooping" module is used to obtain a list of subscribers. Consequently, the list of all connected sector clients is used for the "broadcast" traffic.

  • Transformation of "Multicast" to "Unicast". In case two or more clients are assigned to the same "multicast" stream a copy of source stream will be sent to each of them in the "Unicast" mode.

    • "Unicast 2", "Unicast 3", "Unicast 4", "Unicast 5" - the number of subscribers limitation. Conventional "Multicast" mode will be used when the number is exceeded.

    • "Unicast All" - transformation is always executed.

Transformation to "Unicast" requires memory data copying that increases CPU load. Besides, the use of "Unicast" streams increases the volume of transmitted traffic proportional to the number of subscribers and reduces the sector available throughput.

"Unicast 3" mode is set by default.

Transformation of "Multicast" to "Unicast" via CLI is described in the section "mint command".

Authentication Mode

Set the mode:

  • "static" - the unit can establish connections only with units, which MAC-addresses are listed in the "Static Links" section

  • public - the unit can establish connections with any other units which have the same security key and the corresponding wireless connection settings

  • "remote" - centralized authentication mode with remote server (e.g. RADIUS or relay). In this mode any node can request the information from a remote authentication server (remote authentication server parameters are set using “AAA” command). This means that the node must have an access to this server (e.g. using IP)

On-Demand Routing

Activate routing using the ODR protocol. The following modes are available:

  • "Disable" - routing using ODR is not performed.

  • "Hub" - the device acts as a central node.

  • "Spoke" - the device acts as a peripheral node.

The main advantage of ODR protocol is a network throughput efficient use. Part of the link throughput is usually used by the routing protocol to transmit service information, this part can be released by ODR using. The ODR protocol transmits the hosts IP prefixes using the MINT protocol at the data link layer.

The ODR protocol can only be used in networks with star topology, where all nodes are connected to the central node only. An example of such a network is a point-to-multipoint topology, where each subscriber is connected only to a base station.

The "Spoke Announce" parameter allows to select the type of notifications sent by the spoke node to the hub:

  • "connected" – allows announcing IP addresses/networks set on the spoke’s own interfaces.

  • "kernel" – allows announcing static routes.

  • "full" – allows announcing both types of routes.

  • "none" – forbides all announcement.

OTA

Automatic updates in the MINT domain may be configured in the following modes:

  • “Disabled” - the device does not check if other devices in the MINT domain have a newer software versions.

  • "Passive" - in case a newer software version is detected on one of the neighboring nodes, the device requests and updates the software. The device does not announce own software version.

  • "Active" - the device announces its software version in the MINT domain, making it available to download by other nodes.

Log Level

Set the log level:

  • off

  • normal

  • detailed

Fixed Cost

Allows to set fixed cost value to all routes passing through this interface.

The device will select the route with the lower cost, if any.

Extra Cost

Allows to add additional cost value to all routes passing through this interface.

Join Cost

Allows to add additional cost value to all routes passing through interfaces that are joined to this interface by the join option.

MINT Failover

If the MAC address of a neighbor is specified, then the device will monitor the availability of this address. If the MAC field remains empty - the neighbor's address will be determined automatically.

Current Settings

Parameter
Description

Channel Width

Set the bandwidth of the radio interface in MHz.

Must be the same at both ends of the link.

Frequency

Set the radio interface frequency (in MHz).

Must be the same at both ends of the link.

If it is set to “Auto”, the Slave node is scanning on all frequencies for the Master nodes.

Frequency Range List

Set the frequencies that are allowed to be chosen by the DFS mechanism (available only when the DFS system is enabled).

It is available to support the legacy products.

Note that this option is different from the "Customer Frequency Grid" tool which allows narrowing down the frequency range available in the "Frequency" option from the Radio profile.

Tx Bitrate

Set the maximum operating bitrate of the radio interface.

Acts as a top limit for the bitrate if the Autobitrate mechanism is turned on.

By default, it is turned on (it is strongly recommended to remains “on”).

Adjust the Autobitrate system thresholds when the remote SNR doesn’t have the normal level.

Channel Type

The channel type can be set as:

  • Dual: enables MIMO operational mode with different Tx and Rx data streams (recommended)

  • Single: allows to operate as MIMO with duplicate Tx streams, MISO or SISO depending on the Tx/Rx chain configuration (description below)

Network SID

Set the network system identifier (up to 8-digit HEX figure).

Must be the same at both ends of the link.

Node ID

Set the device identification number.

The parameter is optional.

Node ID can be configured by the administrator for a better representation of a neighbors table (nodes within a wireless network).

Security Key

Set the secret key word for encoding of the protocol messages.

It must be up to 64 characters long, without spaces.

Must be the same at both ends of the link.

On each radio profile, the following options are available (for the Slave unit only):

  • "Disable profile" check box disable a radio profile

  • Add a new radio profile by clicking the «Add Profile» button

  • Copy the radio profile values to a new radio profile by clicking the «Copy» button

  • Remove the radio profile by clicking the «Remove» button.

Frequency limitation

The licensed frequencies range per each bandwidth is displayed in the "rf6.0" subsection, in “Default Frequency Grid” fields. Changes to these default values can be performed in the “Customer Frequency Grid” fields; you can:

  • Limit the licensed frequencies range per each bandwidth (see the screenshot below)

  • Change the center frequency step (for example: 5920-6040/20 means that the step between the center frequencies from 5920 GHz and 6040 GHz is 20 MHz).

The changes performed in “Customer Frequency Grid” will be available in the “Frequency” drop down list from the radio profiles and in DFS page in “Frequency grid” field.

Setting channel type mode

When Channel Type is set to “Single”, then Tx and/or Rx of Chain #1 (for horizontal polarization antenna) can be deactivated:

  • "Chain #0" is connected to the port of the vertical polarized integrated antenna

  • "Chain #1" is connected to the port of the horizontal polarized integrated antenna

If the "Single" mode is selected when, then "Chain #1" column (horizontal polarization) can be disabled for transmission (TX) and / or reception (RX):

NOTE

MIMO, MISO and SISO are defined from the perspective of the data sent by the local unit (not considering the number of physical antennas used for tx and rx like in the classical definition). Therefore, these represent local configuration options. For example, one stream of data can be sent by one chain (1 antenna) corresponding to SISO or the same stream can be sent by both chains (2 antennas) corresponding to MISO.

Settings for "MIMO" mode

Different data streams are transmitted over "Chain #0" and "Chain #1". MIMO uses multiple antennas at both the transmitter and receiver side to improve communication performance and data is sent on both the horizontal and vertical polarizations (data is space-time coded - spatial multiplexing, to improve the reliability of data transmission):

Channel Type: Dual

Radio Chain
#0
#1

Rx

Activated

Activated

Tx

Activated

Activated

Settings for "MISO" mode

The same data streams are transmitted over "Chain #0" and "Chain #1", lowering the performance of the link, but enhancing the ability to transmit data in case of interference or obstacles in transmission path (a special mode of operation of MIMO devices used in NLOS conditions or in a noisy RF environment):

Channel Type: Single

Radio Chain
#0
#1

Rx

Activated

Activated

Tx

Activated

Activated

Settings for "SISO" mode

The data streams are transmitted over Chain #0 (corresponding to vertical polarization) only, lowering the performance of the link, but increasing the link distance (transmitter operates with one antenna as does the receiver; there is no diversity and no additional processing for recomposing the Rx signal):

Channel Type: Single

Radio Chain
#0
#1

Rx

Activated

Deactivated

Tx

Activated

Deactivated

The picture below summarizes the link establishment between two units that are configured in different operational modes. As it can be noticed, only the combination MIMO – SISO is not functional.

"prf" subsection

In the "prf" subsection, you can configure the pseudo-RF link as a MINT network node. The "prf" subsection is available for configurations only after at least one pseudo-RF interface has been created in "Network Settings" section. Pseudo-RF virtual interface is used to provide MINT-over-Ethernet. Every BS or CPE supports PRF interfaces. All parameters available in "prf" subsection are explained in "rf6.0" subsection above:

"Join" subsection

In the "Join" subsection, you can link two or more radio/pseudo-RF interfaces of one unit into one MINT domain. Each of these interfaces may act as an independent MINT network node. The "Join" subsection is available for configurations only after at least one pseudo-RF interface has been created in "Network Settings" section.

In order to join the interfaces, simply enable the check boxes of the corresponding interfaces, as shown in the screenshot below:

Activate the failover function on this interface. For more information about this function proceed to the article "Link aggregation, balancing and redundancy.

"