Documentation Digest: February 20-February 26, 2026

Hannah-C
Meraki Employee
Meraki Employee

Documentation Digest: February 20-February 26, 2026

DocumentationDigest_banner.png

 

New articles:

Change: New articles.
 
Change: New article.
 
Change: New article.
 
Change: New articles.
 
Change: New article.
 
Change: New article.
 
Change: New article.
 
Change: New article.
 
Change: New article.
 
 
Access Manager:
Change: Added additional anchors: #policies, #demo, #demos, #attributes, #conditions, #attrs, #attribute-sources.
 
 
Workflows:
Change: Added release notes for the "February 6, 2026" and "February 20, 2026" releases.
 
 
Security & SD-WAN:
Change: Added C8111-G2-MX and C8121-G2-MX.
 
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."
 
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:
Change: Added "Dynamic Routing (OSPF/BGP): With Cloud managed switches, dynamic routing (OSPF/BGP) are supported with VRRP enabled on the switch."
 
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".
 
Change: Added section "Known Issues and Limitations".
 
Change: Added section "Required Actions for Switches Not Migrating to Configuration Source: Device Before March 31st (Cloud Monitoring Decommission)".
 
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."
 
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."
 
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."
 
Change: Added note regarding new Cloud Entitlement for DNA offering.
 
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."
 
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:
Change: Added Wi-Fi 7 APs; added sections "Ultra-Wideband (UWB) Enhanced Client Wayfinding" and "Wayfinding Status (per floor)".
 
Change: Added "Air Marshal may flag legitimate Wi-Fi Direct SSIDs since Wi-Fi Direct allows simultaneous peer-to-peer and infrastructure WLAN connections."
 
Change: Added "Campus Gateway and Access Points must be in the same Meraki Network. Tunneling across networks is not currently supported."
 
 
Cameras:
Change: Added release notes for up to v1.26.10.
 
 
Platform Management:
Change: Added "StackWise Virtual", "ISSU" and "Cloud EVPN Fabric".
 
Change: Renamed from "Managing Cisco Networking Subscription on EA".
 
Change: Added "C8455-G2-MX".
 
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."
 
Change: Added "It is expected behavior that this alert will omit details from successful events and will only send a summary of the changes."
 
Change: Added "AP Connection to Sensor Connect Down".
 
Change: Updated the Authorization header: "Authorization: Bearer <secret key>".
 
Change: Added Access Manager to the list of unsupported features.
0 Replies 0
Get notified when there are additional replies to this discussion.