# The wireless link cannot be established⁣⁣⁣⁣⁣

### Checking the radio settings <a href="#thewirelesslinkcannotbeestablished-checkingtheradiosettings" id="thewirelesslinkcannotbeestablished-checkingtheradiosettings"></a>

#### **Pre-configuration in the lab** <a href="#thewirelesslinkcannotbeestablished-pre-configurationinthelab" id="thewirelesslinkcannotbeestablished-pre-configurationinthelab"></a>

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.&#x20;

{% 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** <a href="#thewirelesslinkcannotbeestablished-checkingtheradioparameters" id="thewirelesslinkcannotbeestablished-checkingtheradioparameters"></a>

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.

<figure><img src="https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2FOWOYMC8W0C24ZHu4uqGN%2Fimage.png?alt=media&#x26;token=84200fcd-227b-4a0f-af1f-d0eb8e0bc5a6" alt=""><figcaption></figcaption></figure>

**Command line interface**

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

<figure><img src="https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2FuBWja1fk9bUCTYmhRLEj%2Fimage.png?alt=media&#x26;token=f5aa8889-e48c-4ecd-bc84-4632238667e6" alt=""><figcaption></figcaption></figure>

#### **Checking the status of the radio interface** <a href="#thewirelesslinkcannotbeestablished-checkingthestatusoftheradiointerface" id="thewirelesslinkcannotbeestablished-checkingthestatusoftheradiointerface"></a>

Make sure that the radio interfaces of both devices are in the "Up" state.

<figure><img src="https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2FLrnh6cNh2DvYDKCXwgkJ%2Fimage.png?alt=media&#x26;token=05de6862-f412-4c7d-9dd4-63d0a6cc490d" alt=""><figcaption></figcaption></figure>

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

<figure><img src="https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2FyefseCqDtqRGKMxlBxiZ%2Fimage.png?alt=media&#x26;token=72252ee3-3b74-42ec-ab06-9e6066e8f53f" alt=""><figcaption></figcaption></figure>

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** <a href="#thewirelesslinkcannotbeestablished-checkingthefirmwareversion" id="thewirelesslinkcannotbeestablished-checkingthefirmwareversion"></a>

**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.

<figure><img src="https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2F1y3PMsAmB2kPashohE9E%2Fimage.png?alt=media&#x26;token=ebcaf018-4e69-4a33-9a12-cd5edcf673a7" alt=""><figcaption></figcaption></figure>

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 <a href="#thewirelesslinkcannotbeestablished-checkingtheinstallationrequirements" id="thewirelesslinkcannotbeestablished-checkingtheinstallationrequirements"></a>

#### Checking the network infrastructure <a href="#thewirelesslinkcannotbeestablished-checkingthenetworkinfrastructure" id="thewirelesslinkcannotbeestablished-checkingthenetworkinfrastructure"></a>

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 <a href="#thewirelesslinkcannotbeestablished-checkingtheinstallationrequirements.1" id="thewirelesslinkcannotbeestablished-checkingtheinstallationrequirements.1"></a>

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.

<figure><img src="https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2FJTDpIjEDkAGCxDbIovzG%2Fimage.png?alt=media&#x26;token=4cfd94fb-2d4b-45b8-89f2-a54d89e15cb3" alt=""><figcaption></figcaption></figure>

#### **Interference detection** <a href="#thewirelesslinkcannotbeestablished-interferencedetection" id="thewirelesslinkcannotbeestablished-interferencedetection"></a>

**Web interface**

Using the built-in [Spectrum Analyzer](https://wiki.astrawireless.net/astra-wireless-documentation/technical-documentation/astra-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 %}

<figure><img src="https://2734851754-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnG7V17JtC1mMJOmveKc6%2Fuploads%2FNScigGqTilbeGUIfXWos%2Fimage.png?alt=media&#x26;token=c135c067-7228-4d46-81d3-9cfab0fed67a" alt=""><figcaption></figcaption></figure>

**Command line interface**

The radio environment analysis is also available via the command line using the "*muffer sensor*" command.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.astrawireless.net/astra-wireless-documentation/technical-documentation/astra-evolution-technical-user-manual/troubleshooting/the-wireless-link-cannot-be-established.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
