User Tools

Site Tools


wiki:wiki3:troubleshooting

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
wiki:wiki3:troubleshooting [2019/03/18 14:59]
tda
wiki:wiki3:troubleshooting [2019/10/14 16:58] (current)
tda
Line 1: Line 1:
-====== Troubleshooting WMC connexion issue ======+====== Troubleshooting WMC connection issues ​======
  
 ===== Process Flow ===== ===== Process Flow =====
Line 5: Line 5:
 To analyze your potential issues, it is best to go from bottom to top and check every layer: To analyze your potential issues, it is best to go from bottom to top and check every layer:
  
-  - Check basic network +  - Check basic network: 
-    * If Ethernet, ensure that the link is up, a valid IP is set on eth0 interface (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 on wlan0 interface (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 defined on ppp0 interface +    * 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. 
-    * Anyway, issue ''​ifconfig''​ command to check all interfaces status, and try to ping a machine on the Internet (e.g. 8.8.8.8) +    * Anyway, issue an ''​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 and version numbers +  - Check installed software and version numbers: 
-    * On iBTS or iFemtoCell, run the command: ''​opkg list-installed'':​ this will list the installed packages +    * On Wirnet ​iBTS or Wirnet ​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. 
-    * Check the right OpenVPN package is installed +    * Check the right OpenVPN package is installed. 
-    * Anyway, please check that the ''​bscc'',​ ''​snmp'',​ ''​openvpn''​ and the ''​packet forwarder''​ packages are correctly installed with the expected version number +    * Anyway, please check that the ''​bscc'',​ ''​snmp'',​ ''​openvpn''​ and the ''​packet forwarder''​ packages are correctly installed with the expected version number. 
-  - Check that all expected ​process ​are running +  - Check that all expected ​processes ​are running: 
-    * On iBTS or iFemtoCell, run the command: ''​monit status''​ +    * On Wirnet ​iBTS or Wirnet ​iFemtoCell, run the command: ''​monit status''​. 
-    * On all systems, run the command: ''​ps ww''​ +    * On all systems, run the command: ''​ps ww''​. 
-    * Anyway, 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 your system indicates a correct date +  - Check that the gateway ​system indicates a correct date: 
-    * Run the command ''​date''​. If the date is incorrect, check your GPS/NTP configuration in /​etc/​ntp.conf  +    * Run the command ''​date''​. If the date is incorrect, check the GPS/NTP configuration in ''​/​etc/​ntp.conf''​. ​ 
-  - Check that the connection to the WMC is working +  - Check that the connection to the WMC is working: 
-    * Check that VPN interface is set in ''​ifconfig''​ +    * Check that VPN interface ​(tun) is up in ''​ifconfig''​. 
-    * Check the content of the Trustzone (except for Wirnet Station) ''​pnr_uploader -s -b 2'', ​ ''​pnr_uploader -s -b 10''​ +    * Check the content of the Trustzone (except for Wirnet Station) ''​pnr_uploader -s -b 2'', ​ ''​pnr_uploader -s -b 10''​. 
-    * Check that ''​172.18.0.1''​ and ''​10.8.0.1''​ can be ping +    * Check that ''​172.17.0.1''​ and ''​10.8.0.1''​ can be ping. 
-    * Check that you can ping ''​lns''​ and ''​snmp''​ +    * Check that ''​lns''​ and ''​snmp'' ​can be ping. 
-    * In the dashboard, add the station ​to the customer'​s fleet and verify that its status is "​connected"​ +    * In the dashboard, add the gateway ​to the customer'​s fleet and verify that its status is "​connected"​. 
-        * If the status remains "​disconnected"​ and if your gateway is a Wirnet iBTS then issue the command: ''​ iptables -L OUTPUT -n |grep "udp spt:​10161"''​. If this command returns an empty string then issue the command ''/​user/​snmp/​snmpd.init restart''​ and wait few seconds. If the problem remains then reboot the gateway.+        * If the status remains "​disconnected"​ and if your gateway is a Wirnet iBTS then issue the command: ''​iptables -L OUTPUT -n |grep "udp spt:​10161"''​. If this command returns an empty string then issue the command ''/​user/​snmp/​snmpd.init restart''​ and wait few seconds. If the problem remains then reboot the gateway.
         * If the status remains "​disconnected"​ and if your gateway is not a Wirnet iBTS then simply reboot the gateway.         * If the status remains "​disconnected"​ and if your gateway is not a Wirnet iBTS then simply reboot the gateway.
-  - Check that the packet forwarder is working properly +  - 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 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)+    * Check in the dashboard interface that the gateway ​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 : +  * Check main logs: 
-      * iBTS:''/​user/​spf2/​var/​log/''​ +    **Wirnet ​iBTS:**  
-      * iFemtoCell: ''/​user/​spf/​var/​log''​, +      * ''/​user/​spf2/​var/​log/​spf2.log*'' ​//packet forwarder logs.//\\ 
-      * Wirnet Station: ''/​mnt/​fsuser-1/​spf/​var/​log''​  +      * ''/​user/​bscc/​traces/​bscc-*''​\\ 
-  * Check the kernel ​boot log with the ''​dmesg''​ command+      * ''/​user/​snmp/​traces/​snmp.log*''​ 
 +    * **Wirnet ​iFemtoCell:**  
 +      * ''/​user/​spf/​var/​log'' ​//packet forwarder logs.//\\ 
 +      ​* ''/​user/​bscc/​traces/​bscc-*''​\\ 
 +      * ''/​user/​snmp/​traces/​snmp.log*'' ​  
 +    * **Wirnet Station:**  
 +      * ''/​mnt/​fsuser-1/​spf/​var/​log'' ​//packet forwarder logs.//\\ 
 +      * ''/​mnt/​fsuser-1/​bscc/​traces/​bscc-*''​\\ 
 +      * ''/​mnt/​fsuser-1/​snmp/​traces/​snmp.log*''​\\ 
 +      * ''/​mnt/​fsuser-1/​trace_agent/​traceagent-*''​ //in case of cellular connection.//​\\ 
 +  ​ 
 +  * Check the Kernel ​boot log with the ''​dmesg''​ command.
  
 ===== Ask for support ===== ===== Ask for support =====
Line 47: Line 58:
 If you couldn'​t find why your station is not visible on the WMC dashboard or why you can't receive/​send LoRa frames, please contact the support: If you couldn'​t find why your station is not visible on the WMC dashboard or why you can't receive/​send LoRa frames, please contact the support:
  
-  * [[http://​otrs.kerlinkm2mtechnologies.com/​customer.pl]] and open a ticket +  * [[http://​otrs.kerlinkm2mtechnologies.com/​customer.pl]] and open a ticket. 
-  * [[mailto:​support@kerlink.fr|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.
  
 Anyway, please provide information about your product and your issue: Anyway, please provide information about your product and your issue:
wiki/wiki3/troubleshooting.1552917563.txt.gz · Last modified: 2019/03/18 14:59 by tda