Meraki

Ryan_Miles · ‎Mar 26 2025

That deck is talking about Cat persona APs using their built in Sensors. Not MT Sensors. Today, MT Sensors can only communicate with Meraki persona APs and Cameras.

Ryan_Miles · ‎Mar 25 2025

That's incorrect

Ryan_Miles · ‎Mar 20 2025

fixed

Ryan_Miles · ‎Mar 20 2025

Yeah I noticed it's not documented either. Might be an upcoming call or one that is bound to be removed/changed. So, I'd just say keep that in mind. As for the expiration date is that only on the Org you mentioned having a trial or had a trial in the past? All my Orgs are reporting correctly with the call. The co-term ones at least. PDL doesn't show because there is no single expiration date. Not sure how a Sub Org would display.

Ryan_Miles · ‎Mar 19 2025

I don't have a subscription Org in my lab, but I do have co-term and PDL orgs and this endpoint displays the mode (model) each Org is in. Not sure if a subs Org shows as such. You'd have to test. https://api.meraki.com/api/v1/administered/global/overview/licensing/overview/byOrganization

Ryan_Miles · ‎Mar 19 2025

@aplannet Access Manager is starting to roll out to Orgs via the Early Access page. It's not yet available on all Orgs/shards. So, if you don't see it yet it will be coming. Or, you can also reach out to your Cisco team and they can help. https://documentation.meraki.com/Access_Manager With Access Manager you can sync to your Entra deployment and tie that into SSID 802.1X auth now.

Ryan_Miles · ‎Mar 18 2025

Depends if you use local Admins or SAML SSO. Both forms of Admin config are documented here https://documentation.meraki.com/MV/Advanced_Configuration/Restricting_Access_to_Cameras Org > Camera and sensor roles is specifically for SAML and not for standard local Admin accounts.

Ryan_Miles · ‎Mar 12 2025

@MartinLL thanks for testing and confirming. Our documentation mentions three permissions and the first one in my screenshot isn't part of that. Not even sure how that one got in my tenant config. I've since removed it and aligned to only what's mentioned in our doc. Also removed my screenshot as to not confuse matters. And I'm using the free Entra tier as well 👍

Ryan_Miles · ‎Mar 11 2025

@MartinLL I (and some others) had the same thing and had to edit the API permissions then it synced fine. Actually, this is covered in the doc now.

Ryan_Miles · ‎Mar 7 2025

All this new RBAC stuff is for local admins, not SAML.

Ryan_Miles · ‎Mar 7 2025

Is the role in dashboard and your IdP exactly the same? Meaning for example sitea_viewlive;siteb_viewexport. I've done this in several IdPs and they all work the same. As long as the role in the IdP is the semicolon separated list of exact names from dashboard it should be working. If you look at the SAML login history in dashboard, find a recent login, then view the XML and look for the roles section near the end do you see the multiple roles? If yes on one line with semicolons or separate lines? If it's on separate lines it's not configured correctly and won't pass multiple roles and will only honor the first role matched.

Ryan_Miles · ‎Feb 28 2025

I've seen this workaround used in the past for this exact issue Create new entity ID with an alternate URL. Example, https://dashboard.meraki.com:443/

Ryan_Miles · ‎Feb 25 2025

You can track the status of the hosting site here https://mindtouchext.statuspage.io/

Ryan_Miles · ‎Feb 24 2025

The MG runs its own DHCP server. If you connect the MG to a switch connect it to a dedicated L2 VLAN. Any other switchport in that VLAN/containing that VLAN will have access and be able to act as a client to the MG. Example, a MX or direct clients. Many different topology examples can be found here.

Ryan_Miles · ‎Feb 20 2025

I too checked many Orgs on many shards and not seeing the issue. If you still are seeing this I would contact Support ASAP.

Ryan_Miles · ‎Feb 20 2025

Did you add a new hub with a subnet that overlaps with the template subnet?

Ryan_Miles · ‎Feb 20 2025

You'll typically get that error when a hub is advertising a supernet through the VPN Local Networks section. Basically, to avoid this your hub needs more specific advertised routes that won't conflict/overlap with spoke subnets.

Ryan_Miles · ‎Feb 7 2025

I have a slide deck that explains/shows how to use option 119 https://docs.google.com/presentation/d/1PCKpBIodgG1SZxS5f1jv46_aILz9CcJw5JS0Ve4NxRI/edit?usp=sharing

Ryan_Miles · ‎Feb 7 2025

You can use any of the LAN ports. Just ensure they have the same config (access or trunk, same VLAN config, etc). Example from MX95

Ryan_Miles · ‎Feb 6 2025

Eng is working on a fix.

Ryan_Miles · ‎Feb 6 2025

Seeing the same here. Also see at least one Support case opened today on it. I would suggest opening a Support case to get more evidence of it occurring.

Ryan_Miles · ‎Feb 4 2025

Yep, totally doable. As you stated you can't do a VIP on the WAN without the extra IPs. But basic HA will work fine.

Ryan_Miles · ‎Feb 1 2025

You'd get a faster resolution by opening a Support case with Meraki. That way the Engineer can see your network and config and help with troubleshooting.

Ryan_Miles · ‎Jan 24 2025

Here's a practical example of what @GreenMan mentioned using the License Calculator Your current state expiring 2025.10.02 If you were to "Add" a MX84 with a 7 year license it would bump the entire Org to 2026.04.18 adding a little over 6 months to the entire Org. You could of course accomplish this in many different ways using different model licenses and durations. My example is just a basic one.

Ryan_Miles · ‎Jan 21 2025

You really shouldn't post your Meraki serials or MACs in any public forum. Both can be claimed by anyone. Also, if you intend to sell the gear it needs to be unclaimed from any Org so the purchaser can claim it.

About Ryan_Miles

Ryan_Miles

Ryan Miles

Community Record

Badges