Re: SIM Reconnection Issues (Modem Manager 1.20.4)

2024-03-19 Thread Aleksander Morgado
Hey Armand,


>
> Find attached a .zip with 4 logs files:
>
>- *mmlogs_P2.log*: is the ModemManager logs for one of the boards
>(board P2)
>- *nmlogs_P2.log*: is the NetworkManager logs for the board P2 (board
>P2)
>- *mmlogs_P4.log*:  is the ModemManager logs for the other board
>(board P4)
>- *nmlogs_P4.log*: is the NetworkManager logs for the board P4 (board
>P4)
>
> For both of the boards we have reproduced the same scenario in paral·lel
> with the same enabling/disabling SIM times.
>
> The logs start Monday March 11th, at around 2:29 PM UTC for both boards.
> At this point, SIMs are enabled, and get connected.
> Then, aproximetly 3-4 min later, at 2:32 PM UTC, both SIMs are disabled
> remotly:
>
>- For board P4, the epoch where the state changed is
>[1710171130.242576] [modem0] state changed (connected -> registered)
>- For board P2, the epoch where the state changed is
>[1710171121.444769] [modem0] state changed (connected -> registered)
>
> The SIMs are now disabled for an entire day. This is now March 12th, at
> around 8:06 AM UTC. We enable both SIMs.
> In the logs, nothing changes. We leave it be for around 3 more hours to
> see if at some point it is reconnected, but nothing changes.
>
>
The modem is initially registered and connected with the Movistar network
(21407). When the EMnify SIM card is disabled, we get kicked out of the
network and eventually fully unregistered (registration_reject_cause =
'no-suitable-cells-in-location-area'). This process looks good enough to me.

When the SIM card is enabled again, there is obviously no way to ask the
modem to explicitly start a new registration with the Movistar network. We
need to fully rely on the modem's own network search and selection logic.
The problem here is that the modem ends up trying to register with *other*
networks, and eventually it ends up registered with "limited" capabilities
(e.g. for emergency services only) with Vodafone (21401).

I don't have the 3GPP knowledge about this at hand, but I'd guess that
no-suitable-cells-in-location-area instructs the modem not to attempt
registering with the network any more.

Can you try to repeat the test, but once re-enabling the SIM card, run an
airplane mode cycle through NetworkManager, e.g. "nmcli radio wwan off",
wait some seconds and "nmcli radio wwan on". That should put the modem in
low power mode and then back on again, and it should very likely reset any
network-specific state that was cached in the previous run.

-- 
Aleksander


Re: ModemManager Issue with multiple WWAN Sierrawireless Ubuntu 22.04

2024-03-19 Thread Ankur Jain
Thanks, Aleksander for your reply, I will check with them.

BR,
Ankur

On Fri, Mar 8, 2024 at 3:06 PM Aleksander Morgado 
wrote:

> Hey Ankur,
>
> >
> > I want to report an issue with the modem manager in Ubuntu 22.04. Even
> though the modem firmware is updated, the modem manager service causes
> frequent disconnection issues. However, when I disable the modem manager
> service and use qmicli and minicoM methods, the modem works fine without
> any disconnections. I tried contacting the modem using Sierra MC7304 &
> MC7430, but it did not solve the problem. The modem manager provides all
> the necessary details, but it keeps resetting frequently when I use the
> internet or live streaming applications.
> >  I would appreciate your support in resolving this issue.
> >  Please let me know if you require any additional information or logs.
> >
>
> I'm afraid there is not much we can do, if the issue is the modem
> crashing. You said that using qmicli or AT commands makes it more
> stable, so it could really be related to some of the setup MM does,
> but even in that case, only the manufacturer will be able to analyze
> the modem crashes. The best path forward you have would be to contact
> Sierra support so that they guide you in how to retrieve modem traces
> they can analyze :/
>
> The MC7304 is one of the modems that I test on every MM release, and I
> haven't noticed any strange myself, but of course my network
> conditions are not the same as yours.
>
> --
> Aleksander
>


Re: ModemManager hangs SIMCOM A7602E-H modem

2024-03-19 Thread Aleksander Morgado
Hello Artem,

> I am trying to get SIMCOM A7602E-H modem to work with ModemManager 1.14.12 
> and the problem is the modem hangs after some time unless power cycled. If I 
> disable ModemManager, the modem is working for a long time.
>

Any chance you can get MM debug logs to see if any of the requests we
send is the culprit?
https://modemmanager.org/docs/modemmanager/debugging/


-- 
Aleksander