Troubleshooting Common Problems
Using Script
The default UHD installation includes a diagnostic program,
called, crimson_diagnostic.sh, that checks your host system for
various common misconfigurations, and reports them. This
functionality can aid troubleshooting and initial set up. Please
note that this program uses the default IP addresses associated
with Crimson TNG; in the event you have changed the device IP
address, not all the checks will be completed. To run the
diagnostic, as root, type;
[host_pc]$ sudo crimson_diagnostics.shIf you continue to experience problems, please contact us for support.
Common Problems
Unable to connect to Crimson TNG Management Web UI
Table 1: Unable to connect to Crimson TNG Management Web UI
| Possible Cause | Solution |
|---|---|
| No Micro SD card | 1) Turn off Crimson TNG unit |
| 2) Insert Micro SD card | |
| 3) Turn on unit, wait until boots up | |
4) Type 192.168.10.2 into web browser |
|
| Micro SD card is not inserted properly | 1) Turn off Crimson TNG |
| 2) Remove Micro SD card | |
| 3) Re-insert card ensureing it has been properly connected | |
| 4) Turn on unit, wait until it boots up | |
5) Type 192.168.10.2 into web browser |
|
| Ethernet cable is not connected | Ensure Ethernet cable is properly seated in both host computer and Crimson TNG MGMT port |
| Management IP address is not configured properly | Confirm you have enabled the network interface: ip addr show output should say: <BROADCAST, MULTICAST, UP, LOWER_UP> |
Confirm you have configured the correct network interface. If the Crimson TNG MGMT port does not respond to ping, try configuring a different network interface.
Unable to send/receive data
Table 2: Unable to send/receive data
| Possible Cause | Solution |
|---|---|
| SFP+ cables are swapped | Try swapping SFP+ cables, or reconfiguring SFP+ IP addresses with swapped device addresses |
| SFP+ cables are not connected | Ensure SFP+ cables are properly seated in both host computer and CrimsonTNG SFP+ ports |
| SFP+ IP(s) or PHYS are not configured properly | ip addr show output should say: <BROADCAST, MULTICAST, UP, LOWER_UP> |
Confirm you have configured the correct network interfaces, and correctly set the MTU size to 9000. If the Crimson TNG SFP+ port(s) do not respond to ping, try configuring a different network interface.
Other Common Problems
Table 3: Other Common Problems
| Problem | Possible Cause | Solution |
|---|---|---|
| gnuradio error messages | Version mismatch between gnuradio and Per Vices libUHD | 1) Uninstall all versions of GNURadio and Ettus libUHD |
| 2) Reboot computer | ||
| 3) Download and install Per Vices libUHD | ||
| 4) Compile and install GNURadio from source | ||
| MTU size not set | Set SFP+ IP addresses MTU size to 9000 | |
uhd_find_devices doesn’t working |
Network Connection or Firewall errors | Confirm your network connection is properly configured, and that you do not have any security or firewall blocking broadcast packets. |