Documentation Digest: December 2nd - December 5th

Solved
Hannah-C
Meraki Employee
Meraki Employee

Documentation Digest: December 2nd - December 5th

DocDigest_Banner.png

 

New articles:

CW9176I Installation Guide

CW9176D1 Installation Guide

CW9178I Installation Guide

Change: New article.

 

Automated Logins and Users on Cloud-Managed Switches Running Cloud-Native IOS XE

Change: New article.

 

Wi-Fi 7 (802.11be) Technical Guide

Change: New article.

 

Alert Config and Notifications

Change: New article.

 

 

Cloud Monitoring for Catalyst:

Cloud Monitoring Catalyst 9800 Dashboard Provisioned Configurations

Change: Added additional command "ip http authentication local" and the behavior if already present / not present during onboarding.

 

 

MG:

Cellular Gateway (MG) Firmware Features Directory

Change: Added "External multi-carrier SIM cards are not currently supported on any MG or MXC devices. Multi-carrier SIM cards use global roaming functionality to provide access to multiple carriers on a single SIM. If you intend to use these SIM cards at your own discretion, Meraki support won’t be able to assist you if the devices don’t work as expected."

 

 

MX:

MX Warm Spare - High-Availability Pair

Change: Updated requirement: "Ensure that both MXs have their own uplink IP address for dashboard connectivity as mentioned here. If a virtual IP is being used, an additional IP address is needed, and all three IPs must be in the same subnet."

 

 

MS:

MS Layer 3 Switching and Routing

Change: Updated wording to include all Catalyst based switches: "The overlapping subnet limitation does not apply to Catalyst switches (MS390/C9300-M)."

 

MS OSPF Overview

Change: Added "Also supported Cloud managed Catalyst, all C9300/X/L models including MS390."

 

 

MR:

Meraki Health - MR Access Point Details

Change: Added section "Device Health".

 

MR78 Datasheet

Change: Added power option: "Alternative: 12 V DC input".

 

Meraki Auto RF: Wi-Fi Channel and Power Management

Change: Updated configuration capability: "Dual-band operation with band steering can be configured for all SSIDs or on a per-SSID basis."

 

 

SM:

Deploying Store Apps for iOS/macOS and Android

Change: Added section "Searching for Android apps by App ID".

 

Configuration Profiles

Change: Added note "When duplicating profiles, be aware that all existing tags will be retained. Exercise caution, particularly when copying WiFi profiles that have already been deployed to devices, as this may lead to unintended consequences with your current profiles and the devices they are associated with."

 

Apple Volume Purchase Program (VPP)

Change: Added descriptions for "Allowed admins" and "Assignable networks".

 

 

General Administration:

Meraki End-of-Life (EOL) Products and Dates

Change: Added MA-MNT-MV-61.

 

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

Change: Added note "Meraki Support may request a video of the device to during normal device failure analysis, identification, and troubleshooting."

 

Using the Organization Inventory

Change: Added "For Catalyst devices, the Meraki Serial Number is known as Cloud ID. The catalyst serial number or "serial" is not claimable in the Meraki dashboard, use the Cloud ID to claim these devices."; added "If claiming a device via API all uppercase characters must be used."

 

Subscription - Licensing Overview

Subscription - Licensing Claim Cloud

Change: Added "Subscription License keys can only be claimed by an expired organization, an organization in a grace period, or a newly created organization (this includes ones created via Organization split). Subscription License keys cannot be claimed by organizations that are currently using active legacy (Co-term and PDL) licensing models. All trials must either be expired or removed from the organization before claiming the Subscription License key."; added "If you wish to convert an organization using Co-term or PDL Licensing to a Subscription Licensing model, open a case with support. This conversion is permanent."

 

FIPS 140 Devices and Firmware for Cisco Meraki

Change: Added "If you do not find your device on this list, is not FIPS 140 Compliant."

1 Accepted Solution
AmyReyes
Community Manager
Community Manager

Hi @jimmyt234 @PhilipDAth @TyShawn, thank you for alerting us (pun intended 😆). I reached out to the team and will get back to you shortly with an answer! 

Update: The feature is in tiered rollout currently, so within the next week or so it should be available to everyone. 

View solution in original post

9 Replies 9
jimmyt234
Building a reputation


@Hannah-C wrote:

Alert Config and Notifications

Change: New article.

 

Is this 'Configure alerts' button/feature available now? I do not see it when I am navigating to the Organization>Alerts page under our Org?

PhilipDAth
Kind of a big deal
Kind of a big deal

I can't see it either.

RaphaelL
Kind of a big deal
Kind of a big deal

Been waiting for ages for that feature ! Can't wait to test it

RWelch
A model citizen

ConfigureAlerts.png

It's there now @RaphaelL @PhilipDAth 

If you found this post helpful, please give it Kudos. If my answer solves your problem please click Accept as Solution so others can benefit from it.
RaphaelL
Kind of a big deal
Kind of a big deal

Not for everyone though

TyShawn
A model citizen

Same... Alerts are missing in action.

MRCUR
Kind of a big deal

"

MX:

MX Warm Spare - High-Availability Pair

Change: Updated requirement: "Ensure that both MX's have their own uplink IP address for dashboard connectivity as mentioned here. If a virtual IP is being used, an additional IP address is needed, and all three IP's must be in the same subnet."

 

This should be "MXs" and "IPs" without the apostrophes. 

MRCUR | CMNO #12
CarolineS
Community Manager
Community Manager

Thanks, grammar police! Fixed! Always nice to see you here, @MRCUR.

Caroline S | Community Manager, Cisco Meraki
New to the community? Get started here
AmyReyes
Community Manager
Community Manager

Hi @jimmyt234 @PhilipDAth @TyShawn, thank you for alerting us (pun intended 😆). I reached out to the team and will get back to you shortly with an answer! 

Update: The feature is in tiered rollout currently, so within the next week or so it should be available to everyone. 

Get notified when there are additional replies to this discussion.