Connor
Hi there. Update.
So, when using the multi-carrier SIMs, originally we weren't able to get them connected, the MG21 status page showed a connection to a network but WAN IP, no DNS and obviously no Meraki cloud visibility.
Had a call with our partner, had a play with the backend IP stack and allocation on our roaming SIMs, and all now working with just the APN, IP as 'ANY' and with no username and password. All ok.
What we are looking at now is the multi-carrier element to the SIM e.g. if say, a network mast was being work on by an engineer this could take down connectivity to that mast, so the 'multi-carrier' element would kick in.
In testing we tried to initiate this by forcing the SIM to use an alternate network (that had signal) to force over the carrier to use another. This was sort of working, but sometimes needed manual intervention or refreshing from the local status page. Further testing required. And ideally, we don't want to have keep asking end users to reboot the PoE injector for the MG as this isn't practical nor wanted.
What would be good, and I have heard of mention of scripting within the MG21 to auto reboot if a signal is lost (but not found this yet), which would be one thing, but it would be amazing if there was better control of the MGs to do things e.g. reboot, like we can with APs etc, but as the WAN ports of the MXs aren't PoE, this can't be managed via the dashboard to 'shut' and 'reopen' that port to force an MG21 to power cycle if the MG21 had lost cellular connectivity like we could if one a switch?
Anyway, for the forum and interest, I will update you once I know the best format.
Cheers
A