If I'm not mistaken, there's already been another discussion about this. I believe it's only available to those with co-term licensing. ... View more

I don't know the reason, I believe what is displayed is the object code in Meraki, but I can't explain why the name isn't displayed. ... View more

Yes, the Cisco Meraki vMX100 has officially entered its end-of-life cycle.     Meraki End-of-Life (EOL) Products and Dates - Cisco Meraki Documentation ... View more

Last question: Does Analytics appear to you? It needs to be enabled to enable API scanning.   ... View more

This is the correct path Network-wide > Configure > General and ensure "Location and scanning . Are you full admin? If you don't enable this it won't work. ... View more

Either your API key is incorrect or you don't have API scanning enabled. I believe it's the latter, as I validated it here and it worked perfectly. ... View more

It's a little further down in Location and scanning. ... View more

You can try it via Powershell   $headers = @{ "Authorization" = "Bearer YOUR_API_KEY" "Accept" = "application/json" } $url = "https://api.meraki.com/api/v1/organizations/YOUR_ORG_ID/appliance/vpn/vpnFirewallRules" $response = Invoke-RestMethod -Uri $url -Method Get -Headers $headers $response ... View more

Is the Scanning API enabled? Network-wide > General       ... View more

Did you add the correct headers?     ... View more

You need your organization ID and in addition you need to create an API key in your dashboard.   https://developer.cisco.com/meraki/api-v1/get-organizations/   http://documentation.meraki.com/General_Administration/Other_Topics/Cisco_Meraki_Dashboard_API   ... View more

The first one is the API and it doesn't load at all, the second one is working as expected.     ... View more

You can check it here.   https://sec.cloudapps.cisco.com/security/center/softwarechecker.x ... View more

Yes, I understand you perfectly, one of the things that bothers me the most is the fact that you can't define different zones for the rules. ... View more

To be honest, there's no tool that "organizes" the rules. Unfortunately (or fortunately, depending on your perspective), Meraki's intention is to simplify things. Can it be improved? Definitely, but I believe this will only happen if everyone who uses MX today joins forces and requests improvements from Cisco. We must understand that whether Cisco modifies or adds new features will depend on customer requests and the number of customers requesting a new feature. ... View more

Your question was not clear, can you provide more details or give an example with a topology? ... View more

Exactly as explained, just click on details and you will be able to set a higher value.   ... View more

This functionality is only available through the Meraki Dashboard, if your MX devices are configured to send syslog data or support SNMP, you might be able to extract ARP-related info from those sources. ... View more

In this case, I think it would be interesting for you to contact Meraki support. ... View more

Without both MXs being in the same organization, this is impossible. There's no way to have the site's hub act as an outbound hub for an MX that doesn't belong to the same organization. Just as there's no way to create a port forward on the MX at site 1 to access the device at site 2. It's not that port forwarding can't be done via S2S VPN, but in this case, since it will be a non-Meraki VPN, port forwarding isn't possible. Even if it were in SD-WAN, it wouldn't be possible. At most, you could do a VPN Subnet Translation. In other words, it's not possible to do what you want. What you might be able to do is install a Linux Strongswan on both sites and establish a S2S VPN between the two servers. I don't know if it's possible to do this with Strongswan, but I think it's worth looking into. ... View more

Meraki updated Access Manager documentation on October 14, 2025, introducing refinements to identity mapping and certificate-based authentication (EAP-TLS) with Entra ID integration. Key changes include:   Stricter identity reconciliation between the client certificate and the user identity stored in Meraki’s local database (synced from Entra ID). Certificate validation logic now checks for:   Matching identity attributes (e.g., username, UPN, device name). Valid certificate chain (no duplicates, disabled signers). Presence of synchronized user attributes from Entra ID.   This means that if the certificate subject or SAN does not match the expected identity format or if there's a mismatch with Entra ID records, authentication may fail, even if the certificate is technically valid.     Access Manager - Cisco Meraki Documentation ... View more

But this is recorded on the firmware update page, right?     ... View more

Everything seems to be working properly on the switch. Can you test this SFP on a device other than the MX85? Perhaps another switch. ... View more

But on the dashboard, can you check if the SFP was recognized? ... View more