The boot time is variable depending on the platform, most MS switches I'd say are 3-5 minutes, IOS-XE could be longer ~10-15, but all of that can also depend on firmware CS IOS-XE will be slower than regular IOS-XE, etc. To be clear the switches don't gain their config, they will have it already. Unless you are making changes while they are offline they will boot up and not need to apply any new config. If they all  boot simultaneously they will come online nearly simultaneously. If you have concerns that devices won't recover correctly if the network is not fully online, I suggest you have them powered off or just inform the end users that they may need to reboot first thing. ... View more

Presuming you mean Meraki only has the mac and IP from seeing what switch port it's on, then yes, you will need to get up there and look at the device. ... View more

Here is the main documentation page for Workflows: https://documentation.meraki.com/Platform_Management/Workflows It's basically a set of tools that put common api actions into a more user friendly and/or prebuilt format. This specific automation would be a way you could tag your networks in your own way (say release rings or geography) and then schedule the updates. To do what you want (upgrade everything once a new stable is released), you'd need to add a bit more logic to read the stable firmware versions and then when it changes push the update. I'm not actually aware of an API Endpoint that has this info, although I could be missing something. ... View more

I've used it at a client and it was as simple as setting up the third party vpn with a 0.0.0.0/0 remote subnet listing. You seem to have resolved the one problem you were having, is there something specific you are looking for insight on? This wasn't available when I used it, but you may want to look at VPN exclusions for certain known traffic to optimize performance: https://documentation.meraki.com/SASE_and_SD-WAN/MX/Design_and_Configure/Configuration_Guides/Site-to-site_VPN/VPN_Full-Tunnel_Exclusion_(Application_and_IP%2F%2FURL_Based_Local_Internet_Breakout)  ... View more

That changed earlier this year with 19.1. They added SEC to vMX and made it mandatory for SEC or SDW orgs to have SEC vMX. https://documentation.meraki.com/Platform_Management/Product_Information/Licensing/Meraki_Licensing_FAQs In the middle of the big blue box. ... View more

Depends on the quantity of SFP ports needed. If it's 2 or 3 drops sure maybe, also depends on how far things need to be. ... View more

For connection to the cloud they just need internet. I'm not aware of any feature that requires the APs be able to talk to each other directly.  Example: https://documentation.meraki.com/Wireless/Design_and_Configure/Architecture_and_Best_Practices/Seamless_Roaming_with_MR_Access_Points The requirements for roaming have no need for direct communication. ... View more

Is the DDNS updating? if not, contact support If the DDNS is updating, there could  be some sort of ISP issue, especially if you are using the older client vpn. What is your secondary ISP? Do you have public ips from them? ... View more

I'm pretty sure OP is talking about the switch port view which does default to 30 ports and it would be really nice if a lot of the view preferences were referenced from the user profile vs the organization or network. ... View more

You can technically do that if your Hubs are concentrators (or have another firewall to send traffic to) AND you can define the services via static routes. I.e. if you want to reach X.X.X.X/Y via Hub 1 you can advertise that from that Hub.  Unless the services in question have fixed IPs, you would not be able to do this. ... View more

If it's not in your inventory but you remember when it was and it's within the time the change logs keep, you may be able to hunt it down from when you removed it or added it. ... View more

That's curious, I thought that was just for IOS-XE on 17.18. I wonder if it's a GUI bug. ... View more

I remember hearing about this at either Cisco Live or a partner training, It appears you have to load the new aps and then match them up, which is fine, but I'd prefer to  have them pre-loaded and just rely on matching up serials as an option, then things could happen automatically as soon as they are plugged in. I can see why you might want the other way, but having both would be ideal imo. ... View more

https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/How-Tos/Give_your_feedback_(previously_Make_a_Wish) Just in case you aren't aware, the most official way to submit this type of wish feedback. It definitely should be a per admin setting instead of per org, IMO. ... View more

You will need to upgrade the firewall to get higher speeds. See here for what's available at what speeds: https://documentation.meraki.com/?title=MX%2FDesign_and_Configure%2FArchitectures_and_Best_Practices%2FMX_Sizing_Guide_%26_Principles#Performance_Data Be mindful of the various throughput levels depending on what features are enabled. Also bee aware that if you can live with speeds less than your circuit max but still higher than currently and are co-term you can upgrade to an MX67 with no license charge: https://documentation.meraki.com/Platform_Management/Product_Information/Licensing/Meraki_Co-Termination_Licensing_Overview#License_Conversion If you  need full use of the circuit, you will have to pay for a new license for your chose hardware. Your meraki rep may be willing to soften the blow and give you some credit for your existing license, but you will need to talk to them. ... View more

What support can do and what your sales teams can do are different things. Support cannot modify these things, but your Cisco account team may be able to help you with this by doing some sort of modify. I suggest reachout out to them/your partner to ask. ... View more

Oddly, the new switch view loads for me but the old won't.  ... View more

Thanks and congrats to everyone! ... View more

Are you on co-term right now or PDL? It sounds like PDL based on your budget comment as Co-Term you have to renew everything all at once and subscription pricing is pretty similar to doing a co-term renewal based on my recent analysis. The only technical work around would be splitting your org up. That would just make management more difficult, and if you use AutoVPN to any extent, migrating to third party vpns could also be painful. I do highly suggest talking to the reps. There are financial things they have the ability to do and could help make the math work to migrate everything. Technically you can only switch an org when everything is expired, but support has the ability to pull all of your licenses, so I would think the AM team may be able to work something out. Also if you are large enough an EA Subscription might work for you and there is further flexibility there, but again have to talk to your account team.     ... View more

Yes ... View more

Click the pencil next to the Primary/Spare status on the main Appliance Status page, my example below is blank as I don't usually use them, but yours should  have W1 already filled out and you just add the IP to WAN 2         ... View more

This is what is going on. Essentially invisible networks get created for device types you don't have. You can split the combined network, they will become visible and then delete the unused "sub-networks", and recombine. ... View more