Meraki

alemabrahao · ‎Aug 26 2025

You're right, I forgot that detail.

alemabrahao · ‎Aug 26 2025

I can only think of two possibilities: cloning the existing profile or neromear. Can you take this test?

alemabrahao · ‎Aug 26 2025

Even though you're editing an existing profile, Meraki sometimes interprets the action as an attempt to create a new profile with a duplicate name, especially if you're making changes that affect how the profile is applied across devices.

alemabrahao · ‎Aug 26 2025

Take a look at the end of the page and you will see the mounting accessories options. https://meraki.cisco.com/pt-br/product/security-cameras/outdoor-security-cameras/mv93/

alemabrahao · ‎Aug 25 2025

So, it's no possible. Meraki does not expose expiration dates for users authenticated via Google OAuth through the Dashboard API.

alemabrahao · ‎Aug 25 2025

Take a look at this API. https://developer.cisco.com/meraki/api-v1/get-network-meraki-auth-users/

alemabrahao · ‎Aug 25 2025

First, never share your equipment's serial number publicly. Second, I believe it should be on the equipment box or label.

alemabrahao · ‎Aug 25 2025

Currently, Meraki does not offer a built-in alert or report specifically for cameras with retention below a threshold like 90 days. But you can use the Dashboard API to pull retention settings and motion data per camera or create custom reports using the API to flag cameras with estimated retention below your desired threshold. Take a look at the benefits of Smart Retention. Smart Retention - Cisco Meraki Documentation

alemabrahao · ‎Aug 24 2025

Please contact the Meraki support.

alemabrahao · ‎Aug 23 2025

The problem isn't the device license; you need one for the dashboard as well. You probably didn't purchase that license. https://documentation.meraki.com/General_Administration/Organizations_and_Networks/Organization_Menu/License_Info_Page_-_Co-Termination_License_Model#Organization_License_Information

alemabrahao · ‎Aug 23 2025

You need to contact Meraki support. https://documentation.meraki.com/General_Administration/Support/Ways_to_Contact_Meraki_Support

alemabrahao · ‎Aug 23 2025

Once a customer converts to per-device licensing, they cannot convert back to co-termination licensing model. https://documentation.meraki.com/General_Administration/Licensing/Meraki_Per-Device_Licensing_Overview/Meraki_Per-Device_Licensing_-_Configuration

alemabrahao · ‎Aug 22 2025

I've already set it up this way and it works perfectly.

alemabrahao · ‎Aug 22 2025

Yes, the Meraki MS425 supports flexible stacking, and once you configure the stacking ports via the Meraki Dashboard, those settings persist on the switches even before the physical stack cables are connected and the MS425 does not have dedicated stack ports. Instead, any port can be configured as a stack port. Switch Stacks - Cisco Meraki Documentation

alemabrahao · ‎Aug 22 2025

Are you right that this model does not support VRRP, that was one of the reasons that led me to my interpretation? @Daniel23 Can you explain how you configured one as active and one as standby? Please.

alemabrahao · ‎Aug 22 2025

What I mean is that he wants to replace one device with another in case of failure, not that he wants to configure VRRP. That's why I asked him to correct me if I'm wrong. I know that for VRRP you need license for each MS.

alemabrahao · ‎Aug 22 2025

I don't think he's talking about warm spares, but rather replacing one with the other in case of failure. But correct me if I'm wrong.

alemabrahao · ‎Aug 22 2025

If both switches are the same model, yes.

alemabrahao · ‎Aug 22 2025

I strongly believe that the problem is not with Meraki, but with the devices, after all roaming is still a device decision. Or a problem with your network design.

alemabrahao · ‎Aug 22 2025

It's not possible. What you can do is try to create a new template, but even then, you won't be able to create a new template that overrides the current template's range (as far as I can tell). In short, either remove the devices from the template, adjust it, and then add them back, or you'll have to perform a REIP of the network.

alemabrahao · ‎Aug 21 2025

You can try enumerating all networks in the organization using GET /organizations/{organizationId}/networks And then try GET /networks/{networkId}/appliance/dns/local/status This should reveal the active profile ID even if the organization-level assignments endpoint fails. If a match is found, POST /organizations/{organizationId}/appliance/dns/local/profiles/assignments/bulkDelete with the correct assignment ID (if recoverable), or manually remove the assignment through the network-level configuration, if possible.

alemabrahao · ‎Aug 21 2025

GET /organizations/{organizationId}/appliance/dns/local/profiles/assignments This returns all current profile-to-network assignments. Each item includes assignmentId, network.id, and profile.id POST /organizations/{organizationId}/appliance/dns/local/profiles/assignments/bulkDelete And This to unassign these networks using the bulkDelete endpoint.

alemabrahao · ‎Aug 20 2025

I believe it is worth reading some materials. https://meraki.cisco.com/product-collateral/mt-family-datasheet-20220308-english/?file https://documentation.meraki.com/MT/MT_General_Articles/MT11_Temperature_Calibration

alemabrahao · ‎Aug 20 2025

There is no magic formula, it all depends on the customer's needs. But your line of thinking is correct.

alemabrahao · ‎Aug 20 2025

If you're talking about registering and managing these devices through the Meraki Dashboard, that's exactly what you're talking about. You can't add third-party devices.

About alemabrahao

alemabrahao

Alessandro Abrahao

Community Record

Badges