B314 Sudden Loss of Connectivity (Logs Included)

One of my 2G/3G Boron's lost connectivity a few days ago and won't reconnect.

I've tried updating to the latest OS, re-flashing firmware, device doctor, going through device setup again, etc.

What is interesting is that there are 20+ devices running the exact same firmware and hardware setup that have not shown this issue. The device was operating as expected with no observable hardware issues (battery was in good shape, antenna, etc)

I am suspect that the network has kicked this device off for some reason. The device connects to cell every hour and goes to sleep. Sim is active on the console.

Looking through the logs, I see a
PPP error event data=5
and
PPP error event data=6

Here is a full set of logs, they continue to repeat this cycle ad inifitum.

0000017152 [mux] INFO: Openning mux channel 2
0000017823 [net.pppncp] TRACE: NCP event 100
0000017825 [net.pppncp] TRACE: New auth info
0000017826 [net.pppncp] TRACE: NCP event 2
0000017827 [net.pppncp] TRACE: State changed event: 2
0000017828 [net.ppp.client] TRACE: PPP thread event LOWER_UP data=0
0000017828 [net.ppp.client] TRACE: State READY -> CONNECT
0000017829 [net.ppp.client] TRACE: State CONNECT -> CONNECTING
0000017830 [ncp.at] TRACE: > AT+CGATT?
0000017832 [ncp.at] TRACE: < +CGATT: 1
0000017833 [ncp.at] TRACE: < OK
0000018835 [ncp.at] TRACE: > AT
0000018836 [ncp.at] TRACE: < OK
0000018837 [ncp.at] TRACE: > ATH
0000018839 [ncp.at] TRACE: < OK
0000018840 [ncp.at] TRACE: > ATD*99***1#
0000018843 [ncp.at] TRACE: < CONNECT
0000018844 [net.ppp.client] TRACE: PPP phase -> Initialize
0000018845 [net.ppp.client] TRACE: PPP phase -> Establish
0000018846 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x58523da2> <pcomp> <accomp>]
0000018850 [lwip.ppp] TRACE: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xd4fb98a1> <pcomp> <accomp>]
0000018853 [lwip.ppp] TRACE: sent [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xd4fb98a1> <pcomp> <accomp>]
0000018854 [lwip.ppp] TRACE: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x58523da2> <pcomp> <accomp>]
0000018855 [lwip.ppp] TRACE: sent [LCP EchoReq id=0x0 magic=0x58523da2]
0000018856 [net.ppp.client] TRACE: PPP phase -> Authenticate
0000018857 [net.ppp.client] TRACE: PPP phase -> Network
0000018858 [lwip.ppp] TRACE: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <msdns1 8.8.8.8> <msdns2 8.8.4.4>]
0000018861 [lwip.ppp] TRACE: rcvd [LCP EchoRep id=0x0 magic=0xd4fb98a1]
0000019487 [lwip.ppp] TRACE: rcvd [LCP TermReq id=0x2]
0000019487 [net.ppp.client] TRACE: PPP phase -> Establish
0000019488 [lwip.ppp] TRACE: sent [LCP TermAck id=0x2]
0000025487 [net.ppp.client] TRACE: PPP phase -> Disconnect
0000025488 [net.ppp.client] TRACE: PPP phase -> Dead
0000025489 [net.ppp.client] TRACE: PPP thread event ERROR data=6
0000025489 [net.pppncp] ERROR: PPP error event data=6
0000025490 [net.ppp.client] TRACE: PPP thread event DOWN data=0
0000025491 [net.ppp.client] TRACE: State CONNECTING -> DISCONNECT
0000025492 [net.ppp.client] TRACE: State DISCONNECT -> DISCONNECTING
0000025492 [net.ppp.client] TRACE: PPP thread event ERROR data=5
0000025493 [net.pppncp] ERROR: PPP error event data=5
0000025494 [net.ppp.client] TRACE: PPP thread event DOWN data=0
0000025495 [net.ppp.client] TRACE: State DISCONNECTING -> DISCONNECTED
0000025495 [net.ppp.client] TRACE: State DISCONNECTED -> CONNECT
0000025595 [net.ppp.client] TRACE: State CONNECT -> CONNECTING
0000025596 [ncp.at] TRACE: > AT+CGATT?
0000025600 [ncp.at] TRACE: < +CGATT: 1
0000025601 [ncp.at] TRACE: < OK
0000026602 [ncp.at] TRACE: > AT
0000026604 [ncp.at] TRACE: < OK
0000026605 [ncp.at] TRACE: > ATH
0000026607 [ncp.at] TRACE: < OK
0000026608 [ncp.at] TRACE: > ATD*99***1#
0000026612 [ncp.at] TRACE: < CONNECT
0000026613 [net.ppp.client] TRACE: PPP phase -> Initialize
0000026614 [net.ppp.client] TRACE: PPP phase -> Establish
0000026615 [lwip.ppp] TRACE: sent [LCP ConfReq id=0x2 <asyncmap 0x0> <magic 0x40b36677> <pcomp> <accomp>]
0000026619 [lwip.ppp] TRACE: rcvd [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0xc497f658> <pcomp> <accomp>]
0000026622 [lwip.ppp] TRACE: sent [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0xc497f658> <pcomp> <accomp>]
0000026623 [lwip.ppp] TRACE: rcvd [LCP ConfAck id=0x2 <asyncmap 0x0> <magic 0x40b36677> <pcomp> <accomp>]
0000026625 [lwip.ppp] TRACE: sent [LCP EchoReq id=0x0 magic=0x40b36677]
0000026626 [net.ppp.client] TRACE: PPP phase -> Authenticate
0000026626 [net.ppp.client] TRACE: PPP phase -> Network
0000026628 [lwip.ppp] TRACE: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <msdns1 8.8.8.8> <msdns2 8.8.4.4>]
0000026630 [lwip.ppp] TRACE: rcvd [LCP EchoRep id=0x0 magic=0xc497f658]
0000031625 [lwip.ppp] TRACE: sent [LCP EchoReq id=0x1 magic=0x40b36677]
0000031629 [lwip.ppp] TRACE: rcvd [LCP EchoRep id=0x1 magic=0xc497f658]
0000032629 [lwip.ppp] TRACE: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <msdns1 8.8.8.8> <msdns2 8.8.4.4>]
0000036626 [lwip.ppp] TRACE: sent [LCP EchoReq id=0x2 magic=0x40b36677]
0000036630 [lwip.ppp] TRACE: rcvd [LCP EchoRep id=0x2 magic=0xc497f658]
0000038630 [lwip.ppp] TRACE: sent [IPCP ConfReq id=0x1 <addr 0.0.0.0> <msdns1 8.8.8.8> <msdns2 8.8.4.4>]
0000041507 [lwip.ppp] TRACE: rcvd [LCP TermReq id=0x2]
0000041507 [net.ppp.client] TRACE: PPP phase -> Establish
0000041508 [lwip.ppp] TRACE: sent [LCP TermAck id=0x2]
0000047507 [net.ppp.client] TRACE: PPP phase -> Disconnect
0000047508 [net.ppp.client] TRACE: PPP phase -> Dead
0000047509 [net.ppp.client] TRACE: PPP thread event ERROR data=5
0000047509 [net.pppncp] ERROR: PPP error event data=5
0000047510 [net.ppp.client] TRACE: PPP thread event DOWN data=0
0000047511 [net.ppp.client] TRACE: State CONNECTING -> DISCONNECT
0000047511 [net.ppp.client] TRACE: State DISCONNECT -> DISCONNECTING
0000047512 [net.ppp.client] TRACE: PPP thread event ERROR data=5
0000047513 [net.pppncp] ERROR: PPP error event data=5

Where is the device located?

The important part is this; the device is getting a request to terminate the connection before the PDP session is fully established. It's not clear why that is happening, however.

0000041507 [lwip.ppp] TRACE: rcvd [LCP TermReq id=0x2]
1 Like

This device is located in Colorado, USA.

Happy to message you with device identifiers if that would be helpful.

It's unusual that one device is not working but the others are, but you are very much on borrowed time now with the Boron 314. AT&T shut down 2G/3G service in June 2022. T-Mobile mostly completed shutdown by April 2024 but there are some cell sites still operating. It's not expected that any 2G/3G device will be able to connect in the United States reliably at this time. See US 2G/3G sunset.

1 Like

I hear you on the upcoming 2G/3G sunset.
In the US we use the LTE's, however we have international deployments so we test the 314's frequently.