RV50 / Carrier Locked / Not pingable from WAN

Hi,
My fleet experiences Modems Hang-ups in different locations occurring on the same day. Is there any way to ID the cause or keep this from Re-occurring? The Logs show they have lost the DTLS session, this has been confirmed a few times now. Modems are signal locked upon arrival, Signal is good. They go down on the Same day, slightly different times, and need to be physically rebooted to sync back up to bs.airvantage.net:5684? Any Ideas of any settings or Logging I can turn on to try find root cause and stop our truck rolls…

Dec 12 05:43:28 notice ALEOS_LINKMGMT_linkmon: Current: RSSI=-72, RSRQ=-11, RSRP=-102, SINR=16.8
Dec 12 05:58:28 notice ALEOS_LINKMGMT_linkmon: Current: RSSI=-72, RSRQ=-11, RSRP=-102, SINR=15.8
Dec 12 06:13:28 notice ALEOS_LINKMGMT_linkmon: Current: RSSI=-72, RSRQ=-11, RSRP=-102, SINR=14.8
Dec 12 06:28:28 notice ALEOS_LINKMGMT_linkmon: Current: RSSI=-72, RSRQ=-11, RSRP=-102, SINR=15.8
Dec 12 06:32:36 notice ALEOS_CELL_RadioTask: Current time: Sat Dec 12 06:32:35 2020 Radio Network time used to set both system time and HW clock system time to: Sat Dec 12 06:32:36 2020
Dec 12 06:39:38 err ALEOS_ALMS_LWM2M: no matching DTLS session for given transport session.
Dec 12 06:40:26 err ALEOS_ALMS_LWM2M: ACK timeout for mid 13518
Dec 12 06:43:29 notice ALEOS_LINKMGMT_linkmon: Current: RSSI=-72, RSRQ=-11, RSRP=-102, SINR=17
Dec 12 06:44:34 err ALEOS_ALMS_LWM2M: dtls_close: can not find DTLS session to close
Dec 12 06:45:04 warning ALEOS_ALMS_LWM2M: Failed registration, retrying in β€˜10’ seconds, β€˜4’ left
Dec 12 06:45:14 err ALEOS_ALMS_LWM2M: no matching DTLS session for given transport session.
Dec 12 06:45:14 err ALEOS_ALMS_LWM2M: lwm2m_send_registration: failed to send registration message
Dec 12 06:45:14 warning ALEOS_ALMS_LWM2M: Failed registration, retrying in β€˜20’ seconds, β€˜3’ left
Dec 12 06:45:14 warning ALEOS_ALMS_LWM2M: Failed registration, retrying in β€˜40’ seconds, β€˜2’ left
Dec 12 06:45:19 err ALEOS_ALMS_LWM2M: no matching DTLS session for given transport session.
Dec 12 06:45:34 err ALEOS_ALMS_LWM2M: no matching DTLS session for given transport session.
Dec 12 06:45:34 err ALEOS_ALMS_LWM2M: lwm2m_send_registration: failed to send registration message
Dec 12 06:45:34 warning ALEOS_ALMS_LWM2M: Failed registration, retrying in β€˜80’ seconds, β€˜1’ left
Dec 12 06:45:34 warning ALEOS_ALMS_LWM2M: Failed registration, retrying in β€˜160’ seconds, β€˜0’ left
Dec 12 06:45:54 err ALEOS_ALMS_LWM2M: no matching DTLS session for given transport session.
Dec 12 06:45:54 err ALEOS_ALMS_LWM2M: lwm2m_send_registration: failed to send registration message
Dec 12 06:45:54 warning ALEOS_ALMS_LWM2M: Failed registration with connectivity OK, deleting persisted server
Dec 12 06:45:54 warning ALEOS_ALMS_LWM2M: Failed registration, retrying in β€˜10’ seconds, β€˜4’ left
Dec 12 06:45:55 err ALEOS_ALMS_LWM2M: dtls_close: can not find DTLS session to close
Dec 12 06:45:58 notice ALEOS_ALMS_LWM2M: Initializing…
Dec 12 06:46:31 notice ALEOS_ALMS_LWM2M: connecting to bs.airvantage.net:5684
Dec 12 06:46:31 err ALEOS_ALMS_LWM2M: resolve failure
Dec 12 06:46:31 err ALEOS_ALMS_LWM2M: failed to connect to bs.airvantage.net:5684
Dec 12 06:46:31 err ALEOS_ALMS_LWM2M: failed to connect to bootstrap server.
Dec 12 06:46:31 warning ALEOS_ALMS_LWM2M: Failed bootstrap, retrying in β€˜10’ seconds, β€˜4’ left
Dec 12 06:46:31 warning ALEOS_ALMS_LWM2M: Failed bootstrap, retrying in β€˜20’ seconds, β€˜3’ left

After Reboot

Dec 14 18:31:20 notice ALEOS_ALMS_LWM2M: connecting to lw.na.airvantage.net:5686
Dec 14 18:31:20 notice ALEOS_ALMS_LWM2M: connected
Dec 14 18:31:22 warning ALEOS_ALMS_LWM2M: discard older handshake message with seq: 0
Dec 14 18:31:22 warning ALEOS_ALMS_LWM2M: discard older handshake message with seq: 0
Dec 14 18:41:21 notice ALEOS_LINKMGMT_linkmon: Current: RSSI=-68, RSRQ=-11, RSRP=-98, SINR=14.6

Hi @TechZero

Which ALEOS firmware are you using? If you are not in the latest firmware, please download the latest one and retry.
AirLink RV50/RV50X Firmware Packages

Please provide your configuration template and system log on RV50 for analysis.
You can delete sensitive information such as IP, IMEI number, Serial number.

Steps to capture system log on RV50:

  1. Go Admin -> Log Configure Logging, set Verbosity of these sub system to Debug: Cellular, LAN, Services, Network Services, ALMS and set the rest of subsystem to Info. β€œDisplay in Log” set to Yes.
  2. Reboot boot the gateway.
  3. Perform your test again.
  4. Go Admin -> View log -> Download Logs
1 Like

Thank you, I see a new release as of January, Both the RV50 and RV50x Download as the same file and size… Can you confirm this is correct for RV50x as well?

Hi @TechZero ,

Yes, about the latest ALEOS 4.14.0.014, RV50 and RV50X use the same file, but they use different Radio Module Firmware. Please be careful about downloading and applying FW to your devices.

I attach the link again for your reference: https://source.sierrawireless.com/resources/airlink/software_downloads/rv50/rv50-firmware-list/#sthash.HHxlKkey.dpbs

Thanks,

This issue was resolved by enabling the Cellular Monitor in all the RV50 Devices.