Documentation Digest: January 19th - January 26th

Hannah-C
Meraki Employee
Meraki Employee

Documentation Digest: January 19th - January 26th

DocDigest_Banner.png

 

New articles:

Using Umbrella Multi-org with Cisco Secure Connect

Change: New article.

 

Secure Connect:

Cisco Secure Connect Account Setup FAQ

Change: Added note that Umbrella customers with the Multi-org can continue to use Multi-org with Cisco Secure Connect. To do this, they must order Multi-org at the same time when they order Secure Connect. It's crucial to note that there is no direct integration between Secure Connect and Multi-org. Customers can access Multi-org via their existing Multi-org dashboard. Furthermore, the use of Multi-org will remain limited to DNS content and security policy management.

 

Cloud Monitoring for Catalyst:

Cloud Monitoring for Catalyst Onboarding

Change: Added note that when onboarding a stack, the single management IP should be entered which will onboard the entire stack.

 

MX/Z:

MX Cold Swap - Replacing an Existing MX with a Different MX

Change: Added section "Re-generate AnyConnect custom certificate (optional)".

 

MX Routing Behavior

Change: Added note that the mentioned behavior is specific to traffic initiated by the MX appliance itself, any Meraki devices connected downstream will always adhere to the route priority of the MX, added ports for management traffic and AMP registration and file disposition lookups.

 

Configuring Active Directory with MX Security Appliances

Change: Added note that communication with the server will originate from the highest numbered VLAN included in the VPN, if the Server IP address is located over a VPN Tunnel.

 

AnyConnect on the MX Appliance

Change: Updated note that custom hostname certificates require MX firmware version 16.16+.

 

AnyConnect Authentication Methods

Change: Added note that TLS is required to communicate with the Domain Controller for Active Directory authentication.

 

Client VPN Overview

Change: Added note that MX utilizes LCP (Link Control Protocol) to assign IPs to clients, thus DHCP and Static Assignment are not supported.

 

MX75 Hardware Installation Guide

Change: Added MA-PWR-100WAC-A to Accessories.

 

MX250/450 Series Hardware Installation Guide

MX95/MX105 Series Hardware Installation Guide

MX85 Series Hardware Installation Guide

MX85 Datasheet

MX75 Datasheet

MX67 and MX68 Datasheet

Z3 and Z3C Overview and Specifications

Change: Updated throughputs.

 

Z4C Installation Guide

Change: Added Verizon (US) to certified carriers.

 

Meraki MX/Z Security and SD-WAN Licensing

Change: Added Z4 license SKUs.

 

MG MX/Z Cellular TAC Range

Change: Added Z4C TAC Range.

 

MS:

Switch Port View

Change: Added "Topology changes" to packet counter table.

 

MS Switch Access Policies (802.1X)

Change: Updated RADIUS Testing. If unreachable, the switch would transition into an alerting status to indicate a failure. Actual server failover is based on the client authentication requests. Failed client authentications will have the switch failover to the next available configured server.

 

FAQs: Migrate to Meraki management mode

Change: Updated FAQ "If I already have DNAC essential/advantage licenses, do I need to purchase another license to use the Meraki dashboard today?", "Can I access the console after I initiate the migration?" and "What do I need to do if I want to migrate back to DNA management mode?".

 

Catalyst 9300-M Datasheet

MS390 Datasheet

Change: Added warning about MS390s existing in the same co-term Organization will require the same license edition (either Enterprise or Advanced) as the Catalyst 9300-M. License types cannot be mixed and will result in an incompatible license error (and vice versa).

 

MR:

HTTP CONNECT Proxy Support on MR Access Points

Change: Added notes for correct formatting for using the "Option 43" method.

 

Wi-Fi Personal Network (WPN)

Change: Added CW9163E.

 

Scanning API for Location Analytics Solutions

Change: Added differences 4, 5 and 6 to FAQ "What are the fundamental differences between V2 and V3 versions of the Scanning API?".

 

RF Profiles

Change: Updated regarding Wi-Fi 6E / 6 GHz wireless.

 

NAT Mode with Meraki DHCP

Change: Added note that a Lease Time of 24 hours will be given to wireless clients.

 

Meraki Local Authentication - MR 802.1X

Change: Added note to consult vendor-specific documentation to determine the exact path to a device's certificate store or IdenTrust Commercial Root CA 1.

 

High Density Wi-Fi Deployments

Change: Added note that once an antenna is detected by the AP it cannot be changed in dashboard until the antenna is removed and AP is rebooted.

 

MT:

MT Frequently Asked Questions

Change: Added section "2 Free MT Licenses with MR Advance License".

 

General Administration:

Behavior during Connection Loss to Cisco Meraki Cloud

Change: Added reboot behavior for different MX firmware versions.

 

Managing Multiple Networks with Configuration Templates

Change: Added note that Firewall rules on Template networks do not show a hit counter column, which is expected behavior for this column to be missing.

 

Changing the Dashboard Network Time Zone

Change: Added note that Winter and Summer time (Daylights savings time) is automatically applied by the dashboard.

 

How to do a License Transfer in Cotermination

Change: Added note that transferring between a Co-Termination Licensing Organization, to a Per-Device Licensing Organization or vice-versa is not possible.

 

Organization Split Overview and FAQ

Change: Added "Secure Connect Organizations" to section "Limitations of Organization Splits".

 

Managing Dashboard Administrators and Permissions

Change: Added note that Read-Only admins can perform switch port cycles and cable tests.

 

SM:

Windows Enrollment

Change: Added section "Version 4.x+ with Bulk Enrollment Token"; updated section "Version 3.5.x - 3.9.x".

 

Misc:

MV - Smart Cameras

MX Quick Start

Getting Started with Meraki

Change: Added references to free online training courses on the Meraki Learning Hub.

3 Replies 3
RaphaelL
Kind of a big deal
Kind of a big deal

Really interesting : https://documentation.meraki.com/General_Administration/Cross-Platform_Content/Behavior_during_Conne...

 

I had a case open about this feature , but this documention clears any confusion ! Much needed. Good job.

RaphaelL
Kind of a big deal
Kind of a big deal

Is there a typo in : https://documentation.meraki.com/MX/MX_Overviews_and_Specifications/MX67_and_MX68_Datasheet

 

Top section mentions that the MX67 and MX68 have 700/400Mbps of throughput but the bottom section says 600/300Mbps :

 

RaphaelL_0-1706292835462.pngRaphaelL_1-1706292844438.png

 

cmr
Kind of a big deal
Kind of a big deal

In the MX75 datasheet the power supply accessory is listed as a 100W model.  I had an RMA replacement last week and the new MX had a 120W PSU.  This does seem more sensible seeing as the max power draw is 96W.  Can this be checked?

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.