Documentation Digest: February 20-February 26, 2026

Change: Added "During the Early-Access period for this feature, organizations deploying below Design B (Any Spokes with Hybrid and Cloud Hubs) can accommodate up to 1,000 Spokes and 2 MX Hybrid Hubs. To address broader deployment needs, increased scale for Spokes and Hubs is being validated for the product release. If the design you intend to use is not documented here, please contact your account team. Several common scenarios have been identified for additional validation after the initial release and will be incorporated into this document as appropriate."

MX Warm Spare - High-Availability Pair

Change: Added "MXs operating in HA cannot have more than 255 VLANs configured."; added "MX devices in HA randomly assign a VRRP VRID between 1 and 255 at boot. For a static VRID, please contact Support for assistance."; updated Warm Spare compatibility "The spare MX must be the same MX model as the primary. Warm spare functionality is not supported between different MX models (for example, MX85 and MX105) which also includes MXs with the same model but different territorial designations (e.g., MX67C-WW and MX67C-NA)."

Switching:

Cloud-Managed Switching Warm Spare (VRRP) Overview

Change: Added "Dynamic Routing (OSPF/BGP): With Cloud managed switches, dynamic routing (OSPF/BGP) are supported with VRRP enabled on the switch."

Cloud Managed Catalyst Switches FAQs

Change: Added "Cloud-born Catalyst switches (-M) require Meraki licenses, with a 30-day grace period for onboarding to the Meraki Dashboard. Eligible migrated switches can use existing DNA licenses for cloud management until February 1, 2029 - no additional license migration or transfer required. Learn more: http://cs.co/9004hmri2".

Enable Cloud Management for Catalyst Switches with Device Configuration

Change: Added section "Known Issues and Limitations".

Cloud Monitoring End of Service - Transition to Cloud Management - Configuration Source: Device

Change: Added section "Required Actions for Switches Not Migrating to Configuration Source: Device Before March 31st (Cloud Monitoring Decommission)".

Switch ACL Operation

Change: Added "By default, mDNS cannot be blocked by an ACL; if you require mDNS to be blocked, please contact Support. This does not apply to CS or cloud-native IOS-XE managed Catalyst/MS390 switches."

Upgrading Cloud-Monitored Switches to Cloud Management with Device Configuration

Change: Added "When adding stacked switches, all members of the stack must be selected to add to network."; added "Organizations using per-device licensing must use the network-wide add devices page."

MS Switch Access Policies (802.1X)

Change: Updated RADIUS monitoring behavior: "RADIUS Testing should be enabled by default in the new Access Policies UI so that RADIUS Monitoring can track server reachability. A configuration change on a policy using Critical Authentication may be required on the new Access Policies page to enable RADIUS testing."

Cloud Management with IOS XE Overview

Cloud Management with IOS XE

Cloud Managed Catalyst Switches FAQs

Conversion from CLI-managed IOS XE Catalyst Switches to Cloud Management with Cloud Configuration

Change: Added note regarding new Cloud Entitlement for DNA offering.

Client-Tracking in IOS-XE

Change: Added "During onboarding of a C9500 to Device Configuration mode, device tracking will not be modified. Users can choose to modify it via CLI after onboarding."; added "During the onboarding, the above tracking policies will only be applied to interfaces without existing device tracking configuration."; added "When the Meraki device-tracking policy is removed from the interface after the onboarding it will be re-applied automatically. If the policy is replaced with a custom (non-Meraki) policy it will not be overwritten."

Cisco Meraki Local Status Page: MS Switches

Cisco Meraki Local Status Page: Catalyst IOS XE Switches

Change: Added "Any changes on local status page are only intended to be used when necessary to get a switch connected to the dashboard. Before making any changes on the local status page to bring a switch online, ensure the same changes are applied in the dashboard first. Failing to do so will cause the device’s configuration to be overwritten by the dashboard configuration, which may cause the switch to go offline."

Wireless:

AP Auto Locate

Change: Added Wi-Fi 7 APs; added sections "Ultra-Wideband (UWB) Enhanced Client Wayfinding" and "Wayfinding Status (per floor)".

Air Marshal

Change: Added "Air Marshal may flag legitimate Wi-Fi Direct SSIDs since Wi-Fi Direct allows simultaneous peer-to-peer and infrastructure WLAN connections."

Campus Gateway Deployment Guide

Change: Added "Campus Gateway and Access Points must be in the same Meraki Network. Tunneling across networks is not currently supported."

Cameras:

Meraki Vision Portal Changelog

Change: Added release notes for up to v1.26.10.

Platform Management:

Subscription - MS Licensing

Change: Added "StackWise Virtual", "ISSU" and "Cloud EVPN Fabric".

Control Mode of Unified Suites

Change: Renamed from "Managing Cisco Networking Subscription on EA".

Returns (RMAs), Warranties and End-of-Life Information

Change: Added "C8455-G2-MX".

SNMP Overview and Configuration

Change: Added "Starting with MCG 32.2.1, Campus Gateway will support SNMP monitoring only using SNMP V3 with Privacy Mode AES128. SNMP V2C is not supported with Campus Gateway."

Network Alerts and Notifications

Change: Added "It is expected behavior that this alert will omit details from successful events and will only send a summary of the changes."

Dashboard Alerts - Connectivity Issues

Change: Added "AP Connection to Sensor Connect Down".

Cisco Meraki Dashboard API

Change: Updated the Authorization header: "Authorization: Bearer <secret key>".

Cisco Meraki Canada Region

Cisco Meraki India Region

Change: Added Access Manager to the list of unsupported features.

topic Documentation Digest: February 20-February 26, 2026 in Cloud Networking Platform

Documentation Digest: February 20-February 26, 2026