Too many updates to share, but since many of you asked about the absence in changelog announcements, I thought I’d check in and share a few lesser-known additions that dropped recently.
So here’s the deal; I’ll make this brief. You all are a very smart bunch. Our Cisco Meraki enterprise team hires smart people. And we now have openings in three markets.
NorCal, Atlanta, and NYC.
I made a change. A career change. The kind of big career change every technical professional considers at some point in their career.
I’ve got several large work projects in flight which has put a temporary damper on my longform technical writing time. The good news is that one of those projects is pretty interesting (long-haul mesh wireless between two Casinos) and would make for a useful tutorial on design, configuration, and wireless mesh best practices. More to come on that.
For now we’re going to keep this one short. Starting with a few hidden gems.
Systems Manager: iOS App Cellular Data Control
The SM team recently added the ability to control whether or not cellular data is allowed for iOS managed apps.
Firewall and WAN refresh projects have many components, but one of the first steps after vendor selection is hardware sizing. Even when working on POC/POV projects, rightsizing the hardware upfront provides a truer day-two experience and requires less rework once complete.
My goal is to walk you through a consultative sizing process to properly size Meraki MX appliance models for any deployment. The process outlined below applies equally to small, multisite MX deployments as it does to super-scale 10,000+ site deployments. I’ve been involved in the planning, pilot, and deployment phases of dozens of such projects and wanted to share my method.
|Configuration Change History|
|Enhanced Privacy Features|
The Cisco Meraki Dashboard contains several logging subsystems that each have unique data retention and export options available. Datasets like event, configuration, and analytics are used for starkly different purposes (business intelligence, operations, risk management, etc.) and are reflected in the native logging capabilities.
Questions are often asked around how long Meraki stores logs or other metrics, which as you’ll discover shortly, can have many different answers depending on the dataset in question. The same applies for export, syslog, and other local offload options available. Different datasets, different options.
If you weren’t aware, every Meraki device has a local status page for provisioning, configuration, and onsite troubleshooting. No need for a USB-to-console-dingus to get access to the unit locally. Simply connect an Ethernet cable to a LAN or management port on the device, open a web browser, navigate to setup.meraki.com, and be surprised by the lovely HTML5 local web console.
Several new switch features were introduced in Meraki’s MS10 firmware including loop guard, DIA, storm control, and LAN anomaly detection for improved control-plane monitoring and stability.
This serves as a quick look into some of the new enhancements available. More information including a full list of features can be found in the detailed firmware change notes within the Meraki Dashboard (Organization > Firmware upgrades page).
The Cisco Meraki team hit a major milestone this week. CRN, one of the largest network industry vendor publications recently announced the best selling enterprise firewall and wireless access point brnads of Q3, 2017 and the Cisco Meraki portfolio took the top spot in both categories.