> This is part 1 of 3 of the full documentation (pages 1–100 of 202). > The content is paginated: fetch every part to see all of it. > Next part: https://wiki.astrawireless.net/astra-wireless-documentation/llms-full.txt/1 > Page index: https://wiki.astrawireless.net/astra-wireless-documentation/llms.txt # Technical documentation Technical User Manuals # Astrawireless Quasar Technical User Manual **Astrawireless Quasar** is the devices family used for deployment of wireless Point-to-Point links in 4900 - 7100 MHz frequency range, with a maximal performance of up to 2.1 Gbps in 160 MHz band. **Astrawireless Quasar** family combines the wide network functionality of previous generations devices with cutting-edge development in the communication system performance. ## About This Manual This manual provides detailed technical information for the **Astrawireless Quasar** families devices, including system specifications, installation, commissioning, maintenance and troubleshooting. The document is intended to be used by qualified RF engineers/technicians and IT professionals. Qualified personnel should have skills and experience with: * Outdoor/indoor radio equipment installation * Outdoor wireless networks * TCP/IP networking protocols * Safety procedures and instructions for installing antenna equipment * Professional manipulation with electrical equipment and accessories * Safety procedures and instructions for working at height. ## Important Notice ### Legal Rights © Copyright 2026 ⁣Astrawireless. All rights reserved. The information contained in this document is originated by, proprietary, confidential and owned by Astrawireless. No part of this document should be disclosed, reproduced or distributed without the express written permission of Astra Wireless Technology LLC-FZ. Astra Wireless Technology LLC-FZ. reserves the right to change the information contained in this document without prior notice. No part of this document may be considered as a part of any contract or warranty. ### Statement of Conditions Astra Wireless Technology LLC-FZ shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this manual or equipment supplied with it. ### Disclaimer The software is sold on an "AS IS" basis. Astrawireless, its affiliates or its licensors make no warranties, whatsoever, whether express or implied, with respect to the software and the accompanying documentation. Astrawireless specifically disclaims all implied warranties of merchantability and fitness for a particular purpose and non-infringement with respect to the software. Units of product (including all the software) delivered to purchaser hereunder are not fault tolerant and are not designed, manufactured or intended for use or resale in applications where the failure, malfunction or inaccuracy of products carries a risk of death or bodily injury or severe physical or environmental damage (“high risk activities”). High risk activities may include, but are not limited to, use as part of on-line control systems in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, life support machines, weapons systems or other applications representing a similar degree of potential hazard. Astrawireless specifically disclaims any express or implied warranty of fitness for high risk activities. ### Indication of the countries Astrawireless equipment has no geographical limitations for selling and can be supplied to any country of the world. ### Limitation of Liability Astrawireless shall not be liable to the purchaser or to any third party, for any loss of profits, loss of use, interruption of business or for any indirect, special, incidental, punitive or consequential damages of any kind, whether arising under breach of contract, tort (including negligence), strict liability or otherwise and whether based on this agreement or otherwise, even if advised of the possibility of such damages. To the extent permitted by applicable law, in no event shall the liability for damages hereunder of Astrawireless or its employees or agents exceed the purchase price paid for the product by purchaser, nor shall the aggregate liability for damages to all parties regarding any product exceed the purchase price paid for that product by that party (except in the case of a breach of a party’s confidentiality obligations). ### Disposal instructions

### Ports The enclosure has 4 ports: * 1x 2,5 Gigabit Ethernet port (10/100/1000/2,5G Base‑T), RJ‑45 connector: Data + Power. * 1x 10 Gigabit SFP+ port: Data. * 1x SYNC port - for connection external synchronization device\*. * 1x DC IN port - for powering the device directly from a DC source. ### Indication {% hint style="warning" %} NOTE Power and wired statuses indication is performed via glassy plug of the cable gland for ETH, SFP and SYNC ports. {% endhint %}

State	Status	Description
Flash	Initialization	The LEDs on ETH and SFP ports light up with white on second. Then LEDs check is performed: red, blue, green are lightened up sequentially.
Flash	Loading	Only for ETH port: at the beginning green is lightened a few seconds, on the second loading stage switches to blue.
ON/Blue	Power	Only for ETH port.
ON/Green	Speed 1000 Mbps
ON/Light Blue	Speed 2500 Mbps	Only for ETH port.
ON/White	Speed 10000 Mbps	Only for SFP port.
ON/Green	ERConsole stage	Port with the established link lights up with green, the second port remains blue.
ON/Red	Speed 10 Mbps	Only for ETH port.
ON/Yellow	Speed 100 Mbps	Only for ETH port.

\*Pending. ## Accessories To connect the QSR5-Ep/QSR6-Ep models to an external antenna from a third-party manufacturer, some accessories are required. ### Waveguide to coaxial adapter AUX-WCA-5 / AUX-WCA-6

As the QSR5-Ep/QSR6-Ep connector is designed for waveguide of Astrawireless parabolic antennas, antennas from other manufacturers require an adapter for N-type connectors to be installed. ### CAB-RF-1M-LL

The CAB-RF-1M-LL cable is a low-loss coaxial cable with N-type connectors and shrink film at both ends. The cable is one metre long. It is designed to connect Astrawireless's connectorised models QSR5-Ep/QSR6-Ep to external antennas. # Power supply⁣⁣⁣⁣⁣⁣⁣ ### Indoor AC/DC injector IDU-CPE-G(24W)

IDU-CPE-G(24W) is an indoor Gigabit PoE injector which supports 100-240 V input range from the AC mains. IDU-CPE-G(24W) feeds 48 VDC power to the device by injecting it to the CAT5 Ethernet cable.

Parameter	Description
Compatible models	Astra Quanta and Astra Evolution (except E5-BSQ), AUX-ODU-SYNC
Size and weight	97x53.5x33.5 mm, 0.133 kg
Connectors and Interfaces	"LAN" - Ethernet input (Data only) "POE" - Ethernet output (Data+VDC), PASSIVE PoE "PWR" - AC Input
Supported Ethernet Modes	10/100/1000 Mbps
Standards	IEEE 802.3 10Base-T IEEE 802.3U 100Base-TX IEEE 802.3ab 1000Base-T
Input Power Requirements	AC Input Voltage: 100 ... 240 VAC AC Input Current: 0.75 A AC Frequency: 50 to 60 Hz
Consumption	28 W
Operating temperature range	-10 °С ... +40 °С
Operating humidity	Maximum 95 %, Non-condensing
Storage temperature	-40 °С ... +70 °С
Output Power Voltage	48 VDC, 0.5 A
Safety	UL cUL, CE, GS, CCC, FCC, S-MARK, PSE, C-tick, KC(48V0.5A) BIS（24V1A

#### **Ethernet Connectors Pin-out** | Pin | LAN | POE | | --- | --- | --------- | | 1 | A+ | A+ | | 2 | A- | A- | | 3 | B+ | B+ | | 4 | C+ | C+ | | 5 | C- | +VDC/ C- | | 6 | B- | B- | | 7 | D+ | -VDC / D+ | | 8 | D- | -VDC / D- | ### Indoor DC/DC injector for all Astrawireless' units with integrated lightning protection IDU-LA-G(V.01) IDU-LA-G(V.01) is an indoor DC/DC injector. It greatly reduces complexity of the deployment in the cases where DC source is available thus reducing both capital expenditures and total cost of ownership. IDU-LA-G(V.01) may be used for the following purposes: * To serve as a line protection unit for indoor network equipment connected to the second Ethernet port on ODU. * To connect third-party DC power sources to ODU (for example, to power the unit from solar power or wind power sources). #### **Technical parameters**

Parameter	Description
Compatible models	Astra Quanta, Astra Evolution, Astra Quasar
Output Voltage	The same as input
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Pin assignment and polarity	1/2 (+), 3/6 (-), 4/5 (+), 7/8 (-)
Size and Weight	115×65×40 mm, 0.15 kg
Operating temperature range	From 0°С to +40°С

{% hint style="danger" %} CAUTION Exposing unit to the unsupported voltage will result in irreparable damage to the unit! Always observe power requirements! {% endhint %} #### **Connectors description**

#### **Mounting holes sizes**

#### IDU-LA-G(V.01) Packing List

#### **Cable assembly**

### Lightning Protection Unit with Injector AUX-ODU-INJ-G

Optional indoor/outdoor DC injector with built-in lightning protection. It greatly reduces complexity of the deployment in the cases where DC source is available on the rooftop eliminating the need of weather-sealed cabinets. AUX-ODU-INJ-G is compatible with all Astrawireless devices.

Parameter	Description
Size and Weight	34x94x121 mm, 0.28 kg
Connectors and Interfaces	ETH IN - Ethernet input ETH OUT - Ethernet output (data+VDC, protected leg) PWR - DC Input GND - Ground clamp
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Water and Dust Protection	IP66 and IP67
Operating temperature range	-55 °C ... +60 ºC
DC Range	±43...±56 VDC
Lightning Protection	In compliance with: GR-1089 IEC 61000-4-2 (ESD) 15kV (air), 8kV (contact) IEC 61000-4-4 (EFT) 40A (tp = 5/50ns) IEC 61000-4-5 (Lightning) L5, 95A (tp = 8/20us) ETSI ETS 300 386

{% hint style="danger" %} CAUTION Using inappropriate DC source will damage the ODU, which will be not covered by warranty {% endhint %} #### **Ethernet Connectors Pin-out** | Pin | LAN | POE | | --- | ------------ | ------------------- | | 1 | Data pair A+ | Data pair A+ | | 2 | Data pair A- | Data pair A- | | 3 | Data pair B+ | Data pair B+ | | 4 | Data pair C- | +VDC + Data pair C- | | 5 | Data pair C+ | +VDC + Data pair C+ | | 6 | Data pair B- | Data pair B- | | 7 | Data pair D+ | -VDC + Data pair D+ | | 8 | Data pair D- | -VDC + Data pair D- | #### Packing List

AUX-ODU-INJ-G is supplied with a worm clamp TORRO 40-60/9 C7 W4 DIN 3017 - 2 pcs. The clamp is made of stainless steel A4, width 9 mm, allows the installation on a mast with a diameter of 35 to 60 mm. In case of mast diameter more than 60 mm, a similar clamps (up to a 230 mm diameter) with a width of up to 12-13 mm can be used. # Lightning protection unit⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣⁣ ### AUX-ODU-LPU-L

AUX-ODU-LPU-L is a bidirectional external outdoor lightning protection unit for Astrawireless systems designed to withstand the toughest conditions and protect the outdoor unit or the 3rd party networking equipment installed indoors from sudden power surges induced by lightning strikes. Despite the fact every Astrawireless device has a built-in lightning prote ction. AUX-ODU-LPU-L, thanks to its superior GR-1089-grade protection, greatly reduces the risk of damage for the systems operating in harsh environments or difficult-to-reach locations. AUX-ODU-LPU-L is compatible with all Astrawireless devices. {% hint style="warning" %} NOTE The device is not supplied by default and must be ordered separately. {% endhint %}

Parameter	Description
Size and Weight	45x92x55.5 mm, 0.13 kg
Connectors and Interfaces	2 x Ethernet ports Ground clamp
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Water and Dust Protection	IP66 and IP67
Operating temperature range	-55 °C ... +60 ºC
Opening voltage of the arrester	150 V
Lightning Protection	In compliance with: GR-1089 IEC 61000-4-2 (ESD) 15kV (air), 8kV (contact) IEC 61000-4-4 (EFT) 40A (tp = 5/50ns) IEC 61000-4-5 (Lightning) L5, 95A (tp = 8/20us) ETSI ETS 300 386

#### **Ethernet Pin-out** | Pin | Data pair | | --- | --------- | | 1 | A+ | | 2 | A- | | 3 | B+ | | 4 | C- | | 5 | C+ | | 6 | B- | | 7 | D+ | | 8 | D- | #### Packing list

AUX-ODU-LPU-L is supplied with a worm clamp TORRO 40-60/9 C7 W4 DIN 3017. The clamp is made of stainless steel A4, width 9 mm, allows the installation on a mast with a diameter of 35 to 60 mm. In case of mast diameter more than 60 mm, a similar clamp (up to a 230 mm diameter) with a width of up to 12-13 mm can be used. # Packing List Before the installation, please make sure you have all necessary parts and accessories. * Outdoor unit (ODU). * Power supply. * Cable gland (x4). * Shielded RJ-45 connector. * Unshielded RJ-45 connector. * DC connector. * Wrench. * Mounting kit - universal assembling kit for mounting the ODU on standard pole, wall or thick pipe (vertical/horizontal). * Power cord - the model depends on the region, according to the Purchase Order. # Planning considerations⁣⁣⁣⁣⁣⁣⁣⁣⁣ During link planning, such factors as distance, obstacles and the link margin should be taken into account. We strongly recommend to use a planner tool for link planning. ## Range and obstacles Make sure that line of sight is provided when planning the antennas' placement for a point-to-point link in order to achieve maximum range and performance between two antennas. Perform a survey to identify all the obstructions (such as trees or buildings) in the path and to assess the risk of interference. The radio beam is an electromagnetic wave and it is not as thin as a laser beam, for example. The main energy in a radio beam is concentrated along the straight line between the two antennas, inside an area with the shape of an ellipsoid (or a rugby ball). This area is called the 1st Fresnel zone and its exact form and size depend upon the frequency and the signal propagation path length. If most of the 1st Fresnel zone is obstructed, a major part of the radio wave’s electromagnetic energy is lost, which leads to a severe signal quality degradation and as a result to a decreased coverage range or performance. Below is an incomplete list of possible obstructions along the signal propagation path: * Neighboring buildings. * Trees. * Bridges. * Power lines. To obtain the best results, it is necessary to perform a precise analysis of the signal propagation path and possible obstructions that may obstruct the 1st Fresnel zone.

## Antenna Installation General recommendations for antenna installation: * Try to keep the LOS clear of obstructions. In case of installations over vegetation and forest, make sure the direct LOS stays above the trees; in urban environments - above the tallest buildings along the radio path. * The influence of trees can be variable, depending on the season (ice, dew, leaves). Keep in mind that, during spring and summer, leaves can absorb high levels of radio energy. Therefore, when installing during the cold season, over forests and trees without leaves, try to achieve a higher fade margin. * Install the devices at a distance of at least 100-150 meters from power lines having a voltage higher than 35 kV. * Before installation, make sure the devices are located outside the area of water streams and splashes formation, which can affect the enclosure for a long time. * Install antennas as far as possible from other antennas (the recommended distance is at least 2 meters between edges of the antennas). * Reflecting surfaces should be considered (buildings with reflective windows, water surfaces or wet grounds). These can be useful in NLOS situations, if there is no direct clear path between the 2 antennas, so the radio signal needs to be reflected by a surface. However, reflections can also decrease the signal quality when encountered along a clear LOS link, because of fading caused by multipath propagation. * When installing antennas over the water, tune the height bracket within a 1-3 meters range variation, because it can yield significant signal level variations due to multipath fading.

## Spectral aggregation Spectral aggregation should be taken into account when planning composite backhauling links, when installing devices in close proximity to each other on the same pole or in order to implement redundancy and link aggregation. For more information, proceed with the "[Link aggregation, balancing and redundancy](/astra-wireless-documentation/white-papers/link-aggregation-balancing-and-redundancy)" article. The devices located close to each other can cause mutual interference. Do not ignore the spectral aggregation rules, otherwise it can lead to a degradation of the wireless links. The document will provide recommendations on distance and frequency separation for scenarios with and without an external synchronization hub. An external clock source allows you to synchronize the time (the beginning of each second) on multiple devices, up to 7 devices, with an accuracy of less than a microsecond so that all connected devices can turn on the transmitters at the same time. This completely eliminates the mutual influence of neighboring sectors, when one transmitting device with its powerful signal prevents the neighboring device from receiving weak signals from its terminals. Wireless devices synchronization using AUX-ODU-SYNC makes it possible to reuse the frequency within the same site, that is, devices mounted back to back can operate on the same frequency channels. #### Without synchronization * Distance separation (vertical or horizontal) must be at least two meters between the edges of the antennas. * Reduce the transmission power. #### With synchronization In case that the synchronization is enabled, in order to achieve the minimum mutual interference between colocated devices, the distance can be reduced to 1 meter. ### Synchronization settings To perform synchronization using an external hub, each base station sector must be connected to an AUX-ODU-SYNC. The following conditions should be met: * Frame size and DL/UL ratio should be equal on all sync-end units. * The automatic downlink ratio selection is not allowed. {% hint style="warning" %} NOTE The AUX-ODU-SYNC antenna is not included in the standard packing list. {% endhint %} ## Important notice {% hint style="warning" %} NOTE

Changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: * Reorient or relocate the receiving antenna. * Increase the separation between the equipment and receiver. * Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. * Consult the dealer or an experienced radio/TV technician for help. {% endhint %} {% hint style="warning" %} NOTE

On the territory of the European Union, following applies: * the band 5150–5350 MHz is only for indoor use to reduce the potential for harmful interference to co-channel mobile satellite systems and other services. Further, EU regulations enforce EIRP limit in that band of 200mW (23dBm), output power and antenna gain (in case of devices with detachable antenna) shall be chosen accordingly; * in the band 5470-5725 MHz, choice of the transmit power and antenna gain (in case of devices with detachable antenna) shall be such that the equipment still complies with the EIRP limit and EIRP density limit. EIRP limit in that band is 1W (30dBm), EIRP density limit is 50mW/MHz (17dBm/MHz); * in the band 5725-5875 MHz, choice of the transmit power and antenna gain (in case of devices with detachable antenna) shall be such that the equipment still complies with the EIRP density limit. EIRP density limit in that band is 200mW/MHz (23dBm/MHz). {% endhint %} {% hint style="warning" %} NOTE This device contains licence-exempt transmitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canada’s licence-exempt RSS(s). Operation is subject to the following two conditions: * This device may not cause interference. * This device must accept any interference, including interference that may cause undesired operation of the device. This Class B digital apparatus complies with Canadian ICES-003. Following also applies to this radio equipment: * the band 5150–5250 MHz is only for indoor use to reduce the potential for harmful interference to co-channel mobile satellite systems; * for devices with detachable antenna, the maximum antenna gain permitted for devices in the bands 5250-5350 MHz and 5470-5725 MHz shall be such that the equipment still complies with the e.i.r.p. limit; * for devices with detachable antenna, the maximum antenna gain permitted for devices in the band 5725-5850 MHz shall be such that the equipment still complies with the e.i.r.p. limits as appropriate; and * where applicable, antenna type(s), antenna models(s), and worst-case tilt angle(s) necessary to remain compliant with the e.i.r.p. elevation mask requirement set forth in section 6.2.2.3 of the RSS-247 shall be clearly indicated.\ High-power radars are allocated as primary users (i.e. priority users) of the bands 5250-5350 MHz and 5650-5850 MHz and these radars could cause interference and/or damage LE-LAN devices. {% endhint %} {% hint style="warning" %} REMARQUE Cet appareil contient des émetteurs / récepteurs exemptés de licence conformes à la (aux) source(s) RSS de Innovation, Sciences et Développement économique Canada. Le fonctionnement est soumis aux deux conditions suivantes: * Cet appareil ne doit pas causer d'interférences. * Cet appareil doit accepter toutes les interférences, y compris celles susceptibles de provoquer un fonctionnement indésirable de l'appareil. Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada. Ce qui suit s’applique également à cet équipement radio: * la bande 5150–5250 MHz est uniquement destinée à une utilisation en intérieur afin de réduire le risque de brouillage préjudiciable des systèmes de télécommunication par satellite mobiles dans le même canal; * pour les dispositifs avec une antenna détachable, le gain d'antenne maximal autorisé pour les dispositifs des bandes 5250-5350 MHz et 5470-5725 MHz doit être tel que l'équipement soit toujours conforme à la norme e.i.r.p. limite; * pour les dispositifs avec une antenna détachable, le gain d'antenne maximal autorisé pour les dispositifs de la bande 5725-5850 MHz doit être tel que l'équipement soit toujours conforme à la norme e.i.r.p. limites, le cas échéant; et * le cas échéant, type (s) d’antenne, modèle (s) d’antenne et angle (s) d’inclinaison dans le cas le plus défavorable nécessaire pour rester conforme à la norme e.i.r.p. L’exigence de masque d’altitude énoncée à la section 6.2.2.3 du CNR-247 doit être clairement indiquée.\ Les radars à haute puissance sont attribués en tant qu'utilisateurs principaux (utilisateurs prioritaires) des bandes 5250-5350 MHz et 5650-5850 MHz, et ces radars peuvent provoquer des interférences et / ou endommager les dispositifs LE-LAN. {% endhint %} {% hint style="warning" %} Este equipamento não tem direito à proteção contra interferência prejudicial e não pode causar interferência em sistemas devidamente autorizados. Para maiores informações, consulte o site da ANATEL {% endhint %} # Link Pre-configuration in the lab⁣⁣⁣⁣⁣⁣⁣⁣⁣ Usually, before going into the field, it is recommended to pre-configure in the lab the Astrawireless units to verify the link establishment. Take the units out of the package and place them on the table. {% hint style="warning" %} NOTE A minimum set of requirements must be met during devices pre-configuration in the lab: * Make sure that devices are positioned in such a way so that they are not directed right at each other to prevent device damage. * In case of connectorized model configuration, it is recommended to connect the two devices in the link directly, with RF cables and RF attenuators with attenuation of at least 40 dB for each polarization (installation\deinstallation of the RF attenuators and RF cables should only be performed when the devices are switched off). * In case an external antenna or the other unit in the link is connected to only one N-type connector do not switch on the unit. {% endhint %} **Step 1: Scheme connection assembling** The equipment list required for the lab configuration: 1. Outdoor units - 2 pcs. 2. Power supply - 2 pcs. 3. Power cord - 2 pcs. 4. Ethernet cables - 4 pcs. 5. Laptop with Ethernet port available. We will perform the settings mentioned below for each unit and check if the wireless link was established correctly. Use the following instruction to assemble a test scheme: 1. Connect Gigabit Ethernet port at the ODU to the power supply port labeled as "OUT". 2. Connect Ethernet port at the laptop to the power supply port labeled as "IN". 3. Connect the power cord to power supply and plug it to AC mains. {% hint style="warning" %} NOTE Сonnecting third-party equipment via Ethernet (switches, PCs), make sure the PoE, Energy Efficient Ethernet and Green Ethernet functions are disabled on the network interfaces connected to Astra Wireless devices. {% endhint %}

#### **Step 2: Access to the device** Let's access each unit to the default IP address 10.10.10.1 with mask 255.255.255.0 via a web browser. Before, make sure the Ethernet port of the Laptop has an IP address assigned from the same subnetwork as the one for the unit (e.g., set 10.10.10.10 with mask 255.255.255.0). {% hint style="warning" %} NOTE We assume that each unit used in this setup has not been configured before and runs with the factory settings. {% endhint %} Use any letters or numbers for the initial authentication on each unit, for example: * Login: login. * Password: password. {% hint style="warning" %} NOTE We strongly recommend to change your login and password after the first login. {% endhint %} After the first login, let's configure a distinctive name for each unit and set a custom login and password. Go to the "Settings" → "General" section and configure: * Device Name (e.g., Master/Slave). Go to the "Settings" → "Security" → "Change admin password" and configure: * Login (e.g., admin). * Password (e.g., admin). {% hint style="warning" %} NOTE At the next login, type "admin" for the Login and Password (if these are the credentials set before) to access the unit in the privileged mode. {% endhint %} #### **Step 3: Firmware upgrade** Let's upgrade each unit to the latest stable firmware version. In case the laptop has an access to the Internet, a new software version will be detected automatically, update on both devices. Otherwise, the manual firmware upgrade process should be performed: * Download latest release from the ftp server . * In the "Maintenance" section click the "Select file" button and set the path to the downloaded file, or drug it to the specified area. * File will be uploaded to the device. Changes will take force after reboot.

#### **Step 4: Radio parameters configuration** Let's configure the minimum needed radio parameters to establish the link. At the both units, go to the "Settings" → "Radio" section and set this unit with: * Link ID parameter, it must be the same on both sides of the link * Center frequency use values selected at the Link Planning stage. * Channel width: use value selected at the Link Planning stage. * Power limit: set the minimum value in the range, as currently, we are in the lab, and we don't need high output power. The rest of parameters remain with the default values.

#### **Step 5: Check the wireless link status** Let's apply all settings described above for each unit and go to the "Dashboard" section and check if the device status has changed to "Connected". # Installation⁣⁣⁣⁣⁣ ## Mounting kit MONT-KIT-85QR is supplied with all models by default. It allows to make reliable and easy installation of the unit with two-axis adjustment. Mount it to the device from the left or right side, depending on the pole positioning. Assemble the Mounting kit according to the scheme below. The nut must be tightened until the spring washer clicks, without over-tightening.

**Step 1**: attach the Lever (Part 1) to the Holder (Part 2) using positions 4, 5, 6. **Step 2**: attach the finished mount to the device using positions 4, 5, 6. **Step 3**: attach the device and mount to the pole using bracket and positions 7, 8, 9.

Item	Description	Qty
1	Lever (Part 1)	1
2	Holder (Part 2)	1
3	Bracket	1
4	Screw M6x12	5
5	Spring washer 6	5
6	Washer 6	5
7	Screw M8x80	2
8	Spring washer 8	2
9	Washer 8	2

* Screw the waveguide adapter onto the device enclosure and tighten it without applying excessive force; * Rotate the waveguide to ensure that the indicators on the cover are in the required position. * V positioned vertically – transmission is performed using vertical and horizontal polarizations. * X positioned vertically – dual-slant polarisation (±45°) is used for transmission. * Tighten the fasteners. * Connect the AUX-WCA V and H N-type interfaces to the antenna(s) with RF coaxial cables (CAB-RF-1M-LL or similar) and with appropriate connectors. Use cables not longer than 3 m (9.8ft). Tighten the N-type connectors to a torque setting of 1.7 Nm (1.3 lb ft); * Form drip loops near the cable ends at the ODU’s side so that water doesn’t creep towards the ODU connectors; * Weatherproof the N-type connectors (when antenna alignment is complete) using PVC tape and self-amalgamating rubber tape; * Weatherproof the antenna connectors in the same way (unless the antenna manufacturer specifies a different method); * Fix the antenna cables to the supporting structure using site approved methods. Ensure that no undue strain is placed on the ODU or antenna connectors. Ensure that the cables do not flap in the wind, as flapping cables are prone to damage and induce unwanted vibrations in the supporting structure. {% hint style="danger" %} CAUTION In order to prevent device damage make sure that antenna is connected to both N-type connectors with serviceable RF cables before switching on. {% endhint %} Install ODU connector facing down using the mounting kit. Do not tighten the fasteners to the end until the alignment is completed. 2. Connect the Cat5e FTP cable with the cable gland to ODU. 3. Perform ODU grounding. 4. Lay the Cat5e FTP cable from ODU to the power supply. 5. Connect the Cat5e FTP cable with a shielded connector covered by a cap to the "OUT" port of the power supply, having previously touched the power supply connector case with FTP cable connector case. 6. Perform the power supply grounding. 7. Connect the laptop using Cat5e FTP cable to the power supply "IN" port. 8. Connect the power cord to the power supply and then to the power circuit. {% hint style="danger" %} CAUTION The power supply must not operate near a direct heat source, near water or in an environment with high humidity. The cables must be connected in such a way to prevent water flow to the power supply connectors. Use mains supply cords that adhere to safety regulations of the country where the equipment is getting deployed. {% endhint %} Make sure a small loop (at least 10 cable diameters) is provided before the Cat5e FTP cable enter into the building.

{% hint style="danger" %} CAUTION Please note that the pressure equalization system in Astrawireless devices is performed via gas exchange through a cable gland and Ethernet cable jacket with a dry room where the power supply is installed. In order to avoid ODU failure due to moisture entering the device, for example, during the pressure drop during the rain, the cable gland assembly requirements should be met and there are should be no cracks in the Ethernet cable jacket. In addition, you should avoid the Ethernet cable bending near the ODU and pinching with clamps, that can bring to the pressure equalization system fault between the internal volume of the sealed ODU and the external environment during a sudden air temperature change. This may lead to the leakage and device failures. {% endhint %} #### Powering via DC IN port For powering the device via "DC IN" port terminate a cable with the power connector. Power connector scheme is below.

The first DC-in port is supplied with a power source with a voltage ranging from ±12 to ±56 V, while the second contact is connected to zero. Follow requirements: 1. Press on the catchers (1) when the cable is terminated; 2. Use the round cable with diameter from 5mm to 6mm with conductor cross-section from 0.5mm to 2.5mm; 3. FTP Cat5e cable may be used. ## Grounding and lightning protection⁣⁣⁣⁣⁣⁣⁣⁣ This section describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection and equipment location for the wireless device, power supply, AUX-ODU-LPU-L unit (if installed). {% hint style="danger" %} CAUTION Electro-magnetic discharge (lightning) damage is not covered under warranty. The recommendations in this document, when followed correctly, give the user the best protection from the harmful effects of EMD. However 100% protection is neither implied nor possible. {% endhint %} ### Grounding and lightning protection recommendations * The wireless device should be placed on the pole at a height that is at least 1 meter below the top of the pole. In this case, there is a significant probability that the lightning strikes the pole and not the wireless device. The pole should be properly grounded: connected to the building lightning protection circuit according to your local regulations. * All equipment must be connected at stabilized and surge protected power sources which must be properly grounded. * The end of the FTP service cable that is connected to the power supply should be assembled with a shielded RJ-45 connector. The other end of the FTP service cable (connected to the wireless device) should be assembled with unshielded (standard) RJ-45 connector. * The power supply is grounded via a three-conductor power cord and a grounded socket. * AUX-ODU-LPU-L and wireless device grounding is performed using grounding bolt. * Antenna pole and wireless device should be connected to the common ground ring. Grounding cables should be no less than 10AWG thick and must use corrosion-resistant connectors. Grounding bolt is included in the supply list, M6x10 for BS devices, M5x10 for ST devices. ### Requirements to the lightning protection unit AUX-ODU-LPU-L location AUX-ODU-LPU-L is an optional accessory which may be used to serve as a line protection unit for the ODU and for the indoor network equipment connected to the Ethernet port of the IDU. AUX-ODU-LPU-L should be properly assembled, mounted and grounded. General recommendations for installations of lightning protection units: * Install the lightning protection unit on both ends of the cable to protect both the outdoor and the indoor unit. The purpose of the LPU at the top is to protect the ODU from a surge of lightning strike which can hit the long FTP cable run along the height of the pole or on the roof of the building. The purpose of the LPU at the bottom is to protect the IDU and customer equipment. * Use the lightning protection unit to protect all circuits for signal transmission and power supply (video, audio, management signals, Ethernet, etc.) * Regularly (especially before the periods with high thunderstorm activity) check the integrity of lightning protection units, grounding elements and bonding conductors. * The ports of the AUX-ODU-LPU-L device are symmetrical, i.e. the correspondence of ports position to the external unit and the power supply does not matter. Make sure to install the two LPU devices as shown in the scheme below.

{% hint style="danger" %} CAUTION Please note grounding cables should not be connected to the mast. All devices must use separate grounding cable that should be connected to the grounding circuit. The best scenario is when grounding cables are lined parallel to the Ethernet cable. {% endhint %} #### AUX-ODU-LPU-L Mounting AUX-ODU-LPU-L is installed on a mast, using clamp. Attach the grounding cable (min cross-section 2.5 mm2) to the case, using grounding bolt. An M6x10 grounding bolt is included in the supply list.

During AUX-ODU-LPU-L mounting it is necessary to provide a small loop of the FTP cable that should be below the cable gland. This ensures that water is not constantly channeled towards the connector. It will also serve as a cable compensation for the cable linear expansion as the temperature difference result.

{% hint style="danger" %} CAUTION Missing or bad grounding may leave the unit vulnerable to lightning damage. {% endhint %} #### AUX-ODU-LPU-L Cable Ggland Assembly In order to ensure that the cable gland remains sealed under any environmental conditions, please, follow the assembly sequence according to the procedure below: * **Step 1**: Insert the sealing insert into the clamping claw. * **Step 2**: Assemble the cable gland by putting the thread-lock sealing nut, clamping claw with sealing insert and body onto the cable as shown on the figure. * **Step 3**: Insert the clamping claw with sealing insert into the body as shown on the figure. * **Step 4**: Crimp the standard RJ-45 connector onto the cable using crimping tool. Pin-out scheme: T568B wiring standards. {% hint style="danger" %} CAUTION Make sure that the RJ-45 connector is well-crimped. A loose connector can damage the device. Please note that such damage is not covered by the warranty. {% endhint %} * **Step 5**: Insert the RJ-45 connector into the corresponding socket until you hear a click. * **Step 6**: Screw the cable gland body into the port and tighten it. Do not apply excessive force. * **Step 7**: Tighten the thread-lock sealing nut. Do not apply excessive force.

* For rough alignment use the azimuth, elevation angle and suspension height from planner tool report. * For more accurate alignment, use the alignment tool built into the device web interface. * After the initial alignment, the device at the remote side must be fixed. Firstly, the alignment is performed for one device, then for another. ### Alignment tool Use the Alignment tool to point and optimize the antenna in the direction of maximum link signal. The built-in graphical antenna alignment tool displays the signal levels for both devices and both polarizations, this makes an alignment process fast and accurate. To achieve the best performance, RSSI level current values should be -60 ... -40 dBm.

# Operation & Administration⁣⁣⁣⁣⁣ To make changes in the device configuration click the "Changes" button in the upper right corner of the web interface.

The "Applying global changes" window contains a table of parameters whose values have been changed by the user. If you want to undo one change, click the "Roll back" button near the entry. If you need to undo all changes, use the "Roll back all" button at the bottom of the window. Changes will be saved to the device configuration by clicking the "Apply" button.

# Web GUI access⁣⁣⁣⁣ Web User Graphical Interface (**Web GUI**) - is the basic way to configure and operate a wireless unit. **Operation system** starts automatically when you power on the unit, Web GUI is enabled by default. In order to access the unit via Web browser, type an IP address in the address bar. Default IP address is 10.10.10.1 with mask 255.255.255.0. {% hint style="warning" %} NOTE By default any username and any password can be used to login Web GUI. It's strongly recommended to set permanent username and password after the first log in. In order to do this go to the "General settings" section. {% endhint %}

# Dashboard⁣⁣⁣⁣ This section is intended to provide the main information about the wireless unit operation. The Dashboard displays a read-only summary of the current link status information, local and remote device signal strength, capacity , current values of the basic configuration settings and Ethernet network status. ### Device status

Parameter	Description
CPU load	Displays the load percentage of the CPU.
RAM usage	Displays the usage percentage of the random-access memory.
Device uptime	The device operating time since the last reboot.
Firmware version	The firmware version uploaded to the device.

### Wired interface In the "Wired interface status" tab, the wired interfaces status can be monitored, as well as duplex mode and physical interface MAC-address. Current interface load is displayed at the charts for both directions. The wired interface statistic is available on the right side.

Parameter	Description
CRC errors (FCS)	Packets dropped due to checksum mismatch. The possible reasons for the error counter increasement are described in the "Troubleshooting⁣⁣⁣" article.
Oversize packets	Packets larger than 9600 bytes.
Undresize packets (runt)	Packets less than 64 bytes in size.

### Wireless link status The left part of the section contains basic information about link status.

Parameter	Description
Radio interface status	Administrative interface status set in the "Switch" section.
Link status	Wireless connection state.
Device role	Master or Slave.
Link ID	Wireless link can be established only with devices which have the same link ID.
Link uptime	The link operating time since the last outage.
Remote device	Device name set at the remote side.
Center frequency	The downlink and uplink center frequency value set in the "Radio" section manually or by the automatic frequency selection mechanism.
Channel width	The channel width value set in the "Radio" settings.

The right part contains real-time parameters values for local and remote device.

TX parameters: * **Tx power, dBm** - transmit output power level for local and remote device. Automatic or manual if "Automatic transmit power control" is turned off. * **MCS** - selected modulation coding scheme. Automatic or manual if "Automatic modulation control" is turned off. * **Bitrate, Mbps** - available bitrate at transmitter of local and remote device for selected MCS. * **Load, Mbps** - output traffic load on the radio of the local and remote devices. * **Frames** - amount of frames transmitted since the first link was established. * **ARQ, %** - number of frames that were retransmitted RX parameters display values for both polarization: * **RSSI, dBm** - the received signal level. Available values: * **-90...-80 dBm** - close to the receiver sensitivity level, only the lowest modulations are available. * **-80...-60 dBm** - average input range. * **-60...-40 dBm** - the recommended range for achieving best performance. * **>-40 dBm** - input signal level is too high. * **EVM, dBm** - Error vector magnitude is an indicator of the measured input signal quality, telling how far are the received constellation symbols compared to the ideal symbols of the constellation. The parameter value must be as high as possible in absolute value. The recommended level should be less than -21 dB. #### Link statistic The link statistics window can be displayed by clicking "Statistics" button. The "Link Availability" section displays the following information: * The overall wireless link availability since the last device reboot, the number of wireless outages when the connection was unavailable. * Availability statistics for each modulation, for downlink and uplink streams.

The "MCS Usage" section displays amount of packets being transmitted on each modulation (bitrate) for downlink and uplink streams since the last reboot.

### Wired link status PRF This section contains information about Pseudo Radio Interface status. The top part describes prf-interface name, id and role, and the physical parent interface MAC-address. The bottom part describes parameters of joined interfaces (listed on the right side) and link uptime.

# General settings⁣⁣⁣⁣⁣ The "General" section allows to configure basic system parameters, described in the table below. ### Device These parameters are used for identification and link authorization.

Parameter	Description
Device Name	The arbitrary wireless unit name which will be used by network administrators for unit identification. It will be shown in Web GUI side panel.

### SNTP Starts the SNTP time synchronization service. For proper operation, specify the SNTP server time zone and the IP address first. By default, the SNTP service is disabled.

Parameter	Description
SNTP Server Address	The SNTP server IP address, the SNTP service will synchronize the time on the device with. The device must have network access to the SNTP server.
Time Zone	The time zone at the place of device installation. For example: GMT + 5.

### Syslog

Allows to transmit syslog data to the server using the "syslog" protocol. Specify the syslog server address where data should be transmitted. ### LED indicators The power and wired status LED indicators are located in the glass plugs of the cable glands for the ETH, SFP and SYNC ports and are switched on by default. To make the device less visible, the LEDs can be switched off.

# Security settings⁣⁣⁣⁣ The "Security settings" section allows to configure device access and security settings. ### Administrator access Here you may change system administrator account login and password, to change the identification data, click the "Change admin password" button. We strongly recommend you to set a login and password after the first login to the device.

### Radius AAA Here you may configure a device access control using a remote RADIUS server.

Parameter	Description
Address	Set the RADIUS server IP address.
Port	Set the RADIUS server port.
Password	Set the server password.

### Command line interface Allows to enable / disable remote device control by the command line using Telnet and SSH protocols. SSH (Secure Shell) protocol provides secure remote control to network devices. Its functionality is similar to the Telnet protocol, but, unlike Telnet, SSH encodes all protocol messages, including transmitted passwords. By default, only access via Telnet is enabled.

### Network access whitelist This section is used to create a list of subnets from which access to the device will be allowed.

# Radio Settings ## Link Settings

Parameter	Description
Link ID	Wireless link identificator used to avoid connecting a unit to a wrong peer if there are several co-located units using the same center frequency. Specify different ID values for different links. Both ends of the same link must have the same ID.
Center frequency	Set the radio interface frequency (in MHz). Must be the same at both ends of the link.
Channel Width	Set the bandwidth of the radio interface in MHz. Must be the same at both ends of the link.

Parameter

Description

Link ID

Wireless link identificator used to avoid connecting a unit to a wrong peer if there are several co-located units using the same center frequency. Specify different ID values for different links. Both ends of the same link must have the same ID.

Center frequency

Set the radio interface frequency (in MHz).

Must be the same at both ends of the link.

Channel Width

Set the bandwidth of the radio interface in MHz.

Must be the same at both ends of the link.

## Power Settings EIRP value is displayed in the right part of the section and represents the total system power calculated as: Tx Power + Antenna gain + Cable loss (should be specified in the fields below).

Parameter	Description
Power limit	Set the output power of the radio interface in dBm. Available values 0...27 dBm.
Cable loss	In case of external antenna usage, energy fading on cables should be set in accordance to the cable datasheet, in dB.
Antenna gain	In case of external antenna usage, it's gain should be set manually in dBi.
Automatic transmission power control (ATPC)	ATPC enables the transmitter output power of the remote device to be controlled automatically based on the target RSSI value. If the actual RSSI level is lower, the unit increases the remote unit's transmitter output power, and vice versa. ATPC cannot set a value that exceeds the 'Power limit' value. We highly recommend keeping it turned on at all times.
Target RSSI	RSSI value in dBm will be used by ATPC of remote device as target. Optimal values -60...-40 dBm.

## Modulation Settings

Parameter	Description
Automatic modulation control (AMC)	Modulation control algorithm selects the most appropriate modulation-coding scheme at each direction in order to maximize the link performance. By default, it is turned on (it is strongly recommended to remains “on”).
Modulation limit	Set the maximum operating modulation scheme of the radio interface. Acts as a top limit for the modulation if the Autobitrate mechanism is turned on.

Parameter

Description

Automatic modulation control (AMC)

Modulation control algorithm selects the most appropriate modulation-coding scheme at each direction in order to maximize the link performance.

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

Modulation limit

Set the maximum operating modulation scheme of the radio interface.

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

## Frequency Grid The frequency grid allows to limit the scan range in case the center frequency is automatically selected. Also Instant DFS will use these restrictions when monitoring the noise situation. Narrow grid of available frequencies speeds up scanning and link establishing process. Manual center frequency selection will also be limited to the values indicated in the grid. The frequency adjustment step is 1 MHz.

# Switch settings ## Network interface In the "Network Settings" section, there are displayed all physical and logical network interfaces that are already configured. The physical interfaces (eth0 and rf0) are set by default and they cannot be removed. For these two interfaces, you are allowed to change the parameters only. Following layer 2 and 3 logical interfaces can be created with certain parameters by clicking "Add interface" button: * "**VLAN**" can be assigned to a physical interface or to a virtual interface sviX. It is used for the creation of the logical network topology regardless of the physical topology of this network. VLAN allows creating groups of interfaces which have a common set of requirements. It contributes to reducing the multicast traffic in the network, as every VLAN is a separate multicast domain. VLAN usage increases the network security and manageability; * "**SVI**", Switch Virtual Interface is an L3 interface that can be assigned to a switching group for getting access to the unit management via this switching group. This interface becomes part of this switching group and can participate in the exchange of information with other group members so that any packets received by the group (according to its rules), or addressed to the sviX directly, or copies of multicast/broadcast packets, will be received by the unit through the "*sviX"*. This interface allows getting the remote access to the unit management. It is also used for the Management VLAN configuration; * "**PRF**" - Pseudo Radio Interface can be attached to the Ethernet interface in order to allow it to work as a radio interface using the MINT protocol, so that the node can find its neighbors and establish the links with them through this interface. The interface encapsulates MINT-frames into the Ethernet-frames and allows connecting the units of the MINT network using wired interfaces. Also, this interface can be joined with other MINT-interfaces; * "***LAG***" can be assign to two physical interfaces in order to use them as one logical interface for total throughput increasing and system reliability improving. The total throughput of the logical channel represents the sum of the capabilities of associated physical interfaces. In case of failure of any physical channel included in the logical channel, the system will continue to operate, using the rest operable physical channels. Interface allows creating high speed links (between the unit and the network switch, for example) by means of aggregation of the two available Ethernet-interfaces of the unit; Active interfaces are marked with black color, disabled interfaces are displayed with pale overlay, each network interface can be enabled/disabled with check box below it's name. To apply changes to a specific interface, click the tick sign or cross sign to roll back changes.

Following parameters can be configured for each interface: #### Ethernet (ethX) * **X** - interface number is set by default and can not be changed. * **IP address** - IP-address and network mask can be set manually or be obtained automatically via DHCP. The IP address(es) of the "*ethX"* interface is accessible via Ethernet LAN segment only (it won't be accessible via the "*rfX"* interface from other neighbor unit). * **Description** - set the arbitrary interface description (up to 72 characters). * **Mode** - set the interface mode (for example: 1000Base-TX-fullduplex): * The default value is “*Auto*” (recommended) * Optical SFP modules may not work properly in auto-negotiation mode with some devices. In case of troubles with data transmission via the SFP port, it is recommended to set a fixed speed and duplex mode (for example, 1000BaseTX-fullduplex-manual). * Make sure the same duplex mode is set on both devices.

#### Radio interface (rfX) * **X** - interface number is set by default and can not be changed. * **IP address** - IP-address and network mask can be set manually or be obtained automatically via DHCP. * **Description** - set the arbitrary interface description (up to 72 characters).

#### Pseudo Radio Interface (prfX) * **X** - interface number is determined by the numerical order for this interface type at the time of creation. * **IP address** - IP-address and network mask can be set manually or be obtained automatically via DHCP. * **Description** - set the arbitrary interface description (up to 72 characters). * **Parent** - set the parent interface to be transmitted the encapsulated packets (assign the PRF interface to the physical Ethernet interface). * **Channel** - set the channel number (from 0 to 3) on which the frames are sent and received by the parent interface. Both PRF interfaces (of the two units in the link) must have the same channel assigned in order to establish the wireless link.

#### VLAN interface (vlanX) * **X** - interface number is set automatically equal to VLAN ID. * **IP address** - IP-address and network mask can be set manually or be obtained automatically via DHCP. * **Description** - set the arbitrary interface description (up to 72 characters). * **Parent** - set the parent interface to be transmitted the encapsulated packets. * **VLAN-id** - configure the VLAN tag (802.1q) for the current interface (from 1 to 4094).

#### Switch Virtual Interface (sviX) * **X** - interface number is set automatically equal to swich group assigned. * **IP address** - IP-address and network mask can be set manually or be obtained automatically via DHCP. This IP-address is used for the management of the unit via interfaces added to binded switch group. * **Description** - set the arbitrary interface description (up to 72 characters). * **Switch group** - set the Switch group number which this interface is assigned to (bind the SVI interface to a switch group).

#### Link aggregation interface (lagX) * **X** - interface number is determined by the numerical order for this interface type at the time of creation. * **IP address** - IP-address and network mask can be set manually or be obtained automatically via DHCP. * **Description** - set the arbitrary interface description (up to 72 characters). * **Mode** - set standard or fast operational mode, the fast mode can only be used, if MINT based device is on the other side of connection. * **Interfaces** - set the parent interfaces to be aggregated.

#### Default gateway Default gateway field allows to set an IP-address of nearest router. ## Switch groups ### Switch configuration The Switch configuration is based on a set of rules for the switching groups: * An unique numeric identifier (1-4999) for each group * Two or more local network interfaces (*ethX, rfX, vlanX, etc*) and a set of rules (filters) which allow placing different types of traffic into different switching groups * Each node can have several switching groups. The same interfaces or group of interfaces can be used in several groups simultaneously * Switching groups are activated on different nodes of the MINT network. The nodes that have the same switching group identifier in their configurations represent a "switching zone" * "Switching zone" exists only within the MINT network segment. ### Switch groups The MINT network can be viewed as one virtual distributed layer-3 switch, where border nodes act as external ports of the virtual switch. The virtual switch task is to transport frames from one external port to another. It is important to understand that switching groups should be created only on the nodes where frames enter from or leave to the "outside" network ("outside" relative to MINT). On the repeater nodes (in mesh topology) there is no need to create switching groups. ### Management connection to the unit For the management purposes, you can create a dedicated Switch Group for all units in the MINT network, attached to the Switch Virtual Interface (SVI). Assign the IP addresses directly on the SVI interface for native management. All packets sent via SVI interface will be distributed only within the assigned switch group. The universal way to configure Management VLAN via dedicated switch group is presented in the figure below. You have to assign the Management IP addresses to "*sviM"* interface which is the management interface of Group M and includes "*vlanX"* (with parent interface "*eth0"*) and "*rf0"* interface:

### Switch Group parameters

«Enable» - this checkbox enables/disables global switch operation.

Parameter	Description
Group #	Displays the Switch Group number. Assign the switch group identifier (must be unique within the MINT network segment).
VLAN-id list	Set the VLAN ID list to be passed via current switch group.
Description	Type a description sentence for the current switch group.
Interfaces	Add Ethernet or/and Radio as Switch Group interface(s) via the «+» button. "Select": pass (selected by default), strip or tag for VLAN tag modification for each added interface. The Interfaces section provides the means to control the VLAN tag processing mode, as each local interface supports three different scenarios: "Pass" - transparent mode, traffic remains unchanged. "Strip" - all tags are stripped. "Tag" - all packets are tagged with the specified VLAN tag. Another option in this field is to remove one or both added interfaces.
Repeater	Enable/disable repeater support. The unit acts as a simple switch, relaying packets to all ports, except the source port.
Action	Set the default action to permit or deny. If there are no switching rules, or if a packet does not match any of them, the default action for the given group will be performed.

# MINT Settings The "MINT settings" section is intended for the MINT protocol configuration. You can find a description of the MIINT technology in the [article](https://wiki.astrawireless.net/astra-wireless-documentation/white-papers/mint-technology). "Interfaces list" section allows to configure MINT (radio and pseudo-radio) interfaces parameters. Radio interface is created by default and can not be deleted. To perform settings of the previously created pseudo-radio interface click "Add interface" button and select the desired interface.

Following parameters are available to configure:

Parameter	Description
MINT on	Enable / disable MINT protocol on the interface.
Node name	Interface name will be displayed in neighbour's list of the MINT network.
Role	MINT interface role. In Slave role interface can only set the connection with one Master interface. In Master role interface can set the connections with one or more (for prf) interfaces with roles Master and Slave.
Key	MINT interfaces should authorize each other before link establishment. Access key must be up to 64 characters long, without spaces and must be the same at both ends of the link.

## Failover Settings Activate the failover function on this interface. For more information about this function proceed to the article [Link ⁣⁣⁣aggregation, balancing and redundancy](https://wiki.astrawireless.net/astra-wireless-documentation/white-papers/link-aggregation-balancing-and-redundancy). Configuring redundancy using the failover function involves creating a PRF connection with the remote device. This connection is used to monitor the availability of the remote device's radio interface MAC address. This MAC address should be specified in the corresponding field.

## Joins list In the "Join" subsection, you can link two or more radio or pseudo-RF interfaces within one to create a single MINT domain. Each interface can act as an independent MINT network node. After joining, they start acting as one. The "Join" subsection is only available for configurations after at least one pseudo-RF interface has been created in the 'Switch Settings' section. To join the interfaces, simply add them by clicking the plus sign and confirming with the tick icon.

# SNMP settings SNMP allows the administrator to gather information about key device parameters and wireless links, including information about changes. The use of any monitoring system helps to timely receive information about the network infrastructure state using Astra devices. Currently, the devices family supports SNMP protocol versions v1 v2c and v3. The SNMP Protocol has two branches, the agent and the management stations: * The agent sends data to the management station. Monitoring system - provides data gathering from all agents in the network. * The monitoring system receives and processes events. * The information is passed through requests and replies with the use of the MIB. * The management station or monitoring system is responsible for decoding the SNMP packets and providing an interface to the administrator. #### General settings This section allow to enable/disable SNMP protocol support.

Parameter	Description
Location	The geographical location where the unit is installed, used as a reference information about the physical device’s location.
Enabled	Enable/disable the SNMP service in the device.
Contact person	A reference information about the device owner.

#### **SNMP v1/v2c**

Parameter	Description
Enabled	Enable/disable the SNMP v.1 and v.2c support. The first version of the SNMP protocol lacks security, that hinders its use for network management, so SNMP v.1 and v.2c operates in read-only mode. Enabled by default.
Community	Set the community name for read-only mode of SNMP v.1 and v.2c, by default: "public". The community name passes along with the data packet in clear text.

#### SNMP v3 Due to the security level of SNMP v.3 is higher than of SNMP v.1 and v.2c, it allows not only the data collection but also to manage devices. Detailed information about the devices management via the monitoring system is available in the corresponding article.

To add an SNMP v3 user, click the corresponding button and fill in the following fields:

Parameter	Description
Login	SNMP v3 user name.
Password	SNMP v3 password.
Security	Security level: "No auth / No privacy" – the lowest security level without authentication and privacy, only Username needs to be set. This level of protection does not allow management via the monitoring system. "Auth / No privacy" – middle level with authentication but without privacy, Username and Password are required. "Auth / Privacy" – highest level with authentication and privacy, Username, Password, Privacy Password and Privacy Protocol should be set.
Readonly	Enable/disable the read-only mode, readonly is set by defaut.
Admin	Enable/disable the full access to all parameters, for example, the ability to reboot the device. By default an access is limited.
Security key	Set the privacy password, it is necessary when privacy is enabled for the required security level.
Security standard	Data encryption standard DES or AES 128

#### SNMP traps The devices polling cycle of the monitoring system is 5 minutes. To speed up the process of detecting incidents on devices, SNMP traps can be send each time an incident occurs, regardless of the polling process.

Parameter	Description
Enable SNMP traps	Enable/disable SNMP traps sending.
Source IP address	Set the IP address of the device which sends traps

To create a new record, click the "+**SNMP traps receiver**" button. Fill in the following parameters:

Parameter	Description
Destination address	Set the monitoring system server IP address.
Port	Set the monitoring system UDP port.
SNMP traps	The traps type to send.

# Services # Graphs The Graphs tool allows to trace the device parameters represented in the diagrams. Available modes: realtime tracking, displaying data for hour, day, week or month. Choose mode in the drop-down list located in the lower left corner of the "Graphs" section. By default, the system displays the daily data log. To display a diagram of the certain device interface or parameter values, activate this parameter at the right side of the page. There are two display modes available: a list, where all graphs are arranged sequentially one below the other, and tiles with two graphs in a row.

Parameter	Description
Load	Used throughput of the wireless / wired link, in Mbps.
RSSI	The RSSI indicator displays the received signal level for each channel (uplink and downlink). Available values: -90...-80 dBm - close to the receiver sensitivity level, only the lowest modulations are available. -80...-60 dBm - average input range. -60...-40 dBm - the recommended range for achieving best performance. >-40 dBm - input signal level is too high.
EVM	Error vector magnitude - indicator of the measured input signal quality, telling how far are the received constellation symbols compared to the ideal symbols of the constellation. The parameter value must be as high as possible in absolute value. The recommended level should be less than -21 dB.
MCS index	Modulation and coding scheme selected for transmission.
TX power	Output power changed manually or by ATPC mechanism.

To display the precise parameter values at a certain point of time, hover the cursor over the graph at this place. # Maintenance This section is used for firmware updates, operations with licenses and configuration. Allows to view extended information about the device, to reboot the device, reset factory settings, show system log and download diagnostic card in the bottom part of the screen. The "Search device" button can be used to find the device among others on the pole. This will make the LED indicators flash. The diagnostic card is necessary tool which helps to detect and solve an issue faster and more effective in situation then helps of Astrawireless technical support team is required.

### **Device information** The following information is displayed on information panel: * Part number. * Device serial number. * Hardware platform version. * Time since last reboot. * Last reboot reason, following values are possible: * Software fault - firmware needs to be updated. * Unexpected restart - power-on reset. * Manual restart. * Manual delayed restart. * Firmware upgrade. * SNMP managed restart. * Test firmware loaded. * Watchdog - hardware failure. * Panic - critical firmware error.

### Firmware T here are two options to upgrade firmware on the device: * Manually - new firmware should be downloaded from official FTP server . Click on "Upload firmware" button and choose a firmware file. Or you can drag and drop a file from your file manager into the dotted area. * Automatically - the device may offer you new firmware version automatically or after clicking "Check for updates" button. Click on "Update", after that your web browser will try to download the latest firmware version and upload it to the unit. Firmware will be applied after unit reboot.

### Configuration The device allows to upload, download and view current configuration in text form. To view the configuration, click the "Show configuration" button, the file will open in new window. To download the configuration, click the "Save configuration" button, the configuration can be loaded by clicking the "Upload configuration" button, or you can drag and drop a file from your file manager into the dotted area.

To upload and apply the configuration file that has been modified, please follow these steps: * Change the "check\_sum \" command to "check\_sum off" in the configuration file. * Upload the configuration file to the device. * Refresh the web page by pressing F5. * To apply the settings, click "Changes" in the upper right corner and click "Apply" in the window that opens. ### **License** License contains information about allowed frequencies, channel width and power limit. This section allows to view the current license and upload a new one. To upload a license on device, click the "Upload license" button drag and drop a file from your file manager into the dotted area.

# Alignment The graphical antenna alignment tool allows to visualize the signal characteristics on both sides of the link in order to make the antenna alignment process more accurate and easier. It helps to find the best antenna position via comparing the actual received signal level with the calculated reference value. The accuracy of the antenna alignment at the neighbor device is very important for the link quality. Antenna alignment tool operates online and does not break the wireless connection, but switch the devices to the alignment mode, which set MCS0, the maximum Tx power value and disable the ATPC mechanism.

Click the "Start alignment" button to begin. Each side of the link (local and remote) has two similar test indicator sets, corresponding to each antenna polarization. This allows controlling the alignment process for each antenna polarization for the local and for the remote device simultaneously.

On the left edge of the graph there is a RSSI scale, below is a time scale (exact, if a connection to the SNTP server is performed or the time from the device being turned on). Red squares indicates break of the connection. Optimal RSSI values for operation at the highest modulations are -60...-40 dBm. Click the "Stop alignment" button to finish a test. To download picture of current alignment state click the "Save as PNG" button.

# Spectrum analyzer In the "Spectrum Analyzer" menu, you can perform a deep analysis of the radio emissions in the environment where the unit is placed. The unit scans the radio spectrum on all available frequencies. In order to obtain the information as accurate as possible, the scanning process may take a while.

The following parameters are available in order to operate the Spectrum Analyzer:

Parameter	Description
Start Frequency	Set the first frequency for scanning (in MHz).
End Frequency	Set the last frequency for scanning (in MHz).
Scan step	Set the scanning frequency step (in MHz). It is recommended to set 1 MHz “step” value to get more precise scanning results.
Channel width	Set the bandwidth (in MHz).

Click the "Start Scanning" button to begin. There are two scanning modes: one for the local device only and one for both sides of the link.

You may stop scanning by clicking on appropriate button.

By clicking the "Last Snapshot**"** button, you get the final scanning results. The most common usage of this feature is when you perform a spectrum scan at the remote unit on the other side of the wireless link. To download picture of last scanning result click the "Save as PNG" button.

# Speed test The "Speed test" tool performs link throughput tests for the configured channel width and on the current frequency, without radio link interruption. The "Speed test" tool displays the values of the full channel throughput which is available under the current settings, for current bitrate, in Mbps ang packets per second.

By clicking the "Start Tests"/"Stop Tests" buttons at the bottom of the page, you can start/stop the performance tests. * "Test duration" parameter - allows setting the duration (in seconds) of the test. * "Test direction" parameter - allows choosing between bi-directional and unidirectional performance test. # RCMD The "RCMD" page emulates CLI (command line interface) in the Web interface. This allows managing and monitoring the device by using all the commands and functions that are available via standard CLI.

In the "Command Line" menu, the commands are only executed, but not saved into the configuration. To execute the command and save it in the device configuration, use the "config save" command. The principles and commands of the operating system are described in [AstraFleX user manual](https://wiki.astrawireless.net/astra-wireless-documentation/technical-documentation/astraflex-technical-user-manual). # Astrawireless Quanta⁣ Technical User Manual **Astrawireless Quanta** is the devices family used for deployment of wireless Point-to-Point links in 4, 5 and 6 GHz frequency ranges, with a maximal performance of up to 650 Mbps. **Astrawireless Quanta** families devices are based on the Octopus SDR technology which allows to extend functionality of the device at the physical, channel and upper levels by updating the system software. Thus, the main subsystems capabilities can be determined by the software without the need to dismount or replace the device. ## About This Manual This manual provides detailed technical information for the **Astrawireless Quanta** families devices, including system specifications, installation, commissioning, maintenance and troubleshooting. The document is intended to be used by qualified RF engineers/technicians and IT professionals. Qualified personnel should have skills and experience with: * Outdoor/indoor radio equipment installation * Outdoor wireless networks * TCP/IP networking protocols * Safety procedures and instructions for installing antenna equipment * Professional manipulation with electrical equipment and accessories * Safety procedures and instructions for working at height. ## Important Notice ### Legal Rights © Copyright 2026 ⁣Astrawireless. All rights reserved. The information contained in this document is originated by, proprietary, confidential and owned by Astrawireless. No part of this document should be disclosed, reproduced or distributed without the express written permission of Astra Wireless Technology LLC-FZ. Astra Wireless Technology LLC-FZ reserves the right to change the information contained in this document without prior notice. No part of this document may be considered as a part of any contract or warranty. ### Statement of Conditions Astra Wireless Technology LLC-FZ shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this manual or equipment supplied with it. ### Disclaimer The software is sold on an "AS IS" basis. Astrawireless, its affiliates or its licensors make no warranties, whatsoever, whether express or implied, with respect to the software and the accompanying documentation. Astrawireless specifically disclaims all implied warranties of merchantability and fitness for a particular purpose and non-infringement with respect to the software. Units of product (including all the software) delivered to purchaser hereunder are not fault\_ tolerant and are not designed, manufactured or intended for use or resale in applications where the failure, malfunction or inaccuracy of products carries a risk of death or bodily injury or severe physical or environmental damage (“high risk activities”). High risk activities may include, but are not limited to, use as part of on-line control systems in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, life support machines, weapons systems or other applications representing a similar degree of potential hazard. Astrawireless specifically disclaims any express or implied warranty of fitness for high risk activities. ### Indication of the countries Astrawireless equipment has no geographical limitations for selling and can be supplied to any country of the world. ### Limitation of Liability Astrawireless shall not be liable to the purchaser or to any third party, for any loss of profits, loss of use, interruption of business or for any indirect, special, incidental, punitive or consequential damages of any kind, whether arising under breach of contract, tort (including negligence), strict liability or otherwise and whether based on this agreement or otherwise, even if advised of the possibility of such damages. To the extent permitted by applicable law, in no event shall the liability for damages hereunder of Astrawireless or its employees or agents exceed the purchase price paid for the product by purchaser, nor shall the aggregate liability for damages to all parties regarding any product exceed the purchase price paid for that product by that party (except in the case of a breach of a party’s confidentiality obligations). ### Disposal instructions

This symbol means that this product is subject to Waste of electrical and electronic equipment (WEEE) regulations. Do not dispose of your product with other regular/household waste. Instead, hand over your waste equipment to a designated collection point for recycling.
# Introduction⁣⁣⁣⁣⁣⁣⁣ ## Document structure This document consists of the following chapters: * [Introduction](/astra-wireless-documentation/technical-documentation/astrawireless-quanta-technical-user-manual/introduction)⁣⁣⁣⁣⁣⁣⁣ - presents the information about this document’s purpose and structure. * [Planning considerations](/astra-wireless-documentation/technical-documentation/astrawireless-quanta-technical-user-manual/planning-considerations) - describes the principles of wireless system planning. * [Installation](/astra-wireless-documentation/technical-documentation/astrawireless-quanta-technical-user-manual/installation)⁣⁣⁣⁣⁣⁣⁣ - describes the steps to be taken when installing the equipment at the installation sites and installation site requirements. * [Operation & Administration](/astra-wireless-documentation/technical-documentation/astrawireless-quanta-technical-user-manual/operation-and-administration) - presents the functionalities of the web interface, a simple and efficient way to monitor the device status, configure and maintain the equipment. * [Troubleshooting](/astra-wireless-documentation/technical-documentation/astrawireless-quanta-technical-user-manual/troubleshooting) - describes the actions to be taken during occured problems investigation. ## Document marks {% hint style="danger" %} CAUTION All caution warnings are marked with a special warning sign. One should pay a great deal of attention to what is written in the Caution section. {% endhint %} {% hint style="warning" %} NOTE All notes are marked with a special note sign. Notes usually contain useful comments or hints to the described section of the document. {% endhint %} # Key Features⁣⁣⁣⁣⁣ **Astrawireless Quanta** is a wireless point-to-point solution with an impressive maximal performance of up to 650 Mbps, a packet perfomance is up to 1 200 000 pps. **Quantas** are based on the newest Astrawireless proprietary Octopus SDR hardware platform. **Quanta 4** operates in frequency range from 4000 MHz to 5000 MHz**, Quanta 5** operates in frequency range from 4900 MHz to 6000 MHz, **Quanta 6** - from 6000 MHz to 6425 MHz. The solution supports the wide range of channel width between 3.5 MHz and 56 MHz. SC-FDE radio technology is used for data transmission. ### Radio * Extended set of modulation coding schemes – **Astrawireless Quanta** supports 14 modulation-coding schemes. In periodic interference conditions, the performance will stay on the highest level. * Automatic Modulation Control (AMC) – modulation control algorithm selects the most appropriate modulation-coding scheme at each polarization and each end of the link in order to maximize the link performance. * Hybrid-FDD (split-frequency mode) – separate allocation of downlink and uplink channels to utilize the least congested frequency channel at each end of the link. * Automatic Repeat Request (ARQ) – a technology which enables packet re-transmission in case of previous unsuccessful delivery, allows to achieve reliable connectivity even in highly congested spectrum. * Instant DFS (except for Quanta 6 family) – a set of algorithms operating on top of the mandatory DFS/Radar detection/LBT, providing background spectrum scanning and zero-downtime channel reselection in case of congestion or radar detection. For uplink and downlink traffic, different frequencies can be selected to achieve optimum performance. * Automatic Transmit Power Control (ATPC) – a technology which allows to limit the overall power system mode, which takes into account the antenna gain and losses in the RF cable. ### Networking * VLAN support is an important tool which is used to isolate and filter traffic flows. * STP support allows to avoid network loops. * Due to QoS support, traffic prioritization is available in accordance with the 802.1p (8 queues), ensures that the most important data arrives with priority. * One of the network mechanisms to optimize bandwidth by reducing the share of overhead for service headers are Jumbo frames with size up to 9038 bytes. ### Distance **Astrawireless Quanta** devices have a link budget of up to 178 dB for models with 25 dBi antenna and from 125 dB for models with external antennas that allows to achieve reliable connectivity at a distance more than 200 km in clear line-of-sight conditions, as well as provides sufficient margin for near- and non-LOS deployments at shorter distances. Transmit power at the highest modulations is also one of the key performance metrics, allowing devices to achieve the highest performance over long distances and in noisy spectrum. **Quanta** transmit power at QAM256 is up to 24 dBm. ### Environment * Operating temperature range -40 ... +60 ºС, in an extended temperature range: -55 ... +60 ºС. * Dust and water protection in compliance with IP66/IP67. * Wind load up to 160 kph - operation, 200 kph - survival. ### Power The device has following electrical parameters: * Consumption is up to 15 W. * Power options: 90-240 VAC\~ @ 50/60 Hz, ±43..56 VDC. * 802.3at support or proprietary passive PoE. * AC/DC injector IDU-CPE-G(24W) is included to the packing list. # Hardware Platform⁣⁣⁣⁣⁣ ### Octopus SDR SDR platform has been designed based on a Software-Defined Radio technology aimed at increasing link performance several-fold. Astrawireless Quanta addressing challenges such as limited spectrum availability, growing interference challenges and demands for yet more capacity. Due to Octopus SDR platform Quanta allow to bring new PHY, MAC and upper layer features via a firmware upgrade even for the units operating in the field. ### Wireless device An integrated wireless device contains the radio and networking electronics. Implemented in a robust all-weather metal enclosure, this equipment can be used to create point-to-point wireless links at distances in excess of 200 km (depending on country regulations, antenna types, interference, terrain, climate zones, etc.). There are several possible version of Quanta solution enclosures: #### Quanta 4 * with removable antenna 26 dBi; * with two N-type ports for an external antenna. #### Quanta 5 * with removable antenna 29 dBi; * with integrated antenna 28 dBi; * with removable antenna 26 dBi; * with integrated antenna 25 dBi; * with integrated antenna 23 dBi; * with two N-type ports for an external antenna. #### Quanta 6 * with integrated antenna 28 dBi; * with integrated antenna 25 dBi; * with two N-type ports for an external antenna.

#### Grounding bolt For grounding the ODU to the supporting structure. #### **Interfaces**

Interface	Description
Gigabit Ethernet	RJ45 socket for connecting to power supply and data transmission. The network connection to the wireless device is made via a 1000BaseT (Gigabit) Ethernet connection. Power is provided to the device over the 1000BaseT Ethernet connection using a standard IEEE 802.3at passive PoE power supply.
SFP	External optical Gigabit port for plugging of the optical SFP transceiver module.

{% hint style="warning" %} NOTE Only one port can be used for data transmission at a time. Please note, the SFP port has priority in case both ports are enabled. {% endhint %} #### LED Panel The "POWER" indicator has three possible colors: * Red light - the device is connected to the electricity mains, * Yellow light - a wired connection with a speed of 10/100 Mbps * Green light - a wired connection with a speed of 1000 Mbps. Other indicators are used to perform coarse antenna alignment. The more indicators are on, the better wireless connection is established. The blinking indicator means an intermediate state. The maximum value on the scale is the target RSSI level calculated by the device. The RSSI level for intermediate indicators is calculated based on the maximum.

### Part number description **Astrawireless Quanta** part number has the following structure:

Structure items are described below:

Item	Description
1	Product family name: Q - Quanta.
2	Frequency range: 4 - device in the range of 4 GHz. 5 - device in the range of 5 GHz. 6 - device in the range of 6 GHz.
3	Antenna gain: 23 - integrated antenna with 23 dBi gain, Combo port GigabitEthernet/SFP; 25 - integrated antenna with 25 dBi gain, Combo port GigabitEthernet/SFP; 26 - removable antenna with 26 dBi gain, Combo port GigabitEthernet/SFP; 28 - integrated antenna with 28 dBi gain, Combo port GigabitEthernet/SFP; 29 - removable antenna with 29 dBi gain, Combo port GigabitEthernet/SFP; E - devices for an external antenna connection, Combo port GigabitEthernet/SFP.
4	Additional options: t - extended temperature range: -55 ... +60 ºС.

# Power Supply⁣⁣⁣⁣⁣⁣ ### Indoor AC/DC injector IDU-CPE-G(24W)

IDU-CPE-G(24W) is an indoor Gigabit PoE injector which supports 100-240 V input range from the AC mains. IDU-CPE-G(24W) feeds 48 VDC power to the device by injecting it to the CAT5 Ethernet cable.

Parameter	Description
Compatible models	Quanta and Evolution (except E5-BSQ), AUX-ODU-SYNC
Size and weight	97x53.5x33.5 mm, 0.133 kg
Connectors and Interfaces	"LAN" - Ethernet input (Data only) "POE" - Ethernet output (Data+VDC), PASSIVE PoE "PWR" - AC Input
Supported Ethernet Modes	10/100/1000 Mbps
Standards	IEEE 802.3 10Base-T IEEE 802.3U 100Base-TX IEEE 802.3ab 1000Base-T
Input Power Requirements	AC Input Voltage: 100 ... 240 VAC AC Input Current: 0.75 A AC Frequency: 50 to 60 Hz
Consumption	28 W
Operating temperature range	-10 °С ... +40 °С
Operating humidity	Maximum 95 %, Non-condensing
Storage temperature	-40 °С ... +70 °С
Output Power Voltage	48 VDC, 0.5 A
Safety	UL cUL, CE, GS, CCC, FCC, S-MARK, PSE, C-tick, KC(48V0.5A) BIS（24V1A

Parameter	Description
Compatible models	Quanta, Evolution
Output Voltage	The same as input
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Pin assignment and polarity	1/2 (+), 3/6 (-), 4/5 (+), 7/8 (-)
Size and Weight	115×65×40 mm, 0.15 kg
Operating temperature range	From 0°С to +40°С

#### **Mounting holes sizes**

#### IDU-LA-G(V.01) Packing List

#### **Cable assembly**

### Lightning Protection Unit with Injector AUX-ODU-INJ-G

Parameter	Description
Size and Weight	34x94x121 mm, 0.28 kg
Connectors and Interfaces	ETH IN - Ethernet input ETH OUT - Ethernet output (data+VDC, protected leg) PWR - DC Input GND - Ground clamp
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Water and Dust Protection	IP66 and IP67
Operating temperature range	-55 °C ... +60 ºC
DC Range	±43...±56 VDC
Lightning Protection	In compliance with: GR-1089 IEC 61000-4-2 (ESD) 15kV (air), 8kV (contact) IEC 61000-4-4 (EFT) 40A (tp = 5/50ns) IEC 61000-4-5 (Lightning) L5, 95A (tp = 8/20us) ETSI ETS 300 386

#### **Ethernet Connectors Pin-out** | Pin | LAN | POE | | --- | ------------ | ------------------- | | 1 | Data pair A+ | Data pair A+ | | 2 | Data pair A- | Data pair A- | | 3 | Data pair B+ | Data pair B+ | | 4 | Data pair C- | +VDC + Data pair C- | | 5 | Data pair C+ | +VDC + Data pair C+ | | 6 | Data pair B- | Data pair B- | | 7 | Data pair D+ | -VDC + Data pair D+ | | 8 | Data pair D- | -VDC + Data pair D- | {% hint style="danger" %} CAUTION Using inappropriate DC source will damage the ODU, which will be not covered by warranty {% endhint %} #### Packing List

AUX-ODU-INJ-G is supplied with a worm clamp TORRO 40-60/9 C7 W4 DIN 3017 - 2 pcs. The clamp is made of stainless steel A4, width 9 mm, allows the installation on a mast with a diameter of 35 to 60 mm. In case of mast diameter more than 60 mm, a similar clamps (up to a 230 mm diameter) with a width of up to 12-13 mm can be used. # Lightning⁣ ⁣protection unit⁣⁣⁣⁣⁣ ### AUX-ODU-LPU-L

Parameter	Description
Size and Weight	45x92x55.5 mm, 0.13 kg
Connectors and Interfaces	2 x Ethernet ports Ground clamp
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Water and Dust Protection	IP66 and IP67
Operating temperature range	-55 °C ... +60 ºC
Opening voltage of the arrester	150 V
Lightning Protection	In compliance with: GR-1089 IEC 61000-4-2 (ESD) 15kV (air), 8kV (contact) IEC 61000-4-4 (EFT) 40A (tp = 5/50ns) IEC 61000-4-5 (Lightning) L5, 95A (tp = 8/20us) ETSI ETS 300 386

#### **Ethernet Pin-out** | Pin | Data pair | | --- | --------- | | 1 | A+ | | 2 | A- | | 3 | B+ | | 4 | C- | | 5 | C+ | | 6 | B- | | 7 | D+ | | 8 | D- | #### Packing list

AUX-ODU-LPU-L is supplied with a worm clamp TORRO 40-60/9 C7 W4 DIN 3017. The clamp is made of stainless steel A4, width 9 mm, allows the installation on a mast with a diameter of 35 to 60 mm. In case of mast diameter more than 60 mm, a similar clamp (up to a 230 mm diameter) with a width of up to 12-13 mm can be used. # Packing list⁣⁣⁣⁣⁣⁣⁣ This section describes the components that are supplied by default with the Astrawireless Quanta models. Before the installation, please make sure you have all necessary parts and accessories. * Outdoor unit (ODU). * Power supply. * Cable gland (x2). * Shielded RJ-45 connector. * Unshielded RJ-45 connector. * Mounting kit - universal assembling kit for mounting the ODU on standard pole, wall or thick pipe (vertical/horizontal). * Power cord - the model depends on the region, according to the Purchase Order. # Planning considerations⁣⁣⁣⁣⁣⁣⁣ During link planning, such factors as distance, obstacles and the link margin should be taken into account. We strongly recommend to use a [planner tool](https://planner.astrawireless.net/) for link planning. ## Range and obstacles Make sure that line of sight is provided when planning the antennas' placement for a point-to-point link in order to achieve maximum range and performance between two antennas. Perform a survey to identify all the obstructions (such as trees or buildings) in the path and to assess the risk of interference. The radio beam is an electromagnetic wave and it is not as thin as a laser beam, for example. The main energy in a radio beam is concentrated along the straight line between the two antennas, inside an area with the shape of an ellipsoid (or a rugby ball). This area is called the 1st Fresnel zone and its exact form and size depend upon the frequency and the signal propagation path length. If most of the 1st Fresnel zone is obstructed, a major part of the radio wave’s electromagnetic energy is lost, which leads to a severe signal quality degradation and as a result to a decreased coverage range or performance. Below is an incomplete list of possible obstructions along the signal propagation path: * Neighboring buildings. * Trees. * Bridges. * Power lines. To obtain the best results, it is necessary to perform a precise analysis of the signal propagation path and possible obstructions that may obstruct the 1st Fresnel zone.

## Important notice {% hint style="warning" %} NOTE

On the territory of the European Union, following applies: * the band 5150–5350 MHz is only for indoor use to reduce the potential for harmful interference to co-channel mobile satellite systems and other services. Further, EU regulations enforce EIRP limit in that band of 200mW (23dBm), output power and antenna gain (in case of devices with detachable antenna) shall be chosen accordingly; * in the band 5470-5725 MHz, choice of the transmit power and antenna gain (in case of devices with detachable antenna) shall be such that the equipment still complies with the EIRP limit and EIRP density limit. EIRP limit in that band is 1W (30dBm), EIRP density limit is 50mW/MHz (17dBm/MHz); * in the band 5725-5875 MHz, choice of the transmit power and antenna gain (in case of devices with detachable antenna) shall be such that the equipment still complies with the EIRP density limit. EIRP density limit in that band is 200mW/MHz (23dBm/MHz). {% endhint %} {% hint style="warning" %} NOTE This device contains licence-exempt transmitter(s)/receiver(s) that comply with Innovation, Science and Economic Development Canada’s licence-exempt RSS(s). Operation is subject to the following two conditions: * This device may not cause interference. * This device must accept any interference, including interference that may cause undesired operation of the device. This Class B digital apparatus complies with Canadian ICES-003. Following also applies to this radio equipment: * the band 5150–5250 MHz is only for indoor use to reduce the potential for harmful interference to co-channel mobile satellite systems; * for devices with detachable antenna, the maximum antenna gain permitted for devices in the bands 5250-5350 MHz and 5470-5725 MHz shall be such that the equipment still complies with the e.i.r.p. limit; * for devices with detachable antenna, the maximum antenna gain permitted for devices in the band 5725-5850 MHz shall be such that the equipment still complies with the e.i.r.p. limits as appropriate; and * where applicable, antenna type(s), antenna models(s), and worst-case tilt angle(s) necessary to remain compliant with the e.i.r.p. elevation mask requirement set forth in section 6.2.2.3 of the RSS-247 shall be clearly indicated.\ High-power radars are allocated as primary users (i.e. priority users) of the bands 5250-5350 MHz and 5650-5850 MHz and these radars could cause interference and/or damage LE-LAN devices. {% endhint %} {% hint style="warning" %} REMARQUE Cet appareil contient des émetteurs / récepteurs exemptés de licence conformes à la (aux) source(s) RSS de Innovation, Sciences et Développement économique Canada. Le fonctionnement est soumis aux deux conditions suivantes: * Cet appareil ne doit pas causer d'interférences. * Cet appareil doit accepter toutes les interférences, y compris celles susceptibles de provoquer un fonctionnement indésirable de l'appareil. Cet appareil numérique de la classe B est conforme à la norme NMB-003 du Canada. Ce qui suit s’applique également à cet équipement radio: * la bande 5150–5250 MHz est uniquement destinée à une utilisation en intérieur afin de réduire le risque de brouillage préjudiciable des systèmes de télécommunication par satellite mobiles dans le même canal; * pour les dispositifs avec une antenna détachable, le gain d'antenne maximal autorisé pour les dispositifs des bandes 5250-5350 MHz et 5470-5725 MHz doit être tel que l'équipement soit toujours conforme à la norme e.i.r.p. limite; * pour les dispositifs avec une antenna détachable, le gain d'antenne maximal autorisé pour les dispositifs de la bande 5725-5850 MHz doit être tel que l'équipement soit toujours conforme à la norme e.i.r.p. limites, le cas échéant; et * le cas échéant, type (s) d’antenne, modèle (s) d’antenne et angle (s) d’inclinaison dans le cas le plus défavorable nécessaire pour rester conforme à la norme e.i.r.p. L’exigence de masque d’altitude énoncée à la section 6.2.2.3 du CNR-247 doit être clairement indiquée.\ Les radars à haute puissance sont attribués en tant qu'utilisateurs principaux (utilisateurs prioritaires) des bandes 5250-5350 MHz et 5650-5850 MHz, et ces radars peuvent provoquer des interférences et / ou endommager les dispositifs LE-LAN. {% endhint %} {% hint style="warning" %} NOTE Este equipamento não tem direito à proteção contra interferência prejudicial e não pode causar interferência em sistemas devidamente autorizados. Para maiores informações, consulte o site da ANATEL {% endhint %} # Link pre-configuration in the lab⁣⁣⁣⁣⁣ Usually, before going into the field, it is recommended to pre-configure in the lab the Astrawireless units to verify the link establishment. Therefore, let's take the units to be used for this course out of the package and place them on the table. {% hint style="warning" %} NOTE A minimum set of requirements must be met during devices pre-configuration in the lab: * Make sure the devices are not directed at each other in order to prevent radio modules damage. * A minimum transmit output power must be set. * In case of two devices with external antennas, it is recommended to connect them in the link directly, with RF cables and RF attenuators with attenuation of at least 40 dB for each polarization (installation\deinstallation of the RF attenuators and RF cables should only be performed when the devices are switched off). * Grids shoud be the same on both Master and Slave units. {% endhint %} #### **Step 1: Connection scheme** The equipment list required for the lab configuration: 1. Outdoor units - 2 pcs. 2. Power supply - 2 pcs. 3. Power cord - 2 pcs. 4. Ethernet cables - 4 pcs. 5. Laptop with Ethernet port available. We will perform the settings mentioned below for each unit of the link and check if wireless link was established correctly. Use the following instruction to assemble a test scheme:
1. Connect Gigabit Ethernet port at the ODU to the power supply port labeled as "OUT". 2. Connect Ethernet port at the laptop to the power supply port labeled as "IN". 3. Connect the power cord to power supply and plug it to AC mains.

#### **Step 2: Access to the device** Let's access each unit to the default IP address 10.10.10.1 with mask 255.255.255.0 via a web browser. Before, make sure the Ethernet port of the Laptop has an IP address assigned from the same subnetwork as the one for the unit (e.g., set 10.10.10.10 with mask 255.255.255.0). {% hint style="warning" %} NOTE We assume that each unit used in this setup has not been configured before and runs with the factory settings. {% endhint %} Use any letters or numbers for the initial authentication on each unit, for example: * Login: login. * Password: password. {% hint style="warning" %} NOTE We strongly recommend to change your login and password after the first login. {% endhint %} After the first login, let's configure a distinctive name for each unit and set a custom login and password. Go to the "Settings" → "General" section and configure: * Device Name (e.g., Master/Slave). Go to the "Settings" → "Security" section and configure: * Login (e.g., admin). * Password (e.g., admin). {% hint style="warning" %} NOTE At the next login, type "admin" for the Login and Password (if these are the credentials set before) to access the unit in the privileged mode. {% endhint %} #### **Step 3: Firmware upgrade** Let's upgrade each unit to the latest stable firmware version. In case the laptop has an access to the Internet, a new software version will be detected automatically, update on both devices. Otherwise, the manual firmware upgrade process should be performed: * Download latest release from the ftp server .
* In the "Maintenance" section click the "Select file" button and set the path to the downloaded file, or drug it to the specified area.
* File will be uploaded to the device. Changes will take force after reboot.

#### **Step 4: Radio parameters configuration** Let's configure the minimum needed radio parameters to establish the link.
At the unit named Master at step #2 above, go to the "Settings" → "Radio" section and set this unit with: * Unit role: one device should be Master, another one - Slave. * Link ID and Access key parameters, must be the same on both sides of the link. * Downlink center frequency use values selected at the Link Planning stage. * Uplink center frequency: only for the Slave device. * Power limit: set the minimum value in the range, as currently, we are in the lab, and we don't need high output power. * Channel width: use value selected at the Link Planning stage. * Frame length: same on both devices. The rest of parameters remain with the default values.

#### **Step 5: Check the wireless link status** Let's apply all settings described above for each unit and go to the "Dashboard" section and check if the device status has changed to "Connected".

# Installation ## Mounting kit⁣⁣⁣⁣⁣s ### MONT-KIT-85 Mounting kit⁣⁣⁣⁣⁣⁣ MONT-KIT-85 is supplied by default with models Q4-E, Q5-26, Q5-25, Q5-23, Q5-E, Q6-25, Q6-E, MONT-KIT-85S with models Q4-26, Q5-28, Q6-28, Q5-29. It allows to make reliable and easy installation of the unit with two-axis adjustment. Assemble the Mounting kit according to the scheme below. The nut must be tightened until the spring washer clicks, without over-tightening.

Mounting is carried out on a pole with a diameter 30-85 mm. There are also possible options for mounting on a wall or pole with a diameter more than 85 mm.

{% hint style="warning" %} NOTE Clamps and other optional fasteners are not included in the Mounting kit MONT-KIT-85. {% endhint %} ### MONT-KIT-85P Mounting kit⁣⁣⁣⁣⁣⁣ High precision mounting kit MONT-KIT-85P allows to make reliable and easy installation and enables extremely accurate adjustment on azimuth and elevation for optimal wireless link performance. Compatible for Astra Quanta and Astra Evolution, families units. Especially suitable for installing high-gain antenna models that have a narrow beam.

#### Assemble Procedure **Step 1:** Insert and tighten the Assembled kit on the back side of the device using bolts M6x14, washers flat 6 and washers spring 6. **Step 2:** Tighten the Assembled kit and Bracer to the pole using bolt M8, washer flat 8 and washer spring 8. * Bolt M8x50 - used for installation on a pole with Ø 30 ... Ø 55 mm. * Bolt M8x80 - used for installation on a pole with Ø 55 ... Ø 85 mm. **Step 3:** Perform required antenna alignment using adjustment knobs and then tighten nuts M8. {% hint style="warning" %} NOTE M8 nuts are pre-tightened at the manufacturing facility in a position that allows the device to be adjusted using the adjustment knobs and ensures that the wireless device does not shift during the final nuts tighten. If further adjustment is required, weaken the nuts M8 on about 15 degrees. Do not adjust the knobs without weaken the nuts first. {% endhint %}

Mounting is carried out on a pole with a diameter 30 ... 85 mm. There are also possible options for mounting on a wall or pole with a diameter more than 85 mm.

{% hint style="warning" %} NOTE Clamps and other optional fasteners are not included in the mounting kit MONT-KIT-85P. {% endhint %} ## Cable Gland Assembly⁣⁣⁣⁣⁣ ### Cable Gland Assembly for RJ-45 connector {% hint style="warning" %} NOTE The outside diameter value of the FTP Cat5e cable should not exceed 7 mm. {% endhint %} #### Assemble procedure Required components are listed below. 1. Unshielded RJ-45 connector. 2. Shielded RJ-45 connector. 3. FTP Cat5e cable. 4. Cable gland: * Cable gland nut. * Split sealing grommet (with inner diameter 7 mm). * Cable gland threaded coupling. 5. Crimping tool for RJ-45 connector. In order to ensure that the device case remains sealed under any environmental conditions follow the assemble procedure: * **Step 1**: Assemble cable gland nut, the split sealing grommet and the cable gland threaded coupling onto the cable. * **Step 2**: Crimp the standard RJ-45 connector onto the cable using crimping tool. Pin-out scheme: T568B wiring standard. {% hint style="warning" %} NOTE Do not use the shielded RJ-45 connector on this end of the cable as it should be attached on the power supply unit end. {% endhint %} {% hint style="danger" %} CAUTION Make sure that the RJ-45 connector is well-crimped. A loose connector can damage the device. Please note that such damage is not covered by the warranty. {% endhint %} * **Step 3**: Insert the split sealing grommet into the cable gland threaded coupling. * **Step 4**: Insert the RJ-45 connector into the device socket until you hear a click. * **Step 5**: Screw the cable gland threaded coupling into the port and tighten it. Do not apply excessive force. * **Step 6**: Tighten the cable gland nut (4). Do not apply excessive force. ### Cable Gland Assembly for Optical Cable Required components are listed below. 1. Optical cable. 2. Optical connector. 3. SFP module. 4. Cable gland: * Cable gland nut. * Split sealing grommet (with inner diameter 3.2 mm). * Cable gland threaded coupling. #### Assemble procedure * **Step 1**: Put the cable gland nut, the split sealing grommet and cable gland threaded coupling onto the optical cable as shown on the figure below. * **Step 2**: Insert the split sealing grommet into the cable gland threaded coupling. * **Step 3**: Set the SFP module into the socket until you hear a click. * **Step 4**: Insert the optical connector into the SFP module. * **Step 5**: Screw the cable gland threaded coupling into the port and tighten it. * **Step 6**: Tighten the cable gland nut. Do not apply excessive force. {% hint style="warning" %} NOTE In order to disassemble SFP, please disconnect the optical cable, pull the clip of the SFP module and withdraw the SFP module from the slot. SFP module is not included into the packing list. {% endhint %} ## Mounting⁣⁣⁣⁣⁣ Pre-installation **Reqiered tools** * Screwdriwer set. * Pliers / pipe wrench. * Wrench set. **Additional equipment** * GPS receiver. * High magnification binoculars. {% hint style="danger" %} CAUTION Before mounting the equipment in an outdoor environment, please make sure that: * You acknowledge the regulations imposed by the Regulatory Authority for Communications in your country for the radio spectrum to be used. * You chose known locations for the installation of the links; although Astra Wireless devices can also operate in Near-LoS or Non-LoS conditions, to achieve the best performance, it's highly recommended to install the link in locations where Clear-Line-of-Site and clear channels are available. * You performed link planning using the planning tool to determine the link path profiles, radio equipment placement requirements, etc. * You met requirements described in the section "Planning considerations" - > "Wireless device placement". {% endhint %} ### Installation Procedure * In case of device with removable parabolic antenna, to mount the reflector to Quanta, proceed as follows: * Match the antenna reflector with the cover of the outdor unit to coincide the cut parts of the antenna and the slots of the enclosure to prevent rotation of the antenna during operation. * Install the sealing metal ring of the feeder on top of the antenna reflector, screw the feeder into the hole to press the reflector to the device enclosure. * Tighten the feeder with a 45 mm wrench with a force of 700-800 Nm. * In case of device with external antenna, to mount and connect an external antenna to Quanta, proceed as follows: * Mount the antenna according to manufacturer’s instructions; * Connect the ODU V and H N-type interfaces to the antenna with RF coaxial cables and with appropriate connectors. Use cables not longer than 1 m (3.3ft). Tighten the N-type connectors to a torque setting of 1.7 Nm (1.3 lb ft); * Form drip loops near the cable ends at the ODU’s side so that water doesn’t creep towards the ODU connectors; * Weatherproof the N-type connectors (when antenna alignment is complete) using PVC tape and self-amalgamating rubber tape; * Weatherproof the antenna connectors in the same way (unless the antenna manufacturer specifies a different method); * Fix the antenna cables to the supporting structure using site approved methods. Ensure that no undue strain is placed on the ODU or antenna connectors. Ensure that the cables do not flap in the wind, as flapping cables are prone to damage and induce unwanted vibrations in the supporting structure. {% hint style="danger" %} CAUTION In order to prevent device damage make sure that antenna is connected to both N-type connectors with serviceable RF cables before switching on. {% endhint %} * Install ODU connector facing down using the mounting kit. Do not tighten the fasteners to the end until the alignment is completed. * Connect the Cat5e FTP cable with the cable gland to ODU. * Perform ODU grounding. * Lay the Cat5e FTP cable from ODU to the power supply. * Connect the Cat5e FTP cable with a shielded connector covered by a cap to the "OUT" port of the power supply, having previously touched the power supply connector case with FTP cable connector case. {% hint style="danger" %} CAUTION The power supply must not operate near a direct heat source, near water or in an environment with high humidity. The cables must be connected in such a way to prevent water flow to the power supply connectors. {% endhint %} * Perform the power supply grounding. * Connect the laptop using Cat5e FTP cable to the power supply "IN" port. * Connect the power cord to the power supply and then to the power circuit. {% hint style="danger" %} CAUTION Use mains supply cords that adhere to safety regulations of the country where the equipment is getting deployed. {% endhint %} Make sure a small loop (at least 10 cable diameters) is provided before the Cat5e FTP cable enter into the building.

{% hint style="danger" %} CAUTION This equipment is a source of electromagnetic energy and exposes public and personnel to RF electromagnetic emission. Guaranteed safe distance to human body during operation is 20cm (7.9in) and greater.

Surface of device may become hot during operation, contact may cause burn. Allow to cool before handling. {% endhint %} {% hint style="danger" %} Please note that the pressure equalization system in Astra Wireless devices is performed via gas exchange through a cable gland and Ethernet cable jacket with a dry room where the power supply is installed. In order to avoid ODU failure due to moisture entering the device, for example, during the pressure drop during the rain, the cable gland assembly requirements should be met and there are should be no cracks in the Ethernet cable jacket. In addition, you should avoid the Ethernet cable bending near the ODU and pinching with clamps, that can bring to the pressure equalization system fault between the internal volume of the sealed ODU and the external environment during a sudden air temperature change. This may lead to the leakage and device failures. {% endhint %} ## Grounding and lightning protection⁣⁣⁣⁣⁣ This section describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection and equipment location for the wireless device, power supply, AUX-ODU-LPU-L and AUX-ODU-LPU-G unit (if installed). {% hint style="danger" %} CAUTION Electro-magnetic discharge (lightning) damage is not covered under warranty. The recommendations in this document, when followed correctly, give the user the best protection from the harmful effects of EMD. However 100% protection is neither implied nor possible. {% endhint %} ### Grounding and lightning protection recommendations * The wireless device should be placed on the pole at a height that is at least 1 meter below the top of the pole. In this case, there is a significant probability that the lightning strikes the pole and not the wireless device. The pole should be properly grounded: connected to the building lightning protection circuit according to your local regulations. * All equipment must be connected at stabilized and surge protected power sources which must be properly grounded. * The end of the FTP service cable that is connected to the power supply should be assembled with a shielded RJ-45 connector. The other end of the FTP service cable connected to the wireless device should be assembled with unshielded (standard) RJ-45 connector. * The power supply is grounded via a three-conductor power cord and a grounded socket. * AUX-ODU-LPU-G and AUX-ODU-LPU-L grounding is performed using grounding bolt. * Antenna pole and wireless device should be connected to the common ground ring. Grounding cables should be no less than 10AWG thick and must use corrosion-resistant connectors. An M5x10 grounding bolt is included in the supply list. * Special attention should be paid if the external antenna used is not DC-shorted. In this case, an additional lightning arrestor should be used between the antenna and ODU. ### Requirements to the lightning protection unit AUX-ODU-LPU-L location AUX-ODU-LPU-L is an optional accessory which may be used to serve as a line protection unit for the ODU and for the indoor network equipment connected to the Ethernet port of the IDU. AUX-ODU-LPU-L should be properly assembled, mounted and grounded. General recommendations for installations of lightning protection units: * Install the lightning protection unit on both ends of the cable to protect both the outdoor and the indoor unit. The purpose of the LPU at the top is to protect the ODU from a surge of lightning strike which can hit the long FTP cable run along the height of the pole or on the roof of the building. The purpose of the LPU at the bottom is to protect the IDU and customer equipment. * Use the lightning protection unit to protect all circuits for signal transmission and power supply (video, audio, management signals, Ethernet, etc.) * Regularly (especially before the periods with high thunderstorm activity) check the integrity of lightning protection units, grounding elements and bonding conductors. * The ports of the AUX-ODU-LPU-L device are symmetrical, i.e. the correspondence of ports position to the external unit and the power supply does not matter. Make sure to install the two LPU devices as shown in the scheme below.

{% hint style="danger" %} CAUTION Missing or bad grounding may leave the unit vulnerable to lightning damage. {% endhint %} #### AUX-ODU-LPU-L Cable Gland Assembly In order to ensure that the cable gland remains sealed under any environmental conditions, please, follow the assembly sequence according to the procedure below: * **Step 1**: Insert the sealing insert into the clamping claw. * **Step 2**: Assemble the cable gland by putting the thread-lock sealing nut, clamping claw with sealing insert and body onto the cable as shown on the figure. * **Step 3**: Insert the clamping claw with sealing insert into the body as shown on the figure. * **Step 4**: Crimp the standard RJ-45 connector onto the cable using crimping tool. Pin-out scheme: T568B wiring standards. {% hint style="danger" %} CAUTION Make sure that the RJ-45 connector is well-crimped. A loose connector can damage the device. Please note that such damage is not covered by the warranty. {% endhint %} * **Step 5**: Insert the RJ-45 connector into the corresponding socket until you hear a click. * **Step 6**: Screw the cable gland body into the port and tighten it. Do not apply excessive force. * **Step 7**: Tighten the thread-lock sealing nut. Do not apply excessive force.

## Antenna Alignment⁣⁣⁣⁣⁣ ### General recommendations * It is recommended to have two teams prepared for alignment procedure, each team with at least two members: one should take the signal readings and communicate with the remote end, the other should manipulate the antenna. * For rough alignment use the azimuth, elevation angle and suspension height from planner tool report. {% hint style="warning" %} NOTE For devices with an integrated antenna 18 dBi, the mounting kit allows alignment only in the horizontal plane. {% endhint %} * On the device case there is a scale indicating the received signal level. The more often indicator flashes, the better quality of the connection. Blinking indicator shows an intermediate state, the more often indicator is blinking, the higher the connection level. * For more accurate alignment, use the alignment tool built into the device web interface. * After the initial alignment, the device at the remote side must be fixed. Firstly, the alignment is performed for one device, then for another.

### Alignment tool Use the Alignment tool to point and optimize the antenna in the direction of maximum link signal. The built-in graphical antenna alignment tool displays the signal levels for both devices and both polarizations, this makes an alignment process fast and accurate. A green marker indicates the current signal level. To achieve the best performance, this marker should be as close as possible to the pale green area values, which displays the maximum calculated value possible for this link. A gray marker indicates the maximum value that was reached on this channel.

# Operation & Administration⁣⁣⁣⁣⁣ To make changes in the device configuration click the "Changes" button in the upper right corner of the web interface.

The "Applying global changes" window contains a table of parameters whose values have been changed by the user. If you want to undo one change, click the "Roll back" button near the entry. If you need to undo all changes, use the "Roll back" button at the bottom of the window. Changes will be saved to the device configuration by clicking the "Apply" button.

To apply the configuration safely, use the "Try" button. In this case, the previous configuration will be restored after 180 seconds automatically if changes will not be confirmed or test period extended by the administrator. # Web GUI access⁣⁣⁣⁣ {% hint style="warning" %} NOTE Сonnecting third-party equipment via Ethernet (switches, PCs), make sure the PoE, Energy Efficient Ethernet and Green Ethernet functions are disabled on the network interfaces connected to Astra Wireless devices. {% endhint %} Web User Graphical Interface (**Web GUI**) - is the basic way to configure and operate a wireless unit. **Operation system** starts automatically when you power on the unit, Web GUI is enabled by default. In order to access the unit via Web browser, type an IP address in the address bar. {% hint style="warning" %} NOTE By default any username and any password can be used to login Web GUI. It's strongly recommended to set permanent username and password after the first log in. In order to do this go to the "General settings" section. {% endhint %}

# Dashboard⁣⁣⁣⁣ This section is intended to provide the main information about the wireless unit operation. The Dashboard displays a read-only summary of the current link status information, local and remote device signal strength, capacity for downlink and uplink, current values of the basic configuration settings and Ethernet network status. ### Device status

Parameter	Description
Type	The device type: Master or Slave.
Status	Wireless connection state.
Device uptime	The device operating time since the last reboot.
Firmware version	The firmware version uploaded to the device.

### Wired interface In the "Wired interface" tab, the Ethernet interface status can be monitored, as well as media type, duplex mode and traffic load for reception and transmission. The wired interface statistic is available on the right side, it can be reset by the "Clear counters" button.

Parameter	Description
Runt packets	Packets less than 64 bytes in size.
Oversize packets	Packets larger than 9038 bytes.
FCS errors	Packets dropped due to checksum mismatch. The possible reasons for the error counter increasement are described in the "Troubleshooting⁣⁣⁣" article.
Port overflow errors	Packets dropped due to port buffer overflow.

### Wireless link status The “Radio” tab displays the current settings of the wireless connection, as well as the link load in the uplink and downlink directions.

Parameter	Description
Link ID	Wireless link can be established only with devices which have the same link ID.
Distance	The estimated link length.
Link uptime	The link operating time since the last outage.
Remote unit	The remote device name.
Center frequency	The downlink and uplink center frequency value set in the "Radio" section manually or by the automatic frequency selection mechanism.
Channel width	The channel width value set in the "Radio".
Instant DFS	Instant DFS option state (only for Quanta 5 family devices).
Traffic	The wireless link capacity and utilization in the uplink and downlink directions.
Frame size	The frame size value set in the "Radio".
DL / UL ratio	The ratio of the downlink traffic to uplink, set in the "Radio" section manually or by a mechanism for automatically determining the optimal ratio.
Tx power	The transmitter power value on the local device determined by the automatic power control mechanism for each polarization. If the automatic transmit power control tool is disabled, the value set manually by the user will be displayed.
Remote X power	The transmitter power value on the remote device determined by the automatic power control mechanism for each polarization. If the automatic transmit power control tool is disabled, the value set manually by the user will be displayed.

#### Availability statistics The link availability statistics window displays the following information: * The overall wireless link availability since the last device reboot, the number of wireless outages when the connection was unavailable. * Availability statistics for each modulation, for both polarization for downlink and uplink streams.

### Modulation code scheme Modulation and coding schemes are selected independently for each channel (uplink and downlink) for both polarizations. Current modulation for each channel is displayed in the MCS subsection.

### Received signal strength indicator The RSSI indicator displays the received signal level for each channel (uplink and downlink) and both polarizations. Available values: * **-90...-80 dBm** - close to the receiver sensitivity level, only the lowest modulations are available. * **-80...-60 dBm** - average input range. * **-60...-40 dBm** - the recommended range for achieving best performance. * **>-40 dBm** - input signal level is too high.

### EVM Error vector magnitude - indicator of the measured input signal quality, telling how far are the received constellation symbols compared to the ideal symbols of the constellation. The parameter value must be as high as possible in absolute value. The recommended level should be less than -21 dB.

### Retries and Frame loss Retried and lost packets need also to be tracked. Retries should tend to zero, link with the retries value more than 5% should not be allowed to operation.

{% hint style="warning" %} NOTE Downlink - the direction from Master to Slave, Uplink - the direction from Slave to Master. These directions are correct for the whole link and do not depend on the roles of the devices. {% endhint %} # General settings⁣⁣⁣⁣⁣ The "General settings" section allows to configure basic system parameters, described in the table below. ### Unit These parameters are used for identification and link authorization.

Parameter	Description
Device Name	The arbitrary wireless unit name which will be used by network administrators for unit identification. It will be shown in Web GUI side panel.

### SNTP Starts the SNTP time synchronization service. For proper operation, specify the SNTP server time zone and the IP address first. By default, the SNTP service is disabled.

Parameter	Description
SNTP Server Address	The SNTP server IP address, the SNTP service will synchronize the time on the device with. The device must have network access to the SNTP server.
Time Zone	The time zone at the place of device installation. For example: GMT + 5.

### Syslog Allows to transmit syslog data to the server using the "syslog" protocol. Specify the syslog server address where data should be transmitted.

### Radius AAA Here you may configure a device access control using a remote RADIUS server.

Parameter	Description
Address	Set the RADIUS server IP address.
Port	Set the RADIUS server port.
Secret	Set the server password.

### Network access whitelist This section is used to create a list of subnets from which access to the device will be allowed.

# Radio settings⁣⁣⁣⁣ The "Radio settings" section allows to configure radio parameters to establish wireless connection. ### Radio frontend

Parameter	Description
Unit role	One units must be set to Master and the other one to Slave.
Link ID	Wireless link identificator used to avoid connecting a unit to a wrong peer if there are several co-located units using the same center frequency. Specify different ID values for different links. Both ends of the same link must have the same ID. There are 16 identifier values available from 0 to 15.
Access key	Units at both ends of the wireless link should authorize each other before link establishment. Access key must be up to 64 characters long, without spaces and must be the same at both ends of the link.
Dynamic frequency selection	Following modes are possible to operation: Frequency selection off - the center frequency must be selected manually. Mandatory DFS and radar detction - the least noisy frequency will be selected in accordance with the set frequency grid. The device will block the frequency in case it detects a radar. Instant DFS - the least noisy frequency will be selected in accordance with the set frequency grid. The device will change frequency in case the strong interference appears. Instant DFS and radar detction - the least noisy frequency will be selected in accordance with the set frequency grid. The device will change frequency in case the strong interference appears and block the frequency in case it detects a radar. Note: The radar detection mode is only available with "ETSI" regulatory domain. Instant DFS and radar detection are only available for the Quanta 5 family devices. For detailed description of the listed modes proceed to the Instant DFS article.
Regulatory domain	Regulatory domain automatically limits the wireless device operation which is may be needed to meet the local law requirements. Each regulatory domain may limits the following parameters: Range of available center frequencies Requirement of use LBT (Listen Before Talk) technique. Maximum EIRP (Equivalent Isotropically Radiated Power) value. Requirement of use radar detection technique.
Fixed center frequency	Available only on the Slave unit. Enabled - center frequency must be set manually on wich the Slave unit will operate. Disabled - center frequenct will be selected automatically based on frequency channel grids.
Downlink/Uplink center frequencies	Allows to manually set the center frequency. The Quanta 5 family devices allow independent frequencies configuration for uplink and downlink streams. When same frequencies are used on both streams, transmission will be carried out in time division duplex (TDD) mode, when different frequencies are assigned for uplink and downlink traffic, the transmission mode will change to hybrid frequency division duplex (H-FDD). The uplink frequency can be configured only on the master. Note: Downlink - the direction from Master to Slave, Uplink - the direction from Slave to Master. These directions are correct for the whole link and do not depend on the roles of the devices.
Power limit	This parameter limits the transmitter power, there are two modes: Transmitter output power - limits the power of transmitter to the set value. EIRP - limits the total system power calculated as: Tx Power + Antenna gain + Cable loss (an antenna gain and cable losses should be specified in the fields below).

### Air frame

Parameter	Description
Channel width	Channel width, shoud be the same on both Master and Slave units. Available values: 3.5, 5, 7, 10, 14, 15, 20, 28, 30, 40, 50, 56 MHz.
Frame length	Frame period affects the following wireless link metrics: The greater frame period the more payload will be transmitted in one frame. Greater values increase latency. The lower frame period the less payload will be transmitted in one frame. Lower values decrease latency. Please note that frame period value is strongly depends on interference conditions. If larger frames will be dropped the larger payload is lost and system performance is decreased significantly. If smaller frames will be dropped the smaller payload is lost. Available values: 1, 2, 5, 10 ms.
Downlink /Uplink ratio	In automatic mode, the ratio changes dynamically in accordance with the transmitted traffic. Manual mode allows to set a fixed value. Available values depend from: Channel width. Frame length.

Parameter

Description

Channel width

Channel width, shoud be the same on both Master and Slave units. Available values: 3.5, 5, 7, 10, 14, 15, 20, 28, 30, 40, 50, 56 MHz.

Frame length

Frame period affects the following wireless link metrics:

The greater frame period the more payload will be transmitted in one frame. Greater values increase latency.
The lower frame period the less payload will be transmitted in one frame. Lower values decrease latency.

Please note that frame period value is strongly depends on interference conditions. If larger frames will be dropped the larger payload is lost and system performance is decreased significantly. If smaller frames will be dropped the smaller payload is lost. Available values: 1, 2, 5, 10 ms.

Downlink /Uplink ratio

In automatic mode, the ratio changes dynamically in accordance with the transmitted traffic. Manual mode allows to set a fixed value. Available values depend from:

Channel width.
Frame length.

### Automatic modulation and transmit power control

Parameter	Description
AMC strategy	There are following AMC strategies available: Normal - represents a balance between the error rate and throughput values. Conservative - assumes using higher CINR thresholds in order to minimize the error rate. Agressive - lowers the thresholds in order to use higher modulation levels and thus increase the throughput but also increase the error rate. Extreme - lowers the CINR threshold below the Aggressive strategy values in order to maximize selected modulation and throughput.
Automatic transmit power control	ATPC allows to control transmitter output power automatically based on target RSSI value. If actual RSSI level is lower then unit increases transmitter output power of the remote unit and vice versa. ATPC could not set value that may exceed the "Power limit" value. The Master unit manages the transmit power of Slave unit. The Slave unit manages the transmit power of Master unit.
Target RSSI	RSSI value which will be used by ATPC as target.

Parameter

Description

AMC strategy

There are following AMC strategies available:

Normal - represents a balance between the error rate and throughput values.
Conservative - assumes using higher CINR thresholds in order to minimize the error rate.
Agressive - lowers the thresholds in order to use higher modulation levels and thus increase the throughput but also increase the error rate.
Extreme - lowers the CINR threshold below the Aggressive strategy values in order to maximize selected modulation and throughput.

Automatic transmit power control

ATPC allows to control transmitter output power automatically based on target RSSI value. If actual RSSI level is lower then unit increases transmitter output power of the remote unit and vice versa. ATPC could not set value that may exceed the "Power limit" value.

The Master unit manages the transmit power of Slave unit.
The Slave unit manages the transmit power of Master unit.

Target RSSI

RSSI value which will be used by ATPC as target.

### Frequency channel grids The frequency grid allows to limit the scan range in case the center frequency is automatically selected. Also Instant DFS will use these restrictions when monitoring the noise situation. Narrow grid of available frequencies speeds up scanning and link establishing process. Manual center frequency selection will also be limited to the values indicated in the grid. {% hint style="warning" %} NOTE Please note grids shoud be the same on both Master and Slave units. {% endhint %}

# Network settings⁣⁣⁣⁣⁣ This section allows to assign an IP address or several addresses to the wired interface, the default gateway value can also be specified.

Click the "Add IP address" button to add a new address. There are two ways to assign an IP address: * Automatically - the IP address will be obtained automatically from the DHCP server. * Manual - the IP address and netmask are specified manually. The VLAN tag value can also be set in this section, the VLAN ID value should be in range from 1 to 4096. # Switch Settings ### Network ports Each family device has 3 ports: * ge0 - combo port, depends on physical connection type can be Gigabit Ethernet 1000BASE-T or SFP Port 1000BASE-X (to specify the connection type see "Wired interface" section on the Dashboard); * radio - internal radio interface; * mgmt - internal interface for device management.

Only ge0 interface is available to configure. The following parameters can be changed: * **Status:** enabled/disabled. * **Duplex:** duplex mode, "auto" is by default. * **Description:** arbitrary text description.

### QoS Enable/disable prioritization strategy. Unit will recognize the 802.1p tags in Ethernet frame headers. Based on these tags priorities will be autlomatically assigned to the frames when they are sent over the radio interface. After transmission over radio interface frames with tags are sent to Ethernet. Priorities may be adjusted manually if a VLAN based switching is enabled. ### VLAN based switching VLAN based switching allows to create list of allowed VLANs and their handling on the unit switch plane. If VLAN based switching is enabled but no VLANs are added, device ports will allow untagged traffic only. Each entry of list establishes the relationship between VLAN ID and ports VLAN modes. "VLAN 1" is created by default and could not be deleted, it's enough to set all interfaces to "off" mode to disable it.


VLAN ID	VLAN tag in range from 1 to 4095. May be set in a few ways, examples: 12 10-20 100,200,300 23,24,25,50-100
Description	Arbitrary text description.
Priority	Allows to set the priority of a specific VLAN according to 802.1p ranging from 0 to 7, where 0 - the lowest priority level, 7 - the highest, the QoS support function must be enabled.
Port mode	VLAN mode should be set for each of network ports. Mode determines the way which VLAN tagged network packets will be handled by switch. There are three ports modes: Off - denies all traffic of a specified VLAN. If none of the modes is selected, the port will be marked as "Off". Access - operates as access port, allows only untagged traffic. Tagged - operates as trunk port, allows tagged traffic of a specific VLAN to pass through this port Untagged - operates as trunk port, allows untagged traffic of a specific VLAN to pass through this port.

#### Connectivity matrix Allows to configure the traffic transfer between the network ports of the device. Configuration is performed visually using switches. The green switch indicates allowed connections, the red one - denied. Traffic flow between ports is performed in accordance with VLAN modes set, if the VLAN based switching is enabled.

# SNMP settings⁣⁣⁣⁣ SNMP allows the administrator to gather information about key device parameters and wireless links, including information about changes. The use of any monitoring system helps to timely receive information about the network infrastructure state using Astra devices. Currently, the devices family supports SNMP protocol versions v1 v2c and v3. The SNMP Protocol has two branches, the agent and the management stations: * The agent sends data to the management station. Monitoring system - provides data gathering from all agents in the network. * The monitoring system receives and processes events. * The information is passed through requests and replies with the use of the MIB. * The management station or monitoring system is responsible for decoding the SNMP packets and providing an interface to the administrator. #### General settings This section allow to enable/disable SNMP protocol support.

Parameter	Description
Location	The geographical location where the unit is installed, used as a reference information about the physical device’s location.
Enabled	Enable/disable the SNMP service in the device.
Contact person	A reference information about the device owner.

#### **SNMP v1/v2c**

Parameter	Description
Enabled	Enable/disable the SNMP v.1 and v.2c support. The first version of the SNMP protocol lacks security, that hinders its use for network management, so SNMP v.1 and v.2c operates in read-only mode. Enabled by default.
Community	Set the community name for read-only mode of SNMP v.1 and v.2c, by default: "public". The community name passes along with the data packet in clear text.

To add an SNMP v3 user, click the corresponding button and fill in the following fields:

Parameter	Description
User name	SNMP v3 user name.
Password	SNMP v3 password.
Security	Security level: "No auth / No privacy" – the lowest security level without authentication and privacy, only Username needs to be set. This level of protection does not allow management via the monitoring system. "Auth / No privacy" – middle level with authentication but without privacy, Username and Password are required. "Auth / Privacy" – highest level with authentication and privacy, Username, Password, Privacy Password and Privacy Protocol should be set.
Readonly	Enable/disable the read-only mode, readonly is set by defaut.
Admin	Enable/disable the full access to all parameters, for example, the ability to reboot the device. By default an access is limited.
Privacy password	Set the privacy password, it is necessary when privacy is enabled for the required security level.

Parameter	Description
Enable SNMP traps	Enable/disable SNMP traps sending.
Source IP address	Set the IP address of the device which sends traps

To create a new record, click the "**Add SNMP Trap**" button.

In the new window select the traps type to send and fill in the following parameters:

Parameter	Description
Destination address	Set the monitoring system server IP address.
Port	Set the monitoring system UDP port.

# Spectrum Analyzer⁣⁣⁣⁣⁣ In the "Spectrum Analyzer" menu, you can perform a deep analysis of the radio emissions in the environment where the unit is placed. The unit scans the radio spectrum on all available frequencies. In order to obtain the information as accurate as possible, the scanning process may take a while.

The following parameters are available in order to operate the Spectrum Analyzer:

Parameter	Description
Start Frequency	Set the first frequency for scanning (in MHz).
Stop Frequency	Set the last frequency for scanning (in MHz).
Scan step	Set the scanning frequency step (in MHz). It is recommended to set 1 MHz “step” value to get more precise scanning results.
Channel width	Set the bandwidth (in MHz).
Scan Duration	Set the time period for the scanning process (in seconds). After the end of this time period, scanning is stopped and the radio interface will be back to its normal mode operation.
Estimated scan time	Estimated scan duration.

Click on "Start scanning" button to start scanning. You may stop scanning by clicking on appropriate button. By clicking the "Last Snapshot**"** button, you get the final scanning results. The most common usage of this feature is when you perform a spectrum scan at the remote unit on the other side of the wireless link. When running a spectrum scan at such a unit (accessible via the RF interface), connection to this unit will be lost for a scan time. "*Last Snapshot*" option allows viewing scan results when the connection gets up again. # Antenna Alignment Tool⁣⁣⁣⁣⁣ The graphical antenna alignment tool allows to visualize the signal characteristics on both sides of the link in order to make the antenna alignment process more accurate and easier. It helps to find the best antenna position via comparing the actual received signal level with the calculated reference value. The accuracy of the antenna alignment at the neighbor device is very important for the link quality. Antenna alignment tool operates online and does not break the wireless connection. Each side of the link (local and remote) has two similar test indicator sets, corresponding to each antenna polarization. This allows controlling the alignment process for each antenna polarization for the local and for the remote device simultaneously. The main idea is to achieve the actual signal level (green square) is closer to the reference value (pale green area). Grey square shows maximal achieved value on each channel.

# Maintenance⁣⁣⁣ This section is available in the "Service" tab, is used for firmware updates, operations with licenses and configuration. Allows to view extended information about the device, reboot and reset to factory settings.

### **Device information** The following information is displayed on information panel: * Firmware version and build date. * Device serial number. * Device part number. * Hardware platform version. * Time since last reboot. * Last reboot reason, following values are possible: * Software fault. * Unexpected restart. * Manual restart. * Manual delayed restart. * Firmware upgrade. * SNMP managed restart. * Test firmware loaded. * Watchdog. * Panic. * System log.

### **License** License contains information about allowed frequencies, channel width and power limit. This section allows to view the current license and upload a new one. To upload a license on device, click the "Upload license" button drag and drop a file from your file manager into the dotted area.

### **Firmware** There are two options to upgrade firmware on the device: * Manually - new firmware should be downloaded from official FTP server . Click on "Upload firmware" button and choose a firmware file. Or you can drag and drop a file from your file manager into the dotted area. * Automatically - the device may offer you new firmware version automatically or after clicking "check for update" button. Click on "Update", after that your web browser will try to download the latest firmware version and upload it to the unit. Firmware will be applied after unit reboot.

### **Configuration** The device allows to upload, download and view current configuration in text form. To view the configuration, click the "Show current configuration" button, the file will open in new window. To download the configuration, click the "Download current configuration" button, the configuration can be loaded by clicking the "Upload configuration" button, or you can drag and drop a file from your file manager into the dotted area.

To upload and apply the configuration file that has been modified, please follow these steps: * Change the "check\_sum \" command to "check\_sum off" in the configuration file. * Upload the configuration file to the device. * Refresh the web page by pressing F5. * To apply the settings, click "Changes" in the upper right corner and click "Apply" in the window that opens. ### **Diagnostic card** In situation then helps of Astra Wireless technical support team is required, the diagnostic card is necessary tool which helps to detect and solve an issue faster and more effective. Click on "Download" button to create diagnostic card.

# Instant DFS⁣⁣⁣⁣ This section allows to monitor the Instant DFS tool operation in real time. To display the data in this section, the frequency selection must be set to "Instant DFS" or "Instant DFS and radar detection" mode. To enable the required mode, go to the "Radio" section.

At the top of the section there is information about the status of each band participating in the scan in accordance with the frequency grid. The upper stripe displays the band status discovered by the radar detection tool. The columns show the signal levels detected by the Instant DFS tool. There is the RSSI scale displaying the level of the detected signal in this band at the left side. Band statuses are described in the legend at the bottom of the section.

Scanning is performed in two directions: * Uplink - scans the spectrum state on the Master side. * Downlink - scans the spectrum state on the Slave side. Enabling the "Instant DFS" mode on one device automatically starts the scanning process at the remote end of the link.

Detailed information about the band status can be obtained by clicking on the corresponding column.

Use sliders on the scale at the bottom of the section to zoom in or zoom out the layout.

#### Dynamic Frequency Selection operation principles Several dynamic frequency selection modes are available for the Quanta 5 family devices. Please note, the time taken for the initial scan is the same for all modes and depends on the number of frequency channels allowed by the frequency grid. In addition to the described algorithms, an operation frequency can be changed because of the EVM threshold outreaching. **Instant DFS** In the Instant DSF mode the optimal frequency is selected only by analyzing RSSI values. The algorithm of the Instant DSF mode is following: 1. Initial scan of the allowed frequency channels. 2. Selection of the frequency with the lowest RSSI. 3. Establishing a wireless link. 4. Background scan of frequency channels to update information. The less noised frequency channel checking is performed with an interval of 600 seconds. 5. In case a channel with an RSSI indicator ≤ 3 dBm lower than the operational channel values is detected, the device switches to a more clear channel. 6. Go to point 4. In this mode, radars are not detected and processed. **Mandatory DFS and radar detection** In the Mandatory DFS and radar detection mode, both RSSI statistics and the statistics of the radar sequences presence are taken into account when selecting an operating frequency. This mode has the following algorithm: 1. Initial scan of the allowed frequency channels. 2. Selection of the frequency with the lowest RSSI value. 3. Carrying out the on-channel CAC procedure by the Master: the selected frequency is monitored for the presence of radar sequences for a specified time. 4. In case a radar is detected, the device moves to the next frequency with the best RSSI, the on-channel CAC check starts over. 5. The Master device detection by the Slave. 6. Carrying out the on-channel CAC procedure by the Slave. 7. Establishing a wireless link. 8. Background scan of frequency channels to update information. The operation frequency can be changed in case a radar is detected at the operating frequency or when the EVM threshold is outreached. If the Slave hasn't been connected within five minutes, after selecting the optimal frequency, the Master rescan the spectrum with the on-channel CAC procedure and re-selecting frequency. In case the radar is detected on the frequency channel, this channel is blocked and cannot be selected as an operational for 1800 seconds. By default, the on-channel CAC test time for the 5600-5650 frequency range is 600 seconds, for other frequency channels - 60 seconds. **Instant DFS and radar detection** In the Instant DFS and radar detection mode, both RSSI statistics and the statistics of the radar sequences presence are taken into account when selecting an operating frequency. This mode differs from the Mandatory DFS and radar detection by the background tool for checking the radar sequences presence on frequency channels that are not currently used as an operatinal, this tool is named off-channel CAC. 1. Initial scan of the allowed frequency channels. 2. Selection of the frequency with the lowest RSSI. 3. Carrying out the on-channel CAC procedure by the Master: the selected frequency is monitored for the presence of radar sequences for a specified time. 4. In case a radar is detected, the device moves to the next frequency with the best RSSI, the on-channel CAC check starts over. 5. The Master device detection by the Slave. 6. Carrying out the on-channel CAC procedure by the Slave. 7. Establishing a wireless link. 8. Background scan of frequency channels to update information about an RSSI values as well as checking by off-channel CAC. 9. Frequencies been checked by the off-channel CAC mechanism are marked as available. If it is necessary to change the frequency, the channel availability is analyzed first, the RSSI level is analyzed after. The operation frequency can be changed in case a radar is detected at the operating frequency, if the EVM threshold is outreached or a channel with an RSSI indicator ≤ 3 dBm lower than the operational channel values is detected. In case the radar is detected on the frequency channel, this channel is blocked and cannot be selected as an operational for 1800 seconds. **EVM Threshold** The algorithm for changing the operating frequency when the EVM parameter threshold value is outreached has been applied in all three of the above modes in the same way. The operating frequency is changed in case the EVM signal quality indicator passes the threshold value and remains low for a set time interval, by default 20 seconds. When the EVM value falls below the threshold and subsequently increases within the set time, the countdown starts over. # Graphs⁣⁣⁣⁣ The Graphs tool allows to trace the device parameters represented in the diagrams. Available modes: realtime tracking, displaying data for hour, day, week or month. Choose mode in the drop-down list located in the lower right corner of the "Graphs" section. By default, the system displays the daily data log. Scaling can be performed for all active diagrams using the timeline at the bottom of the page. To display a diagram of the certain device parameter values, activate this parameter at the top of the page. There are two display modes available: a list, where all graphs are arranged sequentially one below the other, and tiles with two graphs in a row.

Parameter	Description
ARQ	An indicator of the resent packets number.
Capacity	Available throughput of the wireless link, in Mbps.
EVM	Error vector magnitude - indicator of the measured input signal quality, telling how far are the received constellation symbols compared to the ideal symbols of the constellation. The parameter value must be as high as possible in absolute value. The recommended level should be less than -21 dB.
Frame loss	An indicator of the packets lost during transmission.
Load	Used throughput of the wireless link, in Mbps.
MCS index	Modulation and coding scheme selected for transmission.
RSSI	The RSSI indicator displays the received signal level for each channel (uplink and downlink). Available values: -90...-80 dBm - close to the receiver sensitivity level, only the lowest modulations are available. -80...-60 dBm - average input range. -60...-40 dBm - the recommended range for achieving best performance. >-40 dBm - input signal level is too high.

To display the precise parameter values at a certain point of time, hover the cursor over the graph at this place. # Troubleshooting⁣⁣⁣⁣⁣⁣⁣⁣⁣ This lesson describes basic troubleshooting actions to be taken in case a problem occurs to the wireless link. ### 1.No access to the local unit

#### **Checking the network infrastructure** Make sure there is connectivity between the control center and the device installation point. If the access is missing only to the Astra device, further verification must be performed at the installation site. #### **LED indication** Check the power supply to the device. The "POWER" indicator has three possible colors: * Red light - the device is connected to the electricity mains, * Yellow light - a wired connection with a speed of 10/100 Mbps * Green light - a wired connection with a speed of 1000 Mbps. Other indicators are used to perform coarse antenna alignment. The more indicators are on, the better wireless connection is established. The blinking indicator means an intermediate state. If there is no power, it is necessary to check the power supply, connectors, the Ethernet cables integrity.

#### Access to the unit recovery If the power indicator is on and there is connection via the Ethernet interface, connect to the device directly as it is shown in the scheme below. Make sure that the IP address of the PC is in the same subnet as the IP address of the device. You can restore the IP address and reset the device to the factory settings using the ERConsole utility.

Before starting the access restoring procedure, it is recommended to install the following software: * ERConsole :. Turn off any anti-virus or firewall running on your computer. If no device can be discovered by ERConsole, turn on the firewall, and add an UDP connection port 10009 as an exception . Use a simple unmanaged switch as intermediary device between your PC and the wireless unit. It is essential to reboot the Astra unit each time in order to activate the Emergency Repair Protocol on the unit, therefore the switch would prevent your PC Ethernet interface from flapping up and down. Using Cisco Catalyst switches for unit recovery is not recommended due to a known issue port mode negotiation delay. IP address should be configured on the PC for the ERConsole utility work. {% hint style="warning" %} NOTE ERConsole and Astra Wireless units exchange information only during the bootup process, therefore each time you need to read the units IP-address, to add a new IP-address or to restore to the default configuration, the Astra Wireless unit should be rebooted. {% endhint %} 1. Run the ERConsole application downloaded from our FTP. 2. Connect a network Ethernet cables between the Astra Wireless unit, unmanaged switch and your PC, as shown in the figure above. 3. Turn off the Astra Wireless unit by removing ethernet cable from power supply unit and then turn it on in a few seconds. 4. Wait for 30 seconds and the ERConsole screen should receive update from the unit as shown in the figure below. The Serial number, number of device reset cycles ("*Sequence*" field), IP-address, network mask and MAC-adress will be displayed on the screen.

5. If an IP-address is assigned to the unit, configure on your laptop an IP-address belonging to the same network and connect to the unit. If there is no IP-address displayed (0.0.0.0), proceed with the next step. {% hint style="warning" %} NOTE If the management of the unit is lost due to unknown user name or password it can be restored using factory password. Put an serial number of device in the "User name" field and factory password in the "Password" field. User's PC and Astra unit should belong to the same subnet. {% endhint %} 6. Obtain the Factory Password. In order to do this, please contact the distributor which the device was purchased from. The request must include the device serial number and the value of "Sequence" field (if it's non-zero). {% hint style="warning" %} NOTE In case of purchasing the unit directly in Astra Wireless, you may send a request to the Astra Wireless Technical support. Please be ready to provide a purchasing confirmation. {% endhint %} 7. Click the «**+**» button in the ERConsole application near the required device and a new window will appear. 8. In the new task window enter the Factory Password obtained at the previous step in the "Factory password" field, then click «Add». The password must be entered the same format as it has been got it from the distributor or support (with the gaps).

In the "Wired interface" section, you can monitor the wired interface status and its traffic load for reception and transmission. The wired interface statistics is on the right side and can be reset by clicking the "Clear counters" button. Pay attention to the FCS errors number which indicate a violation of data integrity during transmission over the wired segment. Also, the problem can be caused by a queue (port) overflow or inappropriate frame size (runt and oversize). {% hint style="warning" %} NOTE The FCS errors counter can increase due to the following reasons: * The device connection is performed using inappropriate cable. We strongly recommend to use FTP Cat5e cable with outside diameter not exceed 7 mm. * A shielded RJ-45 connector is used from the outdoor unit side. Make sure RJ-45 connectors are installed in the correct order. The shielded connector must be installed on the power supply side, the standard RJ-45 must be installed on the wireless device end. * The device is grounded incorrectly, make sure the device installation complies with the recommendations specified in the "Grounding ⁣and⁣⁣ Lightning⁣ Protection⁣" article. {% endhint %} Pay attention to the duplex mode on the network devices connected to the wireless bridge. The duplex mode can be changed in the "Switch" - "Network Ports" section. We recommend setting the autonegotiation mode provided by the Ethernet standard. The problem can occur while connecting two devices with different duplex settings. For example, if one device has the autonegotiation mode, and the other - fixed full duplex mode.

### 2. Wireless link is not established

**Pre-configuration in the lab** Before installing the devices on site, we recommend to configure the basic parameters in the lab and to make sure that the link is establishing. Step-by-step instructions for a wireless link configuration are given in the [Link pre-configuration](/astra-wireless-documentation/technical-documentation/astrawireless-quanta-technical-user-manual/link-pre-configuration-in-the-lab) in the lab⁣⁣⁣⁣⁣ article. {% hint style="warning" %} NOTE During the configuration of the devices in a lab, take into account the following requirements: * Make sure that the devices are not directed at each other in order to prevent the damage of the radio modules. It is recommended to place the devices at a distance from each other, with the antennas directed to the floor. * The minimum transmit output power must be set on the devices. * In case of using two devices with "E" index, it is recommended to connect them directly using RF cables and RF attenuators with an attenuation of at least 40 dB for each polarization (the installation\deinstallation of the RF attenuators and of the RF cables should only be performed when the devices are switched off). * The failure or damage of the device's radio module in case of disregarding these requirements is not covered by warranty. {% endhint %} **Checking the radio parameters** If the wireless link is not establishing in lab conditions, make sure that the radio parameters are set to the values determined during the planning stage. To establish a wireless link, one device must be configured as Master, the second (or all subscribers of the base station in the point-to-multipoint topology) as Slave. The following parameters must be identical on both devices: * Channel Width. * Frequency. * Frame length. * Access key.

#### **Checking the firmware version** In the "Maintenance" section, make sure that the same firmware version is installed on both devices. The latest software versions can be downloaded from the official FTP server.

#### Checking the installation requirements Check if the suspension height, azimuth and elevation of the antenna match with the values obtained from planner tool. Make sure that the obstacles on the path profile are not higher than those specified during the planning phase.

#### **Interference detection** Using the built-in Spectrum Analyzer tool, scan the air on both sides of the link to make sure there is no interference that could corrupt the signal on the device's operating frequency and on the adjacent frequencies. To get accurate information about the frequency, hover the mouse cursor over it. The pop-up window below provides information about frequency, maximum signal level, average signal level. The indicators show the signal level in dBm. For operation at the highest modulations, the RSSI parameter value should be in the range of -60 ...- 40 dBm. To get the spectrum scanning results on the remote device, use the "Last snapshot" button.

### 3. The wireless link is established, but there is no access to the remote device #### Checking the switch settings on the local device In the "Switch" section of the web interface, make sure the VLAN-based switching settings are configured in accordance with the network architecture. Make sure the connectivity between the "ge0" and "radio" interfaces is enabled.

#### Checking the switch settings on the remote device Further diagnostics should be performed at the device installation site. Try to access the device directly using the ERConsole utility. When accessing the web interface, in the "Switch" section, make sure the VLAN-based switching settings are configured in accordance with the network architecture. Make sure the connectivity between the "ge0", "radio" and "mgmt" interfaces is enabled in a connectivity matrix. In the "Network" section, make sure the correct VLAN ID is assigned to the management IP address and the default gateway is configured in accordance with network architecture.

### 4. The wireless link throughput is lower than expected #### The wireless link indicators Go to the web interface of both devices, check the new firmware version availability. Update the firmware if available. Check the EVM and RSSI parameters values in the dashboard section: * If the value of the RSSI parameter remains high while the CINR value decreases, it may indicate high interference levels near one of the devices. Use the "Spectrum analyzer" utility built into the web interface to determine the interference level on the current channel and select a new frequency channel. * The deterioration of both the RSSI and the CINR parameters can indicate a misalignment of the devices. Check the antennas alignment, the RF cables condition and the obstacles in the first Fresnel zone. Proceed to the "Radio" section and check the following settings: * The frame length value, if it is too small try to increase it; * Power limit, increase the value, make sure Automatic Transmit Power Control is enabled, target RSSI value matches expected values. Perform an antenna alignment using the built-in utility, especially in case the RSSI and EVM values are low.

#### Availability statistics To analyze the wireless link availability time, proceed to the corresponding statistics in the "Dashboard" - "Availability statistics" of web interface. The opened window displays the link operation statistics for each modulation.

### 5. Common errors in configuration #### Automatic transmit power control Enable the automatic transmit power control (ATPC) in order to increase the operational life of the devices. Set the "Target RSSI" parameter to values from -40 to -60 dBm.

#### Frame length Make sure the selected frame size ensures the best performance for your wireless system. A short frame will transmit less payload than a long one, however it ensures a smaller delay. # Astrawireless Evolution Technical User Manual **Astrawireless Evolution** product family was designed thanks to a combination of innovative technology, high reliability and the advanced functionality of the field‑proven family devices. **Evolution** wireless solutions are ideal for deployment in Point‑to‑Point and Point‑to‑Multipoint network topologies, especially to ensure seamless connection of nomadic and mobile units to central office.\ The new base station provides a sector capacity of up to 800 Mbps, enabling wireless operators of all sizes to not only deploy new infrastructures but also to extend the capacity of their existing networks. **Evolution** devices have full backward compatibility with previous generation wireless systems. ## About This Manual This manual provides detailed technical information for the **Astrawireless** **Evolution** family devices, including system specifications, installation, commissioning, maintenance and troubleshooting. The document is intended to be used by qualified RF engineers/technicians and IT professionals. Qualified personnel should have skills and experience with: * Outdoor/indoor radio equipment installation * Outdoor wireless networks * TCP/IP networking protocols * Safety procedures and instructions for installing antenna equipment * Professional manipulation with electrical equipment and accessories * Safety procedures and instructions for working at height. ## Important Notice ### Legal Rights © Copyright 2026 ⁣Astrawireless. All rights reserved. The information contained in this document is originated by, proprietary, confidential and owned by Astrawireless. No part of this document should be disclosed, reproduced or distributed without the express written permission of Astra Wireless Technology LLC-FZ. Astra Wireless Technology LLC-FZ reserves the right to change the information contained in this document without prior notice. No part of this document may be considered as a part of any contract or warranty. ### Statement of Conditions Astra Wireless Technology LLC-FZ shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this manual or equipment supplied with it. ### Disclaimer The software is sold on an "AS IS" basis. Astrawireless, its affiliates or its licensors make no warranties, whatsoever, whether express or implied, with respect to the software and the accompanying documentation. Astrawireless specifically disclaims all implied warranties of merchantability and fitness for a particular purpose and non-infringement with respect to the software. Units of product (including all the software) delivered to purchaser hereunder are not fault\_ tolerant and are not designed, manufactured or intended for use or resale in applications where the failure, malfunction or inaccuracy of products carries a risk of death or bodily injury or severe physical or environmental damage (“high risk activities”). High risk activities may include, but are not limited to, use as part of on-line control systems in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, life support machines, weapons systems or other applications representing a similar degree of potential hazard. Astrawireless specifically disclaims any express or implied warranty of fitness for high risk activities. ### Indication of the countries Astrawireless equipment has no geographical limitations for selling and can be supplied to any country of the world. ### Limitation of Liability Astrawireless shall not be liable to the purchaser or to any third party, for any loss of profits, loss of use, interruption of business or for any indirect, special, incidental, punitive or consequential damages of any kind, whether arising under breach of contract, tort (including negligence), strict liability or otherwise and whether based on this agreement or otherwise, even if advised of the possibility of such damages. To the extent permitted by applicable law, in no event shall the liability for damages hereunder of Astrawireless or its employees or agents exceed the purchase price paid for the product by purchaser, nor shall the aggregate liability for damages to all parties regarding any product exceed the purchase price paid for that product by that party (except in the case of a breach of a party’s confidentiality obligations). ### Disposal instructions

On the territory of the European Union, following applies: * the equipment is intended for outdoor use only; * in the band 5470-5725 MHz, choice of the transmit power and antenna gain (in case of devices with detachable antenna) shall be such that the equipment still complies with the EIRP limit and EIRP density limit. EIRP limit in that band is 1W (30dBm), EIRP density limit is 50mW/MHz (17dBm/MHz); * In the band 5725-5875 MHz, choice of the transmit power and antenna gain (in case of devices with detachable antenna) shall be such that the equipment still complies with the EIRP limit and EIRP density limit. EIRP limit in that band is 4W (36 dBm), EIRP density limit in that band is 200mW/MHz (23dBm/MHz). {% endhint %} # Introduction⁣⁣⁣⁣⁣⁣ ## Document structure This document consists of the following chapters: * [Introduction⁣⁣](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/introduction) - presents the information about this document’s purpose and structure. * Planning considerations - describes the principles of wireless system planning. * Installation⁣ - describes the steps to be taken when installing the equipment at the installation sites and installation site requirements. * Operation & Administration - presents the functionalities of the web interface, a simple and efficient way to monitor the device status, configure and maintain the equipment. * Troubleshooting - describes the actions to be taken during occured problems investigation. ## Document marks {% hint style="danger" %} CAUTION All caution warnings are marked with a special warning sign. One should pay a great deal of attention to what is written in the Caution section. {% endhint %} {% hint style="warning" %} NOTE All notes are marked with a special note sign. Notes usually contain useful comments or hints to the described section of the document. {% endhint %} # Key Features⁣⁣⁣⁣⁣⁣⁣ Astrawireless Evolution is a wireless point-to-point and point-to-multipoint solution with an impressive maximal performance of up to 800 Mbps. It operates in 5 and 6 GHz frequency ranges: from 4900 to 6425 MHz and supports the channel width 20, 40, 80 MHz. **Base Stations can be used with:** * a dual polarization integrated antenna with an antenna gain 16 dBi and 21 dBi (beamforming); * an external antenna connected to two N-type ports using low-loss RF cables. **Subscriber terminals and PTP devices can be used with:** * a dual polarization integrated antenna with an antenna gain 18 dBi, 23 dBi, 25 dBi, 26 dBi, 28 dBi and 29 dBi; * an external antenna connected to two N-type ports using low-loss RF cables. and operates in LOS and non-LOS conditions. OFDM radio technology is used for data transmission. ### Radio * **Automatic Modulation Control (AMC)** – modulation control algorithm selects the most appropriate modulation-coding scheme in order to maximize the link performance. * **Automatic Repeat Request (ARQ)** – a technology which enables packet re-transmission in case of previous unsuccessful delivery, allows to achieve reliable connectivity even in highly congested spectrum. * **Automatic Transmit Power Control (ATPC)** – a technology which allows to extend the life of devices and optimize energy consumption. * **Automatic range detection** - the guard interval optimal for the actual distance is automatically determined. ### Networking * MAC/IP filtering. * RIPv2 / OSPFv2 /static routing. * Tunneling (Ethernet‑over‑IP, IP‑over‑IP). * L2/L3 Firewall. * NAT (multipool, H.323‑aware). * DHCP client/server/relay. * Stacked VLAN support (Q-in-Q) avoids the limitation in the number of available VLANs (4096), which can be useful for large networks. In addition, Q-in-Q allows you to organize L2 channels within a limited VLAN list, which is widely used in provider networks and on leased communication channels. ### Quality of Service * 17 priority queues. * IEEE 802.1p support. * IP TOS / DiffServ support. * Full voice support. * Traffic limiting (absolute, relative, mixed). * Traffic redirection. ### Environment * Operating temperature range -40 ... +60 ºС, in an extended temperature range: -55 ... +60 ºС. * Dust and water protection in compliance with IP66/IP67. * Wind load up to 160 kph - operation, 200 kph - survival. ### Power The device has following electrical parameters: * Consumption is up to 20 W for base station sectors ( 30W for E5-BSQ) and up to 15 W for subscriber terminals. * Power options: 90-240 VAC\~ @ 50/60 Hz, ±43..56 VDC. * 802.3at support or proprietary passive PoE. * AC/DC injector: * IDU-CPE-G(56W) is included to the packing list of E5-BSQ model. * IDU-CPE-G(24W) is included to the packing list of all other models. # Hardware Platform⁣⁣⁣⁣⁣⁣⁣⁣ ### Wireless device The wireless device contains both the radio and networking electronics. Implemented in a robust all-weather metal enclosure, this equipment can be used to create point-to-point and point-to-multipoint wireless links at long distances. The wireless device is supplied in the following configurations: #### **Base Station Sectors** * with integrated antenna 16 dBi (E5-BSI, E6-BSI, E5-BSIL, E6-BSIL); * with integrated antenna 18 dBi (E5-BS18L, E6-BS18L); * with integrated beamforming antenna 21 dBi (E5-BSQ); * with two N-type ports for an external antenna (E5-BSE, E6-BSE). Appearance for all BS models except for E5-BSIL, E6-BSIL, E5-BS18L, E6-BS18L:

**Base Station Sectors Interfaces** Base station sectors have ports: * 1x Gigabit Ethernet port (10/100/1000 Base‑T), RJ‑45 connector: Data + Power. * 1x SFP port: Data. * 1x SYNC port for AUX‑ODU‑SYNC connection.

Interface	Description
Gigabit Ethernet	RJ-45 socket for connecting to power supply and data transmission. The network connection to the wireless device is made via a 1000Base-T (Gigabit) Ethernet connection. Power is provided to the device over the 1000Base-T Ethernet connection using a standard IEEE 802.3at passive PoE power supply.
SFP	External optical Gigabit port for plugging of the optical SFP transceiver module.
SYNC	RJ-45 socket for connecting to synchronization unit AUX‑ODU‑SYNC.

{% hint style="warning" %} NOTE Power and wired statuses indication is performed via glassy plug of the cable gland. {% endhint %}

State	Status	Description
Flash	Initialization	The LEDs on both ports light up with white on second. Then LEDs check is performed: red, blue, green are lightened up sequentially.
Flash	Loading	Only for Gigabit Ethernet port: at the beginning green is lightened a few seconds, on the second loading stage switches to blue.
ON/Blue	Power	Only for Gigabit Ethernet port.
ON/Green	Speed 1000 Mbps
ON/Green	ERConsole stage	Port with the established link lights up with green, the second port remains blue.
ON/Red	Speed 10 Mbps	Only for Gigabit Ethernet port.
ON/Yellow	Speed 100 Mbps	Only for Gigabit Ethernet port.

#### **Subscriber Terminals, BSL and point-to-point devices** * with integrated antenna 18 dBi; * with integrated antenna 23 dBi; * with integrated antenna 25 dBi; * with removable antenna 26 dBi; * with integrated antenna 28 dBi; * with removable antenna 29 dBi; * with two N-type ports for an external antenna.

**Subscriber Terminals BSL and PTP devices Interfaces** RJ-45 socket for connecting to power supply and network via the PoE power supply. The network connection to the ODU is made via a 1000Base-T (Gigabit) Ethernet connection. Power is provided to the ODU over the 1000Base-T Ethernet connection using a standard IEEE 802.3at passive PoE power supply. **LED Panel** PWR - power indicators will light red when the device is connected to a power source, yellow when 10/100 Mbps wired connection appears and green when 1000 Mbps wired connection appears. Other indicators are used to perform coarse antenna alignment. Seven LEDs are used to indicate the signal level. The displayed value is the SNR level for both reception and transmission (the minimum value is displayed). The SNR range for each indicator is shown in the table below. | SNR, dB | LED indicator | Color | | ------- | ------------- | -------------- | | 10–15 | 0 | Red | | 16–21 | 1 | Red | | 22–27 | 2 | Green | | 28–33 | 3 | Green | | 34–39 | 4 | Green | | 40–45 | 5 | Green | | 46–50+ | 6 | Red (overload) | The more indicators are on, the better wireless connection is established. The blinking indicator means an intermediate state. The more often the indicator blinks the higher level connection is established.

#### Terminal units Terminal units equipped with four N-type connectors, are available in the following variations: * E5-TU - with one 5 GHz radio module * E6-TU - with one 6 GHz radio module * E5/6-TU - with two 5+6 GHz radio modules * E5/5-TU - with two 5+5 GHz radio modules

The following options are available to power the device: \- via Eth0: * 90-240 VAC \~ @ 50/60 Hz ±43..56 VDC * Passive PoE or 802.3at \- via AUX DC-IN: ±12V..56V **Terminal unit Interfaces** Terminal unit have ports: * 1x Gigabit Ethernet port (10/100/1000 Base‑T), RJ‑45 connector: Data + Power. * 1x Gigabit Ethernet port (10/100/1000 Base‑T), RJ‑45 connector: Data, PoE out. * 1x SFP port: Data. * 1x DC-in port for direct power supply ±12V..56V. {% hint style="warning" %} NOTE Power and wired statuses indication is performed via glassy plug of the cable gland. {% endhint %}

State	Status	Description
Flash	Initialization	The LEDs on all ports light up with white on second. Then LEDs check is performed: red, blue, green are lightened up sequentially.
Flash	Loading	Only for Gigabit Ethernet port: at the beginning green is lightened a few seconds, on the second loading stage switches to blue.
ON/Blue	Power	Only for Gigabit Ethernet GE0 port.
ON/Green	Speed 1000 Mbps
ON/Green	ERConsole stage	Port with the established link lights up with green, the other ports remains blue.
ON/Red	Speed 10 Mbps	Only for Gigabit Ethernet port.
ON/Yellow	Speed 100 Mbps	Only for Gigabit Ethernet port.

### Part number description **Astrawireless Evolution** part number has the following structure

Structure items are described below:

Item	Description
1	Product family name: E - Evolution family.
2	Frequency range: 5 - device in the range of 5 GHz. 6 base station sector or terminal unit in the range of 6 GHz . subscriber terminal or BSL in the ranges of 5 and 6 GHz.
3	BS - base station sector. ST - subscriber terminal or PTP device. TU - terminal unit device.
4	Antenna gain. Base Station Sectors: I - integrated antenna with 16 dBi gain; Q - integrated antenna with 21 dBi gain; E - devices for an external antenna connection. Subscriber Terminals and PTP devices: 18 - integrated antenna with 18 dBi gain; 23 - integrated antenna with 23 dBi gain; 25 - integrated antenna with 25 dBi gain; 28 - integrated antenna with 28 dBi gain; E - devices for an external antenna connection.
5	Additional options: t - extended temperature range: -55 ... +60 ºС. c - subscriber terminal for PtMP topology (cannot be a "master"). d - device modified for AstraDRIVE system. L - base station on H26 platform with 5 subscriber limitation. hp - high power ST with output power 27 dBm and 780 Mbps max performance.

# Power supply⁣⁣⁣⁣⁣⁣⁣ ### Indoor AC/DC injector IDU-CPE-G(24W)

IDU-CPE-G(24W) is an indoor Gigabit PoE injector which supports 100-240 V input range from the AC mains. IDU-CPE-G(24W) feeds 48 VDC power to the device by injecting it to the CAT5 Ethernet cable.

Parameter	Description
Compatible models	Astrawireless Quanta and Astrawireless Evolution (except E5-BSQ), AUX-ODU-SYNC
Size and weight	97x53.5x33.5 mm, 0.133 kg
Connectors and Interfaces	"LAN" - Ethernet input (Data only) "POE" - Ethernet output (Data+VDC), PASSIVE PoE "PWR" - AC Input
Supported Ethernet Modes	10/100/1000 Mbps
Standards	IEEE 802.3 10Base-T IEEE 802.3U 100Base-TX IEEE 802.3ab 1000Base-T
Input Power Requirements	AC Input Voltage: 100 ... 240 VAC AC Input Current: 0.75 A AC Frequency: 50 to 60 Hz
Consumption	28 W
Operating temperature range	-10 °С ... +40 °С
Operating humidity	Maximum 95 %, Non-condensing
Storage temperature	-40 °С ... +70 °С
Output Power Voltage	48 VDC, 0.5 A
Safety	UL cUL, CE, GS, CCC, FCC, S-MARK, PSE, C-tick, KC(48V0.5A) BIS（24V1A

IDU-CPE-G(56W) is an indoor AC/DC PoE injector with built-in lightning protection. PoE injector is powered by an AC supply in the 100-240 V range.

Parameter	Description
Compatible models	Astrawireless Quanta, Astrawireless Evolution
Connectors and Interfaces	"LAN" - Ethernet input (Data only) "POE" - Ethernet output (Data+VDC), PASSIVE PoE "PWR" - AC Input
Consumption	60 W over 4-pairs (Guaranteed)
EMC	Meet: FCC Part 15, Class B
Input Voltage	100 ... 240 V
Lightning Protection	In compliance with: IEC 61000-4-2 (ESD) 15kV (air), 8kV (contact) IEC 61000-4-4 (EFT) 40A (tp = 5/50ns) IEC 61000-4-5 (Lightning) L5, 95A (tp = 8/20us)
Operating temperature range	0 °С ... +40 °С
Output Voltage & Current	+56 V, 1 A
Pin Assignment and Polarity	1/2 (+) and 3/6 (-) 4/5 (+) and 7/8 (-)
Size	137.5x62.5x33 mm
Supported Ethernet Modes	10/100/1000Mbps (Gigabit Ethernet pass-through)
Weight	0.24 kg

### Indoor DC/DC injector with integrated lightning protection IDU-LA-G(V.01) IDU-LA-G(V.01) is an indoor DC/DC injector. It greatly reduces complexity of the deployment in the cases where DC source is available thus reducing both capital expenditures and total cost of ownership. IDU-LA-G(V.01) may be used for the following purposes: * To serve as a line protection unit for indoor network equipment connected to the second Ethernet port on ODU. * To connect third-party DC power sources to ODU (for example, to power the unit from solar power or wind power sources). #### **Technical parameters**

Parameter	Description
Compatible models	Astrawireless Quanta, Astrawireless Evolution
Output Voltage	The same as input
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Pin assignment and polarity	1/2 (+), 3/6 (-), 4/5 (+), 7/8 (-)
Size and Weight	115×65×40 mm, 0.15 kg
Operating temperature range	From 0°С to +40°С

#### **Mounting holes sizes**

#### IDU-LA-G(V.01) Packing List

#### **Cable assembly**

### Lightning Protection Unit with Injector AUX-ODU-INJ-G

Parameter	Description
Size and Weight	34x94x121 mm, 0.28 kg
Connectors and Interfaces	ETH IN - Ethernet input ETH OUT - Ethernet output (data+VDC, protected leg) PWR - DC Input GND - Ground clamp
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Water and Dust Protection	IP66 and IP67
Operating temperature range	-55 °C ... +60 ºC
DC Range	±43...±56 VDC
Lightning Protection	In compliance with: GR-1089 IEC 61000-4-2 (ESD) 15kV (air), 8kV (contact) IEC 61000-4-4 (EFT) 40A (tp = 5/50ns) IEC 61000-4-5 (Lightning) L5, 95A (tp = 8/20us) ETSI ETS 300 386

AUX-ODU-LPU-L is a bidirectional external outdoor lightning protection unit for Astrawireless systems designed to withstand the toughest conditions and protect the outdoor unit or the 3rd party networking equipment installed indoors from sudden power surges induced by lightning strikes. Despite the fact every Astrawireless device has a built-in lightning protection. AUX-ODU-LPU-L, thanks to its superior GR-1089-grade protection, greatly reduces the risk of damage for the systems operating in harsh environments or difficult-to-reach locations. AUX-ODU-LPU-L is compatible with all Astrawireless devices. {% hint style="warning" %} NOTE The device is not supplied by default and must be ordered separately. {% endhint %}

Parameter	Description
Size and Weight	45x92x55.5 mm, 0.13 kg
Connectors and Interfaces	2 x Ethernet ports Ground clamp
Supported Ethernet Modes	10/100/1000 Mbps (Gigabit Ethernet pass-through)
Water and Dust Protection	IP66 and IP67
Operating temperature range	-55 °C ... +60 ºC
Opening voltage of the arrester	150 V
Lightning Protection	In compliance with: GR-1089 IEC 61000-4-2 (ESD) 15kV (air), 8kV (contact) IEC 61000-4-4 (EFT) 40A (tp = 5/50ns) IEC 61000-4-5 (Lightning) L5, 95A (tp = 8/20us) ETSI ETS 300 386

#### **Ethernet Pin-out** | Pin | Data pair | | --- | --------- | | 1 | A+ | | 2 | A- | | 3 | B+ | | 4 | C- | | 5 | C+ | | 6 | B- | | 7 | D+ | | 8 | D- | #### Packing list

**AUX-ODU-SYNC** is a TDD synchronization hub, which has been designed to provide a timing reference to Base Stations sectors of Evolution family devices. In combination with proprietary TDMA-based wireless architecture, AUX-ODU-SYNC completes the solution, providing TDD synchronization to its systems, both legacy and newly deployed. TDD synchronization eliminates self-interference between multiple co-located units and enables frequency re-use within the same site. Astrawireless’s implementation supports not only intra-, but inter-site synchronization too, thanks to the fact that the timing reference is GNSS-based.

Parameter	Description
Compatible models	Evolution BS: E5-BSI, E5-BSQ, E5-BSE, E6-BSI, E6-BSE
Compatible power supplies	IDU-BS-G(56W) IDU-CPE-G(24W) AUX-ODU-INJ-G IDU-LA-G(V.01)
Consumption, W	up to 4
GNSS antenna	Embedded, active
GNSS receiver	Embedded, GPS/GLONASS
Indicators	Indicators is located near the power port of AUX-ODU-SYNC: POWER - power. SYNC - TDD synchronization.
Input voltage, VDC	±19..±56
Interfaces and connectors	Port 0-6: sync outs (7 RJ-45 connectors to connect to ODU with special cable CAB-SYNC-E) Power: DC input (1 RJ-45 connector)
PoE type	Passive PoE (4,5,7,8 Ethernet pins used)
Size and Weight	180х170х75mm, 0.65kg
Temperature range	ODU: -40…+60°С IDU: 0...+40°С
Water and Dust protection	IP66 and IP67

### AUX-ODU-SYNC Mounting AUX-ODU-SYNC can be installed on a pole, using fasteners from the delivery package: 1. Screw the threaded rod to the unit case. 2. Tighten the device and the bracer on the pole and fix them by the threaded rod using the nuts and washers as shown at the picture 3. Attach the grounding cable to the unit case using the grounding bolt.

{% hint style="danger" %} CAUTION Missing or bad grounding may leave the unit vulnerable to lightning damage. {% endhint %} ### AUX-ODU-SYNC Cable gland Assembling In order to ensure that the cable gland remains sealed under any environmental conditions, please, follow the assembly sequence according to the procedure below: 1. Put the cable gland nut (1), the split sealing grommet (2) and the cable gland threaded coupling (3) onto the cable 2. Crimp the connector onto the cable using the crimping tool: 1. For connection to the port Power terminate the FTP Cat.5e cable with the unshielded RJ-45 connector (4) according to the EIA/TIA-568B. Do not use the shielded RJ-45 connector on this end of the cable as it should be attached on the IDU end (to provide grounding circuit) 2. For connection to the ports 0-6 use the ready-assembled specialized CAB-SYNC-E (5) cables 3. Insert the connector of the pre-terminated cable into the corresponding socket until you hear a click 4. Screw the cable gland threaded coupling (3) into the port and tighten it. Do not apply excessive force 5. Tighten the sealing grommet (2) by the cable gland nut (1). Do not apply excessive force. {% hint style="danger" %} CAUTION Make sure that the connector is well-crimped. A loose connector can damage the device. Please note that such damage is not covered by the warranty. {% endhint %}

{% hint style="danger" %} CAUTION Please note that the pressure equalization system in Astrawireless devices is performed via gas exchange through a cable gland and Ethernet cable jacket with a dry room where the power supply is installed. In order to avoid AUX-ODU-SYNC failure due to moisture entering the device, for example, during the pressure drop during the rain, the cable gland assembly requirements should be met and there are should be no cracks in the Ethernet cable jacket. In addition, you should avoid the Ethernet cable bending near the AUX-ODU-SYNC and pinching with clamps, that can bring to the pressure equalization system fault between the internal volume of the sealed AUX-ODU-SYNC and the external environment during a sudden air temperature change. This may lead to the leakage and device failures. {% endhint %} ### AUX-ODU-SYNC Connection to ODU To connect AUX-ODU-SYNC to the units use the ready-assembled specialized CAB-SYNC-E cables which must be ordered additionally. Information about CAB-SYNC-E cables is available at Astrawireless web site in the "Accessories" section. To connect AUX-ODU-SYNC to ODU insert the RJ-45 connector with cable gland of the CAB-SYNC-E into the corresponding socket of the ODU until you hear a click. Perform the device port insulation with a cable gland as instructed above.

# ⁣⁣⁣Packing List Before the installation, please make sure you have all necessary parts and accessories. #### Evolution BS packing list * Outdoor unit (ODU). * Power supply. * Cable gland (x3). * Shielded RJ-45 connector. * Unshielded RJ-45 connector. * Mounting kit - universal assembling kit for mounting the ODU on standard pole, wall or thick pipe (vertical/horizontal). * Power cord - the model depends on the region, according to the Purchase Order. #### Evolution STE packing list (except devices with 18 dBi antenna gain) * Outdoor unit (ODU). * Power supply. * Cable gland. * Shielded RJ-45 connector. * Unshielded RJ-45 connector. * Mounting kit - universal assembling kit for mounting the ODU on standard pole, wall or thick pipe (vertical/horizontal). * Power cord - the model depends on the region, according to the Purchase Order. #### E5-ST18, E6-ST18 packing list * Outdoor unit (ODU). * Power supply. * Cable gland. * Shielded RJ-45 connector. * Unshielded RJ-45 connector. * Power cord - the model depends on the region, according to the Purchase Order. * Nut M6 DIN 934 A4 (x2). * Washer 6 flat (x2). * Washer 6 spring (x2). * Threaded rod M6x90 (x2). * Bracer. #### Terminal unit packing list * Outdoor unit (ODU). * Power supply. * Cable gland (x4). * Shielded RJ-45 connector. * Unshielded RJ-45 connector (x2). * Power cord - the model depends on the region, according to the Purchase Order. * Nut M6 DIN 934 A4 (x2). * Washer 6 flat (x2). * Washer 6 spring (x2). * Threaded rod M6x90 (x2). * Bracer. * Basement. # Planning considerations⁣⁣⁣⁣⁣⁣⁣⁣⁣ During link planning, such factors as distance, obstacles and the link margin should be taken into account. We strongly recommend to use a [planner tool](https://planner.astrawireless.net/) for link planning. ### Range and obstacles Make sure that line of sight is provided when planning the antennas' placement for a point-to-point link in order to achieve maximum range and performance between two antennas. Perform a survey to identify all the obstructions (such as trees or buildings) in the path and to assess the risk of interference. The radio beam is an electromagnetic wave and it is not as thin as a laser beam, for example. The main energy in a radio beam is concentrated along the straight line between the two antennas, inside an area with the shape of an ellipsoid (or a rugby ball). This area is called the 1st Fresnel zone and its exact form and size depend upon the frequency and the signal propagation path length. If most of the 1st Fresnel zone is obstructed, a major part of the radio wave’s electromagnetic energy is lost, which leads to a severe signal quality degradation and as a result to a decreased coverage range or performance. Below is an incomplete list of possible obstructions along the signal propagation path: * Neighboring buildings. * Trees. * Bridges. * Power lines. To obtain the best results, it is necessary to perform a precise analysis of the signal propagation path and possible obstructions that may obstruct the 1st Fresnel zone.

### Antenna Installation General recommendations for antenna installation: * Try to keep the LOS clear of obstructions. In case of installations over vegetation and forest, make sure the direct LOS stays above the trees; in urban environments - above the tallest buildings along the radio path. * The influence of trees can be variable, depending on the season (ice, dew, leaves). Keep in mind that, during spring and summer, leaves can absorb high levels of radio energy. Therefore, when installing during the cold season, over forests and trees without leaves, try to achieve a higher fade margin. * Install the devices at a distance of at least 100-150 meters from power lines having a voltage higher than 35 kV. * Before installation, make sure the devices are located outside the area of water streams and splashes formation, which can affect the enclosure for a long time. * Install antennas as far as possible from other antennas (the recommended distance is at least 2 meters between edges of the antennas). * Reflecting surfaces should be considered (buildings with reflective windows, water surfaces or wet grounds). These can be useful in NLOS situations, if there is no direct clear path between the 2 antennas, so the radio signal needs to be reflected by a surface. However, reflections can also decrease the signal quality when encountered along a clear LOS link, because of fading caused by multipath propagation. * When installing antennas over the water, tune the height bracket within a 1-3 meters range variation, because it can yield significant signal level variations due to multipath fading.

### Spectral aggregation It is recommended to place base station sectors above the subscriber terminals as high as possible to provide proper antenna tilt in vertical direction and to minimize self-interference. The optimal antenna tilt is defined by the vertical beam width of the sectoral antenna and by the required sector coverage. It must cover all the area, where you plan to deploy the subscriber terminals. Spectral aggregation should be taken into account when planning composite backhauling links, when installing devices in close proximity to each other on the same pole or in order to implement redundancy and link aggregation. For more information, proceed with the "[Link aggregation, balancing and redundancy](/astra-wireless-documentation/white-papers/link-aggregation-balancing-and-redundancy)" article. The devices located close to each other can cause mutual interference. Do not ignore the spectral aggregation rules, otherwise it can lead to a degradation of the wireless links. The document will provide recommendations on distance and frequency separation for scenarios with and without an external synchronization hub. An external clock source allows you to synchronize the time (the beginning of each second) on multiple devices, up to 7 devices, with an accuracy of less than a microsecond so that all connected devices can turn on the transmitters at the same time. This completely eliminates the mutual influence of neighboring sectors, when one transmitting device with its powerful signal prevents the neighboring device from receiving weak signals from its terminals. Wireless devices synchronization using AUX-ODU-SYNC makes it possible to reuse the frequency within the same base station, that is, different sectors of the same base station can operate on the same frequency channels. When using synchronization, a four-sector base station can operate on only two frequency channels, significantly increasing the real spectral efficiency of the system. Mutual interference occurs not only between sectors and subscriber terminals of one multi-sector base station, but also between different base stations when they are densely located in a limited frequency range. Synchronization of base stations prevents mutual interference of such base stations and subscriber terminals that working with them. Recommendations for istance and frequency separation for a four-sector ABAB base station are given below. #### Without synchronization * Distance separation (vertical or horizontal) must be at least two meters between the edges of the antennas. * Reduce the transmission power. #### With synchronization 4 collocated base stations mounted back-to-back. The recommended guard interval between the end/boundary frequencies of the occupied bands of the neighboring sectors 5 MHz.

### Synchronization settings To perform synchronization using an external hub, each base station sector must be connected to an AUX-ODU-SYNC. The following conditions should be met: * Frame size and DL/UL ratio should be equal on all sync-end units. * The automatic downlink ratio selection is not allowed. {% hint style="warning" %} NOTE The AUX-ODU-SYNC antenna is not included in the standard packing list. {% endhint %} #### Configuration via web interface To enable synchronization via web interface: * Go to the section "Basic Sttings" → "Link Settings" → "rf6.0". * Check the box "Use AUX-ODU-SYNC" and click "Apply". Synchronization status and the number of visible satellites is displayed in the "Device Status" -> "Link Statistics" section.

Additionally in order to determine the device coordinates GNSS position can be enabled. * Go to the section "Basic Settings" -> "System Settings". * Check the box "Enable GNSS Receiver" and click "Apply" button.

Click "Open map" to view the device location. The map is updated in real time that allows to monitor the movement of the device mounted on the mobile object. #### Configuration via CLI Enable synchronization: ``` // tsync enable ``` The synchronization mode information: ``` // tsync ``` The following parameters will be displayed:

Parameter	Description
Total GPS time	Total time of GPS operation
Total nonvalid time	Total time during which the information about coordinates was unavailable
Number of losses	Quantity of cases when the information about coordinates had become unavailable
Now coordinates are valid last ...	Time of GPS operation since last coordinates discovering
Sattelites histogram	Histogram of visible satellites quantity
SATmin	Minimum of visible satellites (since the last time you cleared the statistic)
SATmax	Maximum of visible satellites (since the last time you cleared the statistic)

## Important notice {% hint style="warning" %} NOTE

**Step 2: Access to the device** Let's access each unit to the default IP address 10.10.10.1 with mask 255.255.255.0 via a web browser. Before, make sure the Ethernet port of the Laptop has an IP address assigned from the same subnetwork as the one for the unit (e.g., set 10.10.10.10 with mask 255.255.255.0). {% hint style="warning" %} NOTE We assume that each unit used in this setup has not been configured before and runs with the factory settings. {% endhint %} Use any letters or numbers for the initial authentication on each unit, for example: * Login: login. * Password: password. {% hint style="warning" %} NOTE We strongly recommend to change your login and password after the first login. {% endhint %} After the first login, let's configure a distinctive name for each unit and set a custom login and password. Go to the Basic Settings section, then to System Settings and configure:: * Device Name (e.g., Master/Slave). * User Name (e.g., admin). * Password (e.g., admin).

{% hint style="warning" %} NOTE At the next login set up login and password to access the unit in the privileged mode. {% endhint %} **Step 3: Management IP change** Let's change the management IP of each unit. Go to the "Basic Settings" section, then to Network Settings and change the default IP address of the ‘svi’ interface which is a logical interface used for remote management access in MINT switching mode (MINT switching mode is enabled by default). Network settings for Master:

Network settings for Slave:

**Step 4: Firmware upgrade** Let's upgrade each unit to the latest stable firmware version. Go to the Maintenance section and click on the "Check Latest Release" button. In case a new software version is available, click on the "Upgrade Firmware" to initiate the firmware upgrade process. Before, make sure the laptop which is connected to the unit has an Internet connection, too. Otherwise, the manual firmware upgrade process should be performed from .

**Step 5: Radio parameters configuration** Let's configure the minimum needed radio parameters to establish the link. At the unit named Master at step #3 above, go to the "Basic Settings" section, then to "Link Settings" and set this unit with: * Type: Master. * Tx Power: e.g., -5 dBm (set the minimum value in the range, as currently, we are in the lab, and we don't need high output power anymore). * Node Name: e.g., Master (it is the same as the value set at Device Name if this was saved before). * Channel Width: e.g., 80 MHz. * Frequency: e.g., 6020 MHz. * Frame size: e.g., 5 ms. The rest of parameters remain with the default values.

At the unit named Slave at step #3 above, go to the Basic Settings section, then to Link Settings and set this unit with: * Type: Slave. * Tx Power: e.g., 0 dBm (set the minimum value in the range, as currently, we are in the lab, and we don't need high output power anymore). * Node Name: e.g., Slave (it is the same as the value set at Device Name if this was saved before). * Channel Width: e.g., 80 MHz. * Frequency: e.g., 6020 MHz. The rest of parameters remain with the default values.

**Step 6: Check the wireless link status** Let's apply all settings described above for each unit and after login let's go to the Device Status section, and check the link establishment at Link Statistics. Link Statistics:

**Step 7 (optional): Wi-Fi access point configuration** Configure the Wi-Fi access point. To do this, go to the "Link Settings" - "rf8.0" section and configure the following settings: In the "Access Point Settings" tab: * Enable the access point by checking the "Enable AP" box; * Set a unique SSID; * Select the desired encryption level; * Set the network access key; In the "Main Settings" tab: * Set the channel width: 20 or 40 MHz; * Select the frequency channel you plan to use or "Auto" to select the best channel; * Leave the maximum output power at its default value.

Allow device management via a Wi-Fi access point. To do this, go to the "MAC Switch" section and include the "wlan0" interface in the switching group intended for management.

On a Wi-Fi-enabled mobile device, find the network with the SSID set in the previous step. For this network, assign a static IP address from the same network as the Astrawireless device's "svi" interface. Set the router address and other settings as shown in the image below.

Check access to the device via Wi-Fi network. In the mobile device's web browser, enter the IP address of the Astrawireless device's "svi" interface. # Installation⁣⁣⁣⁣⁣ ## Mounting kit⁣⁣⁣⁣⁣s ### MONT-KIT-85 Mounting kit⁣⁣⁣⁣⁣⁣ MONT-KIT-85 | MONT-KIT-85S is supplied with all models by default except E5-ST18 and E6-ST18. It allows to make reliable and easy installation of the unit with two-axis adjustment. Assemble the Mounting kit according to the scheme below. The nut must be tightened until the spring washer clicks, without over-tightening.

Mounting is carried out on a pole with a diameter 30-85 mm. There are also possible options for mounting on a wall or pole with a diameter more than 85 mm.

{% hint style="warning" %} NOTE Clamps and other optional fasteners are not included in the Mounting kit MONT-KIT-85. {% endhint %} ### MONT-KIT-85QR Mounting kit⁣⁣⁣⁣⁣⁣ For devices with removable parabolic antenna could be used side mountin kit MONT-KIT-85QR. It is specially designed for reliable and easy installation of the parabolic antennas and their two-axis adjustment. ### MONT-KIT-85P Mounting kit⁣⁣⁣⁣⁣⁣ High precision mounting kit MONT-KIT-85P allows to make reliable and easy installation and enables extremely accurate adjustment on azimuth and elevation for optimal wireless link performance. Compatible for Astra Quanta and Astra Evolution, families units. Especially suitable for installing high-gain antenna models that have a narrow beam.

Mounting is carried out on a pole with a diameter 30 ... 85 mm. There are also possible options for mounting on a wall or pole with a diameter more than 85 mm.

{% hint style="warning" %} NOTE Clamps and other optional fasteners are not included in the mounting kit MONT-KIT-85P. {% endhint %} ### Mounting kit for E5-ST18/E6-ST18⁣⁣⁣ E5-ST18 and E6-ST18 models installation is performed using bracer and threaded rod M6x90 that is supplied by default. Install the device according to the scheme below. The nut must be tightened until the spring washer clicks, without over-tightening. Mounting is carried out on a pole with a diameter 30-85 mm.

### Mounting kit for Terminal unit Terminal units installation is performed using basement, bracer and threaded rod M6x90 that is supplied by default. Install the device according to the scheme below. The nut must be tightened until the spring washer clicks, without over-tightening. Mounting is carried out on a pole with a diameter 30-85 mm.

## Cable Gland Assembly⁣⁣⁣⁣⁣⁣⁣ ### Cable Gland Assembly for RJ-45 connector Required components are listed below. 1. Unshielded RJ-45 connector. 2. Shielded RJ-45 connector. 3. FTP Cat5e cable. 4. Cable gland: * Cable gland nut. * Split sealing grommet (with inner diameter 7 mm). * Cable gland threaded coupling. 5. Crimping tool for RJ-45 connector. {% hint style="warning" %} NOTE The outside diameter value of the FTP Cat5e cable should not exceed 7 mm. Cable gland can be assembled on pre-crimped cable. {% endhint %} #### Assemble procedure In order to ensure that the device case remains sealed under any environmental conditions follow the assemble procedure: * **Step 1**: Crimp the standard RJ-45 connector onto the cable using crimping tool. Pin-out scheme: T568B wiring standard. {% hint style="danger" %} CAUTION Make sure that the RJ-45 connector is well-crimped. A loose connector can damage the device. Please note that such damage is not covered by the warranty. Do not use the shielded RJ-45 connector on this end of the cable as it should be attached on the power supply unit end. {% endhint %} * **Step 2**: Assemble cable gland nut, the split sealing grommet and the cable gland threaded coupling onto the pre-terminated cable as shown on the figure below. * **Step 3**: Insert the split sealing grommet into the cable gland threaded coupling. * **Step 4**: Insert the RJ-45 connector into the device socket until you hear a click. * **Step 5**: Screw the cable gland threaded coupling into the port and tighten it. Do not apply excessive force. * **Step 6**: Tighten the cable gland nut (4). Do not apply excessive force. ### Cable Gland Assembly for Optical Cable Required components are listed below. 1. Optical cable. 2. Optical connector. 3. SFP module. 4. Cable gland: * Cable gland nut. * Split sealing grommet (with inner diameter 3.2 mm). * Cable gland threaded coupling. #### Assemble procedure * **Step 1**: Put the cable gland nut, the split sealing grommet and cable gland threaded coupling onto the optical cable as shown on the figure below. * **Step 2**: Insert the split sealing grommet into the cable gland threaded coupling. * **Step 3**: Set the SFP module into the socket until you hear a click. * **Step 4**: Insert the optical connector into the SFP module. * **Step 5**: Screw the cable gland threaded coupling into the port and tighten it. * **Step 6**: Tighten the cable gland nut. Do not apply excessive force. {% hint style="warning" %} NOTE In order to disassemble SFP, please disconnect the optical cable, pull the clip of the SFP module and withdraw the SFP module from the slot. SFP module is not included into the packing list. Is possible to use an SFP (Small Form-factor Pluggable) transceiver of any manufacturer that meets the MSA (MultiSource Agreement) standard. {% endhint %} ## Mounting⁣⁣⁣⁣⁣⁣⁣⁣ ### Pre-installation **Reqiered tools** * Screwdriwer set. * Pliers / pipe wrench. * Wrench set. **Additional equipment** * GPS receiver. * High magnification binoculars. {% hint style="danger" %} CAUTION Before mounting the equipment in an outdoor environment, please make sure that: * You acknowledge the regulations imposed by the Regulatory Authority for Communications in your country for the radio spectrum to be used. * You chose known locations for the installation of the links; although Astra Wireless devices can also operate in Near-LoS or Non-LoS conditions, to achieve the best performance, it's highly recommended to install the link in locations where Clear-Line-of-Site and clear channels are available. * You performed link planning using the planning tool to determine the link path profiles, radio equipment placement requirements, etc. * You met requirements described in the section "Planning considerations" - > "Wireless device placement". {% endhint %} ### Installation Procedure * In case of device with removable parabolic antenna, to mount the reflector to Evolution, proceed as follows: * Match the antenna reflector with the cover of the outdor unit to coincide the cut parts of the antenna and the slots of the enclosure to prevent rotation of the antenna during operation. * Install the sealing metal ring of the feeder on top of the antenna reflector, screw the feeder into the hole to press the reflector to the device enclosure. * Tighten the feeder with a 45 mm wrench with a force of 700-800 Nm. * In case of device with external antenna, to mount and connect an external antenna to Evolution, proceed as follows: * Mount the antenna(s) according to manufacturer’s instructions; * Connect the ODU V and H N-type interfaces to the antenna(s) with RF coaxial cables and with appropriate connectors. Use cables not longer than 3 m (9.8ft). Tighten the N-type connectors to a torque setting of 1.7 Nm (1.3 lb ft); * Form drip loops near the cable ends at the ODU’s side so that water doesn’t creep towards the ODU connectors; * Weatherproof the N-type connectors (when antenna alignment is complete) using PVC tape and self-amalgamating rubber tape; * Weatherproof the antenna connectors in the same way (unless the antenna manufacturer specifies a different method); * Fix the antenna cables to the supporting structure using site approved methods. Ensure that no undue strain is placed on the ODU or antenna connectors. Ensure that the cables do not flap in the wind, as flapping cables are prone to damage and induce unwanted vibrations in the supporting structure. {% hint style="danger" %} CAUTION In order to prevent device damage make sure that antenna is connected to both N-type connectors with serviceable RF cables before switching on. {% endhint %} 1. Install ODU connector facing down using the mounting kit. Do not tighten the fasteners to the end until the alignment is completed. 2. Connect the Cat5e FTP cable with the cable gland to ODU. 3. Perform ODU grounding. 4. Lay the Cat5e FTP cable from ODU to the power supply. 5. Connect the Cat5e FTP cable with a shielded connector covered by a cap to the "OUT" port of the power supply, having previously touched the power supply connector case with FTP cable connector case. 6. Perform the power supply grounding. 7. Connect the laptop using Cat5e FTP cable to the power supply "IN" port. 8. Connect the power cord to the power supply and then to the power circuit. {% hint style="danger" %} CAUTION The power supply must not operate near a direct heat source, near water or in an environment with high humidity. The cables must be connected in such a way to prevent water flow to the power supply connectors. Use mains supply cords that adhere to safety regulations of the country where the equipment is getting deployed. {% endhint %} Make sure a small loop (at least 10 cable diameters) is provided before the Cat5e FTP cable enter into the building.

{% hint style="danger" %} CAUTION Please note that the pressure equalization system in Astra Wireless devices is performed via gas exchange through a cable gland and Ethernet cable jacket with a dry room where the power supply is installed. In order to avoid ODU failure due to moisture entering the device, for example, during the pressure drop during the rain, the cable gland assembly requirements should be met and there are should be no cracks in the Ethernet cable jacket. In addition, you should avoid the Ethernet cable bending near the ODU and pinching with clamps, that can bring to the pressure equalization system fault between the internal volume of the sealed ODU and the external environment during a sudden air temperature change. This may lead to the leakage and device failures. {% endhint %} #### External antenna information Any external antenna of the same type and with a maximum gain not greater than those listed below can be used with the Evolution E5-BSE in the countries abiding by the FCC rules.


Directivity	Type	Manufacturer	Reference	Stated Gain
Sectorized	Flat-panel, dual orthogonal polarization array	MTI Wireless Edge Ltd.	MT-464047/SVH	16 dBi

If other antenna types than above with Gain +16 dBi or LESS are used with this device these antenna types must be approved by FCC with C2PC application by device manufacturer. External antenna must be professionally installed pursuant to the section 15.203 of the FCC Rules. Any external antenna of the same type and with a maximum gain not greater than those listed below can be used with the Evolution E5-STE, E6-STE in the countries abiding by the FCC rules.


Directivity	Type	Manufacturer	Reference	Stated Gain
Sectorized	Flat-panel, dual orthogonal polarization array	MARS Antennas &RF Systems Ltd.	MA-WC56-DP17	18 dBi

If other antenna types than above with Gain +18 dBi or LESS are used with this device these antenna types must be approved by FCC with C2PC application by device manufacturer. External antenna must be professionally installed pursuant to the section 15.203 of the FCC Rules. ## Grounding and lightning protection⁣⁣⁣⁣⁣⁣⁣⁣ This section describes factors to be considered when planning the proposed link end sites, including grounding, lightning protection and equipment location for the wireless device, power supply, AUX-ODU-LPU-L and AUX-ODU-LPU-G unit (if installed). {% hint style="danger" %} CAUTION Electro-magnetic discharge (lightning) damage is not covered under warranty. The recommendations in this document, when followed correctly, give the user the best protection from the harmful effects of EMD. However 100% protection is neither implied nor possible. {% endhint %} ### Grounding and lightning protection recommendations * The wireless device should be placed on the pole at a height that is at least 1 meter below the top of the pole. In this case, there is a significant probability that the lightning strikes the pole and not the wireless device. The pole should be properly grounded: connected to the building lightning protection circuit according to your local regulations. * All equipment must be connected at stabilized and surge protected power sources which must be properly grounded. * The end of the FTP service cable that is connected to the power supply should be assembled with a shielded RJ-45 connector. The other end of the FTP service cable (connected to the wireless device) should be assembled with unshielded (standard) RJ-45 connector. * The power supply is grounded via a three-conductor power cord and a grounded socket. * AUX-ODU-LPU-L, AUX-ODU-LPU-G and wireless device grounding is performed using grounding bolt. * Antenna pole and wireless device should be connected to the common ground ring. Grounding cables should be no less than 10AWG thick and must use corrosion-resistant connectors. Grounding bolt is included in the supply list, M6x10 for BS devices, M5x10 for ST devices. ### Requirements to the lightning protection unit AUX-ODU-LPU-L location AUX-ODU-LPU-L is an optional accessory which may be used to serve as a line protection unit for the ODU and for the indoor network equipment connected to the Ethernet port of the IDU. AUX-ODU-LPU-L should be properly assembled, mounted and grounded. General recommendations for installations of lightning protection units: * Install the lightning protection unit on both ends of the cable to protect both the outdoor and the indoor unit. The purpose of the LPU at the top is to protect the ODU from a surge of lightning strike which can hit the long FTP cable run along the height of the pole or on the roof of the building. The purpose of the LPU at the bottom is to protect the IDU and customer equipment. * Use the lightning protection unit to protect all circuits for signal transmission and power supply (video, audio, management signals, Ethernet, etc.) * Regularly (especially before the periods with high thunderstorm activity) check the integrity of lightning protection units, grounding elements and bonding conductors. * The ports of the AUX-ODU-LPU-L device are symmetrical, i.e. the correspondence of ports position to the external unit and the power supply does not matter. Make sure to install the two LPU devices as shown in the scheme below.

## Antenna Alignment⁣⁣⁣⁣⁣⁣⁣ ### Rough alignment Using the azimuth and elevation values computed by the link planning tool roughly position the antenna (in each location) to detect the opposite system signal. Directly before installing the devices we recommend to set up the maximum output power value. If the link cannot be established, try to switch the bitrate to the minimum value and narrowing the channel width. Assess the link establishment and its quality using the LED indicator on the device case. LED indication are detaily described in the [Hardware Platform](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/introduction/hardware-platform)⁣⁣⁣⁣⁣⁣⁣⁣ section. For more accurate alignment, use the alignment tool built into the device web interface. ### Precise alignment It is recommended to have two teams prepared for alignment procedure, each team with at least two installers: one should notisy the signal values and communicate with the remote side, the other should make the adjustments with the device. After the initial approximate alignment (link up), the antenna with the lowest gain should be locked into position. Both teams should use the Antenna Alignment Tool in the Device Status section of the web GUI.

The team at the antenna which has the highest gain will click on the "Start Test" button and start to change the azimuth slowly while watching the signal indicators * As soon as the best signal has been found (Input Signal stripes must be located in the black area, closer to its center), the antenna must be locked into that position * The same action will be performed for the elevation, and the antenna must be locked into the final position where both elevation and azimuth provide the best signal, according to the indicators provided by the antenna alignment tool: * EVM: higher than 21 in absolute value. * Signal level to interference and noise: higher than 28 dB. * Retries: lower than 5 %. {% hint style="danger" %} CAUTION No contact should be made with the antennas during signal reading because the human body can affect the radiation pattern of the antenna and signal readings. {% endhint %} **The main parameters displayed in the alignment tool:** * RSSI - indicates the power level of the received radio signal, optimal parameter value -60 ... -40 dBm. * CINR - input signal level to noise + interference indicator, >=28 dB. * Crosstalk - indicates how much vertically and horizontally polarized signals influence each other, >20 dB in absolute value. * Error Vector Magnitude (EVM) - indicator of the measured input signal quality (it should be as high as possible in absolute value, the recommended level is not less than 21 dB in absolute value. Some old firmware had EVM value positive, but most the firmware has negative value, so for the troubleshooting, evaluate the absolute EVM value). * Tx bitrate - displays the current bitrate for the remote and local units (measured in Kbps).

As soon as the antennas have been precisely alignment, set the "auto" option for Tx power and bitrate at both units and select values in accordance with the EIRP limitations. Depending on the values for SNR, RSSI, retries and current bitrate, change the following parameters: * Decrease/increase the Tx power level (keeping the auto option checked) to have the SNR at around 25 dB and the RSSI at around -55 dBm. * Decrease the bandwidth to lower the noise and to increase the SNR to above 20 dB.

**Wireless link statistics** * Let's check the link parameters. Go to the Device Status section and in the Link Statistics, check the following parameters: * Retries Rx/Tx: maximum 5 %. * EVM Rx/Tx: not less than 21 dB in absolute value. * SNR Rx/Tx: not less than 27 dB.

If these conditions are met and the maximum bitrate is reached, the wireless connection quality is good. Otherwise, use the diagnostic tools described in the Device Status article. # Operation & Administration⁣⁣⁣⁣⁣⁣⁣ # Web GUI access⁣⁣⁣⁣⁣⁣ {% hint style="warning" %} NOTE Сonnecting third-party equipment via Ethernet (switches, PCs), make sure the PoE, Energy Efficient Ethernet and Green Ethernet functions are disabled on the network interfaces connected to wireless devices. {% endhint %} When you power on the unit, operation system starts automatically and Web management is enabled by default so, in order to access the unit via Web browser (start the graphical user interface), type in the address bar the default address: 10.10.10.1/24. {% hint style="warning" %} NOTE The system allows concurrent login sessions via Web interface. {% endhint %} On the login page, you can type any username and any password and click Login:

{% hint style="warning" %} NOTE Please change the credentials you have just inserted with a permanent username and password for it after the first log in. In order to change the credentials proceed to the "Basic Settings" - "System Settings⁣" section. {% endhint %} The default language is English. After the authentication step, the language can be changed into Russian, French, Italian or Chinese. You can access the unit via HTTPS (HTTP with SSL only) using Astrawireless self-signed certificate (from the Maintenance menu⁣ of Web interface). The «HTTPS Connection» link is available in the right side of the login form:

# Device Status⁣⁣ The "Device Status" page is displayed by default after the authentication step. It displays the main parameters of the unit in real-time. You can set the "*Auto Refresh*" option to refresh the statistics automatically. Refresh frequency can be set by the "*Auto Refresh Time*" parameter. The minimal possible value is “0” seconds and it updates the information instantly. These options are available in the bottom-left side of the "Device Status" screen:

The device statistics can also be refreshed manually by clicking the «**Refresh**» button. The "Device Status" page has the following sections: * "CPU load" - displays the load percentage of the CPU * "Memory load": * Memory (the data stored in volatile memory are valid only during the current session, until the system reset) displays in real-time the total memory available and the used memory by the running processes * Flash memory (non-volatile memory) displays in real-time the total memory available and the used memory by the operation system and configuration files * "Interface Statistics" - displays the main parameters of all configured interfaces (physical and logical) * "Wireless Links Statistics" - displays the main parameters of all wireless connections between the device and the neighbor devices * "Switch Statistics" - displays counters of the frames which have been switched or dropped. ## Interface Statistics The software version is displayed in the right side of Interface Statistics section (for example: TDMAv2.1.26). In case of connection to the AUX-ODU-SYNC synchronization unit, the number of visible GPS/GLONASS satellites will be displayed as well as the current device synchronization status: * "*Sync*": the device is in sync. The value in brackets is current value of the offset (in microseconds) between the internal clock of the device and the external timing reference from GPS/GLONASS * "*Wait Sync*": the device is waiting the external timing reference from GPS/GLONASS * "*Lost Sync"*: the connecting to the AUX-ODU-SYNC was lost * "*No Sync*": the device is not in sync. The current value of offset between the internal clock and the external timing reference from GPS/GLONASS is beyond the allowed value range (±10 microseconds) Following parameters are displayed in the "Interface Statistics" section:

Parameter	Description
Interface	Displays all physical and logical set interfaces
MAC Address	Displays the MAC address of each interface
Status	Displays for each interface whether it is “up and running” or not
Mode	Displays the operation mode of each interface. Ethernet interface: 10,100 or 1000 Mbps; Half or full duplex mode - red value of this parameter informs that transmission is performed in a half-duplex mode. Radio interface: Bitrate; Operating frequency - red value of this parameter indicates an absence of data transmission due to the spectrum scanning by the DFS tool; Channel width; TX Power - red value for this parameter may indicate a problem with the transceiver's hardware.; DFS tool state. AP interface: Network name (SSID); Authorization type; The channel the Wi-Fi access point is operating on. SVI: Switch group number. PRF interface: Parent; Channel number; Frame size - red value of this parameter means impossibility to set the optimal size due to external limitation (MTU value on the switch port). Vlan interface: Parent; Vlan ID; Selected vlan interface operation standard.
Packets	Displays the number of received and transmitted packets for each interface since the unit is operational. The local system packets are counted, too (and not only the ones that are passing through the switching groups - data traffic)
Errors	Displays the number of received and transmitted error packets for each interface since the unit is operational
Load	Displays the packet flow through each interface in real-time (for the system and the data traffic)

All these counters can be reset by clicking the **«Reset All Counters»** button:

{% hint style="danger" %} CAUTION Clearing these counters by clicking the «**OK**» button in the pop-up page means losing the history data about the functionality of your unit. Avoid this operation unless you are completely sure you don’t need these data in the future. If you are not sure you want to permanently delete all statistics of the device for previous periods without the possibility to recover, click the «**Cancel**» button. {% endhint %} ## Links Statistics on rf6.0 This section displays the following information for the radio interface of the unit: * Node name and ID * Noise level * Number of established links * ATPC status (activated or deactivated) * Autobitrate status (activated or deactivated) * Operational mode of the unit (Master/Slave) * For Master - current TDMA parameters: * Time slot duration (in microseconds) * Downlink percentage of the time slot * Maximum RSSI level (in dBm) * Maximum operational distance (in kilometers) * RX/TX Capacity

Parameter	Description
Status	Gives a color indication for the wireless connection quality with the neighbor unit: Red: poor connection Yellow: good connection Green: excellent connection Link Uptime. Displays the link uptime F – relevance of remote unit firmware (optional). Idicates that the remote unit has the older firmware than the local one ? – system password of the remote unit (optional). Idicates that the remote unit has not the system password E – Ethernet port status on the remote device (optional). Indicates that the remote device Ethernet port is flapping
MAC Address	Displays the neighbor’s MAC address
Name	Displays the neighbor’s name
Node ID	Displays the sequential number of the neighboring node
Distance	Displays the calculated (theoretical) distance to the neighbor unit (in Km) Deflection angle from the main antenna direction towards the subscriber terminal, in the column "Distance" (only for sector base station with "Q" index, which have antanna with beamforming technology support).
Tx Power	Displays the power level of the Tx and Rx signals of the neighbor unit (in dBm)
RSSI	Displays the received signal level in dBm, the optimal value is in the range from -60 to -40. "*" – indicates the difference in the signals power of the vertical and horizontal polarizations
SNR	Displays the ratio of the useful signal power to the noise power for the input and output signals at the neighbor unit (in dB). For radio link stable operation, the SNR value must in the range of 12-50 dB, higher modulation are available at values of 27-50 dB
EVM	Displays the input signal quality in dB. For stable operation, its absolute value should be as high as possible - not less than 21 dB
Bitrate	Displays the set bitrate value for the Tx and Rx signals of the neighbor unit
Retries	Displays the percentage of Tx and Rx retries of the neighbor unit
Errors	Displays the percentage of Tx and Rx errors of the neighbor unit
Load	Displays the number of kbps and packets that are going inbound and outbound the radio interface of the neighbor unit (main data)

By clicking the "**Route Map**" button in the right corner under the Link Statistics table you can get the MINT topology schematic map with the visualization of the active and alternative routes to each node.

Schematic topology map allows you to visually determine the network connectivity and complexity and to track the route switching, including mobile objects. The radio interfaces of the Masters devices are marked with a rectangle, the Slaves are marked with ellipses. The device name highlighted in red indicates problems in its operation. Connections are represented by arrows pointing the prevailing direction of data transfer. Arrows have the following color differences: * Blue - wireless connection, thicker the line, the higher a load on the link. * Yellow - PRF connection. * Green - join connection between radio and prf interfaces. * Red - indicates the interruptions of the link. Dashed lines represent backup routes.

For additional information on each node, double click on it to get remote commands (rcmd).

Detailed information about options in this tool is described in the "Command Line" section. ## Links Statistics on rf8.0 This section displays the following information for the Wi-Fi interfaces of the unit: * Wireless connection uptime; * MAC address of the connected device; * Received signal strength (RSSI), dBm; * RX/TX channel capacity (bitrate); * Retry rate, %; * RX/TX channel load, in packets per second. ## Switch Statistics This section displays the number of detected MAC addresses, unicast, broadcast and flood packets switched within each Switch group and also within kernel system (internal traffic), in real-time (since the last reboot):

In addition, this section displays in real time statistics on dropped packets from the last configuration update.

Total forwarded, dropped, ignored and buffer overflow packets are displayed in real-time below the table. All these counters can be reset by clicking the «**Reset All Counters**» button. Switch Statistics parameters:

Parameter	Description
ID	The ID of a switch group or Kernel
MAC Count	The MAC addresses number involved in data transmission within this switch group
Unicast	Sending a packet to a single host (network destination) identified by a unique address
Broadcast	Sending a packet to all hosts (network destinations) simultaneously (broadcasting is done by specifying a special broadcast address on packets)
Flood	Unicast packets whose MAC address is not in the device's switching table are partially discarded in order to reduce the radio link load. A detailed description is available in the Unicast-flood detection⁣⁣⁣⁣ article.
STP	Spanning Tree Protocol - standardized as IEEE 802.1D Creates a spanning tree within a network of connected layer-2 bridges (typically Ethernet switches) and disables those links that are not part of the spanning tree, leaving a single active path between any two network nodes The value displayed in the Switch Statistics table represents the number of the packets blocked by the Spanning Tree Protocol
Unreachable	The number of packets discarded by the flood detection mechanism. A detailed description is available in the Unicast-flood detection⁣⁣⁣⁣ article.
Firewall	A software or hardware-based network security system that controls the incoming and outgoing network traffic by analyzing the data packets and determining whether they should be allowed through or not, based on applied rules set The value displayed in the Switch Statistics table represents the number of the packets dropped by the firewall system in the network
Possible loop	A switching or bridging loop occurs in a network when there is more than one Layer 2 path between two endpoints Because a physical topology that contains switching or bridging loops is needed for the redundancy reasons, the solution is to allow physical loops, but create a loop-free logical topology using the spanning tree protocol (STP) on the network switches The value displayed in the Switch Statistics table represents the number of the packets dropped because they belong to a possible loop (more than one port declares same packet source)
Discard	The value displayed in the Switch Statistics table represents the number of the packets dropped by the configuration (for example: "switch group N start [discard]")
MAC Limit	MAC address-table limit reached (switch maxsources (MAXSOURCES\|0) # default 5000) The value displayed in the Switch Statistics table represents the number of the packets dropped because the limit of MAC address-table was reached
Reverse	The value displayed in the Switch Statistics table represents the number of the packets dropped because they have the same source and destination port (the frame came to the unit through one port and according to the switching table it must leave through the same port)

By clicking the «**System Log**» button, you can view the "System Log" section:

The "System Log" section allows browsing the unit’s system log. It is possible to minimize/enlarge the system log window by clicking the buttons: ![](https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2FRs7fbcRaymLGAF14Nv2U%2Fimage.png?alt=media\&token=c5831910-c98f-429e-a7c3-ad54c60d9d97) You can delete all the information saved in the system log by clicking the «**Clear System Log**» button. You can hide the System Log section by clicking the «**Hide System Log**» button. ## Extended Interface Statistics The "Extended Interface Statistics" tools gather complete information and enhanced statistics for each interface of the unit. Each interface type has its own set of available tools applicable to it. In order to access the "Extended Interface Statistics" tools, click on the row of each interface within the "Interface Statistics" section:

### General Statistics The "General Statistics" tool displays the information about the interface such as the *interface mode, current status, Rx and Tx statistics,* etc. The actual statistics details depend on the interface type. For Ethernet interfaces information about current status, operational mode and load statistics is available.

Rx and Tx statistics parameters: **Receive statistics**

Parameter	Description
Packets	The total number of received packets
Bytes	The sum of lengths of all good Ethernet frames received
Load (kbps)	The link load, Kbit/s
Load (pps)	The link load, packets per second
Frame size (bytes)	The frame size in bytes
CRC errors	Total frames received with a CRC error
Discards	Number of dropped frames
Undersize	Number of received too short packets
Oversize	Number of received too long packets

**Transmit statistics**

Parameter	Description
Packets	The total number of transmitted packets
Bytes	The sum of lengths of all good Ethernet frames sent
Load (kbps)	The link load, Kbit/s
Load (pps)	The link load, packets per second
Frame size (bytes)	The frame size in bytes
Late collisions	The number of times a collision is detected later than 512 bits-times into the transmission of a frame
Underrun	The number of times the transmitter's packet processing rate exceeded the switch capabilities
Retransmit limit	Packets dropped due to queue overflow

For the radio interface information about current status, DFS mode and load statistics is available.

Rx and Tx statistics parameters: **Receive statistics**

Parameter	Description
Broadcast Rate	Current Bitrate for broadcast and multicast frames on the BS depends on the speed of the slowest subscriber
Bytes Received	Number of received bytes including headers
Packets Received OK	Number of correctly received packets
Multicas frames	Number of received multicast frames
Load (kbps)	The link load, Kbit/s
Load (pps)	The link load, packets per second
Frame size (bytes)	The frame size in bytes
RX Medium Load	Time spent on receivin d g frames (%)
Total Medium Busy	The total time medium was busy (both DL and UL) (%)
Frames dropped	The number of dropped frames
Duplicate Received	The number of duplicate frames received
Lost frames	The number of lost frames
RX collision	The number of frames damaged in the receiving channel
CRC Errors	Total frames received with a CRC error
Noise Floor	Input noise level. Measurement cycle –10 seconds
RX subslots/nodes	Frame subslots number allocated for received data / number of subscribers
RX time limit	Payload for incoming traffic, ms
Rx Cap (Mbps)	Throughput limit for UL (Mbps)

**Transmit statistics**

Parameter	Description
Voice Mode	Voice mode ON/OFF value. If turned ON, the mode of voice traffic prioritized processing is turned on
Bytes Transmitted	Number of transmitted bytes including headers
Packets Transmitted OK	Number of correctly transmitted packets
Multicas frames	Number of transmitted multicast frames
Load (kbps)	The link load, Kbit/s
Load (pps)	The link load, packets per second
Frame size (bytes)	The frame size in bytes
TX Medium Load	Time spent on transmitting frames (%)
Frame Time Used	Average loading of frame (%)
Frames dropped	The number of dropped frames
Too short/long frames	Number of frames dropped due to length: too short/long
Aggr Subframe Retries	Number of packet drops in an aggregate due to protocol excesses
Aggr Full Retries	Number of duplicate aggregates transmitted
Excessive Retries	Number of packets which were not transmitted with maximal number of retries
Max aggr frames	Maximal detected number of packets in an aggregate
Max aggr bytes	Maximal detected bytes in an aggregate
RX time limit	Payload for transmitted traffic, ms
Tx Cap (Mbps)	Throughput limit for DL (Mbps)

For the pseudo-radio interface information about parent interface, MTU value and load statistics is available. Rx and Tx statistics parameters: **Receive statistics** | Parameter | Description | | ------------------- | --------------------------------------------------------------------------------------- | | Packets | Number of correctly received packets | | Fragmented | Number of fragmented packets | | Fragments | Number of fragments | | Load (kbps) | The link load, Kbit/s | | Load (pps) | The link load, packets per second | | Frame size (bytes) | The frame size in bytes | | Scattered fragments | Number of frames where one or several fragments were lost, the frame cannot be restored | | Corrupted packets | Number of frames with the wrong length or structure | **Transmit statistics** | Parameter | Description | | --------------------------- | ------------------------------------------------------------------------------------------------------------ | | Packets | Number of correctly transmitted packets | | Fragmented | Number of fragmented packets | | Fragments | Number of fragments | | Load (kbps) | The link load, Kbit/s | | Load (pps) | The link load, packets per second | | Frame size (bytes) | The frame size in bytes | | Double encapsulated packets | Number of frames with double encapsulation | | Out of fragbufs | Number of errors as a result of frame assembly buffer overflow due to too many fragments (neighbors) sources | For the SVI interface information about current status, RX and TX staistics is available. By clicking the «**Close**» button, you return to the "Device Status" page. By clicking the «**Reset**» button, you clear all counters displayed in the page. The "*Auto Refresh*" option is active by default and refreshes the statistics automatically. You can disable the auto refresh. ### Modulation Statistics The "Modulation Statistics" tool displays the information about modulation types, such as receive and transmit statistics for different coding scheme. Please note that lower modulation is used for service traffic transmission, therefore, if such traffic prevails in the network, the counter growth for low modulations is normal.

By clicking the «**Close**» button, you return to the "Device Status" page. By clicking the «**Reset**» button, you clear all counters displayed in the page. The "*Auto Refresh*" option is active by default and refreshes the statistics automatically. You can disable the auto refresh. ### Errors/Drops Statistics/SNR/EVM The "Errors/Drops Statistics/SNR/EVM" window displays the number of errors, retries and droped packets during transmission for each link. This tool provides information about the SNR level for each polarization of the remote and local devices, as well as rates of lost and late delivery acknowledgments. In addition, this section displays the estimated throughput per subscriber in Mbps. The lower values show the guaranteed throughput in the worst case scenario when all subscribers are actively transmitting. The upper values display the throughput in the best scenario, when data is transmitted only by the selected subscriber.

The EVM value is measured not at the operation modulation, but at the lowest possible. In case the misoctl option is enabled and VBR is disabled on Slave, the lowest possible modulation uses a single data stream. If misoctl is turned off or VBR is turned on, both channels will be used for transmission, and the EVM parameter values will be displayed for each modulation. By clicking the «**Close**» button, you return to the "Device Status" page. By clicking the «**Reset**» button, you clear all counters displayed in the page. The "*Auto Refresh*" option is active by default and refreshes the statistics automatically. You can disable the auto refresh. ### Radio Scanner The "Radio Scanner" tool allows to estimate the efficiency of the radio links utilization, analyzing the radio-frequency environment for the current frequency, under the current channel bandwidth, without the radio link interruption and displays the following statistics: * Radio parameters of every source in the radio link * Number of sources, number of packets, including the skipped ones * Number of pulses, their average level and average number of pulses per second

Parameter	Description
Count	Number of the registered frames (packets)
MAC	Host MAC address
Type	Host type
Level	First value - signal level relative to the receiver sensitivity at a given modulation (bitrate), in dB Second value - absolute input signal level, in dBm
Bitrate	Current bitrate value
Length	Average frame length in bytes
Name	Host name
SID	Network system identifier
Freq	Current center frequency
Total sources	Number of sources
Total packets	Total number of the registered frames (packets)
Skipped packets	Number of skipped (unaccounted) packets due to queue overflow or lack of CPU resources
CRC errors	Number of errors in the checksum calculation
Pulses	Pulses noise counter: The first value is the number of electromagnetic energy peaks during the scanner operation. The Pulses counter includes frames for which the modulation and source MAC address could not be recognized. The "avg level" value shows an average noise level, the first value is a noise level relative to the receiver sensitivity at a given modulation (dB), the second is an absolute input signal level (dBm). The "avg pps" value indicates an average pulses per second number. The value over 50 pps indicates a high noise level.

The abbreviations for each node type are also displayed in the interface:

Type	Description
N	Neighbor (connected)
C	Candidate (not connected yet)
n\|u	n - known node in the MINT network u - node in the same MINT domain connected to another sector
-	Unknown source
LA	Locally defined node (not authenticated)
LD	Locally defined node (disabled)
A	Not authenticated MINT node
T	Master devices (in software version with TDMA technology support)

{% hint style="warning" %} NOTE "Frequency" and "Bandwidth" are highlighted in red when the frequency and bandwidth values are already not the same as they were when Radio Scanner was started. This may occur when several profiles at the subscriber terminal link settings are configured. While searching the base station sector the subscriber terminal loops through all available profiles with different settings, highlighting them in red. {% endhint %} By clicking the «**Close**» button, you return to the "Device Status" page. The "*Auto Refresh*" option is active by default and refreshes the statistics automatically. You can disable the auto refresh. ### QoS Statistics QoS (Quality of Service) characterizes the entire network performance which is defined by the parameters such as: throughput, latency, jitter, error rate, available bandwidth, etc. In order to provide the guaranteed Quality of Service for certain applications, users or data flows, different prioritization methods are used. The "QoS Statistics" tool displays the statistics of the MINT priority queues for the interface. Priority is one of the parameters which define in what sequence, different types of data traversing every Evolution device in MINT network are treated. Each channel may be assigned a priority (for example: P01, P02 … P16). Once assigned, a priority is automatically recognized by every node inside the MINT network. Each priority value corresponds to a device queue. Once in a queue, every packet is scheduled according to the queuing algorithm set on the device. QM manager supports **Weighted Fair Queuing** scheduling algorithms. **Weighted Fair Queuing** uses weights for every queue of an interface and allows different queues to have different service shares, depending on that weight. Every channel is also characterized by the latency parameter. This parameter determines the maximum time for the packets to stay in the channel. If a packet is waiting in a queue of the channel more than the time specified in the latency parameter, then it is discarded. Latency can be set for each channel in the "Traffic Shaping⁣" section. | Channal | Priority | | ------------------- | -------- | | BACKGROUND | 16 | | REGULAR Best Effort | 15 | | BUSINESS6 | 14 | | BUSINESS5 | 13 | | BUSINESS4 | 12 | | BUSINESS3 | 11 | | BUSINESS2 | 10 | | BUSINESS1 | 9 | | QOS4 | 8 | | QOS3 | 7 | | QOS2 | 6 | | QOS1 | 5 | | VIDEO2 | 4 | | VIDEO | 3 | | VOICE | 2 | | CONTROL | 1 | | NETCRIT | 0 | Transparent packet prioritization is an operation fystem feature which allows QM manager to transparently map 802.1p/TOS/DSCP priority to MINT priority for the ease of deployment. You have to make sure that “*Dot1p Tags*” and/or “*IP ToS*” options are enabled in the "QoS" section.

MINT Priority	Traffic Types (802.1p)	dot1p
16	Background	1
15	Best Effort	0
9	Excellent Effort	2
5	Critical Applications	3
4	Video	4
2	Voice	5
1	Internetwork Control	6
0	Network Control	7

MINT Priority	TOS	DSCP Name	DS Field Value
15	0	CS0	0
14	1	CS1, AF11-13	8, 10
13			12, 14
12	2	CS2, AF21-23	16, 18
11			20, 22
10	3	CS3, AF31-33	24, 26
9			28, 30
8	4	CS4, AF41-43	32
7			34
6			36
5			38
4	5	CS5, EF	40, 42
3			44, 46
2	6	CS6	48, 50
1			52, 54
0	7	CS7	56, 58, 60, 62

This section displays the number of inbound packets to each priority queue and the number of dropped packets. Of the 32 priority queues 17 are available for user configuration (from P00 to P16), where 0 is the highest priority. The rest are reserved for the system. Packets with 802.1p priority are distributed to queues with "cosX" values.

By clicking the «**Close**» button, you return to the "Device Status" page. The "*Auto Refresh*" option is active by default and refreshes the statistics automatically. You can disable the auto refresh. ## Extended Link Diagnostics Once a wireless connection between the unit and the remote neighbor is established, it is possible to make extended diagnostics and optimization for the wireless link. In order to access the "Extended Link Diagnostics" tools, click on the row of each wireless link within the "Links Statistics on rf6.0" section:

Five options are available: "Performance Tests", "Antenna Alignment Tool", "Statistics Graphs", "Remote Commands" and "Link Restart". ### Performance tests The "Performance tests" tool performs link throughput tests for the configured channel bandwidth and on the current frequency, without radio link interruption. The "Performance tests" tool generates traffic between the devices and displays the channel throughput for the traffic with chosen priority. For the full throughput tests of the channel, you must set the highest priority “0” for the test traffic. In this case, the transmission of any other traffic is stopped for the testing time and the traffic generated by the tool will occupy all the channel. The "Performance tests" tool displays the values of the full channel throughput which is available under the current settings, for current bitrate. {% hint style="warning" %} NOTE All results are given in kilobits per second and retries levels are shown as a red chart. {% endhint %} Performance tests contains of 8 tests performed on established bitrate, test can be performed in one direction or bidirectionally.

By clicking the «**Run Tests**»/«**Stop Tests**» buttons at the bottom of the page, you can start/stop the performance tests. By clicking the «**Exit Test**» button, you return to the "Device Status" page. Each row corresponds to a certain bitrate value and can be selected or deselected for participating in the performance test by marking/unmarking the corresponding check-box on the right side. By marking “*Select all*” check-box, all the bitrates could be selected or deselected at once. Three more parameters are available for management: * “*Test time*” parameter - allows setting the duration (in seconds) of the test for each bitrate (5s by default). * “*Bidirectional*” check-box - allows choosing between bi-directional (when checked) and unidirectional (when unchecked) performance test. * "*Priority (0-16)"* - by default, it is 16, which is lower than the data traffic that has priority 15. You can increase the test priority by setting a lower value. * "*Packet size*" - allows to set the desired packet size in bytes. * "*Load limit*" - sets a limit on the data rate at which the test runs, in Mbps. ### Antenna Alignment Tool The "Antenna Alignment Tool" allows to visualize the signal characteristics on both sides of the link in order to make the antenna alignment process more accurate and easier. The accuracy of the antenna alignment at the neighbor device is very important for the link quality.

By clicking the «**Start Test**»/«**Stop Test**» buttons at the bottom of the page, you can start/stop the alignment test. By clicking the «**Clear History**» button, you delete all data stored from the moment you clicked the «**Start Test**» button. By clicking the «**Exit Test**» button, you return to the "Device Status" page. Once the test is started, the antenna alignment can be monitored using the graphic and text indicators. The indicators for both local and remote devices are displayed together in the same page which allows viewing the alignment process for both sides of the link. Each side of the link (local and remote) has two similar test indicator sets, corresponding to each antenna polarization (one for Vertical polarization and another for Horizontal). This allows controlling the alignment process for each antenna polarization for the local and for the remote device simultaneously. Graphical indicator:

The main indicator is the Input Signal stripe. The height of the Input Signal stripe is measured in dB by the Input Signal Level scale. The higher the stripe is, the stronger the signal is. The stripe may change its position along the Cross Fading scale, showing how much influence the corresponding device antenna has (for example: how much vertically and horizontally polarized signals influence each other). Higher the value of the stripe according to the Cross Fading scale (the farther stripe is from the 0 dB value), less the influence antennas have on each other. The top of the Input Signal stripe can be located in black (Good signal) or red (Bad signal) background areas or somewhere in between them. This means the signal is good, bad or average correspondingly. When aligning the antenna, it is recommended to try achieving the stripe top to be located in the black area. At the bottom of the Input Signal stripe may appear a special red sub-stripe. This sub-stripe indicates the presence of the packet retries and the percentage of the total number of transmitted packets. During the alignment test, the Input Signal stripe may change its position along the Cross Fading scale and increase or decrease in height, indicating the changes in the received signal. When the top of the stripe changes its location, moving from one point on the background area to another, it leaves pink and blue marks behind, indicating the maximum and minimum measured levels of the signal at a particular point. Thus, it makes possible to observe the “history” of the signal changes. You can clear the marks by clicking the «**Clear History**» button at the bottom of the page. The text indicators are: * "*RSSI*" - indicates the power level of the received radio signal (measured in dBm), optimal parameter value -60 ... -40. * "*CINR*" - input signal level to noise + interference (measured in dB) indicator, >=28. * "*Crosstalk*" - indicates how much vertically and horizontally polarized signals influence each other, >20. * "*Error Vector Magnitude (EVM)*" - indicator of the measured input signal quality (it should be as high as possible in absolute value, the recommended level is not less than 21 dB. Some old firmware had EVM value positive, but most the firmware has negative value, so for the troubleshooting, evaluate the absolute EVM value), > 21 in absolute value. * "*Tx bitrate*" - displays the current bitrate for the remote and local units (measured in Kbps). Main recommendations when using the “Antenna Alignment" tool: * It is recommended to start antenna alignment with searching the maximum signal level on a minimal possible bitrate. Afterwards, automatic MINT mechanisms will set the most appropriate bitrate when “*Autobitrate*” mode is enabled. * Input signal level (CINR) should be between 12 dB and 50 dB. * If signal level is more than 50 dB, it is recommended to lower the amplifier power. * If maximal signal level is less than 12, it is recommended to lower the channel width (for example: from 20 MHz to 10 MHz). * In some cases, a signal level that is less than 12 may be enough for the radio link operation. In this case, you should be guided by parameters such as the number of retries and Error Vector Magnitude. If the number of retries is low (close to “0”) and EVM is more than 21 (Input Signal stripe is green) then the radio link is most likely, operating properly. * The top of an Input Signal stripe should be located in the black area. * The signal quality should be good: EVM value should be more than 21. * Input signals of the two antennas of the device should have similar Cross fading values (Input Signal stripes should be symmetrically to the value of 0 dB). All described recommendations are applicable to both ("Local" and "Remote") sections. ### Statistics Graphs The "Statistics Graphs" tool has been developed based on “*digraphs*”, which is a fast, flexible open source JavaScript charting library. The "Statistics Graphs" tool allows you to monitor the device parameters represented in the graphical charts. The following modes are available: real-time monitoring, daily and monthly data logs display (use the dropdown menu from the top of the page to change the mode). The system displays, by default, the daily data logs. All charts support simultaneous zoom to improve usability: the “zoom in” action in a certain region on any of the charts reflects on all other charts that are re-scaled automatically to display the data collected during the same period of time. Critical events like link outages or frequency swaps are marked by small red balloons on the bottom of each graph. The link down periods are marked with red fields. Move the mouse over each balloon for details:

Working with the charts: * Select a chart region to zoom in * Hold the «**Shift**» button and drag the graphs to the pan * Double-click on any chart to reset the zoom. The parameters that can be monitored are:

This chart displays the measured RX (green) and TX (blue) signal levels. Red regions represent link outages. The default graph uses the CINR measurement method; however, the RSSI method can be selected from the drop-down menu.

This chart displays the retry percentage (it provides a quick estimation of the link quality). Similar to the previous graph, RX retries are represented by the green lines, TX retries by the blue lines and link outages by the red lines.

The Bitrate chart displays the bitrate for each of the two units in the link. These parameters indicate the link quality, too.

The load charts display the actual link load information, either in real time or for a set period of time. The yellow lines represent the total link load, the green lines represent the RX load and the blue lines represent the TX load.

The last chart displays the current CPU load and unit temperature (only for the units equipped with temperature sensors). You can view the six graphs presented above into one or two columns per page by clicking the «**Change Layout**» button. ### Remote Commands The "Remote Commands" tool allows one MINT node to perform commands on another or all MINT nodes in the network at L2 level using **AstraFleX OS** CLI commands. Run the string you typed into the “*Command*” field by clicking the «**Execute**» button. For the full list and description of **AstraFleX OS** CLI commands, please refer to the [AstraFleX OS User Manual](/astra-wireless-documentation/technical-documentation/astraflex-technical-user-manual). You can set the key grant access to the remote node using the “*Key*” textbox and clicking the «**Execute**» button. Please note that this key must be prior set at the remote node via CLI (commands "*guestKey"*, "*fullKey"* - see details in the [AstraFlex OS User Manual](/astra-wireless-documentation/technical-documentation/astraflex-technical-user-manual)). Erase the string you typed into the “*Command*” field and all output from the display section by clicking the «**Clear**» button. Stop a command execution during the execution phase by clicking the «**Stop Execution**» button. By clicking the «**Close**» button, you return to the "Device Status" page. You can choose between plain and rich text format by marking/unmarking the corresponding checkbox. You can execute the same command from the BS to all CPEs in the network (to the nodes that are linked to the BS) by marking “*Send to all*” checkbox before clicking the «**Execute**» button. You can upload the configuration file to the remote node by clicking the «**Upload Config…**» button and you can reboot the remote node by clicking the «**Reboot Remote Unit**» button (a warning message pops up before the reboot). For the ease of usage of the "Remote Commands" tool, the corresponding buttons for the most used **AstraFleX OS** CLI commands are available in the right side of the screen:

By clicking the «**System Info**» button, you fill in the command field with "*system version*, *system uptime* and *system cpu"* commands. By clicking the «**System Config**» button, you fill in the command field with "*system uptime* and *config show"* commands. By clicking the «**System Log**» button, you fill in the command field with "*system log show"* command. By clicking the «**Routing Table**» button, you fill in the command field with "*netstat -r"* command. By clicking the «**ARP Table**» button, you fill in the command field with "*arp view"* command. By clicking the «**Switch Statistics**» button, you fill in the command field with "*switch statistics"* command. By clicking the «**Link Status**» button, you fill in the command field with "*mint map detail"* command. By clicking the «**Interface Table**» button, you fill in the command field with "*netstat-i"* command. By clicking the «**Radio Scanner**» button, you fill in the command field with "*muffer rf6.0 -t5 -p mac3"* command. All commands are executed automatically after clicking one of the buttons mentioned above. {% hint style="warning" %} NOTE All **AstraFleX OS** CLI commands can be executed from the "Remote Commands" tool. {% endhint %} ### Link Restart You can restart the wireless link (re-association, re-authentication and re-connection) by selecting the “**Link Restart**” radio button and then by clicking the «**OK**» button in the link options. A warning message pops up before the link restart. If the operation is executed, the link disappears from "Device Status" page until it is reestablished again.

## Extended Switch Statistics The "Extended Switch Statistics" tools allow gathering complete information and enhanced statistics for each group of the unit. In order to access the "Extended Switch Statistics" tools, click on the row of each switch group or kernel within the "Switch Statistics" section:

Two options are available: "Switch DB statistics" and "Switch VLAN statistics". ### Switch DB Statistics The "Switch DB Statistics" tool gathers complete information and enhanced statistics for each switch group, including kernel:

By clicking the «**Close**» button, you return to the "Device Status" page. The "*Auto Refresh*" option is disabled by default. You can enable the auto refresh in order to have the statistics automatically refreshed. ### Switch VLAN Statistics The "Switch VLAN Statistics" tool gathers complete information and enhanced statistics for each VLAN created:

By clicking the «**Close**» button you return to the "Device Status" page. The "*Auto Refresh*" option is disabled by default. You can enable the auto refresh in order to have the statistics automatically refreshed. # Basic Settings⁣⁣⁣⁣⁣ Devices can be configured via Web interface, or via Command-line interface. The parameters for the majority of the Command-line interface commands are displayed in the Web interface. Saving the configuration for these parameters in any of the two interfaces (Command-line and Web) is reflected in both interfaces. However, for some other commands, the most important parameters can be set via Web interface, but the enhanced parameters of these commands can be set via Command-line interface only. The commands that do not have the enhanced parameters displayed in Web interface are: s*ys, ifconfig, prf, qm, tun, route, mint, switch, svi, lag, sntp, dhcpc* (please consult the information about the [Extra commands](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/basic-settings/extra-commands)⁣ section within the current chapter, below). The settings of these enhanced parameters will be lost after saving the configuration via Web interface. The warning message below is displayed in the "Basic Settings" page from the Web interface if the configuration has been previously created via CLI, in order to avoid losing data for those only few commands that don’t reflect their parameters in the Web interface:

{% hint style="warning" %} NOTE This message is not displayed in the default configuration, but only after the first configuration via CLI. {% endhint %} After performing the needed configuration in the "Basic Settings" menu, you must save all the new parameters by clicking the «**Apply**» button. If you are not sure about the effect of the new configuration performed, you can apply the new configuration temporarily by clicking the «**Test**» button. The previous configuration is automatically restored after a grace period of 180 seconds (3 minutes). You have the options to extend the grace period, or immediately accept/reject the changes.

By clicking the «**Preview Configuration**» button, you can view the configuration results in CLI-style format. The «Show changes» button displays all changes added to the configuration in CLI-style format.

After clicking the «**Apply**» button for saving the new configuration, the system will redirect you to the login page. After a 5 seconds timer you can log in back to the unit and check the new configuration. # System Settings⁣⁣⁣⁣⁣⁣ In this section, you can view and edit the basic system settings that are already created.

Parameter	Description
Device Name	Set the device name. This parameter is displayed in the web-page header.
User Name	Displays the username (Login) used to access the unit management interfaces. Allows to change the current username.
Password and Confirm Password	To change the password set in the previous configuration after unmarking the option “keep current system password" in the corresponding checkbox Return to the default settings for "Password" and "User Name" (any values with non-zero length) by unmarking the checkbox “Keep current system password” and leaving the corresponding fields empty and save the configuration at the bottom of the page.
WEB Interface language	Change the default system language (English) into Russian, French, Italian or Chinese language.
HTTPS only	Make all HTTP connections to the unit be performed via HTTPS (HTTP with SSL only) by marking the option “HTTPS only” in the corresponding checkbox. By default, this option is disabled.
Enable Telnet	Enable/disable remote device control by the command line using Telnet protocol.
Enable SSH	Enable/disable remote device control by the command line using SSH protocol. SSH (Secure Shell) protocol provides secure remote control to network devices. Its functionality is similar to the Telnet protocol, but, unlike Telnet, SSH encodes all protocol messages, including transmitted passwords. By default, only access via Telnet is enabled.
Start SNTP	Start SNTP service by marking the option “Start SNTP” in the corresponding checkbox. By default, this option is disabled. SNTP is necessary for correct time display, for example, in system logs.
Use GNSS time	Enable/disable GNSS time. Disabled by default.
SNTP IP Address	Set the IP address of a valid SNTP server. The unit must have an active connection with the SNTP server in order to receive time services.
Time Zone	Set the time zone in POSIX format. For example: GMT+4.
Latitude	Set the latitude of the geographical place where the unit is installed. GPS latitude format is [N/S]YY.YYYYYY. Use the Google Map feature to automatically fill in this field (follow the indications below).
Longitude	Set the longitude of the geographical place where the unit is installed. GPS longitude format is [E/W]XX.XXXXXX. Use the Google Map feature to automatically fill in this field (follow the indications below).
Enable GNSS Receiver	Enable/disable GNSS receiver. Disabled by default.
Access White List	List of IP addresses for restricting access to the device via telnet, ssh, http/https, snmp protocols (ports 22, 23, 80, 162, 443). If there is at least one address in the list, attempts to establish a connection to the device from addresses (networks) not listed in this list will be rejected.

Click the «**Open Map**» button to open the Google map:

Type the location name in the "Address bar", click the «**Find**» button to search for it and then move to the exact location where the unit is installed. Double click in that position on the map and the Google pointer (see picture above) will be placed there. After clicking the «**OK**» button, “*Latitude*” and “*Longitude*” fields are automatically filled in with the GPS coordinates. # Network Settings⁣⁣⁣⁣⁣⁣⁣ In the "Network Settings" section, there are displayed all physical and logical network interfaces that are already configured. The physical interfaces (eth0, rf6.0 and ap0) are set by default and they cannot be removed. For these two interfaces, you are allowed to change the parameters only. {% hint style="warning" %} NOTE Before making the configurations in the "Network Settings" section, please read the information presented in the "[MAC Switch](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/basic-settings/mac-switch)⁣" section. {% endhint %}

For the following layer 2 and 3 logical interfaces, you are allowed to add (by clicking the corresponding buttons and specifying the interface number), remove and change the parameters of the interface: * "**PRF**" - Pseudo Radio Interface can be attached to the Ethernet interface in order to allow it to work as a radio interface using the MINT protocol, so that the node can find its neighbors and establish the links with them through this interface. The interface encapsulates MINT-frames into the Ethernet-frames and allows connecting the units of the MINT network using wired interfaces. Also, this interface can be joined with other interfaces; * "**VLAN**" can be assigned to a physical interface or to a virtual interface sviX. It is used for the creation of the logical network topology regardless of the physical topology of this network. VLAN allows creating groups of interfaces which have a common set of requirements. It contributes to reducing the multicast traffic in the network, as every VLAN is a separate multicast domain. VLAN usage increases the network security and manageability; * "***LAG***" can be assign to two physical interfaces in order to use them as one logical interface for total throughput increasing and system reliability improving. The total throughput of the logical channel represents the sum of the capabilities of associated physical interfaces. In case of failure of any physical channel included in the logical channel, the system will continue to operate, using the rest operable physical channels. Interface allows creating high speed links (between the unit and the network switch, for example) by means of aggregation of the two available Ethernet-interfaces of the unit; * "**SVI**", Switch Virtual Interface is an L3 interface that can be assigned to a switching group for getting access to the unit management via this switching group. This interface becomes part of this switching group and can participate in the exchange of information with other group members so that any packets received by the group (according to its rules), or addressed to the sviX directly, or copies of multicast/broadcast packets, will be received by the unit through the "*sviX"*. This interface allows getting the remote access to the unit management. It is also used for the Management VLAN configuration; * "**Tunnel**" is implemented like a PtP link between two routers that encapsulates the flow into the IP packets and send it to the end point of the link using the existing transport environment. It allows to unite two remote networks (which are not directly connected) in an integrated logical structure (VPNs) which use its own network address allocation and account policies, independent from the ones supplied by the service providers for each of the separate network segments; * "**TAP**" interface simulates a link layer (L2) device and operates with Ethernet frames. TAP interface is used for creating a network bridge.

Interface	Description
ethX	Configure the IP address(es) and the mask of the interface. The IP address(es) of the "ethX" interface is accessible via Ethernet LAN segment only (it won't be accessible via the "rfX" interface from other neighbor unit). The IP address(es) of the "ethX" interface is used in the routing process. Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. DHCP option is disabled by default. Set the interface description (up to 72 characters). Set the interface mode (for example: 1000Base-TX-fullduplex): The default value is “Auto” (recommended) Optical SFP modules may not work properly in auto-negotiation mode with some devices. In case of troubles with data transmission via the SFP port, it is recommended to set a fixed speed and duplex mode (for example, 1000BaseTX-fullduplex-manual). Make sure the same duplex mode is set on both devices.
rfX	Configure the IP address(es) and the mask of the interface. Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. DHCP option is disabled by default. Set the interface description (up to 72 characters).
wlanX	Configure the IP address(es) and the mask of the interface. Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. DHCP option is disabled by default. Set the interface description (up to 72 characters).
sviX	SVI interface is a logical L3 interface of the switch (solely used for the management of the unit). Configure the IP address(es) and the mask of the interface (as the management IP address(es) of the unit). Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically (as the management IP address(es) of the unit). DHCP option is disabled by default. Set the interface description (up to 72 characters). Remove the interface. Set the Switch group number which this interface is assigned to (bind the SVI interface to a switch group).
prfX	PRF interface makes the Ethernet interface that it is assigned to, to appear as a regular RF interface in terms of the MINT network . Configure the IP address(es) and the mask of the interface. Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. Set the interface description (up to 72 characters). Remove the interface. Set the parent interface to be transmitted the encapsulated packets (assign the PRF interface to the physical Ethernet interface). Set the channel number (from 0 to 3) on which the frames are sent and received by the parent interface. Both PRF interfaces (of the two units in the link) must have the same channel assigned in order to establish the wireless link.
vlanX	Configure the IP address(es) and the mask of the interface in case you use this interface for the management of the unit, only (not recommended way). Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. Set the interface description (up to 72 characters). Remove the interface. Set the parent interface to be transmitted the encapsulated packets. Configure the VLAN tag (or VLAN ID) for the current interface (from 1 to 4094). In the drop-down window, you can select the vlan interface operation mode: 802.1q - vlan tag operations are performed according to this standard; 802.1ad - double tagging "QinQ"; 802.1ah - backbone bridge using mac-in-mac technology described by the IEEE 802.1ah-2008 standard.
lagX	Link aggregation interface is a logical interface used to combine multiple physical channels into one logical channel in order to increase link capacity and redundancy (for the units with two physical Ethernet ports). Configure the IP address(es) and the mask of the interface. Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. Set the interface description (up to 72 characters). Remove the interface. Set the parent interface to be aggregated the encapsulated packets. Enable/disable Fast Mode.
tunX	Configure the IP address(es) and the mask of the interface. Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. Set the interface description (up to 72 characters). Remove the interface. Set the tunneling mode: IPIP or GRE.
tapX	Configure the IP address(es) and the mask of the interface. Enable/disable the interface. Enable/disable DHCP - obtain an IP address automatically. Set the interface description (up to 72 characters). Remove the interface.

In the "Network Settings" section, "Routing Parameters" zone, you can configure the static routes:

* In the “*Network*” field, you can configure the destination network IP-address * In the “*Gateway*” field, you can configure the IP-address of the router through which the network address is reachable. As all wireless MINT interfaces are in one virtual Ethernet segment, they can be enumerated by assigning IP addresses from one IP subnet (manually or automatically, via DHCP). Thus, getting to one node (via telnet, for example), you can access all the other nodes. The access from the “outside” network can be established by configuring the necessary routing, so that the “inner” MINT network can be accessible from the administrator’s computer through the Ethernet port of the MINT node which is connected to the “outside” network. From the “inner” MINT network, the route to the administrator’s computer should go through the radio-interface to the border router. # Link Settings⁣⁣⁣⁣⁣⁣ 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 – the node frequently moves under conditions of rapidly changing radio parameters, such as complex topography or high speed. Data exchange occurs during movement. MINT connection costs will be recalculated up to 5 times per second, depending on radio parameters. The bitrate will be recalculated every 200 ms.
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	Activate the failover function on this interface. For more information about this function proceed to the article "Link aggregation, balancing and redundancy". 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):

{% hint style="warning" %} 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. {% endhint %} #### 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.

## "rf8.0" subsection Used to configure Wi-Fi access point settings.

### Protocol Settings Allows to select the wireless access protocol, which will be used for this radio interface. For use in access point mode with third-party devices, the Wi-Fi protocol is used. ### Main Settings This section configures the parameters of the radio interface, on the basis of which several access points (wlanX interfaces) can be created.

Parameter

Description

Channel Width

Set the bandwidth of the radio interface in MHz.

Operating Channel

Determines the center operating frequency; channels 1-13 are available in accordance with the 802.11n standard for 2.4 GHz. Note that adjacent channels overlap, the degree of overlap depending on the selected channel width.

Max Tx Power

Set the output power of the radio interface.

Acts as a top limit for ATPC mechanism.

Available values in range 0...25 dBm.

### Access Point Configuration This section configures the parameters of the wlanX interfaces.

Parameter	Description
Enable AP	Enable/disable wireless connection for this interface (disabled by default).
SSID	Access point name, available values: 0-32 characters.
Encryption	Encryption type. Available values: WPA, WPA2, and open access point.
Access key	Network access key. Available in psk and psk2 modes. Available values: 8-63 characters.

## "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:

# Static Links⁣⁣⁣⁣⁣ In the "Static Links" section it is possible to set restrictions on the connections at the radio and pseudo-radio interfaces of the configured node. When the interface is set to static authorization mode (see [Link Settings](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/basic-settings/link-settings)), connections will be established only with the nodes specified in this section, despite the wireless connection parameters and access key match. The parameters are: * "*MAC"* - MAC address of the neighbor unit * "*Key"* - link security key (up to 64 characters long, without spaces). Another two options are available: * Disable the link by marking the option “*Disabled*" in the corresponding checkbox. This setting works also in public authorization mode (see [Link Settings](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/basic-settings/link-settings)). * Add a link description in the “*Note*" field

By clicking the «**Add**» button, you create a new fixed link to the unit. By clicking the «**Remove**» button, you can delete an already created fixed link. # MAC Switch⁣ ⁣ ## Switch configuration The Switch configuration is based on a set of rules for the switching groups: * An unique numeric identifier (1-4999) for each group * Two or more local network interfaces (*ethX, rfX, tunX, etc*) and a set of rules (filters) which allow placing different types of traffic into different switching groups * Each node can have several switching groups. The same interfaces or group of interfaces can be used in several groups simultaneously * Switching groups are activated on different nodes of the MINT network. The nodes that have the same switching group identifier in their configurations represent a "switching zone" * "Switching zone" exists only within the MINT network segment. ## Switching groups The MINT network can be viewed as one virtual distributed layer-3 switch, where border nodes act as external ports of the virtual switch. The virtual switch task is to transport frames from one external port to another. It is important to understand that switching groups should be created only on the nodes where frames enter from or leave to the "outside" network ("outside" relative to MINT). On the repeater nodes (in mesh topology) there is no need to create switching groups.

In order to put an incoming frame into one of the switching groups, a set of flexible rules is used, which allow sorting frames according to various criteria, like: * VLAN tag * Protocol type * Addresses (MAC/IP) * Ports * Any PCAP expressions. ## Trunk groups Trunk group is a switching group in the "*Trunk"* mode. Input flow from wired segment for trunk group is divided into separate sub-groups (switching groups within trunk group) depending on VLAN-tag of the packet. The group number of the switching group within trunk group will be equal to the VLAN-number of packets which are switched to it. The trunk groups are used for the ease of configuration, when VLAN flows are transmitted to several subscribers. If you enable the trunk group at the BS side to transmit several VLAN-flows to several directions, then at the CPE side, you should use the "*In-Trunk"* option to specify the group number of the trunk group that includes the required switching group.

Trunk groups may also be used to solve the task of connecting several VLAN segments. Special rules on interfaces allow flexible manipulations with VLAN ID tags: deleting, assigning and re-assigning. ## Management connection to the unit For the management purposes, you can create a dedicated Switch Group for all units in the MINT network, attached to the Switch Virtual Interface (SVI). Assign the IP addresses directly on the SVI interface for native management. All packets sent via SVI interface will be distributed only within the assigned switch group. The universal way to configure Management VLAN via dedicated switch group is presented in the figure below (for more information see section "Remote management of Evolution units"). You have to assign the Management IP addresses to "*sviM"* interface which is the management interface of Group M and includes "*vlanX"* (with parent interface "*eth0"*) and "*rf6.0"* interface:

### Switch Group rules Once assigned to one of the switching groups, a frame will never leave it until it reaches one of the external ports. Switching group rules are applied only when the frame enters to MINT network through one of its external ports. When leaving the network, no rules are required as the frame already belongs to one of the switching groups and it is automatically forwarded to an external port(s) that belongs to the corresponding switching group. {% hint style="warning" %} NOTE Frames originated by MINT network nodes (for example: containing RIP/OSPF, ping packets, etc) do not belong to any of the switching groups. Therefore, they cannot leave MINT network via switching through any of the external ports. {% endhint %} Rules are used for the following purposes: * Selecting an appropriate switching group when a packet is received through "*ethX"* interface. The packet is switched by the group the rules of which it fully satisfies. {% hint style="danger" %} CAUTION A packet that cannot be associated with any switching group will not switched by the device. If there is no group with appropriate rules for the packet, it is discarded. {% endhint %} * When the packet is assigned to a switching group, the group decides whether the packet to be sent through one of the interfaces, or to discard it. The packet will only be sent if it satisfies the rules of this interface. The rules consist of a "rules list" and a decision (deny/permit). While parsing the list, the switch checks whether a packet matches the rule. If it matches the rule, the decision set for this rule is applied to the packet. Otherwise, the list of rules is viewed further. Rules are taken one at a time. If a packet does not match to any rule, the default decision for this group or interface is taken. The expression selects which packets will fit into the group. Only the packets for which the expression is “true” will be matched to the group. The expression consists of one or more primitives. Primitives usually consist of an id (name or number) preceded by one or more qualifiers. **Examples packet filter rules:** Single IP subnet: ``` // net 192.168.1.0/24 ``` Several IP subnets: ``` // net 192.168.1.0/24 or net 192.168.100.0/24 ``` Several IP subnets with exceptions: ``` // net 192.168.1.0/16 and not net (192.168.100.0/24 or 192.168.200.0/24) ``` Several IP subnets inside VLAN: ``` // vlan 50 and (net 192.168.1.0/24 or net 192.168.100.0/24) ``` PPPoE traffic: ``` // pppoed or pppoes ``` which is synonym to: ``` // ether proto 0x8863 or ether proto 0x8864 ``` Disable IP multicast and broadcast: ``` // not ip multicast ``` ## Detailed filter expression syntax description The filter expression determines which packets are selected by the filter for further processing. If no expression is given, all the packets on the net are selected. Otherwise, only the packets for which expression is “true” are selected. There are three different kinds of qualifier:

Qualifier	Description
type	Qualifiers say to what the id name or number refers to Possible types are: host, net, port, portrange For example: “host foo”, “net 128.3”, “port 20”, “portrange 6000-6008” If there is no type qualifier, host is assumed
dir	Qualifiers specify a particular transfer direction to and/or from id Possible directions are: src, dst, src or dst and src and dst For example, “src 1.1.1.1”, “dst net 128.3”, “src or dst port 21”. If there is no dir qualifier, src or dst is assumed
proto	Qualifiers restrict the match to a particular protocol Possible protos are: ether, ip, ip6, arp, rarp, tcp and udp For example: “ether src 00:12:13:14:15:16”, “arp net 128.3”, “tcp port 21”, “udp portrange 7000-7009” If there is no proto qualifier, all protocols consistent with the type are assumed For example, “src 1.1.1.1” means “(ip or arp or rarp) src foo” (except the latter is not legal syntax), “net 1.2.3.0/24” means “(ip or arp or rarp) net 1.2.3.0/24” and “port 53” means “(tcp or udp) port 53”

More complex filter expressions are built up by using the words “and”, “or” and “not” to combine primitives. For example: “*host foo and not port ftp and not port ftp-data*”. To save typing time, identical qualifier lists can be omitted. For example: “*tcp dst port ftp or ftp-data or domain*” is exactly the same as “*tcp dst port ftp or tcp dst port ftp-data or tcp dst port domain*”. Allowable primitives are:

Primitive	Description
dst host host	True if the IPv4 destination field of the packet is "host", which may be either an address or a name
src host host	True if the IPv4 source field of the packet is "host"
host host	True if either the IPv4 source or destination of the packet is host Any of the above host expressions can be prefixed with the keywords, ip, ip6, arp, rarp as in: “ip host host” This is equivalent to: “ether proto \ip and host host”
ether dst ehost	True if the Ethernet destination address is "ehost" Ehost must have a numeric format: XX:XX:XX:XX:XX:XX
ether src ehost	True if the Ethernet source address is "ehost"
ether host ehost	True if either the Ethernet source or destination address is "ehost"
dst net net	True if the IPv4 destination address of the packet has a network number of "net"
src net net	True if the IPv4 source address of the packet has a network number of "net"
net net	True if either the IPv4 source or destination address of the packet has a network number of "net"
net net mask netmask	True if the IPv4 address matches net with the specific netmask. May be qualified with "src" or "dst"
net net/len	True if the IPv4 address matches net with a netmask "len" bits wide May be qualified with "src" or "dst"
dst port port	True if the packet is ip/tcp, ip/udp and has a destination port value of "port"
src port port	True if the packet has a source port value of "port"
port port	True if either the source or destination port of the packet is "port"
dst portrange port1-port2	True if the packet is ip/tcp, ip/udp and has a destination port value between "port1" and "port2" "port1" and "port2" are interpreted in the same fashion as the port parameter for "port"
src portrange port1-port2	True if the packet has a source port value between "port1" and "port2"
portrange port1-port2	True if either the source or destination port of the packet is between "port1" and "port2" Any of the above port or port range expressions can be prefixed with the keywords, tcp or udp, as in: “tcp src port port” This matches only tcp packets whose source port is "port"
less length	True if the packet has a length less than or equal to "length" This is equivalent to: “len <= length”
greater length	True if the packet has a length greater than or equal to "length" This is equivalent to: “len >= length”
ip proto protocol	True if the packet is an IPv4 packet of protocol type "protocol" Protocol can be a number or one of the names icmp, icmp6, igmp, igrp, pim, ah, esp, vrrp, udp, or tcp The identifiers tcp, udp, and icmp are also keywords and must be escaped via backslash (\), which is \\ in the C-shell This primitive does not chase the protocol header chain
ip protochain protocol	True if the packet is IPv4 packet, and contains protocol header with type protocol in its protocol header chain For example, “ip protochain 6” matches any IPv4 packet with TCP protocol header in the protocol header chain The packet may contain, for example, authentication header, routing header, or hop-by-hop option header, between IPv4 header and TCP header The code emitted by this primitive is complex and cannot be optimized, so this can be somewhat slow
ether broadcast	True if the packet is an Ethernet broadcast packet The ether keyword is optional
ether multicast	True if the packet is an Ethernet multicast (or broadcast) packet The "ether" keyword is optional This is shorthand for “ether[0] & 1 != 0”
ip multicast	True if the packet is an IPv4 multicast (or broadcast) packet
ether proto protocol	True if the packet is of ether type protocol Protocol can be a number or one of the names ip, ip6 ,arp, rarp, atalk, aarp, sca, lat, mopdl, moprc, iso, stp, ipx, or netbeui These identifiers are also keywords and must be escaped via backslash (\) In the case of Ethernet, system checks the Ethernet type field for most of those protocols The exceptions are: iso, stp, and netbeui checks for an 802.3 frame and then checks the LLC header as it does for FDDI, Token Ring, and 802.11 atalk checks both for the AppleTalk etype in an Ethernet frame and for a SNAP-format packet as it does for FDDI, Token Ring, and 802.11 aarp checks for the AppleTalk ARP etype in either an Ethernet frame or an 802.2 SNAP frame with an OUI of 0x000000 ipx checks for the IPX etype in an Ethernet frame, the IPX DSAP in the LLC header, the 802.3-with-no-LLC-header encapsulation of IPX, and the IPX etype in a SNAP frame
ip, arp, rarp, atalk, aarp, iso, stp, ipx, netbeui	Abbreviations for “ether proto p”, where “p” is one of the above protocols
svlan [vlan_id]	True if the packet is an IEEE 802.1Q Service VLAN packet (ether proto 0x88a8)
vlan [vlan_id]	True if the packet is an IEEE 802.1Q VLAN packet (ether proto 0x8100) If [vlan_id] is specified, only true if the packet has the specified vlan_id The first "vlan" or "svlan" keyword encountered in expression changes the decoding offsets for the remainder of expression on the assumption that the packet is a VLAN packet The "vlan" "[vlan_id]" expression may be used more than once, to filter on VLAN hierarchies Each use of that expression increments the filter offsets by 4 For example, “svlan 100 && vlan 200” filters on VLAN 200 encapsulated within Service VLAN 100, and “vlan 300 && ip” filters IPv4 protocols encapsulated in VLAN 300, and “svlan 100” filters all packets encapsulated within Service VLAN 100
mpls [label_num]	True if the packet is an MPLS packet If [label_num] is specified, only true is the packet that has the specified label_num The first "mpls" keyword encountered in expression changes the decoding offsets for the remainder of expression on the assumption that the packet is a MPLS-encapsulated IP packet The "mpls" "[label_num]expression may be used more than once, to filter on MPLS hierarchies Each use of that expression increments the filter offsets by 4 For example, “mpls 100000 && mpls 1024 “ filters packets with an outer label of 100000 and an inner label of 1024, and “mpls && mpls 1024 && host 192.9.200.1” filters packets to or from 192.9.200.1 with an inner label of 1024 and any outer label
pppoed	True if the packet is a PPP-over-Ethernet Discovery packet (Ethernet type 0x8863)
pppoes	True if the packet is a PPP-over-Ethernet Session packet (Ethernet type 0x8864) The first "pppoes" keyword encountered in expression changes the decoding offsets for the remainder of expression on the assumption that the packet is a PPPoE session packet For example, “pppoes && ppp proto 0x21” filters IPv4 protocols encapsulated in PPPoE
tcp, udp, icmp	Abbreviations for: “ip proto p”, where “p” is one of the above protocols
iso proto protocol	True if the packet is an OSI packet of protocol type protocol Protocol can be a number or one of the names clnp, esis, or isis
clnp, esis, isis	Abbreviations for: “iso proto p”, where “p” is one of the above protocols
expr relop expr	True if the relation holds, where relop is one of >, <, >=, <=, =, !=, and expr is an arithmetic expression composed of integer constants (expressed in standard C syntax), the normal binary operators [+, -, , /, &, \|, <<, >>], a length operator, and special packet data accessors Note that all comparisons are unsigned, so that, for example, 0x80000000 and 0xffffffff are > 0 To access data inside the packet, use the following syntax: “proto [ expr : size ]” Proto* is one of ether, fddi, tr, wlan, ppp, slip, link, ip, arp, rarp, tcp, udp, icmp, and indicates the protocol layer for the index operation (ether, fddi, wlan, tr, ppp, slip and link all refer to the link layer) tcp, udp and other upper-layer protocol types only apply to IPv4 The byte offset, relative to the indicated protocol layer, is given by expr Size is optional and indicates the number of bytes in the field of interest; it can be one, two, or four, and defaults to one The length operator, indicated by the keyword len, gives the length of the packet For example, “ether[0] & 1 != 0” catches all multicast traffic The expression “ip[0] & 0xf != 5” catches all IPv4 packets with options The expression “ip[6:2] & 0x1fff = 0” catches only unfragmented IPv4 datagrams and frag zero of fragmented IPv4 datagrams This check is implicitly applied to the "tcp" and "udp" index operations For instance, "tcp[0]" always means the first byte of the TCP header, and never means the first byte of an intervening fragment Some offsets and field values may be expressed as names rather than as numeric values The following protocol header field offsets are available: icmptype (ICMP type field), icmpcode (ICMP code field), and tcpflags (TCP flags field) The following ICMP type field values are available: icmp-echoreply, icmp-unreach, icmp-sourcequench, icmp-redirect, icmp-echo, icmp-routeradvert, icmp-routersolicit, icmp-timxceed, icmp-paramprob, icmp-tstamp, icmp-tstampreply, icmp-ireq, icmp-ireqreply, icmp-maskreq, icmp-maskreply The following TCP flags field values are available: tcp-fin, tcp-syn, tcp-rst, tcp-push, tcp-ack, tcp-urg

Primitives may be combined using: * A parenthesized group of primitives and operators (parentheses are special to the Shell and must be escaped) * Negation (\`!' or \`not') * Concatenation (\`&&' or \`and') * Alternation (\`||' or \`or'). Negation has highest precedence. Alternation and concatenation have equal precedence and associate left to right. Note that explicit and tokens, not juxtaposition, are now required for concatenation. If an identifier is given without a keyword, the most recent keyword is assumed. For example, “*not host 1.1.1.1 and 2.2.2.2*” is short for “*not host 1.1.1.1 and host 2.2.2.2*” and should not be confused with “*not (host 1.1.1.1 or 2.2.2.2)*”. ## MAC Switch Group parameters In the "MAC Switch Group parameters" section, you can view the Switch Groups and Rules that are already created, including the management switch group; you can change the parameters for these Switch Groups, delete them by clicking the «**Remove Group**» button or create new ones by clicking the «**Create Switch Group**» button. The same operations are available for the switching rules: add a new rule within a switch group by clicking the «**Add Rule**» button (located within sub-menu "Rules" of this group) or delete an existing rule by clicking the «**Remove Rule**» button.

General options in this section: **Enable Switch** This checkbox enables/disables global switch operation {% hint style="danger" %} CAUTION Disabling the switch in the absence of routing settings can lead to termination of packet transmitting through the device. {% endhint %} **Max Sources** Limits the switch's MAC address table. The default number of entries is 5000. **Disable STP Forwarding** Completely prohibits the BPDU frames transmission from external switches through the wireless device. In case the BPDU frames should be allowed within one or more switch groups the STP protocol must be enabled in these groups. **STP MINT mode** Enables/disables the STP MINT mode. STP MINT mode is used to exclude the wired switches with the enabled STP protocol influence on the network operation. STP MINT mode performs the following: * blocks the transmission of standard BPDU frames of the STP protocol configured on the third-party switches, so the switch cannot detect a loop and block its ports; * enables a proprietary form of the STP protocol on the wireless device, which differs from the standard only in the header of the multicast BPDU frame, due to that a separate STP tree is built within the MINT domain. This option is applicable only in conjunction with the RSTP protocol activated in the switch group of the wireless device, in this case the subinterface (eth or prf) within the switch group will be blocked, not the entire wired interface, as it happens when the standard STP protocol is running. «Switch Group configuration» section:

Parameter	Description
Group #	Displays the Switch Group number. Assign the switch group identifier (must be unique within the MINT network segment).
Status	Select the Switch Group status: started, stopped or discard.
Interfaces	Add Ethernet or/and Radio as Switch Group interface(s) via the «Ports» button. "Select": pass (selected by default), strip or tag for VLAN tag modification for each added interface. The Interfaces section provides the means to control the VLAN tag processing mode, as each local interface supports three different scenarios: "Pass" - transparent mode, traffic remains unchanged. "Strip" - all tags are stripped. "Tag" - all packets are tagged with the specified VLAN tag Another option in this field is to remove one or both added interfaces.
STP	Enable/disable STP support. Add VLAN number for STP if STP support is enabled.
Repeater	Enable/disable repeater support. The unit acts as a simple switch, relaying packets to all ports, except the source port.
IGMP	Enable/disable IGMP snooping support. Please refer to the information provided in the next section for details.
Flood	Allow/deny unlimited unicast flood without protection filter.
Inband	Allow/deny access to the device through in-band broadcast/multicast management traffic. Enabled by default.
Mode	Set the working mode of the switching group: normal, trunk, in-trunk (give it the trunk group number created on the BS), upstream, downstream: Normal (standard mode) - the switch group operation is based on the configured Rules, packets are processed without modification (this is the default option) Trunk - the inbound traffic is untagged and placed into switch groups in accordance with its VLAN tag In-Trunk - allows filtering out the traffic that belongs to a certain switch group that is a member of a trunk Switch Group Upstream - used mainly in video surveillance systems for upstream multicast flows Downstream - used in video surveillance systems for downstream traffic
Description	Type a description sentence for the current switch group.
Default Action	Set the default action: permit/deny. In the absence of any Switching rule, or if a packet does not match to any Switching rule, the default action for this group or interface is taken.
Default QM Channel	Allocate a default logical channel The default logical channel must be prior created in the "Traffic Shaping⁣" section. In the absence of any Switching rule, or if a packet does not match to any Switching rule, the default logical channel is allocated. For the indications on how to create a logical channel, please refer to the "Traffic Shaping" section below.
Default Priority	Allocate the default priority for all the packets going through the Switch group: “Up to” - used to increase the packet priority to the specified value only if the processed packet has a lower priority. “Set” - used to assign a new priority regardless of the value already assigned to the packet. In the absence of any Switching rule, or if a packet does not match to any Switching rule, the default priority is allocated.

You can change the list order of the switch group using the "**up/down**" arrows. * «*Remove L3 Management*» - by clicking this button you can delete the "*sviX"* interface, which is available in the default configuration, for the unit management. * «*Create L3 Management*» - by clicking this button you can add an "*sviX"* interface for the unit management via Web interface. A set of rules are applied to all packets within a switch group. You can create several switch rules within a switch group. The following parameters are available for switch rules:

Parameter	Description
Action	Set the action for the packets that match this rule: permit/deny.
QM Channel	Allocate a logical channel if there are logical channels prior created in the "Traffic Shaping⁣" section. If you allocate a number for a logical channel that was not prior created in the "Traffic Shaping" section, it has no effect in the rule configuration. For the indications how to create a logical channel, please refer to the "Traffic Shaping" section below.
Priority	Allocate the priority for all the packets going through the new rule of the filter: “Up to” is used to increase the packet priority to the specified value only if the processed packet has a lower priority. “Set” is used to assign a new priority regardless of the value already assigned to the packet.
Packet capture filter	Set the packet capture filter for Switching. The syntax is called “PCAP expression”. Please refer to filter expression syntax description above. Validate rule by clicking the «Validate» button.
VLAN list	Set the VLAN ID. It is available for the legacy configuration. It can be set also in "PCAP expression" option (for example: VLAN 100 when “PCAP expression” is chosen), PCAP expressions cannot be used in "trunk/in-trunk mode". Validate rule by clicking the «Validate» button.

{% hint style="warning" %} NOTE In all three types of filters: Switching, IP Firewall and Traffic Shaping, there is the same syntax called “PCAP expression” for setting a rule. It is a universal tool for creating filters. {% endhint %} ### IGMP Snooping In this section you can set the IGMP-parameters for the groups for which support of IGMP snooping is enabled (the IGMP check box is marked for these groups in the "MAC Switch" section).

IGMP Snooping is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups. By listening to and analyzing IGMP messages, the device running IGMP Snooping establishes mappings between ports and multicast MAC addresses and forwards multicast data based on these mappings. In order for IGMP snooping to function, a multicast router must exist on the network and generate IGMP queries. The tables created for snooping (holding the member ports for each a multicast group) are associated with the multicast router. Without a multicast router, the tables are not created and snooping will not work. Furthermore, IGMP general queries must be unconditionally forwarded by all switches involved in IGMP snooping. IGMP Snooping parameters can be set within "MAC Switch" section:

Parameter	Description
Router Port Forwarding	Enable/disable forwarding to router ports.
Flood IGMP Reports	Enable/disable flood IGMP reports to all bridging ports, not only to router ports.
Permit Zero IP Querier	Allow/deny query requests with source address 0.0.0.0.
Replace Source IP	Replace source IP in all IGMP reports/query packets.
Last Member Query Timeout (LMQT)	Set the timeout (in seconds).
Group Membership Interval (GMI)	Set the interval (in seconds).
Multicast Group Limit	Set the limit number for the multicast group.
Enable Querier	Start/stop the IGMP querier.
VLAN	Set the IGMP querier VLAN ID in case of a VLAN broadcast domain.
Disable Election	Enable/disable the IGMP querier election process.
Source IP	Set the IP address of the IGMP querier. By default, this is 0.0.0.0.
Interval	Set the IGMP querier send interval (in seconds).

# IP Firewall IP Firewall is a mechanism of filtering packets crossing an IP network node, according to different criteria. System administrator may define a set of incoming filters and a set of outgoing filters. The incoming filters determine which packets may be accepted by the node. The outgoing filters determine which packets may be forwarded by the node as a result of routing. Each filter describes a class of packets and defines how these packets should be processed (reject and log, accept, accept and log). Packets can be filtered based on the following criteria: * Protocol (IP, TCP, UDP, ICMP, ARP) * Source address and/or destination address (and port numbers for TCP and UDP) * The inbound network interface * Whether the packet is a TCP/IP connection request (a packet attempting to initiate a TCP/IP session) or not * Whether the packet is a head, tail or intermediate IP fragment * Whether the packet has certain IP options defined or not * The MAC address of the destination station or of the source station. The figure below illustrates how packets are processed by the filtering mechanism of the router: There are two classes (sets) of filters - prohibiting (reject) and permitting (accept). Furthermore, a filter may be applied to all inbound packets or only to packets arriving via a specific interface. Each received packet is checked against all filters in the order they are put in the set. The first filter that matches the received packet determines how the packet are treated. If the filter is an accept filter, the packet is accepted, otherwise it is rejected. If the packet matches no filter in the set, or if the set is empty, the packet is accepted. {% hint style="warning" %} NOTE The rejected packet are discarded without notification to the sender. {% endhint %} ## Packet filtering rules Every packet entering a router passes through a set of input filters (blocking filters). The packets accepted by the input filter set are further processed by the IP layer of the router kernel. If the IP layer determines that the packet should go further and not landing here, it hands the packet to the set of outgoing filters (forwarding filters). Information on packets rejected by any filter is displayed on the operator’s terminal and the packets themselves are discarded without any notice to their sender. A packet, "advancing through" a set of filters, is checked by every filter in the set, from the first one till the end of the set, or until the first matching filter. The algorithm is the following: 1. If the filter set is empty, the packet is accepted 2. Otherwise, the first matching filter decides what to do with the packet. If it is an accept filter, the packet is accepted. If it’s a reject filter, the packet is rejected (discarded) 3. If no filter has been found that matches the packet, it is accepted. ## IP Firewall parameters In the "IP Firewall parameters" section, you can view the IP Firewall rules that are already created; you can create a new rule for the current switch group by clicking the «**Add Rule**» button, or you can permanently remove the rule from the configuration by clicking the «**Remove Rule**» button.

Rule	Description
Action	Set the action for the rule: permit/deny/pass: “Permit” - the packet is processed by the system (ignoring other firewall rules). “Deny” - the packet is dropped. “Pass” - the packet is passed to the next rule in the list and logged in the system log (only if the log check box is marked).
Channel	Allocate a logical channel if there are logical channels prior created in "Traffic Shaping⁣" section (it is active only if the action "permit" is selected) If you allocate a number for a logical channel that was not prior created in "Traffic Shaping" section, it has no effect in the rule configuration For the indications how to create a logical channel, please refer to "Traffic Shaping" section below.
Priority	Set the priority for the packets going through the new rule of the filter: “Up to” - used to increase the packet priority to the specified value only if the processed packet has a lower priority. “Set” - used to assign a new priority regardless of the value already assigned to the packet.
Log	Enable/disable filter actions logging in the system log.
Direction	Set the input/output direction for applying the new rule: “Input” - the rule is used to process inbound traffic. “Output” - the rule is used to process outbound traffic and for post-routing packet filtering.
Interface	Set the interface for applying the new rule. All the available interfaces are displayed in the dropdown list (physical and logical). If “any” option is used, the rule is applied to all available interfaces.
Group	Set the Switch Group number for the applying of the new rule. The Switch Group must be prior created.
Rule	Set the packet capture filter for IP firewall. It is the same syntax called “PCAP expression”, as in the "Switching" section. Refer to the filter expression syntax description above. By clicking the «Validate» button, you can check the syntax in the expression in the “Rule” field.

The «**Up/Down**» arrows allow you to organize rules list. The rules are processed one by one in a top-down order. # SNMP The SNMP protocol support is an important feature of all communication devices because it allows the system administrator to manage the operation of a network as a whole, as well as of each component. SNMP section contains a set of parameters to exchange data about network activity of the device. The SNMP Protocol has two sides, the agent and the management stations: * The agent sends data to the management station * The management station collects data from all the agents on the network. You can set several destinations of traps with individual set of traps as well as several users with individual access rights. * The agent sends alerts called traps (see Traps zone) and answers requests that were sent by the management station * The management station captures and decodes the traps. The management station also requests specific information from the agent. * The information is passed through requests and replies with the use of the MIB * The management station is responsible for decoding the SNMP packets and providing an interface to the administrator. The interface can be a GUI or a command line. ## Access In the "Access" section, you can view and edit the current SNMP access settings; you can delete the current SNMP v.3 users by clicking the «**Remove User**» button or create new ones by clicking the «**Add SNMP v.3 User**» button:

Parameter	Description
Start SNMP	Enable/disable SNMP daemon in the device.
Version 1 enable	Enable/disable SNMP v.1 and v.2c support. The first version of the SNMP protocol lacks security in the operation of the protocol itself, which hinders its use for network management, so SNMP v.1 and v.2c works only in read-only mode. By default, it is enabled.
Community	Set the community name for read-only mode (SNMP v.1 and v.2c only). The default SNMP v.1 and v.2c community name is "public". It is a security method for SNMP v.1 and v.2c, as Agents can be set to reply only to queries received by accepted community names. In SNMP v.1 and v.2c the community name passes along with the data packet in clear text.
Contact	Set the contact information. Used as a reference information about the device owner.
Location	Set the geographical location where the unit is installed. Used as a reference information about physical device’s location.
User Name	Set the authorization user name of SNMP v.3.
Password	Set the authorization password of SNMP v.3.
Security	Set the security level: the lowest level means no authentication or privacy (No Authorization No Privacy), you have to set the User Name only. the medium level means authorization and no privacy (Authorization No Privacy), you have to set User Name and Password. the highest level means authorization and privacy (Authorization and Privacy), you have to set the User Name, Password and Privacy Password.
Read only	Enable/disable the read-only permission. Read/Write is the default value.
Admin	Enable/disable the full access to the variables. For example: ability to reboot the device. Limited access is the default value.
Privacy Password	Set the privacy password. It is necessary when privacy is enabled for the required security level.

## Traps SNMP protocol operation requires a network agent instance to send asynchronous messages (traps) whenever a specific event occurs on the controlled device (object). Astra Wireless units have a built-in "*SNMP Traps*" support module (which acts as an agent) that performs a centralized information delivery from unit internal subsystems to the SNMP server. This zone focuses on "*SNMP Traps*" agent configuration. In this section, you can view and edit the current "SNMP traps" settings. You can clone, remove and clear target and traps by clicking the corresponding buttons:

Parameter	Description
Enable SNMP Traps	Enable/disable to send "SNMP traps".
Agent IP	Set the IP address of the device which sends traps.
Transport	Set the transport method. Two options are available: “IP” - all SNMP traps are sent to the server specified in the “Destination” field below. “MINT Gateway” - this option should be used when the SNMP server is located beyond a gateway that acts as an SNMP agent for the whole MINT network.
Gateway MAC	Set the MAC address of the gateway in your MINT network (relay device) if you selected “MINT Gateway” option. If there's no MAC address specified, all "SNMP traps" are sent to the MINT SNMP relay. The relay can be specified by checking the "Trap Gateway" check-box in the "Link Settings" section.
Destination	Set the IP address of the server and the UDP port (162 port is commonly used).

## SNMP trap types The check boxes below specify traps or trap groups that are sent to the server:

Parameter	Description
topoGroup	Events about topology changes in MINT network.
topoEvent	Number of neighbors or their status has changed (full neighbor list).
newNeighborEvent	The new Neighbor has appeared.
lostNeighborEvent	The Neighbor has been lost.
radioGroup	Events which are related to changes of radio link parameters.
radioFreqChanged	The Frequency has changed.
radioBandChanged	The Band has changed.
mintGroup	Events about link quality changes in MINT network.
mintRetries	Retries has changed by more than 10%.
mintBitrate	The Bitrate has changed.
mintSignalLevel	Signal Level has changed by more than 10%.
ospfGroup	Events about OSPF table changes in MINT network.
ospfNBRState	The State of the relationship with this Neighbor has changed.
ospfVirtNBRState	The State of the relationship with this Virtual Neighbor has changed.
ospfIFState	The State of the OSPF Interface has changed.
ospfVirtIFState	The State of the Virtual OSPF Interface has changed.
ospfConfigError	Parameters conflict in the configuration of 2 routers.
others	Other changes in MINT network.
linkEvent	One of the communication links represented in the agent’s configuration has come up or come down.
trapdColdStartEvent	Cold Start event has occurred.
snmpdAuthenticationFailureEvent	Not properly authenticated SNMP protocol message has been received.
syslog	Events about messages recorded in a system log.

Click the «**Clone**» button if you need to setup multiple SNMP servers. Each server can have an individual set of traps directed toward it. Click the «**Clear**» button in order to clear all check-boxes for the current server. # QoS Options⁣⁣⁣⁣⁣⁣ QoS manager is a convenient and flexible mechanism to manipulate the data streams going through the device. The user can create up to 200 logical QoS channels characterized by different properties (such as priority levels and data transfer rates) and then assign data streams to these logical channels according to special rules of assignment. Packets going through different channels are thus modifying their own properties as well as the properties of their respective data flows.

The following QoS parameters can be selected for traffic prioritization:

Parameter	Description
RTP Packets	Enable/disable automatic prioritization for all RTP traffic, regardless of the source or the destination IP. Detect and prioritize the RTP packets (for example, if the packet is recognized as a voice packet, then it gets the priority 2, regardless of the previously assigned priority). Enabled by default.
Dot1p Tags	Enable/disable automatic prioritization for the packets tagged with IEEE 802.1p priority tags. Detect and prioritize the packets using 802.1p tags. Enabled by default.
Tunnel Prioritization	Enable/disable automatic prioritization for the tunnel traffic. Allow prioritization within tunnels.
MPLS	Enable/disable automatic prioritization for the packets tagged with MPLS priority tags.
IP DSCP	Enable/disable automatic prioritization for the packets tagged with DiffServ priority tags
IP ToS	Enable/disable automatic prioritization for the packets with a non-zero "ToS" field. Detect and prioritize the packets using IP ToS tags.
TCP Acknowledgments	Enable/disable automatic prioritization for TCP ACK packets. Automatically prioritize TCP acknowledgments.
PPPoE	Enable/disable automatic prioritization for the PPPoE tunnels traffic.
ICMP Prioritization	Enable/disable automatic prioritization for ICMP packets. Allow ICMP traffic prioritization. It does not increase the priority of "ping" packets (although they are ICMP packets).

# Traffic Shaping⁣⁣⁣⁣⁣⁣⁣ The "Traffic Shaping" section allows to manipulate the data streams flowing through the device. Up to 200 logical channels can be created, characterized by different properties (such as priority levels and data transfer rates), and then the data streams can be assigned to these logical channels according to the special rules, previously created. In order to configure distribution of the transmit rate between several channels, can be created the class. In the default configuration, there is no channel or class created. Create the class by clicking the "**Add Class**" button, to set the transmit rate redistribution for one or more channels.

Parameter	Description
Class	Service class number in the range 1-200
Max	Maximal available transmit rate in Kbps

You can delete an existed class by clicking the corresponding "**Remove Class**" button.

In order to prioritize the data flows and/or to set the data transfer rates, create the logical channels by clicking the "**Add Channel**" button. The following parameters can be configured in the "Traffic Shaping" section for the logical channels:

Parameter	Description
Channel	Select the logical channel from the dropdown list. All the parameters of this rule are applied to this channel.
Priority	Set the priority for the packets going through the new rule of the filter: “Up to” - used to increase the packet priority to the specified value only if the processed packet has a lower priority. “Set” - used to assign a new priority regardless of the value already assigned to the packet.
Direction	Set the input/output direction for applying the new rule: “Input” - the rule is used to process inbound traffic. “Output” - the rule is used to process outbound traffic and for post-routing packet filtering.
Interface	Set the interface for applying the new rule. All the available interfaces are displayed in the dropdown list (physical and logical). If “any” option is used, the rule is applied to all available interfaces.
Group	Set the Switch Group number for the applying of the new rule. The Switch Group must be prior created.
Rule	Set the packet capture filter. It is the same syntax called “PCAP expression”, as in the "Switching" section. Refer to the filter expression syntax description above. Validate the rule by clicking the «Validate» button.

You can delete an existed traffic shaping rule by clicking the corresponding «**Remove Rule**» button. # Extra Commands⁣⁣⁣⁣⁣⁣ The "Extra Commands" section allows you to take advantage of the CLI configuration flexibility within the Web interface. While the Web interface is simple to use and understand, there are several parameters that can be configured via CLI **only**. {% hint style="danger" %} CAUTION If any configuration changes are introduced via the Web interface later on, the configuration re-initializes and all CLI configured parameters are reset to default. Use this section to add CLI specific commands to the configuration in order to preserve the fine-tuning settings. {% endhint %} The commands that do not have the enhanced parameters displayed in Web interface are: *sys, ifconfig, prf, qm, tun, route, mint, switch, svi, lag, sntp, dhcpc*:

Parameter

Description

Command

Select the command to add it to the device configuration.

Parameters

Insert the string to specify the command parameters and options.

Please refer to OS User Manual for the full explanation of all command parameters and options.

Disabled

Check this option in order to disable the command temporarily.

* "**Up/Down**" arrows allow you to organize the command list. * Click the «**Remove Command**» button if you want to delete the command from the list permanently. * Click the «**Add command**» button if you want to add the command to the list. In the "[Command Line](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/command-line)" menu, the commands are only executed, but not saved into the configuration, while in "Extra commands" section from "Basic Settings" menu, the commands are executed and saved into the configuration. # Maintenance The "Maintenance" menu allows you to perform service tasks for the device maintenance and to check the hardware and software version, reason for the last reboot, system uptime, current configuration, license, diagnostic card, etc. ## Firmware

Parameter	Description
Firmware Version	Displays the current firmware version. The firmware string contains also the hardware platform type.
Build Date	Displays the firmware build date.
Serial Number	Displays the serial number of the unit.
Part Number	Displays the part number of the unit. It contains information about the unit type.
Platform	Displays the processor model.
Uptime	Displays the system up time since the last reboot.
Last Reboot Reason	Displays the reason for the last reboot of the unit. The options are: Software fault Unexpected restart Manual restart Manual delayed restart Firmware upgrade SNMP managed restart Test firmware loaded

### SSL certificate installation {% hint style="warning" %} NOTE To configure a wireless device via Web GUI using secure protocol HTTPS, a SSL certificate must be installed as trusted into your web browser. Otherwise, the automatic update function will not be available. {% endhint %} The following description shows an installation process for Google Chrome web browser. Configuration of other web browsers is described in the relevant product user guide and is similar to following. 1. Download SSL certificate by clicking the "Install Certificate for upgrade firmware via SSL" link. Please note, this link is available if you connect to the Web GUI via HTTPS only. 2. Open the "Chrome Settings" section and click on the "Manage certificates" button.

3. Click the "Import..." button to launch Certificate Import Wizard. 4. Follow the wizard's instructions and choose the file to be imported. Click the "Browse..." button and choose the SSL certificate that you have downloaded before. Click the "Next" button to proceed. 5. In the next step it is necessary to select the repository where certificate will be placed. All new certificates are installed into the personal repository by default, click on the "Browse..." button and select "Trusted Root Certification Authorities". Click the "Next" button to proceed.

6. Final step is to check all the provided information. Click the "Finish" button if it's correct. The security warning will appear, click the "Yes" button to confirm you really want to install the certificate. ### Firmware update The firmware can be updated in two ways: automatically and manually. #### Automatic update The system checks automatically for the firmware updates on the Astrawireless repository and displays a warning message for 10s at each login to the Web interface if a new software version is available: {% hint style="warning" %} NOTE It is not mandatory for the unit to have access to the Internet for this feature to work. However, the PC that is used to initialize the upgrade procedure must have access to Astra Wireless website (both http and ftp). {% endhint %} In case of new software version availability, after clicking the «Check Latest Release» button, the system provides the following options:

By clicking the «Upgrade Firmware» button, the system starts the firmware upgrade process automatically. After the firmware upgrade process ends, you have to reboot the unit before using the new software version. By clicking the «Save New Firmware» button, you download the new firmware file locally on your PC. If no new firmware version is available, the system provides a full change log for the latest firmware release after clicking the «Check Latest Release» button. The process above is the same in case of Beta firmware version. Click the «Check Latest Beta» button for it. #### Manual update In case the PC does not have an access to the Internet, the device must be updated manually. To do this, proceed to the following steps: 1. Download the required firmware version in advance from the official FTP server . Pay attention to the hardware platform of the device being updated, indicated in the Firmware section. 2. Choose the downloaded firmware file in the "Upload" section. 3. Click the "Upload" button. The upgrade process will be started. ### Mass firmware upgrade Each device has the ability to mass firmware upgrade using OTA (Over the Air) function. The firmware can be distributed to: * All devices within a single MINT domain. The firmware will be applied even to the not directly connected devices. * Neighbor devices, directly connected to the current. {% hint style="warning" %} NOTE Only one firmware version can be applied during one mass upgrade cycle. The uploaded firmware version will be applied only to those devices that are built on the same platform. Thus if the upgraded network includes devices on different platforms, the mass upgrade cycle should be performed for each platform. In case the OTA function is enabled the uploaded firmware will not be applied to the device from which the upgrade is performed. It will be uploaded only to the other network devices. {% endhint %} Mass upgrade cycle includes the following steps: 1. Download the required firmware version from the official FTP server. 2. Choose the downloaded firmware file in the "Upload" section. Enable OTA function. Enable "Neighbors only" in case you want to upgrade only the neighbor devices.

3. Click the "Upload" button. The mass upgrade process will be started. #### Mass upgrade monitoring The mass upgrade progress can be seen in the System Log ([Device Status](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/device-status) section): the number of upgraded devices and progress. The remote devices will be rebooted after upgrade completion. The connection failure duration is approximately 35-40 seconds per device.

## Upload The "Upload" section allows you to upload other license, firmware and configuration files to the unit. For each of the three options, click the «Choose File» button, followed by the «Upload» button after the file has been picked up. After clicking the «Upload» button, the system performs three operations: uploading, saving and validating the new file uploaded and indicates if each of the operation succeeded or failed. In case that the process succeeded, you have to reboot the unit in order to apply the new changes. ## Download The "Download" section allows you to download locally, to the management PC, the current license, firmware and configuration files, by clicking the corresponding buttons: «Download License», «Download Firmware» and «Download Configuration». ## Bottom section of the page The following buttons are available: * «Reboot» - reboots the device. A warning message pops up asking for the permission before the operation to start. During the restart process, you are redirected to the login page and the timeout period of 35 seconds counts down before the new login:

* «Restore Factory Settings» - restores the factory default configuration. A warning message pops up, asking for the permission before the operation to start. During the reset to factory process, you are redirected to the login page and the timeout period of 30 seconds counts down before the new login: * «View Current License» - shows the current device license parameters in a new window * «View Current Configuration» - shows the current device configuration in text format in a new window * «Create Diagnostic Card» - Tech Support Reports Generator. By clicking this button, the system downloads to the local PC a text file that contains the complete information (for the technical support specialists) set from the device such as: full device configuration listing, system log output, license information, “*mint map detail*” command output, interfaces statistics, etc. # Spectrum Analyzer In the "Spectrum Analyzer" menu, you can perform a deep analysis of the radio emissions in the environment where the unit is placed. The unit scans the radio spectrum on all available frequencies. In order to obtain the information as accurate as possible, the scanning process may take a while. {% hint style="danger" %} CAUTION When running spectrum scan on a unit accessible via the RF interface, connection will be lost during scan time (the radio-link will be disconnected). Use "**Last Snapshot**" button to see scan results. {% endhint %}

The following parameters are available in order to operate the Spectrum Analyzer:

Parameter	Description
Interface	rf6.0 radio interface is the only option available, but it is showed for the backward compatibility with the dual radio legacy products.
Start Frequency	Set the first frequency for scanning (in MHz).
Stop Frequency	Set the last frequency for scanning (in MHz).
Band	Set the bandwidth (in MHz).
Step	Set the scanning frequency step (in MHz). It is recommended to set 1 MHz “step” value to get more precise scanning results.
Channel Mask	Select which antenna to be used for scanning the radio environment: “Auto” parameter is set by default. In this case scanning is perfomed by both antennas. "1" - scanning is perfomed by antenna "1". "2" - scanning is perfomed by antenna "2". Parameter "3" means scanning is perfomed by both antennas.
Scan Duration	Set the time period for the scanning process (in seconds). After the end of this time period, scanning is stopped and the radio interface will be back to its normal mode operation.
Enable Grid	Mark/unmark the corresponding checkbox to display/hide the grid lines and highlight the special frequency channel on the scan output. The highlighted frequency channel can be used to mark the channel which the device is currently working on or which it plans to use.
Grid Width	Set the bandwidth value for the highlighted frequency channel (in MHz).
Grid Frequency	Set the central operating frequency for the highlighted frequency channel.
RSSI mode	Select the gradient-color type for the “Max RSSI” values to be displayed on the Spectrum Analyzer output screen. The options are: Normal (by default) Gradient Max Hold – holds the maximum signal values at a given point Peak Hold – holds the peak signal values at a given point
Scan mode	"Local mode" – scanning is performed only on the local device. "Combined mode" – Scanning is performed simultaneously on all devices in the sector. The "Last Snapshot" button will display the blended result.

Start/stop Spectrum Analyzer by clicking the «**Start Sensor Test**»/«**Stop Sensor Test**» buttons. By clicking the «**Last Snapshot**» button, you get the final scanning results. The most common usage of this feature is when you perform a spectrum scan at the remote unit on the other side of the radio link. When running a spectrum scan at such a unit (accessible via the RF interface), connection to this unit will be lost for a scan time. "*Last Snapshot*" option allows viewing scan results when the connection gets up again. When you run spectrum scan on a local unit and the link is interrupted, the remote unit will not disappear from the spectrum picture. So you should silence the remote unit in order to have a real picture without it, otherwise you will always see noise signal on the operating frequency generated by the remote unit. You can get detailed information about the scanned radio signals on a specific frequency. Just point a cursor on the needed frequency and you will see a hint with exact Signal level (dBm), Frequency (MHz), Noise Floor (dBm), indicators of RSSI (dBm), High RSSI (dBm), Max RSSI (dBm) and their values in dB. High RSSI allows you to estimate the signal sources number, if the value is significantly different from the average RSSI, then there are several sources of interference. # DFS The "DFS" page provides the monitoring and management of the DFS operation. The DFS status and availability indicators are shown for each frequency for the given band and grid. The indicators are described in the Legend at the bottom of the page. By clicking the «**Clear NOL**» button, you clear the non-occupation list with the blocked frequencies (due to the radars detected on these frequencies). The DFS subsystem rescans those frequencies and if they are still not available, the scanning starts after the time period displayed in the right bottom corner of the frequency indicator. By clicking the «**Re-select Channel**» button, you restart the DFS scanning.

# Command Line The "Command Line" page emulates CLI (command line interface) in the Web interface. This allows managing and monitoring the device by using all the commands and functions that are available via standard CLI. In order to run one or a set of commands, type them in the command field and then click the «**Execute**» button. The output of the commands is displayed in the section above the command field:

In the "Command Line" menu, the commands are only executed, but not saved into the configuration. To execute the command and save it in the device configuration, use the "config save" command. {% hint style="danger" %} CAUTION After changing the configuration in the web interface, the commands that were previously applied through the CLI and are missing in the web interface will be lost. To add these commands use the "Basic settings" - "Additional commands" section. {% endhint %} # Troubleshooting⁣⁣⁣⁣⁣⁣ # No access to the local unit⁣⁣⁣⁣⁣ Make sure that the connectivity is provided between the control center and the device's installation point. If the access is missing only for the Astrawireless device, further actions must be performed at the device's installation site. ### Indicators Pay attention to the LED indicators on the device's enclosure. {% hint style="warning" %} NOTE The LED indication on the device can be disabled administratively. Make sure there is no "system no indicator" command in the last saved device configuration. We recommend to save backup configurations to the internal memory of the device and to a folder on your PC. The device can store 8 configuration backups. When saving the current configuration, its previous version is automatically added to the backup list with record number 0. All operations with the device configurations are performed using the "config" command. {% endhint %} If the power and Ethernet indicators are off, check the integrity of the power supply, the Ethernet cables and the RJ-45 connectors. Replace the power supply and the cables if necessary. #### Evolution Base Station Sectors LED indicators on the Evolution family base station sectors are located in the the cable glands ports. These indicators help to monitor the device's status during the installation. The correspondence between the state of the indicators and the current device state is shown in the table below.

State	Status	Description
Flash	Loading	Only for Gigabit Ethernet port: at the beginning green is lightened a few seconds, on the second loading stage switches to blue.
ON/Blue	Power	Only for Gigabit Ethernet port.
ON/Red	Speed 10 Mbps	Only for Gigabit Ethernet port.
ON/Yellow	Speed 100 Mbps	Only for Gigabit Ethernet port.
ON/Green	Speed 1000 Mbps
ON/Green	ERConsole stage	Port with the established link lights up with green, the second port remains blue.

#### Evolution Su**bscriber Terminals** Evolution ST devices have a LED indicator set located at the back of each device, displaying the current device state.

PWR - power indicators will light red when the device is connected to a power source, yellow when 10/100 Mbps wired connection appears and green when 1000 Mbps wired connection appears. Other indicators are used to perform coarse antenna alignment. The more indicators are on, the better wireless connection is established. The blinking indicator means an intermediate state. The more often the indicator blinks the higher level connection is established. ### Access recovery If the power indicator is on and there is connection via the Ethernet interface, connect to the device directly as it is shown in the scheme below. Make sure that the IP address of the PC is in the same subnet as the IP address of the device. You can restore the IP address and reset the device to the factory settings using the ERConsole utility. The factory reset process using the ERConsole is described in the "Emergence Repair Console" article.

### Checking the status of the Ethernet interface #### Wired interface statistics **Web interface** If you were able to access the device by connecting directly, try to determine the possible reason for the unavailability through the network. Pay attention to the wired interface statistics. In order to do this, go to the "[Device status](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/device-status)" section of the web interface and open the "General statistics" window for the Ethernet interface in the "Interface statistics" section. Pay attention to the CRC errors number, as they indicate a violation of the data integrity during the transmission over the wired segment. Also, the problem can be caused by a queue overflow (Retransmit limit) or an inappropriate frame size.

The description of the parameters for a complete diagnostic is available in the "Device status" article. **Command line interface** If there is no access to the device's web interface, run the "*ifconfig eth0*" command to get statistics via CLI.
The description of the parameters for a complete diagnostic is available in the "Ifconfig command (interfaces configuration)[" article.](https://wiki.infinetwireless.com/pages/viewpage.action?pageId=17605871) #### **Duplex mode** Pay attention to the duplex mode on the network devices connected to the wireless router. This information is available in the the web interface. Proceed to the "Device status" section - "Interface statistics" and open the "General statistic" for the Ethernet interface, or run the "*ifconfig eth0*" command in the command line interface.

We recommend to set the auto-negotiation mode provided by the Ethernet standard. The problem can occur due to the connection between two devices with different duplex settings. For example, if one device is in auto-negotiation mode and the other is in fixed full duplex mode. Red value of this parameter in the interface statistics "Mode" column informs that transmission is performed in a half-duplex mode. # The wireless link cannot be established⁣⁣⁣⁣⁣ ### Checking the radio settings #### **Pre-configuration in the lab** Before installing the devices on site, we recommend to configure the basic parameters in the lab and to make sure that the link is establishing. {% hint style="warning" %} NOTE During the configuration of the devices in a lab, take into account the following requirements: * Make sure that the devices are not directed at each other in order to prevent the damage of the radio modules. It is recommended to place the devices at a distance from each other, with the antennas directed to the floor. * The minimum transmit output power must be set on the devices. * In case of using two devices with "E" index, it is recommended to connect them directly using RF cables and RF attenuators with an attenuation of at least 40 dB for each polarization (the installation\deinstallation of the RF attenuators and of the RF cables should only be performed when the devices are switched off). * The failure or damage of the device's radio module in case of disregarding these requirements is not covered by warranty. {% endhint %} #### **Checking the radio parameters** If the wireless link is not establishing in lab conditions, make sure that the radio parameters are set to the values determined during the planning stage. To establish a wireless link, one device must be configured as Master, the second (or all subscribers of the base station in the point-to-multipoint topology) as Slave. The following parameters must be identical on both devices: * Channel Width. * Frequency ("auto" settings are possible). * Network SID. * Security Key. **Web interface** To check the wireless link parameters go to the "Basic settings" - Link settings" section. Make sure that the "Enable Link" checkbox is on.

**Command line interface** Use the "*config show*" command to check the configuration via the CLI.

#### **Checking the status of the radio interface** Make sure that the radio interfaces of both devices are in the "Up" state.

If the status of the interface is "Down", enable the radio interface in the "Network settings" section by clicking the checkbox.

If the device does not have a radio interface, the reason for such behavior can be the recovery mode present during the reset of the device using the ERConsole. Complete the recovery process by returning the device to the factory settings from the Maintenance section. Pay attention to the red values of the parameters in the interface statistics "Mode" column: * Operating frequency - red value of this parameter indicates an absence of data transmission due to the spectrum scanning by the DFS tool; * TX Power - red value for this parameter may indicate a problem with the transceiver's hardware. #### **Checking the firmware version** **Web interface** In the "Maintenance" section, make sure that the same software version is installed on both device. We recommend to update the devices to the latest beta software version.

The latest software versions can be downloaded from the official FTP server. **Command line interface** To upload the software via the command line, use the "*flashnet*" command described in the "General Purpose Command Set" article. ### Checking the installation requirements #### Checking the network infrastructure If the link is not established after the installation on site, make sure that the devices were not damaged during shipping, check the integrity of the network infrastructure, the cables and the power supplies. #### Checking the installation requirements Check if the suspension height, azimuth and elevation of the antenna match with the values obtained from planner tool. Make sure that the obstacles on the path profile are not higher than those specified during the planning phase.

#### **Interference detection** **Web interface** Using the built-in [Spectrum Analyzer](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/spectrum-analyzer) tool, scan the air on both sides of the link to make sure there is no interference that could corrupt the signal on the device's operating frequency and on the adjacent frequencies. The current modulation (bit rate) will be selected by the device depending on the carrier to interference and noise ratio (CINR). To operate at higher modulations, the CINR parameter must be greater or equal to 28 dB. To get accurate information about the frequency, hover the mouse cursor over it. The pop-up window below provides information about frequency, noise level (in dBm), maximum signal level (Max RSSI), average signal level (Average RSSI). The "High RSSI" indicator allows to estimate the number of signal sources. If the value differs significantly from the average RSSI, then there are several interference sources. The indicators show the signal level in dB, while the signal in dBm is indicated in parentheses. {% hint style="warning" %} NOTE It is recommended to run the spectrum scanning simultaneously on both devices to avoid a misrepresentation due to the signal received from the remote device. {% endhint %}

**Command line interface** The radio environment analysis is also available via the command line using the "*muffer sensor*" command. # The wireless link is established, but there is no access to the remote device⁣⁣⁣ ### Configuration analysis In the web interface go to the section "Device status" → "Link statistics on rf6.0 interface", then left-click on the device to which the access is missing. Select "Remote commands".

In the pop-up window enter "config show". If the devices are configured via telnet, access to the remote device can be obtained with the "*mint rf6.0 rcmd*" command. #### **"Vlan" interfaces** Make sure that the "vlan" interfaces are configured in accordance with the company's security policy (see point 1 in the figure below). The VLAN configuration process using the command line is described in the "VLAN configuration" article. #### **Filtering rules** Pay attention to the traffic filtering rules in the switch group and in the "IP Firewall⁣⁣ ⁣⁣menu⁣" subsection (point 2).

### Checking the switch settings on the remote device #### Device management Make sure that the switch group for the device management is configured correctly (see point 3 in the figure above): * To access the device via the radio interface, the rf6.0 interface must be added to the management switch group. * The svi interface must be associated with the switch group. The interface can be associated using the "*svi*" command (point 4). * The device's management IP address must be assigned to the svi interface using the "*ifconfig*" command (point 1). The switch groups are configured using the "*switch*" command. #### **Checking the members of the switch group** To display information about the devices included in the switch groups, use the "*mint rf6.0 map swg*" command.

#### **Switch statistics** To display statistics about the dropped/blocked MAC addresses for each switch group, use the "switch statistics" command.

### Checking the switch settings on the local device #### Device management Make sure that the switch group ID assigned for management on the local device matches with the switch group ID on the remote device. Make sure that the rf6.0 interface has been added to the switch group. The svi interface must be associated with the switch group and its IP address is used for the management of the device. For detailed information about the device management configuration proceed to the "Remote management" article. #### **Filtering rules** Pay attention to the traffic filtering rules in the switch group and in the "*IPFirewall*" subsection. Make sure that the traffic from the remote device is not restricted. # The wireless link throughput is lower than expected⁣⁣⁣ ### Performance tests **Web interface** The throughput test can be performed with the "Performance Tests" tool built into the web interface, in the section "[Device status](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/device-status)" → "Link statistics for the rf6.0 interface". This tool generates test traffic between the devices and it allows to obtain data about the real link throughput both in one direction and in a two-way manner. The throughput evaluation is performed using traffic with the specified priority without taking into account the service traffic required to maintain the link operational. To exclude the influence of the data traffic on the test's result, it is recommended to set the highest priority for the test traffic (at least 15). Performance tests are always performed on the highest modulation,the detailed description of the parameters and the performance test settings are available in the "[Device Status](/astra-wireless-documentation/technical-documentation/astrawireless-evolution-technical-user-manual/operation-and-administration/device-status)" article.

**Command line interface** When using the command line interface to manage the device, it is possible to test the radio link via the "*ltest*" command. ### Wireless link status #### Link statistics on the rf6.0 interface **Web interface** To evaluate the quality of the wireless connection with the neighboring device, use the color indication in the "Status" column of the "Link statistics on rf6.0" subsection: * Red: bad connection. * Yellow: good connection. * Green: perfect connection. The following symbols indicate problems: * In the wireless connection uptime column: * F - the local device has a newer software version than the remote device. * E - the Ethernet port of the remote device is flapping. * In the TX power column: * \* - hardware device failure. * In the RSSI column: * \* - significant difference in the signal power between the vertical and horizontal polarizations. Make sure that the "TX Power" and "Bitrate" parameters match with the values of the planning phase. In the "Link statistics on rf6.0" of the "Device status" section, pay attention to the wireless connection parameters. The main parameters are the retries number and the bitrate. It is not recommended to use the link with a retries number exceeding 5%. The actual bitrate (modulation level) depends on the SNR parameter - the signal-to-noise ratio. The highest modulations are available at SNR values of 27-50 dB. For detailed description of the link parameters proceed to the "Device Status" article. **Command line interface** To display information about the wireless link status via the command line interface, use the "mint rf6.0 map detail" command.

Pay attention to the indicators in the "Options" column. The following values are possible: * M - Master device; * S - Slave device; * TM - Master device with software having support for the TDMA technology; * L - the throughput is limited by license; * F - the software version is older than the one on the local device. A question mark in front of the remote's device name indicates that it has no password. Pay attention to the "\*" symbol, which can represent the following: * At the "pwr" column - hardware device failure. * At the "rssi" column - significant difference between the signal power of the vertical and horizontal polarizations. #### **Radio statistics** **Command line interface** To display statistics via the command line interface, use the "*rfconfig stat*" command.

Pay attention to the following indicators: * "Lost Frames" - the number of frames that were not received by the device, even after retrying. * "Aggr Subframe Retries" and "Aggr Full Retries" - the number of frames that the device has sent several times because the other side did not acknowledge the receipt. * "Excessive Retries" - the number of frames that failed to to be sent after all the retry attempts. #### **QoS statistics** **Web interface** The "QoS statistics" section provides information about the transmitted and dropped packets in each priority queue configured on the device. Drops present in the traffic processing queues indicate that the throughput threshold has been exceeded. Losses in queue q00 (P16) are acceptable because this queue contains performance test data.

**Command line interface** To display statistic via the command line interface, use the "*rfconfig rf6.0 stat qos*" command. The number of dropped packets for each configured queue can be displayed by the "*qm stat*" command. ### Statistics graphs If the link has deteriorated during its operation, having the initial parameters corresponding to the calculated ones, it is necessary to find out when the problem has occured. Use the "Statistics graphs" tool to determine when or how often the problem occurs by changing the display options.

### Device status Pay attention to the CPU and memory usage indicators in the "Device status" section. Excessive processes running on a device can overflow the volatile memory and overload the CPU (over 95% usage), leading to a deterioration in the wireless link's quality. The CPU load can be displayed using the "*system cpu*" command and information about the device's memory state can be shown using the "*mem*" command.

### Last reboot reason Disruptions in the wireless link may be caused by the reboot of the device. In the "Maintenance" section or in the "*system uptime*" command output pay attention to the last device reboot reason. The following values are possible: * "*Software fault*". * "*Unexpected restart*". * "*Manual restart*". * "*Manual delayed restart*". * "*Firmware upgrade*". * "*SNMP managed restart*". * "*Test firmware loaded*". * "*Power-on reset*". ### System log Proceed to the System Log tool in the "Device status" section or by using the "*system log*" command. Using the log entries, check if the link degradation was caused by a configuration change ("system reconfiguration" message). Restore the previous version of the configuration if necessary. Detailed information about saving and uploading the configuration is available in the "General Purpose Command Set" article.

Pay attention to the following messages:

Record in log	Description
Link DOWN	The wireless link has disconnected. The reason for the disconnection is indicated in the same entry.
"too many transmit errors"	The wireless link was interrupted due to transmission errors.
"link reconnecting"	The wireless link is reestablished.
"no signal from the remote side detected"	There is no signal received, check the remote device.
Scrambling engine overflow	The hardware capabilities of the scrambling module are exceeded. To connect more subscribers (more than 62) scrambling should be disabled.
Warning: Abnormal transmit power disbalance!	May indicate a hardware problem.

Frequent changes in the status of the Ethernet interface ("Up" and "Down") may indicate problems with the Ethernet interface, the cable connected to it, with the power supply, or with the switch. ### Antenna alignment **Web interface** The link degradation can be caused by antenna misalignment or by the appearance of obstacles along the signal's propagation path. Use the built-in "Antenna Alignment Tool". The recommended parameters are shown in the table below. If the parameters differ significantly from the calculated ones, check the alignment accuracy on both link sides. **RSSI**


-90 ... -80	The value is close to the receiver sensitivity level, only lower modulations are available
-80 ... -60	Low level. Average modulations are available
-60 ... -40	The recommended value for maximum performance
>-40	The received signal level is too high

**Absolute value EVM (dB)** Recommended value: >21 **CINR (dB)** Recommended value for higher modulations are available: >28 **Absolute value Crosstalk (dB)** Recommended value: >20 If the value of the RSSI parameter remains high while the CINR value decreases, it may indicate high interference levels near one of the devices. The deterioration of both the RSSI and the CINR parameters can indicate a misalignment of the devices. A detailed description of the "Antenna Alignment" tool is available in the "Device status" article. **Command line interface** When using the command line to manage the device, fine antenna alignment can be performed using the "ltest rf6.0 MAC ADDRESS -align" command. The command output will show the average CINR for the local and the remote devices.

# Common errors in configuration⁣⁣⁣⁣ Some device modes and options can significantly affect the link's stability and throughput. ### Autobitrate and ATPC To keep a balance between the wireless link's performance and the retries number, we recommend to always set the "Bitrate" parameter to "Auto" mode. Also enable the automatic transmit power control (ATPC) in order to increase the operational life of the devices. ### Frame size Make sure that the selected frame size ensures the best performance for your wireless system. A short frame will transmit less payload than a long one, however it ensures a smaller delay. ### Packet retries management The "Turbo" mode is available in the TDMA software version, which allow to increase the wireless link throughput in case that the degradation is caused by a large number of errors in the radio. Detailed information about the radio parameter configuration via the web interface is available in the "Link⁣ ⁣Settings⁣" article or via CLI in the "mint command" article. # Emergence Repair Console⁣⁣ If the management of the unit is completely lost (of the local and/or the remote one), the ERConsole recovery procedure should be used. ERConsole is a software application created to reset the Astra Wireless units to the factory default configuration. ### Required software * Download ERConsole from our ftp site: . ### Network Requirements * Turn off any anti-virus or firewall running on your computer. If no device can be discovered by ERConsole, turn on the firewall, and add an UDP connection port 10009 as an exception. * Use a simple unmanaged switch as intermediary device between your PC and the Astra unit. It is essential to reboot the Astra unit each time in order to activate the Emergency Repair Protocol on the unit, therefore the switch would prevent your PC Ethernet interface from flapping up and down. Using Cisco Catalyst switches for unit recovery is not recommended due to a known issue port mode negotiation delay.

* Set default gateway address to the same network interface configuration connected to Astra Wireless unit or to switch connected with Astra Wireless unit. Turn off all the network interfaces (except Ethernet interface connected to Astra Wireless unit). {% hint style="warning" %} NOTE ERConsole and Astra Wireless units exchange information only during the bootup process, therefore each time you need to read the units IP-address, to add a new IP-address or to restore to the default configuration, the Astra Wireless unit should be rebooted. {% endhint %} ### ERConsole recovery procedure 1. Run the ERConsole application downloaded from our FTP. 2. Connect a network Ethernet cables between the Astra Wireless unit, unmanaged switch and your PC, as shown in the figure above. 3. Turn off the Astra Wireless unit by removing ethernet cable from power supply unit and then turn it on in a few seconds. 4. Wait for 30 seconds and the ERConsole screen should receive update from the unit as shown in the figure below. The Serial number, number of device reset cycles ("*Sequence*" field), IP-address, network mask and MAC-adress will be displayed on the screen.

9. Turn off and on the unit and then wait for about 30 seconds until the "Complete" sign will uppear. 10. The unit will start in special emergency mode with the IP-address 10.10.10.1 and mask 255.255.255.0. 11. Login to the unit and use "Restore Factory Settings" button on the "Maintenance" page if you use Web GUI or by command "*config clear*" by CLI to switch off emergency mode. 12. Set new login and password, then save the configuration and restart the unit. # Unicast-flood detection⁣⁣⁣⁣ **Unicast-flood** occurs when the unicast frame's destination MAC-address is unknown for the switch (not included in its routing table), it sends this frame to all interfaces of the network, besides the sender interface. The most common reasons of unicast-flood are: * MAC address table overflow (a common problem in large networks) * Hosts with ARP timers longer than the ARP cache time on switches * Incorrect STP settings * Incorrect switch groups settings (in particular, when the IDs of switch groups for the receiving and sending traffic are different). The unicast flooding process on devices works as follows. If the destination MAC address of a frame is not in the switch forwarding table of the device, the frame is sent to all interfaces except the sender's. When a device first receives a frame, it adds an entry with the destination MAC address to the table. However, packets continue to be sent to all interfaces for four seconds. During this time, if the device receives a response frame with this MAC address as the source, the MAC address is added to the switch's forwarding table and assigned to the interface from which the response was received. If the device does not receive a response within four seconds, the table entry is locked for one second. Then, the entry is removed from the table and the process begins again. | Time since record creation | Switch action | | -------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- | | 0 - 4 sec | Record created. Frames are sent to all interfaces except the sender interface. Frames increment the "flood" counter in the switch statistics. | | 4 - 5 sec | Frames are discarded. Frames increment the "Unreachable" counter in the switch statistics. | | ≥ 5 sec | Record deleted. The cycle starts over. | This process has the following representation in the unit's interfaces and links graphs:

Also, unicast-flooding can be detected in the "Switch Statistics" → "Device Status" tab in "Flood" column:

To remove restrictions on unicast flooding through a switching group, check the "Flood" box in the "Basic Settings" → "MAC Switch" section. This will prevent entries from being created in the flood table, and the destination MAC address will not be blocked every four seconds.

# AstraFleX⁣ Technical User Manual ## Important Notice ### Legal Rights © Copyright 2026 ⁣Astrawireless. All rights reserved. The information contained in this document is originated by, proprietary, confidential and owned by Astra Wireless Technology Ltd. No part of this document should be disclosed, reproduced or distributed without the express written permission of Astra Wireless Technology Ltd. Astra Wireless Technology Ltd. reserves the right to change the information contained in this document without prior notice. No part of this document may be considered as a part of any contract or warranty. ### Statement of Conditions Astra Wireless Technology Ltd. shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this manual or equipment supplied with it. ### Disclaimer The software is sold on an "AS IS" basis. Astra Wireless Technology Ltd, its affiliates or its licensors make no warranties, whatsoever, whether express or implied, with respect to the software and the accompanying documentation. Astra Wireless Technology Ltd specifically disclaims all implied warranties of merchantability and fitness for a particular purpose and non-infringement with respect to the software. Units of product (including all the software) delivered to purchaser hereunder are not fault\_ tolerant and are not designed, manufactured or intended for use or resale in applications where the failure, malfunction or inaccuracy of products carries a risk of death or bodily injury or severe physical or environmental damage (“high risk activities”). High risk activities may include, but are not limited to, use as part of on-line control systems in hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, life support machines, weapons systems or other applications representing a similar degree of potential hazard. Astra Wireless Technology Ltd specifically disclaims any express or implied warranty of fitness for high risk activities. ### Indication of the countries Astra Wireless equipment has no geographical limitations for selling and can be supplied to any country of the world. ### Limitation of Liability Astra Wireless shall not be liable to the purchaser or to any third party, for any loss of profits, loss of use, interruption of business or for any indirect, special, incidental, punitive or consequential damages of any kind, whether arising under breach of contract, tort (including negligence), strict liability or otherwise and whether based on this agreement or otherwise, even if advised of the possibility of such damages. To the extent permitted by applicable law, in no event shall the liability for damages hereunder of Astra Wireless or its employees or agents exceed the purchase price paid for the product by purchaser, nor shall the aggregate liability for damages to all parties regarding any product exceed the purchase price paid for that product by that party (except in the case of a breach of a party’s confidentiality obligations). ## About This Manual This manual lists the commands of the AstraFleX operating system used in the all Astrawireless families devicess. This manual is fully applicable for **Evolution** family. For device’s management and configuration a Unix-like command line interface is used. Every command is having power right after Enter key is pressed. However, each command lifetime duration is limited within one configuration session. In order to save a current configuration *config save* command is used. Several commands can be grouped in one line using “**;**” character. If a wrong-syntax line is met in the group, the rest of the string is checked anyway and the wrong command is ignored. Command name can be shortened unless the ambiguity occurs. If your terminal supports VT100 or ANSI standard you can move around the list of recently executed commands using cursor keys. Numbered list of these commands can be reviewed by “*!h*” command. Any command from this list can be available using “*!\*” command. TAB key performs substring search of recently executed commands. Ctrl/R combination refreshes the command string if its content was disturbed by system messages. The command executed with no arguments prints a short hint about its keys, parameters and syntax. Context help can be obtained by printing “*?*” in any position of the line. # Getting started with AstraFleX User Manual ## Document structure This document consists of the following chapters: * “Getting started” - This chapter presents the information about this document’s purpose and structure * "IP-address format" - This chapter presents the information about IP-address format * "General Purpose Command Set" - This chapter presents the information about general commands and their purpose * "Layer 2 commands set -PHY and MAC" - This chapter presents the information about Layer 2 commands and their purpose * "Layer 3 Command set -IP Networking" - This chapter presents the information about Layer 3 commands and their purpose * "Other commands" - This chapter presents the information about other commands. ## Abbreviations The following abbreviations are used in this document: * ABR - Area Border Router * ACL - Access Control List * ARP - Address Resolution Protocol * TPC - Automatic Transmit Power Control * BDR - Backup Designated Router * BS - Base Station * CD - Carrier Detect * CPE - Customer Premises Equipment * CPU - Central Processing Unit * CRC - Cyclic redundancy check * CS - Command Shell * CSMA/CA - Carrier Sense Multiple Access with Collision Avoidance * DFS - Dynamic Frequency Selection * DR - Designated Router * DRA - DHCP Relay Agent * DSCP - Differentiated Services Code Point * ERP - Emergency Repair Procedure * FTP - File Transfer Protocol * HTTP - Hyper Text Transfer Protocol * ICMP - Internet Control Message Protocol * IDU - Indoor Unit * IP - Internet Protocol * IRC - Internet Relay Chat * LACP - Link Aggregation Control Protocol * LAN - Local Area Network * LED - Light Emitting Diode * MAC - Media Access Control * MIB - Management Information Base * MINT - Mesh Interconnection Networking Technology * MTU - Maximum Transfer Unit * NAS - Network Access Server * NAT - Network Address Translation * ODR - On-Demand Routing * OSPF - Open Shortest Path First * PRF - Pseudo Radio Interface * PtMP - Point to MultiPoint * PtP - Point-to-Point * QoS - Quality of Service * RAS - Registration, Admission, Status * RF - Radio Frequency * RIP - Routing Information Protocol * RPCAP - Remote Packet Capture * RSH - Remote Shell * SID - System Identification Number * SNMP - Simple Network Management Protocol * SNR - Signal To Noise Ratio * SNTP - Simple Network Time Protocol * SSH - Secure Shell * SSID - Service Set Identifier * SVI - Switch Virtual Interface * TCP - Transmission Control Protocol * TDM - Time Division Multiplexing * Telnet - TrminaL Network * UDP - User Datagram Protocol * VLAN - Virtual Local Area Network * VPN - Virtual Private Network * VR - Virtual Router * VRRP - Virtual Router Redundancy Protocol * WMA - Wireless Marker Access ## Document marks {% hint style="danger" %} **CAUTION** All caution warnings are marked with a special warning sign. One should pay a great deal of attention to what is written in the Caution section. {% endhint %} {% hint style="warning" %} **NOTE** All notes are marked with a special note sign. Notes usually contain useful comments or hints to the described section of the document. {% endhint %} # ⁣⁣IP-address format Many commands of the operating system require specification of IP-addresses. In **OS AstraFleX**, the IP-addressees may be specified in traditional numeric format. Optionally, the mask may be specified either by its bit length (the specified number of leading bits in the mask are set to 1, the remaining bits are reset to 0) or numeric value. The IP-address 0/0 denotes all possible IP-addresses. Therefore, the possible formats to specify IP-addresses are: nn.nn.nn.nn (no mask is used) nn.nn.nn.nn/N (N is the bit length of the mask) nn.nn.nn.nn:xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx is the numerical value of the mask) **Example:** The 192.168.9.0/24 address describes the network address 192.168.9.0 and the mask with leading 24 bits on. The same set of addresses may be denoted as 192.168.9.0:255.255.255.0. # General Purpose Command Set ## help Displays system commands information. It is executed automatically, if the user types an unknown command. **Syntax:** ``` help ``` ## system The command is used to review and update system parameters. **Syntax:** ``` sys [args...] args are: user [Login] password [Password] [no]useAAA [no]useLocalAAA contact [String] guest [guest login] name [System Name] prompt [any_word] location [String] mgmtAccount [user:pass@host] gpsxy XX.XXXXX YY.YYYYY log {on|off} | {show [offset] | clear}| [no]filter | {ADDR | -} factorypassword {single|otp} search [seconds] [no]indicator [no]fastroute [no]mintgateway [no]authFailLog [no]sendredirects [no]dropredirects OfficialAddress X.X.X.X | 0 icmplimit N [200] uptime cpu [no]pager [no]ipforwarding info [-f] [NAME] version ```

Parameter	Description
user [Login]	Assigns a name under which the system administrator enters the router from the console or remotely, using telnet/http.
password [Password]	Sets the system administrator's password.
[no]useAAA	Enables/disables device access control using a RADIUS server. To use the authentication the AAA module should be running (see "AAA (access control using RADIUS server)). Remember that the AAA authentication method has the highest priority and local login database is used only in case when the required account is not found on the RADIUS server. If there is no local user account the management interface will be accessible with any login and password even if the AAA authentication is turned on.
[no]useLocalAAA	Changes the authentication priority; the local account is checked first, in case it's not found, authentication is performed via RADIUS.
contact [String]	Contact details.
guest [guest login]	Specifies a login for entering a guest mode, any password may be used. In the guest mode the router's configuration parameters neither security-related parameters can't be modified.
name [System Name]	The device name that will be displayed in the browser tab title while the web interface is used.
prompt [any_word]	Replaces the prompt on the screen with the given word of a maximum length of 16 characters.
location [String]	Describes the system location; for example in SNMP protocol.
mgmtAccount [user:pass@host]	Access details for the software update server via SNMP.
gpsxy XX.XXXXX YY.YYYYY	Sets the geographical coordinates of the device (longitude, latitude).
log {on\|off} \| {show [offset] \| clear}\| [no]filter \| {ADDR \| -}	Manages the system log operation: "on" – display messages on the current console. "off" – stop displaying messages on the console. "show" – show the system log (time is expressed in seconds/milliseconds back from the current time). "clear" – clear the system log. "[no]filter" – removes neighboring identical lines from system log leaving only one copy of each message and counts their recurrence (enabled by default). "ADDR" – IP address parameter specifies the UNIX host where the system log is located to which messages are directed under the standard "syslog" protocol. In the "syslogd" settings set the "facility.level" equal to "user.notice" or just a numeric value 15. "-" – disable logging on the remote host.
factorypassword {single\|otp}	Sets the access mode on the device with the factory password. Each unit has its unique factory access password that can be obtained via the technical support. Once obtained this password stays the same for each factory login attempt (the "single" mode). Setting the unit to "otp" mode tells it to ask for a new password each time the factory login is given (the unit will provide different sequences, that should be submitted to the technical support in order to obtain a new password). Whenever the unit is set to "single" mode again, its unique factory access password is restored.
search [seconds]	Forces all indication to blink for searching the devices in a group of one type units. By default, this mode turns off after 10 seconds.
[no]indicator	Enables/disables LED indicators on the unit in order to hide the active device.
[no]fastroute	Enables/disables the fast routing mode. In this mode the router becomes invisible for traceroute network tracing procedures, while still performing all routing functions. It is not recommended to enable the fast routing mode simultaneously on several devices connected to the same cable Ethernet segment, because this may produce a IP packets storm.
[no]mintgateway	Позволяет использовать в качестве шлюза по умолчанию (default gateway) ближайший узел MINT, который сконфигурирован с опцией “mint extg”, если такой имеется.
[no]authFailLog	Enables/disables the unsuccessful authentication attempts logging.
[no]sendredirects	Enables/disables sending "icmp redirect" messages for the packets source suppression if routing is incorrectly configured.
[no]dropredirects	Enables/disables receiving "icmp redirect" messages for routing tables updating if routing is incorrectly configured.
OfficialAddress X.X.X.X \| 0	Sets the IP address which will be used as a source IP address in all outgoing connections of the unit. The "0" value removes the current address.
icmplimit N [200]	Sets the limit of the outcoming ICMP packets number per second (0 by default, no limitation applied). It helps to avoid the device reboot while network scanning programs are working. The "0" value removes all limitations.
uptime	Displays the time since the last system's reboot.
cpu	Indicates current CPU load (in percent).
[no]pager	Enables/disables page splits in the console output.
[no]ipforwarding	Enables/disables IP Forwarding.
info [-f] [NAME]	Displays device information: "-f" – full information. "NAME" – information about specified section.
version	Displays the software version.

{% hint style="warning" %} **NOTE** Any parameter can be deleted by setting a "-" value. Any changes in configuration can be saved by the "config save" command. {% endhint %} ## config Allows to view, save, export, and import the device configuration.. **Syntax:** ``` config [show [KeyWords ...] | save | clear] config {import | export} login:password@host/file show - show current configuration save - store current configuration to flash clear - clear configuration in flash import - import configuration from file export - export configuration to file ----------------------------------------------- backup [list] - show list of backups backup save N "Comment" - create configuration backup number N [1..8] backup replace N "Text" - replace configuration backup number N backup restore N - restore backup number N backup del N - delete backup number N backup show N - view text of backup number N backup comment N "Comment" - change comment for backup N backup {import | export} N ftp://login:password@host/file ```

Parameter	Description
show	Displays the current configuration of the system. Any change of the system parameters may be immediately viewed using the config show command. The optional parameter may contain a selection of AstraFleX commands (abbreviated to their initial letters), as shown in the following examples; only those system parameters will then be displayed which relate to the commands selected. Example: Display MINT and RIP protocols configuration: co show mint rip Display the configuration of all commands started with "r" , except "rip": co show r !rip
diff	Displays all modifications made since the configuration was saved last time.
save	Saves the current system configuration in the router's flash memory for subsequent permanent use. All modifications to the system parameters, if not saved by this command, are valid only during the current session (until the system reset). After applying this command, the previous configuration is automatically saved as a backup with 0 number.
clear	Clears (resets to default) configuration in device flash. After entering device should be rebooted without saving the configuration.
import	Downloads the device configuration from the remote server. The information is performed using FTP . The file name shall be specified in full, in the format of the remote server's file system.
export	Saves the device configuration to the remote server. The information is performed using FTP. The file name shall be specified in full, in the format of the remote server's file system.
backup [list]	Displays backup configuration list.
backup save N "Comment"	Creates backup configuration N (1 ... 8).
backup replace N "Text"	Replace backup configuration.
backup restore N	Restore backup configuration N.
backup del N	Removes backup configuration N.
backup show N	Displays backup configuration N.
backup comment N "Comment"	Changes backup configuration N description.
backup {import \| export} N ftp://login:password@host/file	Imports/exports backup configuration from/to ftp server.

## set Sets time zone settings. Supports automatic summer/winter time switching. {% hint style="warning" %} **NOTE** Timezone is determined on Master device and automatically distributed on all other devices, connected with it. Thus, if on Slave devices the timezone is set, then it will be redefined to the timezone of Master. {% endhint %} **Syntax:** ``` set TZ TIMEZONE ```

Parameter

Description

TIMEZONE

Time zone in POSIX format:

"std offset" – time zone name and time offset, which must be added for a UTC time value. If only these parameters are specified, then the time zone will be applied without daylight saving time.

The following parameters are optional, must be used if automatic summer/winter time switching is needed.

"[dst] [offset]" – the name and offset for the corresponding Daylight Saving Time zone.
start[/time],end[/time] – the day and time of the beginning and end of the period when summer time is applied. The "start" and "end" values are set in the "Mm.n.d" form:
- "Mm" – month, 1...12;
- "d" – day of week, 0...6, there 0 – is sunday;
- "n" – week in month, 1...5, there 1 – first week, 5 – last.

**Example:** ``` set TZ EST+5EDT,M4.1.0/2,M10.5.0/2 set TZ GMT+5 ``` {% hint style="warning" %} **NOTE** For detailed information about TIMEZONE format: {% endhint %} ## flashnet Uploads a new software version. **Syntax:** ``` flashnet get|put login:password@host/file [-S src_addr] ```

Parameter

Description

get

Loads a new software version into the device from a remote server using FTP. The file name shall be specified in full, in the format of the remote server's file system.

The download process has two phases:

Reading a file from a remote server and checking its integrity.
Upload the system image to the device's memory.

The second phase is indicated with symbol ".".

To update the firmware from FTP server use command:

flashnet get ftp:ftp@ftp://92.168.100.34/firmware.H11S01v1.6.6.bin

where

"H11" – hardware platform.
"1.6.6" – latest firmware version.
"ftp" – username.
"ftp" – password.

NOTE

After firmware updating, restart the unit with the command:

restart yes

put

Uploads current software from the device to a remote server.

-S

Any other IP address (SourceAddress) may be set as default.

## restart Full reset and re-initialization of a router. Equivalent to power off and on. May be used to restore initial configuration after a number of unsuccessful attempts to understand what exactly is done wrong, and after loading a new version of software. **Syntax:** ``` restart [y] | [SECONDS] | [stop] ```

Parameter	Description
y	Restart is executed immediately, without asking for confirmation.
SECONDS	The time for which the device restart will be delayed, in seconds. This option can be useful in case of dangerous manipulations with device's configuration when there is a risk to lose control over the device. Repeated entering of this command will start the countdown from the beginning.
stop	Cancels a postponed restart.

## ping Sends test packets ("ICMP\_ECHO\_REQUEST") to the given IP-address. It allows estimating the attainability of a host and the destination response time. **Syntax:** ``` ping IP [-s size_in_bytes] [-c count_packets] [-S IP] [-t sec] [-q] [-l] ```

Parameter	Description
-s size_in_bytes	The test packet length within the range of 10 to 8000 bytes (optional, 56 by default).
-c count_packets	Specifies the number of request messages sent, 5 by default.
-S IP	Sets different source IP address. By default, the sending interface's address is put in the "source address" field of the packets.
-t sec	Interval between sending each request, 1 second by default. Fractional values are possible.
-q	Quiet mode. Displays only summary information.
-l	Same as -q, but displays lost packets.

## telnet Sets up a connection with a remote host specified by the IP address in the terminal emulation mode. The "*telnet"* command uses transparent symbols stream without any intermediate interpretation; therefore, the terminal type is defined by the terminal from which the command has been executed. To interrupt the terminal emulation session, press "Ctrl/D*"*. **Syntax:** ``` telnet address [port] [-S source] ```

Parameter	Description
port	Telnet port.
-S source	Device's IP address

## tracert Traces the packet transmission path up to the host, specified by the "*HostAddress"* parameter. The command sends packets to the specified host, assigning different values to the "*time to live*" field in their IP headers, and analyzes "*ICMP TIME\_EXCEEDED*" indications coming from different routers along the path to that host. By default, the sending interface's address is put in the "*source address*" field of the packets. Using the "*-s"* option, any other IP address (SourceAddress) may be substituted for this default address. Tracing is limited to a path with maximum 30 intermediate nodes. Trace packets are 36 bytes long. The trace procedure makes 3 attempts for every intermediate node. Every trace result contains the IP address of an intermediate node and the response time (in milliseconds) of every attempt. **Syntax:** ``` tracert host [-S src_addr] ```

Parameter	Description
-S src_addr	Node IP address.

{% hint style="warning" %} **NOTE** In addition, it may contain some special symbols corresponding to specific reply codes of the ICMP protocol: * "!" – port unattainable. * "!N" – network unattainable. * "!H" – node (host) unattainable. * "!P" – inappropriate protocol. * "!F" – too long packet. * "!X" – access to a node is administratively restricted (filter, proxy etc.). * "\*" – no reply. {% endhint %} ## webcfg Web-interface support module. **Syntax:** ``` Available commands are: sta[rt] Start WEBCFG service sto[p] Stop WEBCFG service cmd[s] Show additional commands added by WEBCFG clrc[md] Clear additional commands added by WEBCFG Available options are: -http={on,off} Off if Web interface access by HTTPS only -help -h -? Help -lang={en|ru|fr|it|cn} Default language at service startup ```

Parameter	Description
sta[rt]	Enables web-interface support on the device. Web-interface allows easy graphical device configuration with the help of a web-browser.
sto[p]	Disables web-interface support on the device.
cmd[s]	Displays commands applied via web-interface.
clrc[md]	Removes commands applied via web-interface .
-http={on,off}	Enables/disables access to the web-interface via HTTPS.
-help -h -?	List all " webcfg " command arguments.
-lang={en\|ru\|fr\|it\|cn}	Sets web-interface localization: English, Russian, French, Italian and Chinese.

## rshd Remote Shell (RSH) Server is useful for periodic removal of accumulated statistics from the device . The built-in RSH server makes it possible remote command execution using the "*rsh*" program. Identification is based on using privileged TCP ports and a list of authorized hosts. By default RSH is disabled. **Syntax:**

rshd {enable | ipstat | disable} RUSER RHOST LUSER
rshd start | stop | flush | [-]log

Parameter	Example
enable	Enters the system with three parameters: "RUSER" – the remote user name (up to 16 symbols). "RHOST" – remote host IP address. "LUSER" – the local user name (up to 16 symbols).
ipstat	Allows specified user to use the "ipstat" command only.
disable	Disables an entry with defined parameters.
start	Starts server. When started, the server ignores requests for command execution until at least one valid system entry is enabled. A request for command execution is serviced only if for all three parameters it specifies the values corresponding to a valid entry. Up to 6 independent entries may be defined. The name of a local user is in no relation with the AstraFleX main authorization system; it may be considered simply as a keyword.
stop	Stops server.
flush	Clears the RSH server configuration.
[-]log	Enables/disables logging attepts of RSH protocol command using.

**Example:** ``` rshd enable admin 195.38.44.1 mysecretuser rshd enable root 195.38.45.123 mysecret2 rshd start ``` Remove the statistics from the device using RSH: ``` #!/usr/bin/perl -w for(;;) { my $stat; do { $stat = system("rsh -t 30 -n -l root AWR_IP ips fixit >/dev/null"); if(int($stat) != 0) { sleep(5); } } while (int($stat) != 0); do { $stat = system("rsh -t 30 -n -l root AWR_IP ips fixget >stat.tmp"); if(int($stat) != 0) { sleep(5); } } while (int($stat) != 0); do { $stat = system("rsh -t 30 -n -l root AWR_IP ips fixclear >/dev/null"); if(int($stat) != 0) { sleep(5); } } while (int($stat) != 0); system("cat stat.tmp >>stat.txt"); sleep(300); } ``` ## ipstat The IP statistics gathering module provides for collecting information on data flows traversing the router, for further analysis and/or for accounting. Information is accumulated in the router's RAM memory as a series of records having three fields: source address, destination address, number of bytes transferred. By default, only outgoing packets are counted, at the moment they are sent to a physical interface. **Syntax:** ``` ipstat enable [incoming|outgoing|full] [detail] [SLOTS] | disable ipstat clear ipstat traf [detail] [speed | total_bytes | pps] [reverse] [[if=IFNAME] [swg=N] -f "PCAP"] ipstat fixit | fixget | fixclear ipstat strict | -strict ipstat add [intf] [swg=N] -f "PCAP" ipstat del num ipstat rearrange [N] ```

Parameter	Description
enable [incoming\|outgoing\|full] [detail] [SLOTS] \| disable	Enables/disables IP statistics gathering: "incoming/outgoing" – allows gathering only incoming/outgoing packets. "full" – gathering both incoming and outgoing packets. "detail" – detailed IP statistics gathering including ports and protocols information. "SLOTS" – allows to set the maximum number of records in the "ipstat" table. By default – 1000, this amount is usually enough for 15-20 minutes on a common subscriber terminal. One record takes 12 bytes.
clear	Clear accumulated statistical info.
traf [detail] [speed \| total_bytes \| pps] [reverse] [[if=IFNAME] [swg=N] -f "PCAP"]	Allows visually inspect statistics collection process in real time: "detail" – switches on detailed IP statistics gathering including ports and protocols information. "speed" – sorts the command output by transmission rate. "total_bytes" – sorts "ipstat" output according to the number of transmittered bytes for the whole period. "pps" – sorts the command output by the number of transmittered bytes in second. "reverse" – allows to sort by the specified criterium (speed \| total_bytes \| pps) in reverse order. "if=IFNAME" – the command output for the specified port. "swg=N" – the command output for the specified switch group. "-f "PCAP" – the command output for the specified pcap expression.
fixit	Dumps the statistic from the router's memory into an intermediate buffer. The memory is cleared, statistic accumulation starts from the begginig.
fixget	Shows the dump buffer content. This command may be executed any number of times, with no damage to the dumped statistical info.
fixclear	Clears the temporary dump buffer.
strict \| -strict	If the record table in the router memory overflows, or if there is not enough memory currently available, an appropriate warning is written into the system log, and further statistical data are discarded. If the "strict " option is enabled, then at the overflow condition the transit routing is disabled, but the router still responds to any protocol.
add [intf] [swg=N] -f "PCAP"	Limits the packets number to those that satisfy the added rule: "intf" – the interface name through which the packet enters the system. "swg=N" – accepts packets belonging to the switch group N. "-f "PCAP" – pcap expression filter. NOTE The syntax of the rules is equal to the "ipfw" command syntax.
del num	Deletes the N-th rule from the list.
rearrange [N]	Renumbers all the ipstat rules with the given increment (default step is 1).

## sflowagent Realization of a standard Sflow protocol. Sflow – is protocol for monitoring computer networks. It is commonly used by Internet Providers to capture traffic data in switched or routed networks. **Syntax:** ``` Available commands are: sta[rt] Start Sflow agent sto[p] Stop Sflow agent wi[pe] Stop Sflow agent and clean all configuration add[instance] 'name' Add instance (default 'ipstat') del[instance] 'name' Delete instance (default 'ipstat') stat 'name' Show statistics for instance (default 'ipstat') cl[earstat] 'name' Clear statistics for instance (default 'ipstat') Available options are: -collector=IPaddress[:port] Set collector address (default 0.0.0.0:6343 ) -agent=IPaddress Set agent address (default 0.0.0.0) -maxpacket=size Set maximal datagram size (default 1472) -interval=number Set statistics receive interval, in seconds (default 15) -datagrams=number Set datagrams per statistics interval (default 100) -rawheader={on|off} Send packets raw header instead IPv4 data (default off) -debug={on|off} Display debug output (default off) -version -v Display Version ```

Parameter	Description
sta[rt]	Starts Sflow agent.
sto[p]	Stops Sflow agent.
wi[pe]	Stops Sflow agent and clears its configuration.
add[instance] 'name'	Adds statistics gathering component ("ipstat" by default).
del[instance] 'name'	Deletes statistics gathering component ("ipstat" by default).
stat 'name'	Shows statistics for a component ("ipstat" by default).
cl[earstat] 'name'	Clears component statistic ("ipstat" by default).
-collector=IPaddress[:port]	Sets address of a collector that process sflow-packets. Default port is 6343.
-agent=IPaddress	Sets agent's own address (device).
-maxpacket=size	Sets maximum size of a Sflow-packet in bytes. 1472 bytes by default. Upper bound is limited by hardware and operational system capabilities. In case of its exceeding packet size will be decreased to acceptable value.
-interval=number	Time in seconds equal to interval with which statistics is delivered from instance. Increasing of this parameter leads to increasing in overall system efficiency but in case of unexpected network activity splash data could be lost. 15 seconds by default.
-datagrams=number	Maximum number of datagrams between times of receiving statistics from instance. Increasing of this parameter leads to the decrease in datagram average size and increases in theoretical number of delivered statistics data. Reduces the load on the CPU but in the same time reduces overall system efficiency. However, reducing of system efficiency doesn’t happen with low traffic. It is recommended to increase this parameter when decreasing maxpacket parameter and/or when increasing interval parameter. 100 by default. Maximum flow: sflow= datagrams/interval* maxpacket, (Bytes/sec)
-rawheader={on\|off}	Sends original ip4v headers in spite of statistics data ("off" by default). Used for compliance with traffic monitoring programs.
-debug={on\|off}	Adds debug output to the log.
-version -v	Shows current Sflow agent version.

Output parameter description.

Parameter	Description
Cycles	Overall number of gathering statistics success cycles.
Overflow records	Number of records in Instance for all cases when Instance overflowed earlier then interval period had ended.
Overflow count	Number of times when Instance overflowed earlier then interval period had ended.
Samples	Number of grouped records delivered from "flow records".
Datagrams	Overall number of sent datagrams.
Records	The number of statistics records.
Bytes	Overall number of transmitted data by Sflow protocol.
Unused datagrams	Number of datagrams that could be created in compliance with datagrams parameter but was not used.
Dropped records	Number of discarded datagrams.
Dropped samples	Number of discarded records delivered from "flow records".
Pending datagrams	The number of datagrams waiting to be sent.
Lost flow records	Number of "flow records" that were discarded because of "maxpacket", "interval" and "datagrams" parameters low values.
Lost overflow records	Number of times when Instance overflowed earlier then interval period had ended and data were lost.

**Example:** ``` ipstat enable full detail 3000 sflow add ipstat sflow -collector=1.2.3.4 start ``` ## acl While network planning it is often necessary to group similar parameters in lists which can be used for different filters (e.g. "*ipfw*", "*qm*", "*ipstat*"). Access control lists can effectively solve this problem. **Syntax:** ``` acl add $NAME TYPE XXX ... acl del $NAME [XXX ...] acl ren $NAME1 $NAME2 acl flush Possible TYPES: net num Predefined ACL names: $ACLOCAL net - Hosts (networks) permitted to access the device. $LOCAL net - all local IPv4 addresses (only for ipfw/qm). ```

Parameter	Description
add $NAME TYPE XXX ...	Creates an access list with "NAME" title and "TYPE" type. Lists names must start with $ symbol and can include up to 7 letters, digits and other symbols excluding spaces and semicolon. At the same time the command can contain several parameters of "TYPE" type which will be included in the list. If the list with this name has been already created listed parameters will be attached to this list.
del $NAME [XXX ...]	Removes specified parameters from the "NAME" list. If none of parameters are mentioned all list will be deleted.
ren $NAME1 $NAME2	Changes list's name from "NAME1" to "NAME2".
flush	Removes all lists

**Accepted list types** **(TYPE)**

net

Contains network addresses in dot format:

xxx.xxx.xxx.xxx или xxx.xxx.xxx.xxx/MASKLEN or
xxx.xxx.xxx.xxx/xxx.xxx.xxx.xxx.

Lists of "net" type optimize their parameters by excluding duplicates and by having the feature that enables bigger networks include smaller networks. For example, if the list contained 1.1.1.1 parameter, when you include 1.1.1.0/24 parameter in the list 1.1.1.1 will be excluded.

Example:

acl add $LIST1 net 10.0.0.0/8 192.168.0.0/16 5.5.5.5

acl del $LIST1 100.100.100.100/28

**Reserved access lists**

$ACLOCAL net

List of IP addresses for access limitation to the device via telnet, ssh, http/https, snmp protocols (ports 22, 23, 80, 162, 443).

In case "$ACLOCAL" access list is in the configuration all attempts to establish a connection with the device from addresses (networks) that are not in this list will be rejected. There is no need to create rules.

Example:

acl add $ACLOCAL net 10.0.0.0/8 192.168.0.0/16

$LOCAL net

All local IP addresses assigned to the device. It can be used to set filters to restrict/allow access to the device via telnet, ssh, http/https, snmp (ports 22, 23, 80, 162, 443). For detailed information about filters configuration see the "ipfw command (IP Firewall)" article.

## sntp Allows the system to synchronize the time with configured NTP server using fourth version of SNTP protocol [RFC 2030](http://www.ietf.org/rfc/rfc2030.txt). Client works in unicast server request mode in certain time range. Since MINT provides both time and timezone synchronization it's not necessary to use SNTP protocol for host to host time synchronization. So the optimal synchronization scenario is as follows: 1. Master device
* SNTP client is disabled and configured to receive time from corporate or public source. * SNTP server is disabled. 2. Slave device
* SNTP client is disabled - synchronization is performed by MINT. **Syntax:** ``` sntp [options] [command] where commands are: start - start service stop - stop service where options are: -server={ipaddr} - set sntp server address -gps={on|off} - enable/disable GPS time source -interval={seconds} - specify poll interval in seconds [1800] -supplier={on|off} - enable/disable server mode -debug={on|off} - enable/disable debug information ```

Parameter	Description
start	Starts time synchronization process.
stop	Stops process.
-server={ipaddr}	Set SNTP server IP address. Example: sntp -server=9.1.1.1
-gps={on\|off}	Enable/disable GPS time source. In case the external synchronization unit AUX-OUT-SYNC is connected to the device, the built-in GNSS receiver can be used as a precise time source (if there are signals from satellites constellation). It is not necessary to set the external SMTP server address. Example: sntp -server=''ip-external-sntp-server' -gps=on In this case, the device will use both the satellite and the external SNTP server as the source of the precise time, and the satellite source will be the priority.
-interval={seconds}	Specifies poll interval in seconds, by default is 1800. Example: sntp -interval=5000
-supplier={on\|off}	Enables/disables server mode support.
-debug={on\|off}	Enables/disables debug information logging. Example: sntp -debug=on sntp -debug=off

## date Date and time management. Shows or sets the date and time in AstraFleX system. While setting the date and time not only kernel clock is being changed but hardware clock changes its value either (if the device supports this feature). **Syntax:**

date [[[[[cc]yy]mm]dd]HH]MM[.ss]]

Parameter	Description
cc	Century, 20 or 21.
yy	Year in abbreviated form (i.e. 89 for 1989, 05 for 2005).
mm	Month in numeric form (1 to 12).
dd	Day (1 to 31).
HH	Hour (0 to 23).
MM	Minute (0 to 59).
ss	Second (0 to 61 - 59 plus maximum two leap seconds).

**Examples:** ``` date 20040210053004 Tue Feb 1005:30:042004 ``` ``` date Tue Feb 1005:30:102004 ``` ## erp Emergency Repair Procedure utility allows restoring lost system password to the device. **Syntax:** ``` erp [options] [command] [options]: -serial - device serial number -code - ERP code (Factory password) -ip

- interface IP address -mask - interface IP address mask [command]: boot - force continuing boot on device(s). Device serial number may be unspecified and means 'any device'. reset - resets device's configuration. Serial number and ERP code must be specified ifup - turns up device's interface and adds IP address and mask alias to it. Serial number, IP address and IP address mask should be specified If command is not specified, then it's assumed the 'boot' command. ```

Parameter	Description
-serial <n>	Device serial number.
-code <c>	Special ERP code (factory password).
-ip <address>	IP address of device’s Ethernet interface.
-mask <mask>	Network mask.
boot	Device reboot.
reset	Resets device configuration including system user name and password. Serial number and special ERP code must be specified.
ifup	Turns up device's Ethernet interface (eth0) and adds IP address and net mask alias to it. Serial number, IP address and net mask should be specified.

Two Astra Wireless devices are required to perform Emergency Repair Procedure. First device is a device which should be repaired, second – device on which ERP utility will be run to repair the first device. Both of the devices should be connected to the same Ethernet segment via their Ethernet interfaces. The second device should have no "*switch local tag <х>*" option configured on its Ethernet interface. **Password restore procedure:** * Run the ERP utility with "*serial*" option and specify a repairing device serial number. ERP will go to standby mode waiting for a first device to reboot. ``` erp –serial ``` * Reboot device which should be repaired by power off and on. * After device is rebooted ERP will show "*Sequence*" parameter value and serial number of device. Please contact Astra Wireless tech support and provide these values. * The tech support write back an ERP code. * Run the following ERP command: ``` erp –serial -code reset ``` * Reboot a repairing device again. * The utility will reset login, password and configuration on device to default. * Login to a repairing device with any non-blank username and password and enter the following command: ``` config save ``` To change IP address on Ethernet interface of a repairing device from a second device without login use the following command: ``` erp –serial -ip

-mask ifup ``` ## aaa (access control using RADIUS server) The "*aaa*" module allows access control configuration on the device using remote RADIUS server. **Syntax:** ``` aaa [options] [command] where commands are: start - start service stop - stop service where options are: -auth=ip[:port],secret[,identifier] - RADIUS server parameters, address - Server IP Address secret - shared secret identifier - NAS Identifier this option can be repeated. -remove=ip[:port] - Remove RADIUS server. ```

Parameter	Description
start	Starts "aaa" utility.
stop	Stops "aaa" utility.
-auth=ip[:port],secret[,identifier]	Sets parameters to access remote RADIUS server: "ip[:port]" – IP address and port of a RADIUS server. "secret" – password to access the server. "identifier" – Network Access Server ID.
-remove=ip[:port]	Removes information about a RADIUS server from the configuration.

Whenever the debug mode is activated on a device that uses "*aaa*" access authentication via the remote RADIUS server, the authentication debug info is displayed on the local console to verify the settings.

Parameter	Description
Request id	Internal unique id of the request.
Type	Request type, i.e. "Access-Request".

The RADIUS attributes for Access-Request and Access-Accept requests are shown in the tables below. **Access-Request**

Attribute	Description
1 - User-Name	The user name
2 - User-Password	The password
4 - NAS-IP-Address	IP address of the remote access server
6 - Service-Type	The Login (1) value is sent
31 - Calling-Station-Id	IP address of the connecting device
32 - NAS-Identifier	Base station symbolic name
61 - NAS-Port-Type	The Virtual (5) value is sent

Simplified, extended support of the RADIUS server for the wireless connections identification is provided: | Attribute=Value | Description | | --------------------------------------------------- | ------------------------------------ | | ***1 - User-Name = "00-00-00-00-00-00"*** | Connecting device MAC address | | ***2 - User-Password = "dummy"*** | Dummy predefined value | | ***6 - Service-Type = Framed (2)*** | The Framed (2) value is sent | | ***31 - Calling-Station-Id = "00-00-00-00-00-00"*** | MAC address of the connecting device | | ***2 - NAS-Identifier = "Base 1"*** | Base station symbolic name | | ***61 - NAS-Port-Type = Wireless-802.16 (27)*** | Value Wireless-802.16 (27) | **Access-Accept**

Attribute	Description
Session-Timeout	If the response from the RADIUS server contains the Session-Timeout parameter, then after a specified time (sec.), a new authentication request will be sent to extend or break the existing link. Value: 3600 seconds

## license The "*license*" command manages operations with a license file on the device. **Syntax:** ``` license [options] options are: --install= - install new license --export= - export current license to external server --show - show license info = ftp://[login[:password]@]host/file ```

Parameter	Description
-install=<url>	Uploads license file into the device from a remote server using FTP.
-export=<url>	Downloads license file from the device to a remote server using FTP.
-show	Displays license information on the screen.

**Example:** ``` li --export=ftp://ftp_login:ftp_password@192.168.145.1/license_file li --show ``` ## dport This command sets a console port bitrate. Available values are: 9600, 19200, 38400, 57600, 115200 Bit/sec. Default value is 38400 Bit/sec. **Syntax:** ``` dport BAUD ``` ## mem This command show statistics for allocated device memory, network buffers, queues and drops on interfaces. Command output is described in the picture below. **Syntax:** ``` mem ```

## grep The "*grep*" command searches the output of the given command for lines matching the given PATTERN and displays the result. **Syntax:** ``` grep [OPTIONS] [-e]PATTERN "command" or command | grep [OPTIONS] [-e]PATTERN OPTIONS: -e PATTERN, --regexp=PATTERN Use search PATTERN possibly begining with (-) -i, --ignore-case Ignore case distinctions in PATTERN -v, --invert-match Invert the sense of matching, to select non-matching lines -w, --word-regexp Select only those lines containing matches that form whole words -x, --line-regexp Select only those matches that exactly match the whole line -c, --count Suppress normal output; instead print a count of matching lines With the -v, --invert-match option, count non-matching lines -m NUM, --max-count=NUM Stop parsing after NUM matching lines -n, --line-number Prefix each line of output with the 1-based line number -A NUM, --after-context=NUM Print NUM lines of trailing context after matching lines Places a group separator line (--) between contiguous groups of matches -B NUM, --before-context=NUM Print NUM lines of leading context before matching lines Places a group separator line (--) between contiguous groups of matches -C NUM, --context=NUM Print output context NUM lines before and NUM lines after matching lines Places a group separator line (--) between contiguous groups of matches ```

Parameter	Description
-e PATTERN, --regexp=PATTERN	Uses a searching PATTERN that starts with "-" sign.
-i, --ignore-case	Ignore case distinction between capital and lowercase letters.
-v, --invert-match	Perform the invert filtering.
-w, --word-regexp	Display only those lines that matches the whole word.
-x, --line-regexp	Display only those lines that matches the whole line.
-c, --count	Does not display output, but number of lines matched, in combine with "-v, --invert-match" option - number of non-matching lines.
-m NUM, --max-count=NUM	Stops searching after the specified number of matching lines
-n, --line-number	All the command output lines are index numbered starting from 1.
-A NUM, --after-context=NUM	Prints the specified number "NUM" of lines, situated after "А" lines, matching given PATTERNs. Resulting output is separated from other matching entries with a special line (--).
-B NUM, --before-context=NUM	Prints the specified number " NUM " of lines, situated after "В" lines, matching given PATTERNs. Resulting output is separated from other matching entries with a special line (--).
-C NUM, --context=NUM	Prints the specified number " NUM " of lines, situated after "С" lines, matching given PATTERNs. Resulting output is separated from other matching entries with a special line (--).

## gps Manages GPS/GLONASS module. **Syntax:** ``` gps [options] [command] Options: -t= - turn trace level (1, 2 or 0 - turn trace off) -i= - set integrator time constant in seconds -a[=(0:1)] - turn the power on the antenna amplifier -r[=(0:1)] - set reset signal -p= - set TCP port for service (2323 by default) -s= - set baud rate for GPS NMEA port (0 - set 115200) Command: start - start GPS service stop - stop GPS service coordinates - show GPS coordinates console - map GPS NMEA port to stdin/stdout tcp - map GPS NMEA port to TCP service stat - show GPS statistics clear - clear GPS statistics ```

Parameter	Description
-t=<level>	Service messages logging level: "2" – logging all NMEA messages received from GPS/GLONASS module. "1" – logging information about connection/disconnection to GPS/GLONASS, changing the number of visible satellites or a significant change in coordinates. "0" – no logging is perfomed.
-a[=(0:1)]	Turn on/off the power supply to the antenna amplifier (if any): "1" – turn on (by default, if value is not specified). "2" – turn off.
start	Starts GPS/GLONASS module.
stop	Stops GPS/GLONASS module.
coordinates	Displays information about current GPS/GLONASS receiver state. Command output: ______________ #1> gps coordinates Satellites: 8 LAT/LONG: 56.811911/60.547041 Altitude: 275.89 HDOP: 0.92 FIX: 3D, GLONASS Total GPS time: 17:43:19 Total nonvalid time: 00:00:01(0%) Number of losses: 0 Now coordinates are valid last 17:43:18 Satellites histogram: ^ \| 2.0 + \| 3.0 + \| 4.0 + \| 5.0 + \| <1% 6.0 + \| 1% 7.0 + \|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\|\| 99% v SATmin= 5 SATmax= 10 ______________ "Satellites" – current number of visible satellites. "LAT/LONG" – receiver geographic coordinates in degrees: "LAT" – latitude -90.0000000° ... +90.0000000°. "LONG" – longitude -180.0000000° ... +180.00000°. "Altitude" – height above sea level in meters. "HDOP" – horizontal plane coordinates accuracy reduction coefficient. CAUTION For reliable time synchronization, it is recommended to use less then 1,5 the " HDOP" parameter values. The GNSS system can have following values: GPS. GLONASS. GPS+GLONASS. Statistic data (can also be displayed by "gps stat" command): "Total GPS time" – total time of GPS service operation. "Total nonvalid time" – total time during which the coordinates were nonvalid. "Number of losses" – coordinates losses number. "Now coordinates are valid last …" – time of GPS service operation since coordinates become valid. "Satellites histogram" – visible satellites histogram. "SATmin" and "SATmax" – the minimum and maximum number of visible satellites recorded since the last statistics reset. "FIX - NO FIX\|2D\|3D" – coordinate determination current state. Following values are available: "NO FIX" – coordinates are not defined. "2D" – latitude and longitude are defined. "3D" – latitude, longitude and height above sea level are defined.
stat	Dislays statistic about GPS/GLONASS module operation (without current receiver state).
clear	Clears statistic.

{% hint style="danger" %} **CAUTION** Note, that "*tcp*", "*console*", "*-i*", "*-r*", "*-p*" and "*-s*" parameters are used for diagnostics and debugging in case of emergency and only by specialists. {% endhint %} {% hint style="warning" %} **NOTE** The "*gps*" command is available in software version with the TDMA technology support. {% endhint %} ## tsync Manages external synchronization source. **Syntax:** ``` tsync [command] Command: enable [BAUDRATE] - enable external synchronization sources disable - disable external synchronization sources [no]trace - turn trace (debug) messages output to syslog [show] - show statistics clear - clear statistics ```

Parameter	Description
enable [BAUDRATE]	Enable synchronization by using external source.
disable	Disable external source.
[no]trace	Enable message output tracing (debugging) in the syslog.
[show]	Displays statistic.
clear	Clears statistic.

{% hint style="warning" %} **NOTE** The "*tsync*" command is available in software version with the TDMA technology support. {% endhint %} ## SSH protocol SSH (Secure Shell) protocol allows secure remote management of network devices. Its functionality is similar to Telnet protocol but, as opposed to Telnet, SSH encodes all protocol messages/datagrams including transmitted passwords. For using SSH protocol SSH Server and SSH Client is needed. SSH Server accepts connections from client hosts (SSH Clients), performs their authentification and start serving the authorized clients. Astra Wireless devices has built-in SSH Server and SSH Client functionality. ### sshd Built-in SSH Server (SSH daemon) configuration is performed using "*sshd*" command. By default, the SSH Server is disabled. Access to the device via SSH protocol may be limited by using "*$ACLOCAL*" access control list. When "*$ACLOCAL*" list is configured on the device SSH Server rejects all connection attempts from SSH Clients with IP address or networks that are not present in the list. **Syntax:** ``` sshd -help, -h sshd -port=PORT sshd -window=SIZE sshd -keepalive=TIME sshd -banner=on | off sshd -log-level={emerg|alert|crit|error|warning|notice|info|debug|LEVEL} [notice] sshd -algo-list sshd -kex-algos[=ALGO-LIST] sshd -hostkey-algos[=ALGO-LIST] sshd -cipher-algos[=ALGO-LIST] sshd -hash-algos[=ALGO-LIST] sshd -comp-algos[=ALGO-LIST] sshd -auth-methods[=AUTH-METHODS-LIST] sshd -none-cipher=on | off sshd start sshd stop sshd newkeys sshd pub[key] {sh[ow] | cl[ear] | de[lete] N} sshd pub[key] {in[stall] | im[port] [LOGIN[:PASSWORD]@]HOST/FILE} [COMMENT] sshd tun[nel] add LOGIN PASSWORD IFNAME sshd tun[nel] del LOGIN | clear ```

Parameter	Description
-help, -h	Displays the command syntax.
-port=PORT	SSH Server TCP port number, which is used to receive connections SSH, by default is 22.
-window=SIZE	Allows changing SSH Server internal receiving window size in bytes. SSH Server window size defines maximum allowed bandwidth for "SSH Client - SSH Server" data channel. By default, SSH Server window size is 24576 bytes.
-keepalive=TIME	Sets session activity check duration period in seconds. By default server doesn’t make activity check (“0” value).
-banner=on \| off	Shows/hide AstraFleX SSH information banner after loggin.
-log-level={emerg\|alert\|crit\|error\|warning\|notice\|info\|debug\|LEVEL} [notice]	Allows choosing logging levels of the SSH Server service information that will be written into the system log, to manage system log please use "sys log" command. Different levels of logging can be chosen by "emerg", "alert", "error", "warning", "notice", "info", "debug" parameters or specified by the number of the needed level (from 0 to 7) using numeric "LEVEL" parameter. By default, "info" (6th level) is chosen.
-algo-list	Shows a list of all available SSH algorithms for key exchange ( kex ), authentification ( host key ), data encoding (cipher), data verification ( hash ) and data compression ( compress ).
-kex-algos[=ALGO-LIST]	Choosing kex algorithms from the list of algorithms (ALGO-LIST), to be used in SSH key exchange process.
-hostkey-algos[=ALGO-LIST]	Choosing host key algorithms from the list of algorithms (ALGO-LIST), to be used in SSH Server-Client authentification process.
-cipher-algos[=ALGO-LIST]	Choosing cipher algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data encoding.
-hash-algos[=ALGO-LIST]	Choosing hash algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data verification.
-comp-algos[=ALGO-LIST]	Choosing compression algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data compression.
-auth-methods[=AUTH-METHODS-LIST]	C hoosing an available authentication method from the (AUTH-METHODS-LIST) list. An "all" value enables all authentication methods (set by default).
-none-cipher=on \| off	Enable/disable encoding usage. Used when the simple TCP tunnel is needed, that significantly reduces the CPU load.
start	Starts SSH Server.
stop	Stops SSH Server.
newkeys	Host Keys re-generation. NOTE When first-time started SSH Server generates DSS and RSA Host Keys to be used for public key based SSH Server authentication.
pub[key] {sh[ow] \| cl[ear] \| de[lete] N}	"show" – shows SSH Client’s public keys that are registered in the SSH Server list. "clear" – deletes all the SSH Client’s public keys from the SSH Server. "delete" – deletes a certain SSH Client’s public key from the SSH Server list. Parameter "N" – is an index of the key in the list.
pub[key] {in[stall] \| im[port] [LOGIN[:PASSWORD]@]HOST/FILE} [COMMENT]	Allows enabling public key based authentification of SSH Clients. In the Public key authentication mode SSH Server authorize SSH Client bypassing password login procedure. This mode is enabled automatically once a public key of the SSH Client is cached in SSH Server’s registry: "install" – sets the SSH client public key in the SSH server registry. "import" – imports an SSH client's public key into the SSH server registry from a remote FTP server: "HOST" – remote FTP server IP address. "FILE" – file containing SSH Client’s RSA/DSS public key in OpenSSH or SSH2 format. If login and password are set on the remote FTP server they should be specified as "LOGIN" and "PASSWORD" parameters. "COMMENT" – allows adding a comment to the public key entry in the SSH Server list of clients public keys. By default, a comment with clients IP address or FTP IP address from where the key was obtained is added.
tun[nel] add LOGIN PASSWORD IFNAME	Sets separate authentication parameters for each tap interface: "LOGIN" – username. "PASSWORD" – password. "IFNAME" – tap interface name. If the values above are not specified, default authentication parameters will be used.
tun[nel] del LOGIN \| clear	"del LOGIN" – deletes specified username from the SSH Tunnel configuration. "clear" – deletes all SSH Tunnel users from SSH Server configuration.

{% hint style="warning" %} **NOTE** By default SSH Server applies only password authentication. However, this may not be enough to provide the necessary security level. Astra Wireless devices have several built-in SSH authentication methods, which are managed by "*sshd pubkey*" and "*sshd -auth-methods*" command. At the same time, an SSH Server will keep the connected SSH client public key. {% endhint %} ### sshc Built-in SSH Client configuration is performed using "*sshc*" command. **Syntax:** ``` sshc [options] [LOGIN@]HOST[:PORT] [REMOTE-COMMAND] options: -help, -h -window=SIZE -keepalive=TIME -compress, -C -bind-addr=ADDR, -b ADDR -pubkey-show -pubkey-new[=BITS] -pubkey-clear -pubkey-export=[LOGIN[:PASSWORD]@]HOST/FILE -algo-list -kex-algos[=ALGO-LIST] -hostkey-algos[=ALGO-LIST] -cipher-algos[=ALGO-LIST], -c ALGO-LIST -hash-algos[=ALGO-LIST], -m ALGO-LIST -comp-algos[=ALGO-LIST] ```

Parameter	Description
[options] [LOGIN@]HOST[:PORT] [REMOTE-COMMAND]	Connect to the remote SSH Server: "LOGIN" – username (maybe omitted when default logging name is used on the remote device). "HOST" – a remote device IP address. "REMOTE-COMAND" – defines a command that should be executed on the SSH Server after successful login.
-help, -h	Displays the command syntax.
-window=SIZE	Allows changing SSH Server internal receiving window size in bytes. SSH Server window size defines maximum allowed bandwidth for "SSH Client - SSH Server" data channel. By default, SSH Server window size is 24576 bytes.
-keepalive=TIME	Sets a frequency of sending compulsory session activity confirmations to the server. This allows not to loose the session to the server when SSH Client leaved unused for a long time period. By default, SSH Client doesn’t send any special activity confirmations ("0" value). Measured in seconds.
-compress, -C	Enables data compression.
-bind-addr=ADDR, -b ADDR	Sets SSH packets source IP address. This source IP address substitutes the default sending interface's IP address field of the SSH packets.
-pubkey-show	Displays generated public keys.
-pubkey-new[=BITS]	Generates new DSS and RSA SSH Client’s public keys. "BITS" parameter should be specified as a key size in bits, possible values: 512-4096.
-pubkey-clear	Deletes public keys on SSH Client.
-pubkey-export=[LOGIN[:PASSWORD]@]HOST/FILE	Exports public keys from SSH Client to a file on the remote FTP server: "HOST" – remote FTP Server IP address. "FILE" – a file name that will contain SSH Client’s RSA/DSS public keys. If login and password are set on the remote FTP server they should be specified as "LOGIN" and "PASSWORD" parameters.
-algo-list	Shows a list of all available SSH algorithms for key exchange ( kex ), authentification ( host key ), data encoding (cipher), data verification ( hash ) and data compression ( compress ).
-kex-algos[=ALGO-LIST]	Choosing kex algorithms from the list of algorithms (ALGO-LIST), to be used in SSH key exchange process.
-hostkey-algos[=ALGO-LIST]	Choosing host key algorithms from the list of algorithms (ALGO-LIST), to be used in SSH Server-Client authentification process.
-cipher-algos[=ALGO-LIST], -c ALGO-LIST	Choosing cipher algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data encoding.
-hash-algos[=ALGO-LIST], -m ALGO-LIST	Choosing hash algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data verification.
-comp-algos[=ALGO-LIST]	Choosing compression algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data compression.

{% hint style="warning" %} **NOTE** For compulsory SSH Client’s session interruption (for example, if SSH Server is not responding to SSH Client’s requests) please use the following key sequence: "Enter\~." (on the keyboard, firstly, press "Enter" key, then "\~" key, then "." key). {% endhint %} ### sshtun The "*sshtun*" command allows to create upto 16 independent L2 tunnels via SSH connection. In order to create tunnel, it is necessary to create tap interfaces on the both sides by using "*ifconfig tapX up*" command. The tap interface can have an IP address and be used as independent network interface, e.g. for routing, as well as a part of switch group. In addition, the tap interface can be used as the parent interface for the vlan, lag and prf interfaces, also as MINT network part. The client SSH Tunnel module automatically re-establishes the connection to the remote server when the device is rebooted or the connection is broken. It can work with NAT, including addresses that are obtained dynamically via DHCP. **Syntax:** ``` sshtun -help, -h sshtun -log-level={emerg|alert|crit|error|warning|notice|info|debug|LEVEL} sshtun -algo-list sshtun start | stop | clear sshtun IFNAME [options] [LOGIN[:PASSWORD]@HOST[:PORT]] [start | stop | del[ete]] options: -window=SIZE -keepalive=TIME -compress=on | off, -C on | off -bind-addr=ADDR, -b ADDR -remote-if=REMOTE_TAP_NUM -reconnect-delay=TIME -kex-algos[=ALGO-LIST] -hostkey-algos[=ALGO-LIST] -cipher-algos[=ALGO-LIST], -c ALGO-LIST -hash-algos[=ALGO-LIST], -m ALGO-LIST -comp-algos[=ALGO-LIST] -auth-methods[=AUTH-METHODS-LIST] -none-cipher=on | off ```

Parameter	Description
-help, -h	Displays the command syntax.
-log-level={emerg\|alert\|crit\|error\|warning\|notice\|info\|debug\|LEVEL}	Allows choosing logging levels of the SSH Server service information that will be written into the system log, to manage system log please use "sys log" command. Different levels of logging can be chosen by "emerg", "alert", "error", "warning", "notice", "info", "debug" parameters or specified by the number of the needed level (from 0 to 7) using numeric "LEVEL" parameter. By default, "info" (6th level) is chosen.
-algo-list	Shows a list of all available SSH algorithms for key exchange ( kex ), authentification ( host key ), data encoding (cipher), data verification ( hash ) and data compression ( compress ).
start \| stop \| clear	Starts/stops/clears SSH Tunnel configuration.
IFNAME [options] [LOGIN[:PASSWORD]@HOST[:PORT]] [start \| stop \| del[ete]]	Starts/stops/removes specified SSH tunnel. Parameters for an SSH tunnel establishing: "IFNAME" – remote SSH server tap interface name. "LOGIN" – remote SSH server username . "PASSWORD" – remote SSH server password. "HOST" – remote SSH server IP address. "PORT" – remote SSH server port number.
-window=SIZE	Allows changing SSH Server internal receiving window size in bytes. SSH Server window size defines maximum allowed bandwidth for "SSH Client - SSH Server" data channel. By default, SSH Server window size is 24576 bytes. NOTE For maximum performance, the "-window" parameter value should be not less than 128000 on the both tunnel sides.
-keepalive=TIME	Sets a frequency of sending compulsory session activity confirmations to the server. This allows not to loose the session to the server when SSH Client leaved unused for a long time period. By default, SSH Client doesn’t send any special activity confirmations ("0" value). Measured in seconds.
-compress=on \| off, -C on \| off	Enables/disables data compression.
-bind-addr=ADDR, -b ADDR	Sets SSH packets source IP address. This source IP address substitutes the default sending interface's IP address field of the SSH packets.
-remote-if=REMOTE_TAP_NUM	The tap interface number on the remote site.
-reconnect-delay=TIME	Timeout for reconnection in case the connection is broken.
-kex-algos[=ALGO-LIST]	Choosing kex algorithms from the list of algorithms (ALGO-LIST), to be used in SSH key exchange process.
-hostkey-algos[=ALGO-LIST]	Choosing host key algorithms from the list of algorithms (ALGO-LIST), to be used in SSH Server-Client authentification process.
-cipher-algos[=ALGO-LIST], -c ALGO-LIST	Choosing cipher algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data encoding.
-hash-algos[=ALGO-LIST], -m ALGO-LIST	Choosing hash algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data verification.
-comp-algos[=ALGO-LIST]	Choosing compression algorithms from the list of algorithms (ALGO-LIST), to be used in SSH data compression.
-auth-methods[=AUTH-METHODS-LIST]	Choosing an available authentication method from the (AUTH-METHODS-LIST) list. An "all" value enables all authentication methods (set by default).
-none-cipher=on \| off	Enable/disable encoding usage. Used when the simple TCP tunnel is needed, that significantly reduces the CPU load.

## nslookup Nslookup utility sends requests to the DNS server for direct and reverse domain names exchange. **Syntax:** ``` nslookup {name|ip} ``` | Parameter | Description | | ---------- | ----------------------------------------- | | ***name*** | Domain name is used to get an IP address. | | ***ip*** | IP address is used to get a domain name. | ## DNSclient DNS module provides the node address definition by its full name. **Syntax:** ``` dnsclient [options] [command] where commands are: start - start service stop - stop service where options are: -domain={name} - set local domain name. -server={address} - set Internet address (in dot notation) of a name server, this option can be repeated. ```

Parameter	Description
start	Starts DNS client service.
stop	Stops DNS client service.
-domain={name}	Sets a local d omain name.
-server={address}	Sets a server IP address. This parameter can be set several times.
get	Loads a new software version to the device. Loading is performed via FTP. The file name shall be specified in full, in the format of the file system. The download process has two phases: Reading a file from a remote server and checking its integrity. Upload the system image to the device's memory. The second phase is indicated with symbol ".". To update firmware from FTP server use command: flashnet get ftp:ftp@ftp://92.168.100.34/firmware.H11S01v1.6.6.bin where "H11" – hardware platform. "1.6.6" – latest firmware version. "ftp" – username. "ftp" – password. NOTE After firmware updating, restart the unit with the command: restart yes
put	Downloads current software from the device.
-S	Any other IP address (SourceAddress) may be set as default.

## cron The AstraFleX firmware allows to set execution of some commands at a specified time or periodically with a certain frequency. Thus, is possible to perform regular configuration backup without the participation of the system administrator. **Syntax:** ``` cron start cron stop cron clear cron add commandID "command" [from][-to][\interval] cron del commandID cron dump Examples from or to: 31/12/2016 12:00:00 31/12/2016 12:00 12:00:00 12:00 Any field can be set as '.' - don't care. Examples of intervals DD HH:MM:SS \ 2 12:33:15 \ 2 12:33 \ 12:33:15 \ 12:33 \ 2 Don`t care not allowed. ```

Parameter	Description
start	Starts the Cron service.
stop	Stops the Cron service.
clear	Clears all records in the table.
add commandID "command" [from][-to][\interval]	Adds new record to the Cron table: "commandID" – arbitrary name of the record. "command" – command to be executed. "from" and "-to" – allow to set the exact date and/or time of the command execution. Valid formats (any character can be replaced with "." to set "don't care" value) are: 31/12/2016 12:00:00 31/12/2016 12:00 12:00:00 12:00 "\interval" – allows to adjust the frequency of the command application. Valid formats (the "." character is not allowed) are: \ 2 12:33:15 \ 2 12:33 \ 12:33:15 \ 12:33 \ 2 NOTE Records that contain the exact date and/or time will be valid only if the system date and time are set by sntp or gps. Otherwise, only records with execution frequency will be executed, every 7 days for example (since the device last reboot).
del commandID	Removes the record from the Cron table.
dump	Displays the Cron table.

**Example:** Set the configuration backup every 6 days. ``` #1> cron add TEST "co export test:admin@11.12.13.14/testserver/1111" \6 cron: ID 'TEST' replaced #1> cron start #1> cron dump id='TEST' range=' \ 6' command='co export test:admin@11.12.13.14/testserver/1111' next='23/07/2019 10:40:29' ``` # Layer 2 commands set -PHY and MAC # ⁣prf ⁣command ### Description The command allows to control pseudo-radio interfaces. MINT architecture protocol can work not only via radio interfaces but through wired Ethernet interfaces. For this purpose, "prf" interface is used which can be attached to the physical interface. The "prf" driver allows sending network frames of a proprietary format through Ethernet network. When sending frames to Ethernet, the driver encapsulates them into IEEE802.3 frames. If the driver settings allow the frames transmission longer than 1514 bytes, then encapsulation can also be performed in "Jumbo frame" in accordance with the document IETF "[Extended Ethernet Frame Size Support](http://www.ietf.org/proceedings/50/I-D/kaplan-isis-ext-eth-02.txt)". If specified maximal length of Ethernet frame is not enough to send a fully encapsulated original frame, this frame will be fragmented and then assembled at the remote side. Fragmentation algorithm uses the feature of Ethernet to avoid a delivery of frames out of turn. There is a possibility to create up to four isolated pseudo-radio networks within one Ethernet segment. Each prf interface can be assigned a number from 0 to 3. Frames sent to Ethernet with a specific channel number can be received on other nodes only by prf interfaces with the same channel number. To activate the pseudo-radio interface, the following command must be entered: ``` ifconfig prfN up ``` **Syntax:** ``` prf N parent IFNAME [hwmtu N] [channel N] prf N clear ``` ### Parameters

Parameter	Description
parent IFNAME	Sets parent interface through which encapsulated (fragmented) packets will be sent. Only Ethernet-type interfaces can be configured. "IFNAME" – interface identifier.
hwmtu N	The radio frames are often longer than the standard Ethernet frame size, PRF interfaces using Ethernet as the transmission medium must split the jumbo frames into multiple pieces and reassemble them at their destination. To calculate the maximum frame size that can be transmitted over Ethernet, the system performs a range of measurements by sending special test packets with different lengths and determines the maximum length (hwmtu) that was successfully received by the destination device. The "hwmtu" parameter is measured for each neighbor, to display this value use the "mint map detail" command. Thus, when MINT based switching is activated, the "hwmtu" parameter is calculated automatically by the system, the value set manually will be overwritten.
channel N	Sets channel number (0-3) with which the frames are sent and received by parent interface. By default channel number is 0.
clear	Removes prf with a specified number.

### Examples Create pseudo-radio interface 5. Set the "*eth0*" interface as parent, and assign channel number 3. ``` ifconfig prf5 up prf5 link administratively up prf 5 parent eth0 prf 5 channel 3 ``` By using the "*ifconfig*" command display an information about the created prf interface. ``` ifconfig -a prf5: flags=8003 mtu 1500 inet 0.0.0.0 netmask 0x0 ether 00:04:35:03:5e:4e Parent interface eth0 Hardware MTU 1514 --------------------------------------------------------------- Transmitted packets 0 Transmit fragmentation 0 packets in 0 fragments Load (pps) 0 Load (kbps) 0 --------------------------------------------------------------- Received packets 0 Receive fragmentation 0 packets in 0 fragments Load (pps) 0 Load (kbps) 0 --------------------------------------------------------------- Scattered fragments 0 Corrupted packets 0 Double encapsulated packets 0 Out of fragbufs 0 Out of mbufs 0 ``` * "*Scattered fragments*" *–* number of frames where one or several fragments were lost, the frame cannot be restored. * "*Corrupted packets*" *–* number of frames with the wrong length or structure. * "*Double encapsulated packets*" *–* number of frames with double encapsulation. * "*Out of fragbufs*" *–* the number of errors as a result of frame assembly buffer overflow due to too many fragments (neighbors) sources. * "*Out of mbufs*" *–* the number of errors as a result of system buffers overflow. # ⁣⁣lag command (Link Aggregation ) ### Description Link Aggregation is using multiple physical channels at once as one logical channel to increase the total link capacity and provide redundancy. This technology can be used, for example, to set up a high-capacity link between a device and a network switch, aggregating two available Ethernet interfaces. The total speed of such link will be a sum of the Ethernet interfaces speeds. Moreover, in case of one Ethernet connection failure its traffic will be passed to the other one without stooping the services. If later the fallen Ethernet connection will be reestablished the traffic will be sent over both Ethernet interfaces again. Astra Wireless LACP (Link Aggregation Control Protocol) realization fully complies with the IEEE 802.3ad standard for link aggregation. In addition, special proprietary LACP mode can be enabled that provides process efficiency enhancement over the standard mode.
The link aggregation functionality is configured on the device using a "*lagN*" logical interface. To activate the logical interface, the following command must be used: ``` ifconfig lagN up ``` Otherwise, the settings will be applied to the interface, but will not be executed. {% hint style="warning" %} **CAUTION** In case it is necessary to aggregate the interface through which the device management is perfomed, before activating the "*lagN*" interface, assign it an IP address by using the "*ifconfig*" command, to avoid loss of access. {% endhint %} **Syntax:** ``` lag N [command] [(port|-port) (IFNAME | IFNAME...)] where [command] is: status - show lag interface status migrate - enable session migrate -migrate - disable session migrate balance - enable session-oriented load balancing -balance - disable session-oriented load balancing mode - switch lag inteface mode. Modes: (stand|fast) clear - remove lag interface from configuration loadm - show realtime per-port load status ``` ### Parameters

Parameter	Description
IFNAME \| IFNAME...	An argument that defines the physical network interfaces (parent interfaces) that will be used for aggregation.
port\|-port	Enables link aggregation on the device. Creates logical "lagN" interface in the system and assigns parent physical interfaces to it. "-port" – removes one or more parent interfaces from configuration.
status	Displays the "aggregation id" value, the load on each of the parent interfaces and its status.
migrate\|-migrate	Enables/disables existing sessions migration between the available parent interfaces in case of the difference in the overload. By default, migration is allowed.
balance\|-balance	Enables/disables distribution of new-coming sessions between the available parent interfaces depending on their load. By default, balancing is enabled.
mode (stand\|fast)	Sets the LACP mode. In "standard" mode, LACP acts in accordance to the IEEE 802.3ad standard. In "fast" mode, AW proprietary extensions are used: the timeout value is reduced to 2 seconds, the current network interface load information is added to the packet reserve fields, allowing to speed up the LACP response significantly depending on network conditions, optimize the aggregation systems, and obtain more accurate statistics.
clear	Removes the "lagN" interface configuration.
loadm	Shows the load statistics in real time on each of the parent interfaces.

### Examples Creates logical "*lag1*" interface, using both device Ethernet interfaces. Assign an "*10.10.30.16/24*" IP address to created interface. Activate the logical interface. ``` lag 1 port eth0 eth1 ifconfig lag1 10.10.30.16/24 ifconfig lag1 up lag1 link administratively up ``` Remove "*eth1*" interface from configuration. ``` lag 1 -port eth1 ``` # ⁣⁣svi command ### Description SVI interface is a virtual L3 interface. Can be assigned to a switch group to provide the device management using this switch group. Each unit supports 5000 virtual "*sviN"* switch interfaces (in range 0...4999). An SVI interface has the following characteristics: * Each SVI interface can be assigned to a switch group. Once assigned the interface becomes an active member of that switch group and can exchange traffic with other group members. All traffic ingressed by this switch group (depending on the rules set) that is addressed to this SVI interface as well as all broadcast and multicast packets will be processed by the unit. * Each SVI interface can have one or several IP addresses configured. * An SVI interface can act as a parent interface for VLAN virtual interfaces. In this case the VLAN interface also becomes a member of the switch group assigned to the parent SVI interface - not recommended. * An SVI interface (or any other interface that uses it as a parent interface) can not be included into a switch group directly. * An SVI interface can be used for channel aggregation using lag interfaces.. * An SVI interface is considered active once it is up and assigned to a switch group. Following command allows to create the SVI interface and assign an IP address to it: ``` ifconfig sviN IP_ADDR up ``` {% hint style="warning" %} **NOTE** In order to set communication with other devices via protocols, that utilize the broadcast/multicast packets (such as OSPF, RIP, DHCP) use one of two options: * Use only the IP address assigned to the SVI interface, if the traffic enters a switch group that has an SVI interface. * It is possible to use the IP address assigned to the physical interface (radio or Ethernet), if this interface is not included in the switch group, or there is no SVI interface in the switch group. Otherwise, communication between the devices will not be established. {% endhint %} **Syntax:** ``` svi N group G [addpri|setpri N|-1] svi N clear ``` ### Parameters

Parameter	Description
N	Identifier of the SVI interface to configure.
group G	Assigns specified SVI interface to the switch group. "G" – switch group identifier.
[addpri\|setpri N\|-1]	Allows to provide priority management. "setpri N" – sets the packet priority with the value "N". "-1" – resets the priority. "addpri" – changes the priority only if new is higher than already available for the package. Thus, the "addpri" parameter allows only to increase the priority.
clear	Removes SVI interface settings.

### Examples Set the priority 5 for all the packets passing through the "*svi1*" interface. ``` svi 1 setpri 5 ``` Assign "*svi100*" interface to switch group # 100. ``` svi 100 group 100 ``` # ⁣⁣ltest (radio link test) ### Description This command is intended for radio link testing. It is recommended for using in the antenna alignment process when establishing a new radio link or for existing radio channel testing. For successful radio link establishment the following factors have to be considered: 1. It is recommended to start antenna alignment with searching on maximum Tx power. During link operating automatic MINT mechanisms will set the most appropriate bitrate if "*MINT – autobitrate*" mode will be enabled. 2. Current incoming signal level in "*amp/max*" columns must be between 12 and 40 dBm. If it is more than 40 it is recommended to lower Tx power. If maximal signal level is less than 12 it is recommended to lower bitrate or channel width (for example, from 20MHz to 10MHz on the both sides of the radio link). In some cases signal level that is less than 12 may be enough for radio link operation. In this case such parameters as number of retries, number of undelivered packets and number of undelivered acks have to be monitored. If the undelivered packets number and the undelivered acks number is zero, the retries number is small and all these parameters are constant in time then the radio link, most often, will be operating properly. 3. Number of retries value in "*rt%*" columns must be as close to zero as possible. 4. Number of undelivered packets value in "*up%*" columns must be zero; if this value is not zero then the radio link couldn’t be exploited. 5. Number of undelivered acks value in "*ua%*" columns must be zero; if this value is not zero then the radio link couldn’t be exploit. If this value is constantly not less then 50 then most probably "*distance*". parameter is set with a wrong value. If radio link distance is more than 20 km then "*long*" mode must be enabled. 6. All described parameters must be observed in the both ("*Local"* и "*Remote"*) sections of the "*ltest*" command output. **Syntax:** ``` usage: ltest IFNAME target [-r rate[,reply_rate]] [-s packet_size[,reply_size]] -- max 1728 [-b] -- send as broadcast [-p priority] -- set priority (0 to 16) [-align [L[,R]]] -- MIMO antenna alignment mode L,R - local/remote tx antenna (0/1 or V/H) [-evm] -- display Error Vector Magnitude [-tu [seconds]] -- unidirectional throughput test [-tb [seconds]] -- bidirectional throughput test [-load N[m|k] -- limit throughput to N: m - Mbps, k - Kbps [-mint] -- do throughput test through MINT ltest -key [PASSWORD] ltest (-disable|-enable) -- disable/enable ltest ``` ### Parameters

Parameter	Description
IFNAME	The radio interface on which testing will be performed.
target	A target device MAC address on the other side of a tested radio link.
-r rate[,reply_rate]	Sets bitrates for transmitting test packets from the local device and toward it. This parameter is optional. There are two situations when these parameters are not configured: Local device is tested with its neighboring node, i.e. we can view remote device and "tx/rx bitrate" values for it in a "mint map" command output. In this case "tx/rx bitrate" values from "mint map" command output are taken for "rate" and "reply rate" parameters. Local device doesn't consider remote device as a neighboring node. In this case "rate" and "reply rate" parameters will be equal to minimal possible local device "bitrate" value for current bandwidth (for example, 6 Mbps for 20 MHz bandwidth, 3 Mbps for 10 MHz, 5 Mbps for 5 MHz).
-s packet_size[,reply_size]	Sets test packet size from the local device and toward it. Test packet size by default is 1024 bytes. Maximal possible test packet size is 1728 bytes.
-b	Transmitting broadcast test packets.
-p priority	Sets the test packets priority in range 0...16.
-align [L[,R]]	Alignment mode for antenna with MIMO technology. The "L" parameter sets which antenna will be used to transmit test packets from the local device. The "R" parameter sets which antenna will be used to transmit test frames from the remote device on the other side of the link. If "L" and "R" parameters are not specified, the average signal level from all antenna outputs will be displayed. "L" and "R" parameters can have the following values: 0 – antenna with vertical polarization, 1 – antenna with horizontal polarization (or V and H).
-evm	Indicates the measured input signal quality (Error Vector Magnitude). It should be as high as possible. The recommended level is not less than 21.
-tu [seconds]	Unidirectional test: packets are transmitted only from the current side to the specified MAC address. Packet size by default - 1536 bytes (to change packet size use "-s" option). "seconds" – test duration in seconds (by default – 5 seconds). Maximum value is – 60 seconds.
-tb [seconds]	Bidirectional test: packets are transmitted in both directions. Packet size by default - 1536 bytes (to change packet size use "-s" option). "seconds" – test duration in seconds (by default – 5 seconds). Maximum value is – 60 seconds.
-load N[m\|k]	Limits maximal link testing bandwidth. "N" – bandwidth value: "m" – Mbps. "k" – Kbps.
-mint	Allows to perfom testing with such MINT functions enabled as ATPC (Automatic Transmit Power Control) and autobitrate. In this mode the statistic for errors and retries is not available. As the "target" parameter can be specified any MINT node’s MAC address including nodes that are not direct neighbors of the current node . NOTE Is available only with "-tu" or "-tb" parameter, the "-r" parameter is ignored.
-key [PASSWORD]	Sets password for testing. If a password is set on the testing device, only the device with the same password can be tested with it.
-disable\|-enable	Disables/enables ability to perform link test. By default is enabled.

### Examples Start test with default parameters and "00043513724f" neighbouring node MAC address. ``` ltest rf6.0 00043513724f Unicast test to 00043513724F via rf6.0 with priority 16 packet size 1024, reply size 1024, bitrate 104000, reply bitrate 104000 ----------+----------+----- local | remote | est. amp/max | amp/max | rtt dB | dB | ms ----------+----------+----- 16/16 | 16/16 | 17 17/17 | 16/16 | 15 16/17 | 16/16 | 15 17/17 | 16/16 | 15 ``` The table contains the following data for the local and remote end of the link: * "*amp/max*" *–* current and maximum incoming signal levels. * "*rtt*" *–* estimated round-trip time. Start test where "*rate"* parameter value is 24 Mbps. The "*reply rate"* parameter in this case will be set as default. ``` ltest rf6.0 000435135e4e –r 24000 ``` Start test using the "*-align*" parameter. The difference of this output from the standard one is that "*ant.amps"*, column is used instead of "*amp/max"*. The "*ant.amps"* column indicates signal levels from 0, 1 and 2 antennas divided by ":" correspondingly. ``` ltest rf6.0 00043513724f -align Unicast test to 00043513724F via rf6.0 with priority 0 packet size 64, reply size 64, align, tx antennas: local(all), remote(all) ----------+----------+----- local | remote | est. ant.amps | ant.amps | rtt dB | dB | ms ----------+----------+----- 39:35:00 | 37:33:00 | 15 39:35:00 | 36:34:00 | 15 38:35:00 | 36:34:00 | 15 39:35:00 | 36:34:00 | 15 ``` The table contains the following data for the local and remote end of the link: * "*ant.amps"* *–* signal to noise + interference levels (CINR) from 0, 1 and 2 antennas. * "*rtt*" *–* estimated round-trip time. Start bidirectional link bandwidth test of a local device with a remote device which have "*000435230A20*" MAC address. ``` ltest rf6.0 000435230a20 -tb Bidirectional throughput test to 000435230A20 via rf6.0 with priority 16 packet size 1512, bitrate 117000, reply bitrate 130000 Please wait..... ============================================================================= Direction | Kbit/s | Pkt/s | Retries | Errors | min/avg/max/stddev (usec) ============================================================================= Transmit | 60285 | 4983 | 0.00% | 0.00% | 4/200/7649/661 Receive | 60287 | 4984 | 0.01% | 0.00% | 1/200/13476/712 ----------------------------------------------------------------------------- Total | 120572 | 9967 | ----------------------------------------------------------------------------- ``` # macf command (addresses mapping) ### Description The command performs filtering by use static mapping of IP addresses to MAC addresses in an Ethernet network. It may be useful for service providers when they connect to their network a group of clients (such as individual users in an apartment block) via one common access unit. In this case, clients may be tempted to change their IP address to that of a neighbor, thus deceiving provider's accounting system. Using of "*macf*" command does not guarantee total protection, however, for the common user it is much more difficult to change the MAC address, than the IP address. **Syntax:** ``` macf IFNAME {MAC|"any"} {IP|"any"} "Comment" macf IFNAME del N macf IFNAME {[-]dhcp [-]strict | [-]reverse | [-]simple | [-]quiet} macf show | clear ``` ### Parameters

Parameter	Description
IFNAME	An interface identifier to the mapping table of which the filter is added.
{MAC\|"any"} {IP\|"any"} "Comment"	Adds the filter to the mapping table. "MAC" – device MAC address. "IP" – IP address assigned to the device. "any" – any MAC or IP address. "Comment" – symbolic comment for ease identification. NOTE Two filters with the same MAC addresses can not be added to the table.
del N	Removes the filter with "N" number from the mapping table. Filter number can be checked using the "show" parameter.
{[-]dhcp [-]strict \| [-]reverse \| [-]simple \| [-]quiet}	Allows to select packets filtering mode. "[-]" – cancels the parameter's action. The MAC filter algorithm consists of two steps: The filter searches for the MAC address in the table. If the MAC address is found, the IP address matching check is performed. "strict" – enables strict filtering mode. In this mode all packets received from units not described in the mapping table are discarded. By default "strict" mode is disabled. CAUTION If you are remotely configuring a router using telnet, make sure, when enabling the strict mode, that your own workstation is already added correctly in the mapping table. Otherwise you lose control over the router, and disabling the strict mode will be only possible through the router's diagnostics port. "reverse" – swaps the processing steps: first, an IP address is searched, then the MAC addresses are compared. "simple" – only the first step of the above algorithm is executed. If the address is found in the mapping table, then the packet is normally handled by the router. Otherwise, the packet will be discarded, regardless of whether the "strict" option is enabled or not (the second address is not checked). "dhcp" – in this mode macf filter is automatically supplemented with addresses issued by local DHCP server. These records are not stored in a permanent configuration and work until the given address is deleted by DHCP server. "quiet" – switches off logging to the system log. If the network packet is discarded by a filter, this fact is logged. To reduce the number of registrated packages, only the first attempt from the similar packets group is logged. If there is an intermediate router between the subscriber terminal and the local network, "reverse strict" or "reverse simple" can be used with all valid workstations IP addresses, and the intermediate router MAC address. In case, the several local networks are connected to the subscriber terminal, separated by intermediate routers, it is possible to use "simple" or "reverse strict" with intermediate routers MAC addresses. NOTE In many cases, this problem can be solved easier by using the "arp" command.
show	Displays the mapping table current state.
clear	Clears the mapping table.

### Examples Add two filters to the mapping table: to "*102030405060*" and "*203040506070*" MAC addresses are assigned "*1.1.1.1*" and "*2.2.2.2*" IP addresses. Add comments to label the IP addresses ownership. ``` macf 102030405060 1.1.1.1 Room123 macf 203040506070 2.2.2.2 Room125 ``` Display the mapping table current state. ``` macf show macf 1 0020af915099 192.78.64.99 Server macf 2 0020af9150a3 192.78.64.194 Room94 macf 3 0020af9150a4 192.78.64.134 Room57 macf 4 0020af9150a7 192.78.64.174 Admin ``` All local network workstations are connected directly to the subscriber terminal "*eth0"* interface. In this case, simplest filter version can be used, with the "*strict*" parameter. ``` macf eth0 strict ``` # ⁣⁣arp command (ARP protocol) ### Description The "*arp*" command is used to manipulate with ARP tables. ARP protocol serves for IP to MAC address mapping and vice versa. For example in Ethernet it allows to transform IP destination address into its 48-bit Ethernet address for packet forwarding over LAN. In common case ARP works automatically making address resolution as it is necessary. But there are some cases when ARP tables should be corrected manually and arp command solves this problem. **Syntax:** ``` arp view [IP] arp add IP {MAC | auto} [proxy] arp del {IP | all} [proxy] arp [-]freeze arp [-]proxyall [$ACL] ``` ### Parameters

Parameter	Description
view [IP]	Displays the ARP table. "IP" – IP address which records must be shown.
add IP {MAC \| auto} [proxy]	Adds record into the ARP table. "IP" – IP address to add a compliance. "MAC" – MAC address which is mapped to IP address. "proxy" – if specified then the system will announce this information as response to requests from other stations, acting as proxy ARP server, even if this IP address is not system own address. "auto" – if specified, network interface MAC address from same subnetwork as the IP address will be set.
del IP\|all [proxy]	Removes records from the ARP table. "IP" – IP address which information need to be removed. "all" – all records in the ARP table. "proxy" – IP address for which system acting as proxy ARP server.
[-]freeze	Enables to freeze ARP table. No more automatically updates allowed. The command fixes only manual records and does not affect on the radio interface with active protocol MINT. Be careful when entering this command via telnet.
[-]proxyall [$ACL]	Enables/disables "proxyall" mode. In this mode the system will reply on all ARP requests, if respective target IP address resides in the routing tables and reachable via interface other than source MAC address. I.e. if there is a route to the target IP address then the device can be considered as a gateway. "$ACL" – list of addresses/networks, which limits this command.

### Examples Add the "*00:11:22:33:44:55*" MAC address which is mapped to "*10.10.10.10*" IP address to the table. ``` arp add 10.10.10.10 00:11:22:33:44:55 ``` Make system act as proxy ARP server for the "*192.168.103.35*" IP address. ``` arp add 192.168.103.35 auto proxy using interface svi1 for proxy with address 020435035E4E ``` --- [Next Page](https://wiki.astrawireless.net/astra-wireless-documentation/llms-full.txt/1)