User Tools
wiki:troubleshooting
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
wiki:troubleshooting [2017/09/13 17:03] bdu created |
wiki:troubleshooting [2017/12/11 12:16] (current) tda |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Troubleshooting ====== | ====== Troubleshooting ====== | ||
| - | ===== Architecture ===== | + | ===== System Overview ===== |
| The RAN as a whole is structured as follows: | The RAN as a whole is structured as follows: | ||
| * In the gateway: | * In the gateway: | ||
| - | * The packet forwarder receives LoRa frames and forwards them to the server at ''lns'' which is usually ''172.18.0.1'' on UDP port 1700 | + | * The packet forwarder receives LoRa frames and forwards them to the lns server which address is usually ''172.18.0.1'' using UDP port 1700 |
| * There is a ''bscc'' daemon that will be interfaced with the RAN BSC component | * There is a ''bscc'' daemon that will be interfaced with the RAN BSC component | ||
| * There is a ''snmp'' daemon that will be interfaced with the RAN | * There is a ''snmp'' daemon that will be interfaced with the RAN | ||
| Line 20: | Line 20: | ||
| - Check basic network | - Check basic network | ||
| - | * if Ethernet, ensure that the link is up, a valid IP is set (either manually or through DHCP) | + | * if Ethernet, ensure that the link is up, a valid IP is set on eth0 interface (either manually or through DHCP) |
| - | * if WiFi, ensure that the SSID is properly connected and that a valid IP is configured (either manually or through DHCP) | + | * if WiFi, ensure that the SSID is properly connected and that a valid IP is configured on wlan0 interface (either manually or through DHCP) |
| - | * if cellular, ensure that the APN is properly configured, that the cell signal is good and that there is an IP | + | * if cellular, ensure that the APN is properly configured, that the cell signal is good and that there is an IP defined on ppp0 interface |
| - | * either way, it is usually checked through the ''ifconfig'' command, and possibly by trying to ping a machine on the Internet (e.g. 8.8.8.8) | + | * Anyway, issue a ''ifconfig'' command to check all interfaces status, and try to ping a machine on the Internet (e.g. 8.8.8.8) |
| - | - Check installed software | + | - Check installed software and version numbers |
| - | * On iBTS or iFemtoCell, run the command: ''ipkg list-installed'': this will list the installed packages | + | * On iBTS or iFemtoCell, run the command: ''opkg list-installed'': this will list the installed packages |
| * On Wirnet Station, run the command: ''get_version -u -v'' and check the update log | * On Wirnet Station, run the command: ''get_version -u -v'' and check the update log | ||
| - | * Either way, please check that the ''bscc'', ''snmp'', ''openvpn'' and the packet forwarder packages are installed | + | * Anyway, please check that the ''bscc'', ''snmp'', ''openvpn'' and the ''packet forwarder'' packages are correctly installed with the expected version number |
| - | - Check that the software is running | + | - Check that all expected process are running |
| * On iBTS or iFemtoCell, run the command: ''monit status'' | * On iBTS or iFemtoCell, run the command: ''monit status'' | ||
| * On all systems, run the command: ''ps ww'' | * On all systems, run the command: ''ps ww'' | ||
| - | * Either way, please ensure that the ''bscc'', ''snmp'', ''openvpn'' and the packet forwarder processes are running | + | * Anyway, please ensure that the ''bscc'', ''snmp'', ''openvpn'' and the ''packet forwarder'' processes are running |
| - Check that the connection to the RAN is working | - Check that the connection to the RAN is working | ||
| * Check that you have VPN interface in ''ifconfig'' | * Check that you have VPN interface in ''ifconfig'' | ||
| + | * Check the content of the Trustzone (except for Wirnet Station) ''pnr_uploader -s -b 2'', ''pnr_uploader -s -b 10'' | ||
| * Check that you can ping ''172.18.0.1'' and ''10.8.0.1'' | * Check that you can ping ''172.18.0.1'' and ''10.8.0.1'' | ||
| * Check that you can ping ''lns'' and ''snmp'' | * Check that you can ping ''lns'' and ''snmp'' | ||
| + | * In the dashboard, add the station to the customer's fleet and verify that its status is "connected" | ||
| + | - Check that the packet forwarder is working properly | ||
| + | * Check the configuration of the packet forwarder in the json config file ("lns" should be defined as the server and port 1700 should be used) | ||
| + | * Check in the dashboard interface that the station has received some messages (be sure that at least one end-device is located in the neighborhood of the gateway) | ||
| + | |||
| ===== Logs to check ===== | ===== Logs to check ===== | ||
| * Check main system logs at ''/var/log/messages'' | * Check main system logs at ''/var/log/messages'' | ||
| - | * Check packet forwarder logs at ''/user/spf2/var/log/'' for iBTS, ''/user/spf/var/log'' for iFemtoCell and ''/mnt/fsuser-1/spf'' for Wirnet Station | + | * Check packet forwarder logs at ''/user/spf2/var/log/'' for iBTS, ''/user/spf/var/log'' for iFemtoCell and ''/mnt/fsuser-1/spf/var/log'' for Wirnet Station |
| * Check the kernel boot log with the ''dmesg'' command | * Check the kernel boot log with the ''dmesg'' command | ||
| Line 48: | Line 54: | ||
| * [[http://otrs.kerlinkm2mtechnologies.com/customer.pl]] and open a ticket | * [[http://otrs.kerlinkm2mtechnologies.com/customer.pl]] and open a ticket | ||
| - | * support@kerlink.fr if you don't have an OTRS account yet | + | * [[mailto:support@kerlink.fr|support@kerlink.fr]] if you don't have an OTRS account yet |
| - | Either way, please provide information about your product and your issue: | + | Anyway, please provide information about your product and your issue: |
| * serial number | * serial number | ||
| * product version | * product version | ||
wiki/troubleshooting.1505315003.txt.gz · Last modified: 2017/09/13 17:03 by bdu
Page Tools
