Resolve Issues with Radio Setup Validation

Issue

Once you have connected and set up your radio using the Radio Setup wizard, the Validate step runs several tests to verify the correct configuration of the host and radio. If any of these tests fail, the wizard prompts you to take additional actions.

Possible Solutions

Host IP Address Configuration Test

If the host IP address configuration test fails, check that the host IP address that you selected in the Select Link Configuration step in the wizard matches the host network configuration of the host operating system (OS).

Host-Radio Connection Test

Radio Cannot be Detected. If the host-radio connection test fails because the radio cannot be detected:

Check that you are using the correct cable and that the physical connection between the radio and host is through the correct ports. For details, see Connect Radio to Host Computer.
Check that the radio is on or try turning the radio off and on again. Try turning on your radio and allowing it to boot before you boot your host computer.
Disable your VPN. If this action resolves the issue, contact your VPN administrator to check that local (LAN) access is enabled while the VPN is connected.
Disable the OS firewall on your NIC. The firewall settings may be managed by your system administrator.
Go back to the Set Up SD Card step in the wizard and set up the SD card again with a compatible image.
If your device is a USRP™ E320 radio and you have just written the microSD card, ensure you are setting up your radio using a 1 Gigabit Ethernet connection. To set up your radio for a 10 Gigabit Ethernet connection, see Set Up USRP E320 Radio for 10 Gigabit Ethernet.

Resolve MTU Mismatch. If the host-radio connection test fails due to an maximum transmission unit (MTU) mismatch, update the host MTU.

For a 1 Gigabit connection, set the MTU to 1500 on Linux^® or 1498 on Windows^®.

Note
In UHD™ version 4.6.0.0, the radio firmware adds two bytes to the MTU value that you set using netsh on Windows (since R2025a). The maximum payload of a standard Ethernet frame is 1500 bytes, so you must set the MTU value to 1498.
For a 10 Gigabit connection, set the MTU to 9000.

For details about how to configure your network adapter settings on Windows, see Configure Network Settings on Windows Host.

Radio Filesystem Image Version Test

If the version test fails for a USRP E320 radio or a USRP N3xx radio with a UHD version earlier than 4.0, return to the Set Up SD Card step in the wizard and rewrite the SD card.

If the version test fails for a USRP N3xx or X410 radio, and the radio has UHD version 4.0 or later, follow these steps to update the radio filesystem using the wizard.

Disable any OS firewall for the host network interface that is connected to the radio.
Click Update Image and follow the steps to download, validate, and update the image.

Note

Closing MATLAB^® during a radio filesystem update can leave an incomplete file on the radio filesystem. This can cause the process to fail the next time you try to update the image. The log file will indicate the following error.

There is not enough space on your device. Mounting point: <>; 
space required: <> kB; space available: <> kB. 
Free up space and try again.

To resolve this, reboot the device and try again.

If the version validation of the NI™ USRP N3xx, or X410 radio filesystem image fails after you follow the steps to update the filesystem using the wizard, you can update the filesystem manually. If your host computer has a Windows OS, OpenSSH Client is required.

Follow the steps in the wizard to download, extract, and validate the correct filesystem image file.
Update your radio filesystem by using a Windows PowerShell or Linux terminal. By default, the radio IP address is 192.168.10.2. If you configured your radio with a different IP address in the network configuration step of the wizard, specify that IP address instead of 192.168.10.2 in these commands.
1. Copy the extracted .mender filesystem image file onto the radio. If necessary, provide the full path to the image file.
```
$ scp -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no <mender_filesystem_image> root@192.168.10.2:/tmp/wt-uhd-image.mender
```
2. Log in to the radio.
```
$ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.10.2
```
3. Install the new filesystem image. Then restart your radio. These steps take several minutes.
```
# mender install /tmp/wt-uhd-image.mender
# reboot
```
4. Log in to the radio.
```
$ ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no root@192.168.10.2
```
5. Make the filesystem changes permanent on the radio.
```
# mender commit
```
For more information on updating the radio filesystem, see Installing the Mender Artifact on the hardware vendor website.
Return to the Radio Setup wizard and follow the instructions to revalidate your radio setup.

Host OS Optimization Test

The Radio Setup wizard validates the optimization settings on your OS. Any validation failure that occurs during this test does not stop you from progressing to the next wizard step. However, if the host OS optimization test fails, you can manually update your OS.

On a Windows OS, follow these steps:
1. Locate the FastSendDatagramThreshold.reg file at UHD_INSTALL/win64 path by running these commands in MATLAB.
  >> uhd_install_location = getUHDInstallLocation >> winopen(fullfile(uhd_install_location,'win64'))
2. Run the FastSendDatagramThreshold.reg file.
3. Restart your computer.

On a Linux OS, run these commands in a terminal:

`echo "net.core.rmem_max=33554432" | sudo tee -a /etc/sysctl.conf`
`echo "net.core.wmem_max=33554432" | sudo tee -a /etc/sysctl.conf`
`sudo sysctl -p`

Radio Transmit and Receive Test

During the final validation test, the Radio Setup wizard validates the data transfer by transmitting and receiving a test waveform. Any validation failure that occurs during this step does not stop you from progressing. However, you can take the following steps:

Fix any OS optimization test failure that occurs in the previous validation test. For details, see Host OS Optimization Test.
Check that you have attached an antenna or a loopback cable to the correct port. For details, see Connect Radio to Host Computer.
Implement the possible solutions in Resolve Issues with Data Transfer.

Non-Default Synchronization Options. If you have configured non-default synchronization options in the Configure Radio step in the wizard, the radio transmit and receive test uses the selected clock and time source. To determine if the test has failed because the radio is unable to lock to the selected reference clock, follow these steps:

Return to the Configure Radio step and set the clock and time sources to internal.
Continue to the Validate step and validate your radio setup configuration using the internal clock and time sources.

If the radio transmit and receive test passes, then the issue is related to clock and/or time source.

If your radio is a USRP X310 and the radio transmit and receive test fails when non-default synchronization options are configured, the radio will repeat the test using the internal clock and time source. The test returns this warning:

Transmit and receive test passed without locked clock reference. 
Check external clock and PPS connections, then try again.

To resolve issues with using an external clock or time source, check the connections and verify that the correct signals are being provided.

To resolve issues with using the onboard GPS disciplined oscillator as the clock or time source, verify that the module is connected and working correctly. You can use the hasGPSDO function to check that your radio has a GPSDO onboard and the radio object is able to communicate with the module.