Meraki

javalins

Hi @CrazyIvan, MGs are the only Meraki products that support dual SIMs, this call was designed for the MG platform. Still no ability to trigger based on data usage or monitor data usage.

javalins

Make sure you are on the most recent code and if still not success, open up a support ticket. They should be able to pull modem logs and help identify what is happening.

javalins

Can you clairfy what you mean when you say "I already changed the WAN 1 configuration to reflect the IP4 settings on the cellular router?" If there was something connected to the MX64, maybe you have a bad arp table, have you tried rebooting the MX64? If the cellular router just hands off DHCP to the device behind it, then we shouldn't need any configuration of the WAN 1 interface - this should be about as plug and play as plugging in a ethernet connection from a standard SP L3 demark like a DSL Modem.

javalins · ‎Mar 12 2024

@SeeBee69 the ports on the MG are designated as LAN ports. They are not designed in normal functionality to serve as uplinks for the MG, the uplink for the MG is the Cellular Interface. If the MX85 is configured for active-backup on WAN 1 and WAN 2, when WAN 1 fails, all traffic regardless will go over the MG. When WAN 2 (assuming this is where the MG is connected) is in the backup state on the MX, no data outside of the MG's telemetry data would be traversing the cellular link. Firmware updates are released by the PM team typically on a 6-12mo cadence for the MG, we won't know what enhancements are coming until we are closer to that release. We just released MG 3.102 which contains some improvements and bug fixes, more info can be found in the release notes. As for the 6-8MB it is in the document in a blue bubble about midway through.

javalins · ‎Mar 12 2024

There is functionality that can be enabled by support to apply cellular failover rules to WAN2 in this instance. We are working on bringing this into UI in the future.

javalins · ‎Mar 12 2024

The MG51 cellular gateway uses 6 to 8 megabytes a day of data for telemetry on dashboard and connection monitoring when the unit is idle. Any additional Cisco Meraki devices that are added to the MG51 may increase data usage further. Cisco Meraki products are cloud connected devices that report telemetry into Dashboard for network monitoring purposes. The usage will be reduced in future firmware updates. https://documentation.meraki.com/MG/MG_Datasheets/Page_TitleMG51%2F%2F51E_Technical_Specifications

javalins · ‎Dec 4 2023

Most (if not all) SPs do this in their networks, MPLS or Internet core - there could be extra complexity for marginal improvement to the security story doing this at the branch.

javalins · ‎Nov 29 2023

https://developer.cisco.com/meraki/api/get-device-cellular-sims/ You should be able to adjust the "IsPrimary" parameter from true to false and trigger a SIM failover event assuming SIM Failover is enabled. Try it out!

javalins · ‎Nov 21 2023

Did a support ticket ever get opened on this?

javalins · ‎Oct 26 2023

Please do, if this is a defect it will need to be routed to engineering.

javalins · ‎Oct 25 2023

It shouldn't, what code version are you running?

javalins · ‎Oct 17 2023

No Problem, if you have a minute can you please mark this as solved for future Meraki MG customers that might have a similar question? Thank you!

javalins · ‎Oct 17 2023

Not officially. If you have design concerns, I'd reach out to your Meraki Account Team and they can help technically validate what you are trying to do.

javalins · ‎Oct 17 2023

It really depends on your budget, if you want to layer in switches between the MX's and MG's to create a mesh of connectivity, you absolutely can, just scales the price of the solution accordingly.

javalins · ‎Oct 10 2023

@PatWruk what code version are you testing on? There is an icmp issue that was fixed in 3.101..

javalins · ‎Oct 10 2023

Hi @JD4, The MG41 and MG41E have not been announced EOS, as the product was released in 2021, we still have lots of shelf life. In the event of an EOS notification on any Meraki product, there is typically still 5-yrs of life before it goes End-of-Support. Ref: https://documentation.meraki.com/General_Administration/Other_Topics/Returns_(RMAs)%2C_Warranties_and_End-of-Life_Information#:~:text=End%2Dof%2Dsale%20(EOS,for%20sale%20via%20any%20channel tl;dr, No, the MG41/41E is not EOS or EOST.

javalins · ‎Oct 3 2023

A manual fix is available for the RACH issue found in the Telit FN980 Chipset that contains the Qualcomm SDX55 Modem affected by this bug. This bug only impacts MG51 and MG51E devices, and an automated fix to this issue is still being developed. This fix is currently only available to North American customers and requires manual intervention with Cisco Meraki Support. This does require a reboot and will disrupt network connectivity during the reboot process. If you'd like to deploy this fix, please contact Cisco Meraki Support. Details on how to contact Cisco Meraki Support can be found in the link below. https://documentation.meraki.com/General_Administration/Support/Contacting_Support If you have any additional questions or concerns, please reach out to your Cisco Meraki Account team.

javalins · ‎Sep 14 2023

Hi @Netjcp thanks for using the community space. I would suggest in the future this post (or ones like it) to go under Wireless LAN (Meraki MR) instead of Wireless WAN. This Wireless WAN community is focused on the Meraki Gateway and MX-C cellular products and their accompanying software features.

javalins · ‎Aug 18 2023

Meraki is aware of the RACH issue impacting the Telit FN980 Modem. We have worked very closely with Telit over the last few months and understand that the global failure rate of the FN980 chip across all customers is extremely low. We have not experienced any failures as a result of this bug today. In the event of a failure, support has been briefed and the device will be RMAd. Once Radio Firmware LE 1.4 is released, this issue will be patched.

javalins · ‎Aug 17 2023

This should work without issue, just tested.

javalins · ‎Jul 26 2023

Hi @JPScolar, Right now the best way to pull that information is via the API, /organizations/{organizationId}/uplinks/statuses. Assuming that the CP is always WAN 2, you would be able to parse out that information with a simple Python script. Same goes for embedded cellular. Likewise, if you have a Meraki Insight License, you would be able to see that as well. Either a USB 3G/4G modem or built-in LTE (for MX67C/MX68CW only) will be detected as secondary, cellular. But for CP coming in over ethernet, it will just appear as another broadband link. -jv

javalins · ‎Jul 26 2023

Is the device online? Something doable via the API: https://developer.cisco.com/meraki/api-latest/update-device-cellular-sims/

javalins · ‎Jul 11 2023

Hi @RaphaelL, you have posted in the Wireless WAN section (intended for our cellular product families like MG). For better response for MR inquiries, this should be moved into the Wireless LAN community.

javalins · ‎Jun 26 2023

The MG51/51E has an integrated CAT20 LTE modem for failback when 5G is not available, 4G/LTE SIMS will work fine as long as 4ff form factor as noted above. Jamie

javalins · ‎Jun 26 2023

This would provide active-active-backup, which gets you to three. @Speakup11 is the goal 3 Active Uplinks? Or just have a third uplink as an option? If we aren't concerned about the number of active carriers at a single point in time, either the solution above by @PhilipDAth or @cmr achieves that.

About javalins

javalins

Community Record

Badges