r_kawai
2024年7月9日 16時18分
いつもお世話になっております。
客先に納入した端末で、表題の件が突然発生するようになりました。
客先で稼働時の現象を①、弊社で回収して動作確認時の現象を②として以下に概要を記載いたします。
お手数をおかけしますが、原因について思い当たる点がありましたらご教示いただけませんでしょうか。
①客先で稼働時の現象
■現象
6月頭くらいから客先で使用を開始しましたが、6/26以降LTE通信ができなくなりました。
再起動を実施しましたが現象は改善しませんでした。
7/1に代替品と交換したところ、LTE通信ができるようになりました。SIMは替えず端末のみ交換しています。
現象が発生していた端末を弊社で回収しmessagesを確認したところ、以下のようにModemManagerの処理でsimple connect state (5/8): register以降進んでいないように見えています。
★ここまでは接続できていた模様 ... Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] simple connect started... Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] simple connect state (4/8): wait to get fully enabled Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] simple connect state (5/8): register Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] simple connect state (6/8): bearer Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] simple connect state (7/8): connect Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] state changed (registered -> connecting) Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] state changed (connecting -> connected) Jun 26 03:15:15 armadillo daemon.info [1937]: <info> [modem0] simple connect state (8/8): all done ... Jun 26 03:15:15 armadillo daemon.notice pppd[13579]: local IP address 100.74.32.3 Jun 26 03:15:15 armadillo daemon.notice pppd[13579]: remote IP address 10.64.64.64 Jun 26 03:15:15 armadillo daemon.notice pppd[13579]: primary DNS address 210.147.235.3 Jun 26 03:15:15 armadillo daemon.notice pppd[13579]: secondary DNS address 133.205.66.51 ... ★これ以降はLTE網への接続に失敗し続けている Jun 26 03:39:22 armadillo daemon.info [1937]: <info> [modem0] simple connect started... Jun 26 03:39:22 armadillo daemon.info [1937]: <info> [modem0] simple connect state (4/8): wait to get fully enabled Jun 26 03:39:22 armadillo daemon.info [1937]: <info> [modem0] simple connect state (5/8): register Jun 26 03:39:22 armadillo daemon.info [1937]: <info> [modem0] 3GPP registration state changed (idle -> searching) Jun 26 03:39:22 armadillo daemon.info [1937]: <info> [modem0] state changed (enabled -> searching) Jun 26 03:40:25 armadillo daemon.info [1937]: <info> [modem0] 3GPP registration state changed (searching -> idle) Jun 26 03:40:25 armadillo daemon.info [1937]: <info> [modem0] state changed (searching -> enabled) Jun 26 03:40:25 armadillo daemon.warn NetworkManager[1358]: <warn> [1719340825.0100] modem-broadband[ttyCommModem]: failed to connect modem: Network timeout Jun 26 03:40:25 armadillo daemon.info NetworkManager[1358]: <info> [1719340825.0101] device (ttyCommModem): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface- state: 'managed') Jun 26 03:40:25 armadillo daemon.info NetworkManager[1358]: <info> [1719340825.0112] manager: NetworkManager state is now DISCONNECTED Jun 26 03:40:25 armadillo daemon.warn NetworkManager[1358]: <warn> [1719340825.0133] device (ttyCommModem): Activation: failed for connection 'gsm-ttyCommModem' Jun 26 03:40:25 armadillo daemon.info NetworkManager[1358]: <info> [1719340825.0146] device (ttyCommModem): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed ') ★再起動後も変わらず Jun 26 10:36:04 armadillo kern.info kernel: [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] ... Jun 26 10:41:45 armadillo daemon.info [1939]: <info> [modem0] simple connect started... Jun 26 10:41:45 armadillo daemon.info [1939]: <info> [modem0] simple connect state (4/8): wait to get fully enabled Jun 26 10:41:45 armadillo daemon.info [1939]: <info> [modem0] simple connect state (5/8): register Jun 26 10:41:45 armadillo daemon.info [1939]: <info> [modem0] 3GPP registration state changed (idle -> searching) Jun 26 10:41:45 armadillo daemon.info [1939]: <info> [modem0] state changed (enabled -> searching) Jun 26 10:42:48 armadillo daemon.info [1939]: <info> [modem0] 3GPP registration state changed (searching -> idle) Jun 26 10:42:48 armadillo daemon.info [1939]: <info> [modem0] state changed (searching -> enabled) Jun 26 10:42:48 armadillo daemon.warn NetworkManager[1355]: <warn> [1719366168.0089] modem-broadband[ttyCommModem]: failed to connect modem: Network timeout Jun 26 10:42:48 armadillo daemon.info NetworkManager[1355]: <info> [1719366168.0089] device (ttyCommModem): state change: prepare -> failed (reason 'gsm-registration-timeout', sys-iface- state: 'managed') Jun 26 10:42:48 armadillo daemon.info NetworkManager[1355]: <info> [1719366168.0102] manager: NetworkManager state is now DISCONNECTED Jun 26 10:42:48 armadillo daemon.warn NetworkManager[1355]: <warn> [1719366168.0115] device (ttyCommModem): Activation: failed for connection 'gsm-ttyCommModem' Jun 26 10:42:48 armadillo daemon.info NetworkManager[1355]: <info> [1719366168.0139] device (ttyCommModem): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed ')
■SIM情報
biglobe タイプD 30GB
■ソフトバージョン
armadillo:~# cat /etc/sw-versions
base_os 3.16.3-at.5-ec.1
other_boot 2020.04-at10
boot 2020.04-at10
extra_os.initial_setup 2
firmware 2.2.0
3.16.3-at.5ベースに弊社で手を加えています。LTE周りは変更しておりません。
■messages
log_1.zip
②弊社で回収後の現象
端末を回収し、弊社にあるSIMで動作を確認しましたが、客先で運用時と同様にsimple connect state (5/8): register以降進まない現象が発生しています。
また、モデム初期化での改善を期待しec25-clean-resetを実行しましたが、現象は変化しませんでした。
SIM情報にある2種類のSIMで確認しています。
添付のログは、ModemManagerのデバッグログを有効にし(1)biglobe タイプD 20GBのSIMを挿入した状態で取得したログとなります。
■SIM情報
(1)biglobe タイプD 20GB
→客先で使用しているSIMとは異なります。他のデバイスでLTE接続できることは確認済みです。
armadillo:~# mmcli -m 0
--------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 691b650f40802dc320676566e3bc27a0d008cdcc
--------------------------------
Hardware | manufacturer: Quectel
| model: EC25
| firmware revision: EC25JFAR06A05M4G
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 865036049341116
--------------------------------
System | device: /sys/devices/platform/soc@0/32f10108.usb/38200000.dwc3/xhci-hcd.2.auto/usb3/3-1/3-1.2
| drivers: option
| plugin: quectel-ec25
| primary port: ttyCommModem
| ports: ttyCommModem (at), ttyUSB0 (qcdm), ttyUSB1 (gps),
| ttyUSB3 (at)
--------------------------------
Numbers | own: 02001011660399
--------------------------------
Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: searching
| power state: on
| signal quality: 0% (cached)
--------------------------------
Modes | supported: allowed: 2g, 3g, 4g; preferred: none
| current: allowed: 2g, 3g, 4g; preferred: none
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: 865036049341116
| registration: searching
--------------------------------
3GPP EPS | ue mode of operation: csps-2
--------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
armadillo:~# send-at /dev/ttymxc3 AT+CSQ echo
+CSQ: 30,99
OK(2)IIJ typeI
→客先で使用しているSIMとは異なります。他のデバイスでLTE接続できることは確認済みです。
armadillo:~# mmcli -m 0
--------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 691b650f40802dc320676566e3bc27a0d008cdcc
--------------------------------
Hardware | manufacturer: Quectel
| model: EC25
| firmware revision: EC25JFAR06A05M4G
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 865036049341116
--------------------------------
System | device: /sys/devices/platform/soc@0/32f10108.usb/38200000.dwc3/xhci-hcd.2.auto/usb3/3-1/3-1.2
| drivers: option
| plugin: quectel-ec25
| primary port: ttyCommModem
| ports: ttyCommModem (at), ttyUSB0 (qcdm), ttyUSB1 (gps),
| ttyUSB3 (at)
--------------------------------
Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: searching
| power state: on
| signal quality: 0% (cached)
--------------------------------
Modes | supported: allowed: 2g, 3g, 4g; preferred: none
| current: allowed: 2g, 3g, 4g; preferred: none
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: 865036049341116
| registration: searching
--------------------------------
3GPP EPS | ue mode of operation: csps-2
--------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0■ソフトバージョン
①と同じです。
■messages
log_2.zip
コメント
r_kawai
2024年7月9日 18時57分
吉田様
ご返信いただきありがとうございます。
ご教示いただいた手順を以下のように実施いたしましたので、お手数ですがご確認をお願いいたします。
SIMは(1)biglobe タイプD 20GBを使用しています。
■手順
armadillo:~# rc-service connection-recover stop connection-recover | * Stopping connection-recover ... [ ok ] armadillo:~# rc-service modemmanager stop modemmanager | * Stopping modemmanager ... [ ok ] armadillo:~# ec25-clean-reset OK OK armadillo:~# rc-service connection-recover start connection-recover | * Starting connection-recover ... [ ok ] armadillo:~# nmcli connection add type gsm ifname ttyCommModem apn biglobe.jp user user password 0000 gsm.network-id 44010 Connection 'gsm-ttyCommModem' (c6ba77ac-ee48-4012-8fb6-85163c9cb1ec) successfully added. armadillo:~# nmcli d DEVICE TYPE STATE CONNECTION ttyCommModem gsm connecting (prepare) gsm-ttyCommModem eth0 ethernet unavailable -- eth1 ethernet unavailable -- lo loopback unmanaged -- armadillo:~# cat /etc/NetworkManager/system-connections/ Wired connection 2.nmconnection gsm-ttyCommModem.nmconnection armadillo:~# cat /etc/NetworkManager/system-connections/gsm-ttyCommModem.nmconnection [connection] id=gsm-ttyCommModem uuid=c6ba77ac-ee48-4012-8fb6-85163c9cb1ec type=gsm interface-name=ttyCommModem [gsm] apn=biglobe.jp network-id=44010 password=0000 username=user [ipv4] method=auto [ipv6] addr-gen-mode=stable-privacy method=auto [proxy]
■状況
以下のように一時的にLTE網との接続が確立するようになりましたが、pingの通りが悪く、
connection-recoverでping fail⇒モデム再起動というような動きを繰り返しているようです。
また、registerを越えてall doneまで進んでもIPアドレスが取得できてないケースもあるように見えています。
armadillo:~# egrep 'IP address|simple connect|connection-recover' /var/log/messages Jul 9 17:54:02 armadillo daemon.info [2138]: <info> [1720515242.019449] [modem0] simple connect started... Jul 9 17:54:02 armadillo daemon.info [2138]: <info> [1720515242.019970] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 17:54:02 armadillo daemon.info [2138]: <info> [1720515242.020081] [modem0] simple connect state (5/8): register Jul 9 17:55:53 armadillo user.debug : Will stop /usr/bin/connection-recover Jul 9 17:56:54 armadillo daemon.info [2313]: <info> [1720515414.772374] [modem0] simple connect started... Jul 9 17:56:54 armadillo daemon.info [2313]: <info> [1720515414.772714] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 17:56:54 armadillo daemon.info [2313]: <info> [1720515414.772791] [modem0] simple connect state (5/8): register Jul 9 17:57:40 armadillo daemon.info [2313]: <info> [1720515460.573761] [modem0] simple connect state (6/8): bearer Jul 9 17:57:40 armadillo daemon.info [2313]: <info> [1720515460.575936] [modem0] simple connect state (7/8): connect Jul 9 17:57:40 armadillo daemon.info [2313]: <info> [1720515460.743820] [modem0] simple connect state (8/8): all done Jul 9 17:57:41 armadillo daemon.warn pppd[2475]: Could not determine remote IP address: defaulting to 10.64.64.64 Jul 9 17:57:41 armadillo daemon.notice pppd[2475]: local IP address 100.74.111.196 Jul 9 17:57:41 armadillo daemon.notice pppd[2475]: remote IP address 10.64.64.64 Jul 9 17:58:30 armadillo user.notice connection-recover: ttyCommModem ping fail Jul 9 17:58:30 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.130776] [modem0] simple connect started... Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.132230] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.132356] [modem0] simple connect state (5/8): register Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.132505] [modem0] simple connect state (6/8): bearer Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.133683] [modem0] simple connect state (7/8): connect Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.194217] [modem0] simple connect state (8/8): all done Jul 9 17:58:37 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4 Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.303870] [modem0] simple connect started... Jul 9 17:58:37 armadillo daemon.info [2313]: <info> [1720515517.304294] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 17:58:38 armadillo daemon.info [2313]: <info> [1720515518.312280] [modem0] simple connect state (5/8): register Jul 9 17:58:38 armadillo daemon.info [2313]: <info> [1720515518.313671] [modem0] simple connect state (6/8): bearer Jul 9 17:58:38 armadillo daemon.info [2313]: <info> [1720515518.315786] [modem0] simple connect state (7/8): connect Jul 9 17:58:38 armadillo daemon.info [2313]: <info> [1720515518.369126] [modem0] simple connect state (8/8): all done Jul 9 17:58:38 armadillo daemon.info [2313]: <info> [1720515518.482781] [modem0] simple connect started... ...中略 Jul 9 18:00:37 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 9 18:00:42 armadillo daemon.info [2313]: <info> [1720515642.507121] [modem0] simple connect started... Jul 9 18:00:42 armadillo daemon.info [2313]: <info> [1720515642.507958] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:00:42 armadillo daemon.info [2313]: <info> [1720515642.508068] [modem0] simple connect state (5/8): register Jul 9 18:00:42 armadillo daemon.info [2313]: <info> [1720515642.508204] [modem0] simple connect state (6/8): bearer Jul 9 18:00:42 armadillo daemon.info [2313]: <info> [1720515642.509261] [modem0] simple connect state (7/8): connect Jul 9 18:00:42 armadillo daemon.info [2313]: <info> [1720515642.567538] [modem0] simple connect state (8/8): all done Jul 9 18:00:47 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4 Jul 9 18:00:47 armadillo user.notice connection-recover: exec wwan-restart Jul 9 18:01:03 armadillo daemon.info [2313]: <info> [1720515663.206189] [modem0] simple connect started... Jul 9 18:01:03 armadillo daemon.info [2313]: <info> [1720515663.207057] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:01:03 armadillo daemon.info [2313]: <info> [1720515663.207164] [modem0] simple connect state (5/8): register ...中略 Jul 9 18:04:37 armadillo daemon.info [2313]: <info> [1720515877.518255] [modem0] simple connect started... Jul 9 18:04:37 armadillo daemon.info [2313]: <info> [1720515877.518652] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:04:37 armadillo daemon.info [2313]: <info> [1720515877.518777] [modem0] simple connect state (5/8): register Jul 9 18:06:06 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 9 18:06:11 armadillo daemon.info [2313]: <info> [1720515971.699954] [modem0] simple connect started... Jul 9 18:06:11 armadillo daemon.info [2313]: <info> [1720515971.700314] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:06:11 armadillo daemon.info [2313]: <info> [1720515971.700441] [modem0] simple connect state (5/8): register ...中略 Jul 9 18:06:19 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4 Jul 9 18:06:19 armadillo user.notice connection-recover: exec wwan-restart Jul 9 18:06:29 armadillo daemon.info [2313]: <info> [1720515989.910183] [modem0] simple connect started... Jul 9 18:06:29 armadillo daemon.info [2313]: <info> [1720515989.910919] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:06:29 armadillo daemon.info [2313]: <info> [1720515989.911010] [modem0] simple connect state (5/8): register Jul 9 18:06:45 armadillo daemon.info [2313]: <info> [1720516005.011146] [modem0] simple connect state (6/8): bearer Jul 9 18:06:45 armadillo daemon.info [2313]: <info> [1720516005.012596] [modem0] simple connect state (7/8): connect Jul 9 18:06:45 armadillo daemon.info [2313]: <info> [1720516005.088668] [modem0] simple connect state (8/8): all done Jul 9 18:06:45 armadillo daemon.warn pppd[14521]: Could not determine remote IP address: defaulting to 10.64.64.64 Jul 9 18:06:45 armadillo daemon.notice pppd[14521]: local IP address 100.114.9.251 Jul 9 18:06:45 armadillo daemon.notice pppd[14521]: remote IP address 10.64.64.64 Jul 9 18:10:57 armadillo user.notice connection-recover: ttyCommModem ping fail Jul 9 18:10:57 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 9 18:11:04 armadillo daemon.info [2313]: <info> [1720516264.097430] [modem0] simple connect started... Jul 9 18:11:04 armadillo daemon.info [2313]: <info> [1720516264.097809] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:11:04 armadillo daemon.info [2313]: <info> [1720516264.097896] [modem0] simple connect state (5/8): register Jul 9 18:11:04 armadillo daemon.info [2313]: <info> [1720516264.098036] [modem0] simple connect state (6/8): bearer Jul 9 18:11:04 armadillo daemon.info [2313]: <info> [1720516264.099181] [modem0] simple connect state (7/8): connect Jul 9 18:11:28 armadillo daemon.info [2313]: <info> [1720516288.023400] [modem0] simple connect started... ...中略 Jul 9 18:11:28 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4 Jul 9 18:11:28 armadillo daemon.info [2313]: <info> [1720516288.264958] [modem0] simple connect started... Jul 9 18:11:28 armadillo daemon.info [2313]: <info> [1720516288.265324] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:11:29 armadillo daemon.info [2313]: <info> [1720516289.270009] [modem0] simple connect state (5/8): register Jul 9 18:11:29 armadillo daemon.info [2313]: <info> [1720516289.272714] [modem0] simple connect state (6/8): bearer Jul 9 18:11:29 armadillo daemon.info [2313]: <info> [1720516289.280141] [modem0] simple connect state (7/8): connect Jul 9 18:11:29 armadillo daemon.info [2313]: <info> [1720516289.335120] [modem0] simple connect state (8/8): all done ...中略 Jul 9 18:13:28 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 9 18:13:33 armadillo daemon.info [2313]: <info> [1720516413.480423] [modem0] simple connect started... Jul 9 18:13:33 armadillo daemon.info [2313]: <info> [1720516413.480775] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:13:33 armadillo daemon.info [2313]: <info> [1720516413.480872] [modem0] simple connect state (5/8): register Jul 9 18:13:33 armadillo daemon.info [2313]: <info> [1720516413.481018] [modem0] simple connect state (6/8): bearer Jul 9 18:13:33 armadillo daemon.info [2313]: <info> [1720516413.482158] [modem0] simple connect state (7/8): connect Jul 9 18:13:33 armadillo daemon.info [2313]: <info> [1720516413.541784] [modem0] simple connect state (8/8): all done Jul 9 18:13:33 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4 Jul 9 18:13:33 armadillo user.notice connection-recover: exec wwan-restart Jul 9 18:13:49 armadillo daemon.info [2313]: <info> [1720516429.135782] [modem0] simple connect started... Jul 9 18:13:49 armadillo daemon.info [2313]: <info> [1720516429.136629] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:13:49 armadillo daemon.info [2313]: <info> [1720516429.136767] [modem0] simple connect state (5/8): register Jul 9 18:14:25 armadillo daemon.info [2313]: <info> [1720516465.011487] [modem0] simple connect state (6/8): bearer Jul 9 18:14:25 armadillo daemon.info [2313]: <info> [1720516465.013053] [modem0] simple connect state (7/8): connect Jul 9 18:14:25 armadillo daemon.info [2313]: <info> [1720516465.089020] [modem0] simple connect state (8/8): all done Jul 9 18:14:25 armadillo daemon.warn pppd[24596]: Could not determine remote IP address: defaulting to 10.64.64.64 Jul 9 18:14:25 armadillo daemon.notice pppd[24596]: local IP address 100.113.96.50 Jul 9 18:14:25 armadillo daemon.notice pppd[24596]: remote IP address 10.64.64.64 Jul 9 18:16:36 armadillo user.notice connection-recover: ttyCommModem ping fail Jul 9 18:16:36 armadillo user.notice connection-recover: exec wwan-restart Jul 9 18:16:53 armadillo daemon.info [2313]: <info> [1720516613.103707] [modem0] simple connect started... Jul 9 18:16:53 armadillo daemon.info [2313]: <info> [1720516613.104083] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:16:53 armadillo daemon.info [2313]: <info> [1720516613.104170] [modem0] simple connect state (5/8): register Jul 9 18:17:56 armadillo daemon.info [2313]: <info> [1720516676.015501] [modem0] simple connect started... Jul 9 18:17:56 armadillo daemon.info [2313]: <info> [1720516676.016012] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:17:56 armadillo daemon.info [2313]: <info> [1720516676.016119] [modem0] simple connect state (5/8): register Jul 9 18:18:01 armadillo daemon.info [2313]: <info> [1720516681.388578] [modem0] simple connect started... Jul 9 18:18:01 armadillo daemon.info [2313]: <info> [1720516681.388965] [modem0] simple connect state (4/8): wait to get fully enabled Jul 9 18:18:01 armadillo daemon.info [2313]: <info> [1720516681.389078] [modem0] simple connect state (5/8): register ★18:19:59にrc-service modemmanager stopを実行、18:37:23にrc-service modemmanager startで再開 Jul 9 18:31:31 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 9 18:31:36 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4 Jul 9 18:33:36 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 9 18:33:41 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4 ...
LTE接続中の電波品質を取得したところ、signal quality: 20%となっており、AT+CSQは前回の30から31に変化していました。
場所は前回質問投稿時から変えておりません。
他デバイスで同じSIM、場所で試した際にはそのデバイスでの最高のアンテナレベルとなっているので、確認環境の電波自体は悪くはないのではないかと考えております。
armadillo:~# mmcli -m 0
--------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 691b650f40802dc320676566e3bc27a0d008cdcc
--------------------------------
Hardware | manufacturer: Quectel
| model: EC25
| firmware revision: EC25JFAR06A05M4G
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 865036049341116
--------------------------------
System | device: /sys/devices/platform/soc@0/32f10108.usb/38200000.dwc3/xhci-hcd.2.auto/usb3/3-1/3-1.2
| drivers: option
| plugin: quectel-ec25
| primary port: ttyCommModem
| ports: ttyCommModem (at), ttyUSB0 (qcdm), ttyUSB1 (gps),
| ttyUSB3 (at)
--------------------------------
Numbers | own: 02001011660399
--------------------------------
Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: connected
| power state: on
| access tech: lte
| signal quality: 20% (recent)
--------------------------------
Modes | supported: allowed: 2g, 3g, 4g; preferred: none
| current: allowed: 2g, 3g, 4g; preferred: none
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: 865036049341116
| operator id: 44010
| operator name: NTT DOCOMO NTT DOCOMO
| registration: home
--------------------------------
3GPP EPS | ue mode of operation: csps-2
--------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
--------------------------------
Bearer | paths: /org/freedesktop/ModemManager1/Bearer/13
| /org/freedesktop/ModemManager1/Bearer/12
| /org/freedesktop/ModemManager1/Bearer/11
| /org/freedesktop/ModemManager1/Bearer/10
| /org/freedesktop/ModemManager1/Bearer/9
| /org/freedesktop/ModemManager1/Bearer/8
| /org/freedesktop/ModemManager1/Bearer/7
| /org/freedesktop/ModemManager1/Bearer/6
| /org/freedesktop/ModemManager1/Bearer/5
| /org/freedesktop/ModemManager1/Bearer/4
| /org/freedesktop/ModemManager1/Bearer/3
| /org/freedesktop/ModemManager1/Bearer/2
| /org/freedesktop/ModemManager1/Bearer/1
| /org/freedesktop/ModemManager1/Bearer/0
armadillo:~# send-at /dev/ttymxc3 AT+CSQ echo
+CSQ: 31,99
OK
armadillo:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:11:0c:33:06:42 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:11:0c:33:06:43 brd ff:ff:ff:ff:ff:ff
10: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 3
link/ppp
inet 100.114.9.251 peer 10.64.64.64/32 scope global ppp0
valid_lft forever preferred_lft forever
inet 100.114.9.251/32 scope global noprefixroute ppp0
valid_lft forever preferred_lft forever
armadillo:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=116 time=2018.711 ms
64 bytes from 8.8.8.8: seq=1 ttl=116 time=1018.255 ms
64 bytes from 8.8.8.8: seq=2 ttl=116 time=50.828 ms
64 bytes from 8.8.8.8: seq=4 ttl=116 time=68.137 ms
64 bytes from 8.8.8.8: seq=5 ttl=116 time=75.538 ms
64 bytes from 8.8.8.8: seq=7 ttl=116 time=66.692 ms
64 bytes from 8.8.8.8: seq=9 ttl=116 time=73.694 ms| ファイル | ファイルの説明 |
|---|---|
| messages.zip | 手順実施後のログ |
at_mitsuhiro.yoshida
2024年7月10日 8時28分
吉田です。
ご確認ありがとうございます。
お手数ですが、一旦 LTE アンテナケーブルの接続を確認いただけますでしょうか。
Armadillo-IoT ゲートウェイ G4 のケースの開け方は以下の動画を参照ください。
https://www.youtube.com/watch?v=jvxnqR4fGdM&list=PLMXzFqu1lnCzraWwc07Ht…
アンテナは製品マニュアル「インターフェースレイアウト LTEモデル(ケース内部)」の CON21 と CON22 の位置となります。
https://manual.atmark-techno.com/armadillo-iot-g4/armadillo-iotg-g4_pro…
アンテナを挿しなおしても状況が変わらないようでしたら、
「故障かなと思ったら(Armadillo-IoT ゲートウェイ G4)」を参照の上、ご対応のご検討をお願いします。
https://armadillo.atmark-techno.com/faq/troubleshooting-aiotg4
r_kawai
2024年7月10日 9時55分
吉田様
ご回答ありがとうございます。
2本のアンテナ、CON21 と CON22について、いずれもゆるみは無く固くはまった状態でしたので、接続自体は問題はなさそうでした。
確認時の状態は添付の写真となります。
念のために2本のアンテナ、CON21 と CON22について接続し直してみました。
signal quality: 100%、となっており、all doneまで進むようにはなっているのですが、
pingが通らないことによりconnection-recoverでモデム再起動を繰り返しているため、
LTE通信ができない現象自体は改善していない状況です。
端末を再起動をしましたが現象に変化はありませんでした。
システム起動自体に問題はなく、
「故障かなと思ったら(Armadillo-IoT ゲートウェイ G4)」
の「7. 問題が解決しなかった場合は？」に該当する状態の認識のため、弊社内で今後の対応について検討したいと思います。
追加でご相談させていただく場合があるかもしれませんが、その際はよろしくお願いいたします。
armadillo:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:11:0c:33:06:42 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:11:0c:33:06:43 brd ff:ff:ff:ff:ff:ff
15: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 3
link/ppp
inet 100.74.78.199 peer 10.64.64.64/32 scope global ppp0
valid_lft forever preferred_lft forever
inet 100.74.78.199/32 scope global noprefixroute ppp0
valid_lft forever preferred_lft forever
armadillo:~# ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
^C
--- 8.8.8.8 ping statistics ---
20 packets transmitted, 0 packets received, 100% packet loss
armadillo:~# mmcli -m 0
--------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 691b650f40802dc320676566e3bc27a0d008cdcc
--------------------------------
Hardware | manufacturer: Quectel
| model: EC25
| firmware revision: EC25JFAR06A05M4G
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 865036049341116
--------------------------------
System | device: /sys/devices/platform/soc@0/32f10108.usb/38200000.dwc3/xhci-hcd.2.auto/usb3/3-1/3-1.2
| drivers: option
| plugin: quectel-ec25
| primary port: ttyCommModem
| ports: ttyCommModem (at), ttyUSB0 (qcdm), ttyUSB1 (gps),
| ttyUSB3 (at)
--------------------------------
Numbers | own: 02001011660399
--------------------------------
Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: connected
| power state: on
| access tech: lte
| signal quality: 100% (recent)
--------------------------------
Modes | supported: allowed: 2g, 3g, 4g; preferred: none
| current: allowed: 2g, 3g, 4g; preferred: none
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: 865036049341116
| operator id: 44010
| operator name: NTT DOCOMO NTT DOCOMO
| registration: home
--------------------------------
3GPP EPS | ue mode of operation: csps-1
--------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
--------------------------------
Bearer | paths: /org/freedesktop/ModemManager1/Bearer/11
| /org/freedesktop/ModemManager1/Bearer/10
| /org/freedesktop/ModemManager1/Bearer/9
| /org/freedesktop/ModemManager1/Bearer/8
| /org/freedesktop/ModemManager1/Bearer/7
| /org/freedesktop/ModemManager1/Bearer/6
| /org/freedesktop/ModemManager1/Bearer/5
| /org/freedesktop/ModemManager1/Bearer/4
| /org/freedesktop/ModemManager1/Bearer/3
| /org/freedesktop/ModemManager1/Bearer/2
| /org/freedesktop/ModemManager1/Bearer/1
| /org/freedesktop/ModemManager1/Bearer/0
armadillo:~# send-at /dev/ttymxc3 AT+CSQ echo
+CSQ: 31,99
OK
armadillo:~# egrep 'IP address|simple connect|connection-recover' /var/log/messages|tail -n 100
Jul 10 09:21:16 armadillo daemon.info [1934]: <info> [1720570876.482275] [modem0] simple connect started...
Jul 10 09:21:16 armadillo daemon.info [1934]: <info> [1720570876.482647] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:21:17 armadillo daemon.info [1934]: <info> [1720570877.491052] [modem0] simple connect state (5/8): register
Jul 10 09:21:17 armadillo daemon.info [1934]: <info> [1720570877.492371] [modem0] simple connect state (6/8): bearer
Jul 10 09:21:17 armadillo daemon.info [1934]: <info> [1720570877.494232] [modem0] simple connect state (7/8): connect
Jul 10 09:21:17 armadillo daemon.info [1934]: <info> [1720570877.549068] [modem0] simple connect state (8/8): all done
Jul 10 09:21:17 armadillo daemon.info [1934]: <info> [1720570877.667651] [modem0] simple connect started...
Jul 10 09:21:17 armadillo daemon.info [1934]: <info> [1720570877.667990] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:21:18 armadillo daemon.info [1934]: <info> [1720570878.675691] [modem0] simple connect state (5/8): register
Jul 10 09:21:18 armadillo daemon.info [1934]: <info> [1720570878.677002] [modem0] simple connect state (6/8): bearer
Jul 10 09:21:18 armadillo daemon.info [1934]: <info> [1720570878.678852] [modem0] simple connect state (7/8): connect
Jul 10 09:21:18 armadillo daemon.info [1934]: <info> [1720570878.728599] [modem0] simple connect state (8/8): all done
Jul 10 09:22:42 armadillo user.notice connection-recover: ttyCommModem reconnect start...
Jul 10 09:22:47 armadillo daemon.info [1934]: <info> [1720570967.684551] [modem0] simple connect started...
Jul 10 09:22:47 armadillo daemon.info [1934]: <info> [1720570967.685034] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:22:47 armadillo daemon.info [1934]: <info> [1720570967.685174] [modem0] simple connect state (5/8): register
Jul 10 09:22:47 armadillo daemon.info [1934]: <info> [1720570967.685316] [modem0] simple connect state (6/8): bearer
Jul 10 09:22:47 armadillo daemon.info [1934]: <info> [1720570967.686435] [modem0] simple connect state (7/8): connect
Jul 10 09:22:47 armadillo daemon.info [1934]: <info> [1720570967.748354] [modem0] simple connect state (8/8): all done
Jul 10 09:22:49 armadillo daemon.warn pppd[2270]: Could not determine remote IP address: defaulting to 10.64.64.64
Jul 10 09:22:49 armadillo daemon.notice pppd[2270]: local IP address 100.113.58.248
Jul 10 09:22:49 armadillo daemon.notice pppd[2270]: remote IP address 10.64.64.64
Jul 10 09:22:49 armadillo user.notice connection-recover: ttyCommModem reconnect success
Jul 10 09:25:00 armadillo user.notice connection-recover: ttyCommModem ping fail
Jul 10 09:25:00 armadillo user.notice connection-recover: ttyCommModem reconnect start...
Jul 10 09:25:06 armadillo daemon.info [1934]: <info> [1720571106.844113] [modem0] simple connect started...
Jul 10 09:25:06 armadillo daemon.info [1934]: <info> [1720571106.844860] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:25:06 armadillo daemon.info [1934]: <info> [1720571106.844995] [modem0] simple connect state (5/8): register
Jul 10 09:25:06 armadillo daemon.info [1934]: <info> [1720571106.845237] [modem0] simple connect state (6/8): bearer
Jul 10 09:25:06 armadillo daemon.info [1934]: <info> [1720571106.846747] [modem0] simple connect state (7/8): connect
Jul 10 09:25:06 armadillo daemon.info [1934]: <info> [1720571106.905846] [modem0] simple connect state (8/8): all done
Jul 10 09:25:07 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4
Jul 10 09:25:07 armadillo daemon.info [1934]: <info> [1720571107.032943] [modem0] simple connect started...
Jul 10 09:25:07 armadillo daemon.info [1934]: <info> [1720571107.033345] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:25:08 armadillo daemon.info [1934]: <info> [1720571108.043179] [modem0] simple connect state (5/8): register
Jul 10 09:25:08 armadillo daemon.info [1934]: <info> [1720571108.044560] [modem0] simple connect state (6/8): bearer
Jul 10 09:25:08 armadillo daemon.info [1934]: <info> [1720571108.046636] [modem0] simple connect state (7/8): connect
Jul 10 09:25:08 armadillo daemon.info [1934]: <info> [1720571108.100461] [modem0] simple connect state (8/8): all done
Jul 10 09:25:08 armadillo daemon.info [1934]: <info> [1720571108.213725] [modem0] simple connect started...
Jul 10 09:25:08 armadillo daemon.info [1934]: <info> [1720571108.214058] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:25:09 armadillo daemon.info [1934]: <info> [1720571109.223057] [modem0] simple connect state (5/8): register
Jul 10 09:25:09 armadillo daemon.info [1934]: <info> [1720571109.224163] [modem0] simple connect state (6/8): bearer
Jul 10 09:25:09 armadillo daemon.info [1934]: <info> [1720571109.225813] [modem0] simple connect state (7/8): connect
Jul 10 09:25:09 armadillo daemon.info [1934]: <info> [1720571109.279073] [modem0] simple connect state (8/8): all done
Jul 10 09:25:09 armadillo daemon.info [1934]: <info> [1720571109.399026] [modem0] simple connect started...
Jul 10 09:25:09 armadillo daemon.info [1934]: <info> [1720571109.399390] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:25:10 armadillo daemon.info [1934]: <info> [1720571110.405927] [modem0] simple connect state (5/8): register
Jul 10 09:25:10 armadillo daemon.info [1934]: <info> [1720571110.407295] [modem0] simple connect state (6/8): bearer
Jul 10 09:25:10 armadillo daemon.info [1934]: <info> [1720571110.409284] [modem0] simple connect state (7/8): connect
Jul 10 09:25:10 armadillo daemon.info [1934]: <info> [1720571110.462191] [modem0] simple connect state (8/8): all done
Jul 10 09:27:07 armadillo user.notice connection-recover: ttyCommModem reconnect start...
Jul 10 09:27:12 armadillo daemon.info [1934]: <info> [1720571232.235040] [modem0] simple connect started...
Jul 10 09:27:12 armadillo daemon.info [1934]: <info> [1720571232.235741] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:27:12 armadillo daemon.info [1934]: <info> [1720571232.235845] [modem0] simple connect state (5/8): register
Jul 10 09:27:12 armadillo daemon.info [1934]: <info> [1720571232.235983] [modem0] simple connect state (6/8): bearer
Jul 10 09:27:12 armadillo daemon.info [1934]: <info> [1720571232.237076] [modem0] simple connect state (7/8): connect
Jul 10 09:27:12 armadillo daemon.info [1934]: <info> [1720571232.293082] [modem0] simple connect state (8/8): all done
Jul 10 09:27:20 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4
Jul 10 09:27:20 armadillo user.notice connection-recover: exec wwan-restart
Jul 10 09:27:36 armadillo daemon.info [1934]: <info> [1720571256.240630] [modem0] simple connect started...
Jul 10 09:27:36 armadillo daemon.info [1934]: <info> [1720571256.241448] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:27:36 armadillo daemon.info [1934]: <info> [1720571256.241579] [modem0] simple connect state (5/8): register
Jul 10 09:27:40 armadillo daemon.info [1934]: <info> [1720571260.046725] [modem0] simple connect state (6/8): bearer
Jul 10 09:27:40 armadillo daemon.info [1934]: <info> [1720571260.048023] [modem0] simple connect state (7/8): connect
Jul 10 09:27:40 armadillo daemon.info [1934]: <info> [1720571260.129349] [modem0] simple connect state (8/8): all done
Jul 10 09:27:40 armadillo daemon.warn pppd[8752]: Could not determine remote IP address: defaulting to 10.64.64.64
Jul 10 09:27:40 armadillo daemon.notice pppd[8752]: local IP address 100.114.104.148
Jul 10 09:27:40 armadillo daemon.notice pppd[8752]: remote IP address 10.64.64.64
Jul 10 09:29:51 armadillo user.notice connection-recover: ttyCommModem ping fail
Jul 10 09:29:51 armadillo user.notice connection-recover: exec wwan-restart
Jul 10 09:30:08 armadillo daemon.info [1934]: <info> [1720571408.136655] [modem0] simple connect started...
Jul 10 09:30:08 armadillo daemon.info [1934]: <info> [1720571408.137010] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:30:08 armadillo daemon.info [1934]: <info> [1720571408.137129] [modem0] simple connect state (5/8): register
Jul 10 09:30:47 armadillo daemon.info [1934]: <info> [1720571447.014224] [modem0] simple connect state (6/8): bearer
Jul 10 09:30:47 armadillo daemon.info [1934]: <info> [1720571447.015659] [modem0] simple connect state (7/8): connect
Jul 10 09:30:47 armadillo daemon.info [1934]: <info> [1720571447.095060] [modem0] simple connect state (8/8): all done
Jul 10 09:30:47 armadillo daemon.warn pppd[12850]: Could not determine remote IP address: defaulting to 10.64.64.64
Jul 10 09:30:47 armadillo daemon.notice pppd[12850]: local IP address 100.74.78.199
Jul 10 09:30:47 armadillo daemon.notice pppd[12850]: remote IP address 10.64.64.64
Jul 10 09:34:59 armadillo user.notice connection-recover: ttyCommModem ping fail
Jul 10 09:34:59 armadillo user.notice connection-recover: ttyCommModem reconnect start...
Jul 10 09:35:05 armadillo daemon.info [1934]: <info> [1720571705.945838] [modem0] simple connect started...
Jul 10 09:35:05 armadillo daemon.info [1934]: <info> [1720571705.946563] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:35:05 armadillo daemon.info [1934]: <info> [1720571705.946687] [modem0] simple connect state (5/8): register
Jul 10 09:35:05 armadillo daemon.info [1934]: <info> [1720571705.946844] [modem0] simple connect state (6/8): bearer
Jul 10 09:35:05 armadillo daemon.info [1934]: <info> [1720571705.948002] [modem0] simple connect state (7/8): connect
Jul 10 09:35:06 armadillo daemon.info [1934]: <info> [1720571706.003025] [modem0] simple connect state (8/8): all done
Jul 10 09:35:06 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4
Jul 10 09:35:06 armadillo daemon.info [1934]: <info> [1720571706.111652] [modem0] simple connect started...
Jul 10 09:35:06 armadillo daemon.info [1934]: <info> [1720571706.112013] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:35:07 armadillo daemon.info [1934]: <info> [1720571707.123333] [modem0] simple connect state (5/8): register
Jul 10 09:35:07 armadillo daemon.info [1934]: <info> [1720571707.124578] [modem0] simple connect state (6/8): bearer
Jul 10 09:35:07 armadillo daemon.info [1934]: <info> [1720571707.126289] [modem0] simple connect state (7/8): connect
Jul 10 09:35:07 armadillo daemon.info [1934]: <info> [1720571707.182642] [modem0] simple connect state (8/8): all done
Jul 10 09:35:07 armadillo daemon.info [1934]: <info> [1720571707.302515] [modem0] simple connect started...
Jul 10 09:35:07 armadillo daemon.info [1934]: <info> [1720571707.303291] [modem0] simple connect state (4/8): wait to get fully enabled
Jul 10 09:35:08 armadillo daemon.info [1934]: <info> [1720571708.306971] [modem0] simple connect state (5/8): register
Jul 10 09:35:08 armadillo daemon.info [1934]: <info> [1720571708.308029] [modem0] simple connect state (6/8): bearer
Jul 10 09:35:08 armadillo daemon.info [1934]: <info> [1720571708.310760] [modem0] simple connect state (7/8): connect
Jul 10 09:35:08 armadillo daemon.info [1934]: <info> [1720571708.364005] [modem0] simple connect state (8/8): all done| ファイル | ファイルの説明 |
|---|---|
| Image.jpg | アンテナ接続状態 |
r_kawai
2024年7月10日 17時07分
吉田様
connection-recover を停止状態で何度かpingを実行しところすべて導通可能でした。
停止していた時間は7～8分だと思います。
また、connection-recoverを起動している状態でも、LTE接続直後はping導通しました。
ただ、10分以上導通確認後、一旦ping停止し再度pingを実行したところ、connection-recoverによる再接続が走り導通不可となりました。
■connection-recover停止後
★15:27:30頃stop
armadillo:~# rc-service connection-recover stop
connection-recover | * Stopping connection-recover ... [ ok ]
armadillo:~# rc-status
Runlevel: default
zramswap [ started ]
iptables [ started ]
watchdog [ started ]
buttond [ started ]
chronyd [ started ]
connection-recover [ stopped ]
ecomott-ddns [ stopped ]
podman-atmark [ started ]
reset_bootcount [ started ]
sshd [ started ]
local [ started ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
fsck [ started ]
root [ started ]
dbus [ started ]
Dynamic Runlevel: manual
modemmanager [ started 05:39:30 (0) ]
armadillo:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:11:0c:33:06:42 brd ff:ff:ff:ff:ff:ff
3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 00:11:0c:33:06:43 brd ff:ff:ff:ff:ff:ff
123: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 3
link/ppp
inet 100.74.130.66 peer 10.64.64.64/32 scope global ppp0
valid_lft forever preferred_lft forever
inet 100.74.130.66/32 scope global noprefixroute ppp0
valid_lft forever preferred_lft forever
armadillo:~# ping -I ppp0 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=116 time=59.779 ms
64 bytes from 8.8.8.8: seq=1 ttl=116 time=58.138 ms
64 bytes from 8.8.8.8: seq=2 ttl=116 time=58.812 ms
...
64 bytes from 8.8.8.8: seq=70 ttl=116 time=68.885 ms
^C
--- 8.8.8.8 ping statistics ---
71 packets transmitted, 68 packets received, 4% packet loss
round-trip min/avg/max = 47.724/66.186/126.303 ms
armadillo:~# ping -I ppp0 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=116 time=6588.821 ms
64 bytes from 8.8.8.8: seq=1 ttl=116 time=5597.036 ms
64 bytes from 8.8.8.8: seq=2 ttl=116 time=4596.916 ms
64 bytes from 8.8.8.8: seq=3 ttl=116 time=3596.492 ms
64 bytes from 8.8.8.8: seq=4 ttl=116 time=2596.077 ms
64 bytes from 8.8.8.8: seq=5 ttl=116 time=1595.943 ms
64 bytes from 8.8.8.8: seq=6 ttl=116 time=595.436 ms
64 bytes from 8.8.8.8: seq=7 ttl=116 time=73.876 ms
64 bytes from 8.8.8.8: seq=8 ttl=116 time=65.958 ms
64 bytes from 8.8.8.8: seq=9 ttl=116 time=65.518 ms
...
64 bytes from 8.8.8.8: seq=117 ttl=116 time=66.289 ms
64 bytes from 8.8.8.8: seq=118 ttl=116 time=65.826 ms
^C
--- 8.8.8.8 ping statistics ---
119 packets transmitted, 114 packets received, 4% packet loss
round-trip min/avg/max = 48.429/281.002/6588.821 ms
armadillo:~# ping -I ppp0 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=116 time=4774.244 ms
64 bytes from 8.8.8.8: seq=1 ttl=116 time=3781.718 ms
64 bytes from 8.8.8.8: seq=2 ttl=116 time=2781.308 ms
64 bytes from 8.8.8.8: seq=3 ttl=116 time=1781.134 ms
64 bytes from 8.8.8.8: seq=5 ttl=116 time=70.934 ms
64 bytes from 8.8.8.8: seq=6 ttl=116 time=70.163 ms
...
64 bytes from 8.8.8.8: seq=28 ttl=116 time=69.428 ms
64 bytes from 8.8.8.8: seq=29 ttl=116 time=62.068 ms
^C
--- 8.8.8.8 ping statistics ---
30 packets transmitted, 29 packets received, 3% packet loss
round-trip min/avg/max = 61.374/510.987/4774.244 ms
armadillo:~# mmcli -m 0
--------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 691b650f40802dc320676566e3bc27a0d008cdcc
--------------------------------
Hardware | manufacturer: Quectel
| model: EC25
| firmware revision: EC25JFAR06A05M4G
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 865036049341116
--------------------------------
System | device: /sys/devices/platform/soc@0/32f10108.usb/38200000.dwc3/xhci-hcd.2.auto/usb3/3-1/3-1.2
| drivers: option
| plugin: quectel-ec25
| primary port: ttyCommModem
| ports: ttyCommModem (at), ttyUSB0 (qcdm), ttyUSB1 (gps),
| ttyUSB3 (at)
--------------------------------
Numbers | own: 02001011660399
--------------------------------
Status | unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: connected
| power state: on
| access tech: lte
| signal quality: 100% (recent)
--------------------------------
Modes | supported: allowed: 2g, 3g, 4g; preferred: none
| current: allowed: 2g, 3g, 4g; preferred: none
--------------------------------
IP | supported: ipv4, ipv6, ipv4v6
--------------------------------
3GPP | imei: 865036049341116
| operator id: 44010
| operator name: NTT DOCOMO NTT DOCOMO
| registration: home
--------------------------------
3GPP EPS | ue mode of operation: csps-1
--------------------------------
SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
--------------------------------
Bearer | paths: /org/freedesktop/ModemManager1/Bearer/119
| /org/freedesktop/ModemManager1/Bearer/118
| /org/freedesktop/ModemManager1/Bearer/117
| /org/freedesktop/ModemManager1/Bearer/116
| /org/freedesktop/ModemManager1/Bearer/115
| /org/freedesktop/ModemManager1/Bearer/114
| /org/freedesktop/ModemManager1/Bearer/113
| /org/freedesktop/ModemManager1/Bearer/112
| /org/freedesktop/ModemManager1/Bearer/111
| /org/freedesktop/ModemManager1/Bearer/110
| /org/freedesktop/ModemManager1/Bearer/109
| /org/freedesktop/ModemManager1/Bearer/108
| /org/freedesktop/ModemManager1/Bearer/107
| /org/freedesktop/ModemManager1/Bearer/106
| /org/freedesktop/ModemManager1/Bearer/105
| /org/freedesktop/ModemManager1/Bearer/104
| /org/freedesktop/ModemManager1/Bearer/103
| /org/freedesktop/ModemManager1/Bearer/102
| /org/freedesktop/ModemManager1/Bearer/101
| /org/freedesktop/ModemManager1/Bearer/100
| /org/freedesktop/ModemManager1/Bearer/99
| /org/freedesktop/ModemManager1/Bearer/98
| /org/freedesktop/ModemManager1/Bearer/97
| /org/freedesktop/ModemManager1/Bearer/96
| /org/freedesktop/ModemManager1/Bearer/95
| /org/freedesktop/ModemManager1/Bearer/94
| /org/freedesktop/ModemManager1/Bearer/93
| /org/freedesktop/ModemManager1/Bearer/92
| /org/freedesktop/ModemManager1/Bearer/91
| /org/freedesktop/ModemManager1/Bearer/90
| /org/freedesktop/ModemManager1/Bearer/89
| /org/freedesktop/ModemManager1/Bearer/88
| /org/freedesktop/ModemManager1/Bearer/87
| /org/freedesktop/ModemManager1/Bearer/86
| /org/freedesktop/ModemManager1/Bearer/85
| /org/freedesktop/ModemManager1/Bearer/84
| /org/freedesktop/ModemManager1/Bearer/83
| /org/freedesktop/ModemManager1/Bearer/82
| /org/freedesktop/ModemManager1/Bearer/81
| /org/freedesktop/ModemManager1/Bearer/80
| /org/freedesktop/ModemManager1/Bearer/79
| /org/freedesktop/ModemManager1/Bearer/78
| /org/freedesktop/ModemManager1/Bearer/77
| /org/freedesktop/ModemManager1/Bearer/76
| /org/freedesktop/ModemManager1/Bearer/75
| /org/freedesktop/ModemManager1/Bearer/74
| /org/freedesktop/ModemManager1/Bearer/73
| /org/freedesktop/ModemManager1/Bearer/72
| /org/freedesktop/ModemManager1/Bearer/71
| /org/freedesktop/ModemManager1/Bearer/70
| /org/freedesktop/ModemManager1/Bearer/69
| /org/freedesktop/ModemManager1/Bearer/68
| /org/freedesktop/ModemManager1/Bearer/67
| /org/freedesktop/ModemManager1/Bearer/66
| /org/freedesktop/ModemManager1/Bearer/65
| /org/freedesktop/ModemManager1/Bearer/64
| /org/freedesktop/ModemManager1/Bearer/63
| /org/freedesktop/ModemManager1/Bearer/62
| /org/freedesktop/ModemManager1/Bearer/61
| /org/freedesktop/ModemManager1/Bearer/60
| /org/freedesktop/ModemManager1/Bearer/59
| /org/freedesktop/ModemManager1/Bearer/58
| /org/freedesktop/ModemManager1/Bearer/57
| /org/freedesktop/ModemManager1/Bearer/56
| /org/freedesktop/ModemManager1/Bearer/55
| /org/freedesktop/ModemManager1/Bearer/54
| /org/freedesktop/ModemManager1/Bearer/53
| /org/freedesktop/ModemManager1/Bearer/52
| /org/freedesktop/ModemManager1/Bearer/51
| /org/freedesktop/ModemManager1/Bearer/50
| /org/freedesktop/ModemManager1/Bearer/49
| /org/freedesktop/ModemManager1/Bearer/48
| /org/freedesktop/ModemManager1/Bearer/47
| /org/freedesktop/ModemManager1/Bearer/46
| /org/freedesktop/ModemManager1/Bearer/45
| /org/freedesktop/ModemManager1/Bearer/44
| /org/freedesktop/ModemManager1/Bearer/43
| /org/freedesktop/ModemManager1/Bearer/42
| /org/freedesktop/ModemManager1/Bearer/41
| /org/freedesktop/ModemManager1/Bearer/40
| /org/freedesktop/ModemManager1/Bearer/39
| /org/freedesktop/ModemManager1/Bearer/38
| /org/freedesktop/ModemManager1/Bearer/37
| /org/freedesktop/ModemManager1/Bearer/36
| /org/freedesktop/ModemManager1/Bearer/35
| /org/freedesktop/ModemManager1/Bearer/34
| /org/freedesktop/ModemManager1/Bearer/33
| /org/freedesktop/ModemManager1/Bearer/32
| /org/freedesktop/ModemManager1/Bearer/31
| /org/freedesktop/ModemManager1/Bearer/30
| /org/freedesktop/ModemManager1/Bearer/29
| /org/freedesktop/ModemManager1/Bearer/28
| /org/freedesktop/ModemManager1/Bearer/27
| /org/freedesktop/ModemManager1/Bearer/26
| /org/freedesktop/ModemManager1/Bearer/25
| /org/freedesktop/ModemManager1/Bearer/24
| /org/freedesktop/ModemManager1/Bearer/23
| /org/freedesktop/ModemManager1/Bearer/22
| /org/freedesktop/ModemManager1/Bearer/21
| /org/freedesktop/ModemManager1/Bearer/20
| /org/freedesktop/ModemManager1/Bearer/19
| /org/freedesktop/ModemManager1/Bearer/18
| /org/freedesktop/ModemManager1/Bearer/17
| /org/freedesktop/ModemManager1/Bearer/16
| /org/freedesktop/ModemManager1/Bearer/15
| /org/freedesktop/ModemManager1/Bearer/14
| /org/freedesktop/ModemManager1/Bearer/13
| /org/freedesktop/ModemManager1/Bearer/12
| /org/freedesktop/ModemManager1/Bearer/11
| /org/freedesktop/ModemManager1/Bearer/10
| /org/freedesktop/ModemManager1/Bearer/9
| /org/freedesktop/ModemManager1/Bearer/8
| /org/freedesktop/ModemManager1/Bearer/7
| /org/freedesktop/ModemManager1/Bearer/6
| /org/freedesktop/ModemManager1/Bearer/5
| /org/freedesktop/ModemManager1/Bearer/4
| /org/freedesktop/ModemManager1/Bearer/3
| /org/freedesktop/ModemManager1/Bearer/2
| /org/freedesktop/ModemManager1/Bearer/1
| /org/freedesktop/ModemManager1/Bearer/0
armadillo:~# ping -I ppp0 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: seq=0 ttl=116 time=102.335 ms
64 bytes from 8.8.8.8: seq=1 ttl=116 time=56.068 ms
64 bytes from 8.8.8.8: seq=2 ttl=116 time=55.178 ms
...
64 bytes from 8.8.8.8: seq=20 ttl=116 time=66.930 ms
^C
--- 8.8.8.8 ping statistics ---
21 packets transmitted, 21 packets received, 0% packet loss
round-trip min/avg/max = 54.027/67.830/102.335 ms■connection-recover起動後
★15:35頃start armadillo:~# rc-service connection-recover start ... ★何度かping失敗するうちに接続できたので放置 armadillo:~# ping -I ppp0 8.8.8.8 ping: bad address 'ppp0' armadillo:~# ping -I ppp0 8.8.8.8 ping: bad address 'ppp0' armadillo:~# ping -I ppp0 8.8.8.8 ping: bad address 'ppp0' armadillo:~# ping -I ppp0 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=116 time=49.752 ms 64 bytes from 8.8.8.8: seq=1 ttl=116 time=48.325 ms ... 64 bytes from 8.8.8.8: seq=760 ttl=116 time=53.603 ms 64 bytes from 8.8.8.8: seq=761 ttl=116 time=51.393 ms ^C --- 8.8.8.8 ping statistics --- 762 packets transmitted, 752 packets received, 1% packet loss round-trip min/avg/max = 36.342/53.810/293.710 ms ★16:02:43あたりにping停止 ★16:02:59あたりにping再度実行 armadillo:~# ping -I ppp0 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes ^C --- 8.8.8.8 ping statistics --- 13 packets transmitted, 0 packets received, 100% packet loss armadillo:~# date Wed Jul 10 16:03:20 JST 2024 armadillo:~# egrep 'IP address|simple connect|connection-recover' messages ... Jul 10 16:03:41 armadillo user.notice connection-recover: ttyCommModem ping fail Jul 10 16:03:41 armadillo user.notice connection-recover: ttyCommModem reconnect start... Jul 10 16:03:47 armadillo daemon.info [1925]: <info> [1720595027.831387] [modem0] simple connect started... Jul 10 16:03:47 armadillo daemon.info [1925]: <info> [1720595027.831748] [modem0] simple connect state (4/8): wait to get fully enabled Jul 10 16:03:47 armadillo daemon.info [1925]: <info> [1720595027.831828] [modem0] simple connect state (5/8): register Jul 10 16:03:47 armadillo daemon.info [1925]: <info> [1720595027.832003] [modem0] simple connect state (6/8): bearer Jul 10 16:03:47 armadillo daemon.info [1925]: <info> [1720595027.834216] [modem0] simple connect state (7/8): connect Jul 10 16:03:47 armadillo daemon.info [1925]: <info> [1720595027.893835] [modem0] simple connect state (8/8): all done Jul 10 16:03:48 armadillo daemon.info [1925]: <info> [1720595028.015653] [modem0] simple connect started... Jul 10 16:03:48 armadillo daemon.info [1925]: <info> [1720595028.016057] [modem0] simple connect state (4/8): wait to get fully enabled Jul 10 16:03:48 armadillo user.notice connection-recover: ttyCommModem reconnect fail: 4
| ファイル | ファイルの説明 |
|---|---|
| log_connection-recover-start_stop.zip |
at_mitsuhiro.yoshida
2024年7月9日 17時00分
吉田です。
確かに register 以降進んでいない様に見受けられます。
電波品質もある程度ある状況ですので、アンテナの接続を疑うのも難しいです。
お手数ですが、再度 3G/LTE モジュールの初期化を実施いただいて、
https://manual.atmark-techno.com/armadillo-iot-g4/armadillo-iotg-g4_pro…
MCC/MNC を指定した 3G/LTE のコネクションを作成する
https://manual.atmark-techno.com/armadillo-iot-g4/armadillo-iotg-g4_pro…
の手順で docomo 44010 を指定して接続を試してもらえますでしょうか？