I have not had any dealings with T-Mobile, but for other US carriers, I have told them I want to activate a hotspot device and here is the IMEI number for it. Sometimes they want to see the device and other times they have not. You also need to tell them it is for business and not personal use and that should get you a better level of service from the carrier, but not always. The nice thing about the new MG52 is that you can now provision the ESIM on it with AT&T directly from the Meraki dashboard and never have to speak with anyone at AT&T. Right now it's $65/month for 100 megabits of bandwidth on AT&T and it says that coming soon that will increase to unlimited bandwidth for $65/month. ... View more

MX 19.1.3 is an early beta firmware. I have had to recently migrate several customers that were early adopters back to 18.211.2 due to several different problems, so the problem you experienced likely occurred due to bugs in it too. ... View more

You can send an email to Certifications@meraki.com to see if they can get it for you. ... View more

I ordered some Z4s recently for a customer in the US and they came with power cords, so I assume this applies to the Z4C too. ... View more

When will AFC support for 6 GHz be incorporated into the 31.x firmware versions?   ... View more

The Z4 with the Security License is specifically designed for a home office worker. It provides wired, wireless and VPN access. The Z4C also adds a backup internet connection via cellular. ... View more

If you have an Insight license assigned to your MX, you can go to the WAN Health section under the Insight tab and run a speed test, but it is only for the download speed.   ... View more

I will be there. Looking forward to it! ... View more

I had a customer that had to rollback to 18.210 this morning because 18.211 broke site-to-site AutoVPN. He told me Meraki TAC told him that they have a number of customers experiencing issues with this version today. I installed it on all of my company's MX and it is working fine for us and we have one AutoVPN connection that is also working fine. My advice is to test it on non-production networks first to see if your environment is impacted. ... View more

I could not reach cisco.com from Oklahoma until I removed the Hong Kong country from my layer 7 rules. I'm pretty sure the closest Akami Edge node to Oklahoma is not in Hong Kong. It took me several hours on Tuesday to figure this out because some geolocation services were correct and others were not. I finally found one of the bad geolocation services that showed the IP address in Hong Kong. As soon as I removed that country, I could reach cisco.com again. Very frustrating. ... View more

I agree. I think both settings do work together to contribute to the total client count.  ... View more

I believe this setting only impacts how the switch(es) monitor clients and does not have anything to do with how the MX tracks clients. There is a separate setting for MX client tracking. ... View more

I ran into this recently. This impacted me when I was trying to upgrade the code on an MS320 switch. The switch kept failing to upgrade because too much memory was be used trying to keep up with all of the clients. Go to switches > configure > switch settings Look at the last option on the bottom of that screen "network client sampling". Make sure it is set to "Exclude uplink interfaces", which is supposed to be the default. If it is set to "all interfaces" you make want to think about changing it. Making this change does not cause an instant impact. It can take up to 24 hours for this to clear up. Let us know what you find? ... View more

Tik Tok also needs to be added to the social web category too. ... View more

I plugged the MG51E into the MX WAN2 and immediately got IPV4 and IPV6 addresses on it. So it is confirmed that the MG51E can provide an IPV6 address and it does not show up on WAN3 on the MX. ... View more

I have implemented this on my MX85 and it is working fine, now. I inserted the Copper SFP in Ports #1 and #2, rebooted the firewall and moved the ethernet connections over to the SFP ports. Once I verified those were working again, then I switched over to Multi-WAN and connected my MG51 to Port #4. The MX was able to pull an IPV4 address from the MG51 NAT Pool. I tried disconnected the ethernet cables from both SFP modules and the firewall did not switch over to WAN3. The firewall completely dropped off the internet and the dashboard. I connected both internet ethernet cables back to the MX and once those came back up and the MX was visible on the dashboard, I rebooted the MX again. Once the MX came up, I tried again to unplug both internet ethernet cables and this time the firewall did switch over to WAN3. It also sent an email alert stating that it had switched over to the cellular port. In this case that is correct, but I think the alert should say WAN3 and not the cellular port. I connected the two internet ethernet ports back to the MX and it immediately started using them again. So a second reboot of the firewall after switching to Multi-WAN seems necessary for the failover to WAN3 to work correctly.   One bug that I see is that even though IPV6 is enabled on WAN3, the MX is not pulling an IPV6 address from my MG51, which is getting an IPV6 address from the cellular carrier and is enabled to pass IPV6 through to the MX.   Overall, the implementation of Multi-WAN is not too bad, but finding out that a second reboot of the firewall is necessary for the failover to work was a nasty surprise that will likely impact many customers that choose this feature. Maybe this is also a bug that will be fixed in future firmware versions? ... View more

If the MX95 is powering the MG21E, you would need a power injector to provide it power in the standalone configuration. ... View more

Her Here's a snapshot from a customer's dashboard. They only have Starlink at their house and they are using a site-to-site VPN connection back to their office. You can clearly see the 100.67.251.73 CGNAT IPV4 address that Starlink is providing. They have been using this for over a year. MX75 on one side and MX67 on the other side of site-to-site VPN. No complaints from the customer on this and they would tell me if they are having problems. Starlink dish is directly connected to WAN1 port on the MX. ... View more

Another Cisco solution is Duo Device Health:  https://blogs.cisco.com/security/enforce-endpoint-compliance-and-cyber-hygiene-with-duo-device-trust   ... View more

Take a look at this article: https://community.meraki.com/t5/Security-SD-WAN/Connecting-to-VPN-from-Windows-11/m-p/173543 Microsoft took away some of the settings in the native Windows 11 VPN client that were present in the Windows 10 VPN client. But if you run the rasphone.exe program, you can set the additional configurations items that are needed to connect to an MX from Windows 11. I have customers that are connecting to MX appliances from Windows 11 computers using the native VPN client everyday and it works fine. ... View more

I have Starlink service too and they made a change in the past where only one device can obtain an IPV4 CGNAT DHCP address from the Starlink dish. It's first come, first serve, so which ever device is first to request a DHCP address from the Starlink service is the winner. I have my Dish connected directly to the WAN 2 port on my MX85. Another other option is to move up to the business class Starlink service. You still have to rely on a DHCP address, but it will be a real public IP address. And then their is IPV6, where you will get a /56 block of addresses. This document from Starlink provides more information about your options:  https://starlink-enterprise-guide.readme.io/docs/ip-addresses   ... View more