Meraki

GreenMan · ‎Jan 28 2022

The Dashboard itself holds the backups (and backups of the backups). In fact, the backup is created before the live config; config is created in Dashboard, then pushed down to the device. It is possible to take details of configs out of the Dashboard via the API, but the API would still need to be used to apply them back again, too. There are a bunch of scripts out there that can be used for this purpose, not least one created by the legend that is @PhilipDAth https://www.ifm.net.nz/cookbooks/meraki-backup.html (can you update the link, if I've pasted an old one, Philip?)

GreenMan · ‎Jan 26 2022

For co-term Orgs, I'd claim licences (or orders / serials) using https://developer.cisco.com/meraki/api-v1/#!claim-into-organization

GreenMan · ‎Jan 26 2022

An intermittent performance problem or capacity issue with your WAN, maybe? Assuming both your DNS and RADIUS servers are in some centralised datacentre...

GreenMan · ‎Jan 25 2022

I'm referring to the default gateway of the host devices at each end. The static route on your switch will indeed supersede its default route (provided the destination traffic matches that defined in the route) but if your client or your server isn't sending it's traffic to the Layer-3 switch where that route is configured, it won't help you. Look at the default gateway of your client and server, then check the routing table on the configured gateways: check that they have a route to the other end, via the next-hop Meraki switch.

GreenMan · ‎Jan 25 2022

As @ww said - they should work fine, but you'll need to configure your existing networking gear to allow the MV cameras access to the necessary Meraki resources in the cloud (PoE, DHCP & routing, DNS etc. ) Plus any firewall rules necessary - shown under Help > Firewall info in the Meraki Dashboard.

GreenMan · ‎Jan 25 2022

Have you got the hosts at each end configured with the correct default gateway? (i.e. the Meraki switch at each end) Either that or, if they have an existing gateway, which you can't change (a firewall maybe?), you'll need an extra route on there, pointing the appropriate subnets (those at the other end of the link) to the local Meraki Layer-3 switch.

GreenMan · ‎Jan 20 2022

Use Tags para configurar qué redes construyen un túnel a qué pares Non-Meraki https://documentation.meraki.com/MX/Site-to-site_VPN/Site-to-Site_VPN_Settings#Peer_availability

GreenMan · ‎Jan 20 2022

You could maybe use AnyConnect VPN into the MX. With RADIUS authentication, it would be possible to use Meraki Group Policies to apply a different set of network access controls to contractors, versus your employees, if that's the primary concern. https://documentation.meraki.com/MX/AnyConnect_on_the_MX_Appliance#Group_Policies

GreenMan · ‎Jan 20 2022

Yes - both of those things are available, while the device remains licensed. Note the End of Support date for the MX100: Feb 1st 2027 Given the 3-yr license you mention, the MX would likely need re-licensing between now and then. Although the hardware is End of Sale, you should still be able to purchase licensing.

GreenMan · ‎Jan 19 2022

Why do you have so many IP addresses assigned to one interface on one PC? This is extremely unusual, unless I'm missing something; The rest of the world, for one PC with one interface uses just one IP address. If that PC requires access to multiple IP subnets, you provide routing within your network, via a Default Gateway.

GreenMan · ‎Jan 19 2022

Yes - when you do a renewal, the co-termination date will move out into the future. Bear in mind though that if you only renew the MXs you mention, your Dashboard will be out of compliance and you will go straight into the 30-day grace period. If you aren't using the MX250 and the wireless APs that you say you won't be renewing, you should remove them from the Networks to which they are assigned (you can leave them in the Inventory, unassigned) Basically; check that the Current device count column matches what you want to keep working, after you apply the renewal and make sure the renewal license covers all of those items. Don't forget too - the MX licences must be Advanced Security ones. If you do need the MX250 and the APs to carry on working, after the renewal you must include them in the order for the renewal licences. Basically - you can only Renew an entire co-termination Organization. Any remaining time left on the devices you do renew will be rolled into the updated co-termination date.

GreenMan · ‎Jan 4 2022

There are a number of other endpoints relating to MV cameras - have a look here: https://developer.cisco.com/meraki/api-v1/#!get-device-camera-analytics-live (look under Camera > monitor and > Configure on the Left Hand Side.) You should find this page really useful for reviewing (and trying) available API endpoints across the whole Meraki portfolio, too. Note; I'd suggest switching fully to v1 endpoints; v0 has been deprecated for over a year and is scheduled to sunset in about a month's time. There are a number of calls also available for MT sensors, but they are currently beta, I believe and you would need to apply via your Meraki account team to have this enabled in the required dashboard. I would also recommend that you look into the capabilities available through the MV Sense license (which you can try via free licences included with your cameras) and MQTT more generally: https://developer.cisco.com/meraki/mv-sense/#!mv-sense-overview

GreenMan · ‎Dec 10 2021

I would suggest you contact your Cisco & Meraki partner account team - and also similar for the big customers in question (to get more weight behind your ask). I can't help thinking also that, if you're wanting to automate your processes using API, why not do that for all the Networks, individually, rather than manipulating Templates via API as an interim step? I can see you have big customers, which may make a difference, but it's generally the case that people use Templates until they doesn't really do what you need (and most can keep the number of Templates to a manageable number, where they work ok) but then move solely to API, to manage at scale, if not.

GreenMan · ‎Dec 10 2021

MX appliance utilization is shown under an appliance Network-specific Organization > Summary report. More info here: https://documentation.meraki.com/MX/Monitoring_and_Reporting/Device_Utilization

GreenMan · ‎Dec 10 2021

You should have a look through the Organization > Monitor > Change log to see who disabled it. If you can't find anything there, find the port in the Dashboard and look at the Event log for it (through live tools, top centre of the page)

GreenMan · ‎Dec 2 2021

No - @PhilipDAth describes the capabilities accurately; connectivity via one SIM or the other, not both. I believe 5CA is more like the cellular version of using multiple 20 MHz-wide channels in WiFI (40 MHZ, 80 MHz etc.) to achieve higher throughput. https://www.4gmobiletech.com/carrier-aggregation

GreenMan · ‎Nov 24 2021

If you configure a switch port as access, rather than trunk, it automatically sets the equivalent of portfast: https://documentation.meraki.com/MS/Deployment_Guides/Advanced_MS_Setup_Guide#Automatic_edge_port I would concur with running DHCP on your MX, if you have one. If your chosen MX is sized appropriately, as per the Sizing Guide, DHCP performance should be very good: https://meraki.cisco.com/product-collateral/mx-sizing-guide/

GreenMan · ‎Nov 24 2021

@antonis_sp is right - this is absolutely not the way to do it. The ANT-27 is fine, in general, but you'd need two of them and you need to point them in the same direction.

GreenMan · ‎Nov 23 2021

As you have to purchase Meraki licensing, to work with Meraki devices at all - and the licensing, provides you with the Dashboard and all the infrastructure that hosts it - and Dashboard has a built-in 'API Gateway', with which all your Meraki devices interact by default... I'm not sure why you'd want to build you own, even if you could? (Note; Meraki devices are essentially managed solely via our cloud infrastructure, in order to keep the platform secure) The Dashboard natively provides (Organization > Summary) reports via the GUI, which can be modified, to a certain degree and scheduled. If you want ultimate flexibility with data reporting, such information can virtually all be accessed by combining different combinations of endpoints pulled via the Dashboard API, which you can then manipulate freely at your end.

GreenMan · ‎Nov 22 2021

If, by this enquiry, you mean: "Can my Meraki devices interact, via (NB) API, directly with a controller other than the Meraki Dashboard?" No - Meraki devices work via the Dashboard. Given that the Dashboard itself has a wide range of API inputs and outputs however, it it possible to understand dynamically what's going on with a device (via Dashboard and the REST API) and then implement a related change to that device (via Dashboard and the REST API). Does that help?

GreenMan · ‎Nov 15 2021

It's important to understand who owns the licensing here, currently - licences are not transferrable ( see the End User Agreement linked here: https://meraki.cisco.com/support/#policies:eca ) If the customer already owns the licensing then either pass on Admin control of the existing Organization - as per @BrandonS ' suggestion, or have Meraki Support 'move' licences from the existing to a target destination, by raising a Support case. Bear in mind that the latter option requires that the Admin raising the case with support have full permissions in both Organizations: https://documentation.meraki.com/General_Administration/Licensing/How_to_Request_a_License_Transfer

GreenMan · ‎Nov 15 2021

Devices enrolled into Systems Manager appear (for MDM purposes) primarily under Systems Manager > Monitor > Devices, within the relevant SM network in your Dashboard. Your device would only appear under Network-wide > Clients if it's a Combined network and it is physically plugged into a Meraki switch managed in the same Network. The latter functionality would essentially have no relationhip to SM specifically.

GreenMan · ‎Nov 11 2021

I don't know of a way to do precisely what you're asking, by way of tagging in SM. About the most effective method I've found for encouraging staff to use the right SSID is simply to make the recommended SSID better suited to their needs, e.g: Set the Guest SSID to require them to login and re-login every few hours Apply more rigorous traffic shaping / firewall rules to guest clients Make the recommended SSID as seamless a signon experience as possible (use Trusted Access, for example?) - and loosen traffic shaping constraints.

GreenMan · ‎Nov 11 2021

It sounds like they are probably referring to the processing power of your firewall, rather than any specific compatibility. Your new APs are very likely capable of carrying significantly more traffic than any they are replacing. How much of that extra capacity your wifi client base can realistically make use of will depend on your device mix and how they are used (what apps etc). You have to think that those devices will become more capable, over the years though, as they're replaced. Moreover, you may well be (more) constrained by your available Internet uplink, beyond your firewall. If your link is just 100 Mbps or so, how will a Gig-capable firewall help? That having been said, your Internet pipe will probably be upgraded, within the lifespan of your APs and a replacement firewall anyway. I try to think about your whole traffi-flows and any bottlenecks along the way. Bear in mind too that you needn't necessarily upgrade the existing Fortigate with a new Fortigate; what about an MX? 😏

GreenMan · ‎Nov 10 2021

Yeah - I don't believe that combination is possible. You would like to use source-based default routes, but they can only be defined via another MX (an AutoVPN tunnel) or a LAN port, not a non-Meraki VPN tunnel, as here. Is there a reason why you can't run the DHCP on the MX, as I suggested? It's the closest you will get to the traffic pattern you want, right now, I think.

About GreenMan

GreenMan

Community Record

Badges