Meraki

MyHomeNWLab · ‎Oct 31 2022

MX 17.10.1 was promoted from "stable release candidate" to "stable". In my environment, an upgrade to MX 17.10.1 is currently not automatically scheduled. As of November 01, 2022, the stable versions are MX16.16, MX16.16.6 and MX17.10.1. [Related topic] New MX 17.10.1 stable release candidate firmware - AutoVPN fix - The Meraki Community https://community.meraki.com/t5/Security-SD-WAN/New-MX-17-10-1-stable-release-candidate-firmware-AutoVPN-fix/m-p/171517

MyHomeNWLab · ‎Oct 29 2022

It is very helpful to know easily what's new! I look forward to it every month.

MyHomeNWLab · ‎Oct 29 2022

@Ryan_Miles Thanks for your quick response!

MyHomeNWLab · ‎Oct 27 2022

The English documentation (General MX Best Practices) is located under the Japanese help. I can't find this same document in the English category. General MX Best Practices - Cisco Meraki https://documentation.meraki.com/%E6%97%A5%E6%9C%AC%E8%AA%9E/Architectures_and_Best_Practices/Cisco_Meraki_Best_Practice_Design/Best_Practice_Design_-_MX_Security_and_SD-WAN/General_MX_Best_Practices Home > 日本語ヘルプ > アーキテクチャおよびベストプラクティス > ... [Notes] 日本語ヘルプ = Japanese help アーキテクチャおよびベストプラクティス = Architectures and Best Practices ( https://documentation.meraki.com/Architectures_and_Best_Practices )

MyHomeNWLab · ‎Oct 25 2022

Meraki MS intercepts the DNS communication and returns its own IP address (1.1.1.100) if it is "switch.meraki.com". It could be a problem with the client's DNS settings, so I suggest trying with IP addresses (1.1.1.100) to break down a problem. Using the Cisco Meraki Device Local Status Page - Cisco Meraki https://documentation.meraki.com/General_Administration/Tools_and_Troubleshooting/Using_the_Cisco_Meraki_Device_Local_Status_Page > MS - 1.1.1.100 > In order to access this address, configure a device with the following IP settings, and then browse the address in a web browser. > IP address: 1.1.1.99 > Subnet mask: 255.255.255.0

MyHomeNWLab · ‎Oct 24 2022

I will share supplemental information. The documentation does not indicate that management communication is always through Uplink. However, as far as I have previously verified, when uplink is down, management communication is lost. MX Routing Behavior - Cisco Meraki https://documentation.meraki.com/MX/Networks_and_Routing/MX_Routing_Behavior#Behavior_of_Management_Traffic ref. Behavior of Management Traffic > The following services/tools will specifically adhere to the route priority and not necessarily ingress or egress the primary WAN/Internet uplink: > > Advanced Malware Protection registration > Meraki Cloud Authentication > Meraki Cloud Communication on TCP ports 80,443 and 7734 > Ping and Dashboard Throughput Live Tools > List Updates for the following services: Content Filtering, IDS/IPS Rule Updates and Geo-IP Lists for Layer 7 Country-Based Firewall rules

MyHomeNWLab · ‎Oct 20 2022

Memo: Microsoft's official announcement about Public IP SKU Upgrade to Standard SKU public IP addresses in Azure by 30 September 2025—Basic SKU will be retired | Azure updates | Microsoft Azure https://azure.microsoft.com/en-us/updates/upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired/

MyHomeNWLab · ‎Oct 20 2022

I will share the latest info. The documentation now clearly states that LACP and Link Aggregation are not supported on Meraki MX. MX Layer 2 Functionality - Cisco Meraki https://documentation.meraki.com/MX/Networks_and_Routing/MX_Layer_2_Functionality > LACP & Link Aggregation > The MX does not run LACP or any link aggregation protocols. Connecting aggregated ports to the LAN of the MX is not supported; all connected ports should be un-aggregated. If multiple ports are connected to the MX from a single switch for redundancy, it is highly recommended that you run STP on that switch, to ensure that one of the redundant ports is safely put into a blocking state.

MyHomeNWLab · ‎Oct 18 2022

My usage is active technical information gathering. Japanese customers care about detailed specifications. They also ask questions that are not covered in Meraki's documentation. I want to keep track of the latest documentation, as frequent inquiries to support can be annoying. That is also why I created a Meraki Community account to gather information. About search frequency. I would like to search the latest documentation when Document Digest is posted.

MyHomeNWLab · ‎Oct 18 2022

It appears that the existing license has been overwritten by the new license. (The number of devices has been overwritten by the new license.) When you added your license, did you choose "Renew my Dashboard license"? [Notes] The Co-Term licensing method offers two options. * License more devices Select 'License more devices' if you will be connecting more devices to the Meraki cloud. * Renew my Dashboard license Select 'Renew my Dashboard license' if you wish to extend your current expiration date without adding more devices. NOTE: selecting this option will replace your Organization's license limit to match the applied license key.

MyHomeNWLab · ‎Oct 17 2022

It's too late now, this case was published in the document. Cloud Maintenance New IP Ranges 2022 FAQ - Cisco Meraki https://documentation.meraki.com/General_Administration/Other_Topics/Cloud_Maintenance_New_IP_Ranges_2022_FAQ > Last updated: Oct 13, 2022 I found it while looking for the latest documentation.

MyHomeNWLab · ‎Oct 15 2022

FYI. This topic is very helpful. And, it is easy to get hits from search engines. So I'll share some recent new information. If you use the Webhook Payload Template (Beta feature), you can send alerts directly from Meraki to Microsoft Teams. Now in beta! Webhook Payload Template Editor Dashboard GUI page - The Meraki Community https://community.meraki.com/t5/API-Early-Access-Announcements/Now-in-beta-Webhook-Payload-Template-Editor-Dashboard-GUI-page/ba-p/171360 You must be a member of the API Early Access Group to view the topics above. API Early Access Group - The Meraki Community https://community.meraki.com/t5/API-Early-Access-Group/gh-p/api-early-access I was confusing "Webhook Payload Template" with "Webhook Payload Template Editor". [Sample Alerts] [Meraki Settings (Key Point)] Enable "Early API Access". Without customization, activation of Early API Access was not required. "Payload template" setting will be displayed. Set to "Microsoft Teams (included)". Don't forget to specify webhook in "Default recipients". Memo: I used "Incoming Webhook" for the Microsoft Teams side.

MyHomeNWLab · ‎Oct 11 2022

Note: Document for vMX and Azure Route Server have been published. More choices are now available. vMX and Azure Route Server - Cisco Meraki https://documentation.meraki.com/MX/Deployment_Guides/vMX_and_Azure_Route_Server

MyHomeNWLab · ‎Oct 6 2022

Can you find the order number from the email? Mail Subject: Your Meraki order has shipped

MyHomeNWLab · ‎Oct 5 2022

HTTPS Inspection is still a BETA feature. I recently enabled it and tried it, but the functionality appears to be broken. HTTPS Communication is not established even if HTTPS Inspection is bypassed. According to support, to prevent the problem from spreading, the HTTPS Inspection documentation is being kept private. [Related Topic] MX HTTPS Inspection Coming ... - The Meraki Community https://community.meraki.com/t5/Security-SD-WAN/MX-HTTPS-Inspection-Coming/m-p/45870

MyHomeNWLab · ‎Oct 4 2022

I would like to be able to sort by timestamp so that I can identify the most recent articles. Currently, I try to follow it from the Document Digest. Topics with Label: Documentation Digest - The Meraki Community https://community.meraki.com/t5/forums/filteredbylabelpage/board-id/general/label-name/documentation%20digest

MyHomeNWLab · ‎Sep 29 2022

When deploying vMX in Azure, the SKU depends on the Availability Zone (AZ) setting. * If AZ is set to None, the Public IP SKU is deployed as Basic. Client VPN works when SKU is Basic. * If AZ is set to 1 - 3, the Public IP SKU is deployed as Standard. Client VPN does not work when SKU is Standard. I know about it from the following topic. https://community.meraki.com/t5/Security-SD-WAN/vMX-and-Client-VPN-on-Microsoft-Azure/m-p/103379 In addition, vMX (Azure) is a managed Resource Group and its settings cannot be changed.

MyHomeNWLab · ‎Sep 26 2022

There was a workaround to add #{Number} (e.g. #1) to the end of the Identifier (Entity ID). The following is an example for AWS. https://github.com/MicrosoftDocs/azure-docs/issues/57571 > Adding "#" and followed by a unique number is required only when there are multiple instances of Amazon Web Services (AWS) enterprise application added to the same Azure AD tenant. I'm interested in MSP-specific considerations. This topic is nice.

MyHomeNWLab · ‎Sep 21 2022

For reference, I have organized information on the dCloud environment. * Catalog: SASE-Cisco Meraki Secure Edge - Instant Demo I am concerned that the MX tunneling to the Umbrella SIG was also tunneling to another MX's Hub.

MyHomeNWLab · ‎Sep 21 2022

Meraki MX changes the behavior of Auto VPN tunnel establishment when Cloud On-Ramp is used. [Related document] Meraki Umbrella SDWAN Connector Deployment Guide - Cisco Meraki https://documentation.meraki.com/MX/Meraki_Umbrella_SDWAN_Connector/Deployment_Guide > Due to the default Meraki Auto-VPN design, all VPN hubs in an organization will automatically tunnel to all other hubs in an organization. This behaviour changes for the Meraki Umbrella SDWAN Connector solution, when the connector hubs are deployed, all other hubs in the organization will not automatically tunnel to SIG and all hub traffic will not be defaulted to Umbrella. The Meraki Umbrella SDWAN Connector network hubs will not automatically tunnel to other hubs in the organization. I contacted support to verify this information in more detail. Therefore, unless I am mistaken in my perception, it should be correct. I have organized that information and will share it with you. [Notes] I do not have a Umbrella license, so I have not been able to verify this on the actual device. I only confirmed the MX specifications. Also, dCloud has several Meraki SASE environments, but they seem to work differently with undocumented features and were not helpful. I have checked the following catalogs. * SASE-Cisco Meraki Secure Edge - Instant Demo * Cisco SASE Lab v2 So I should say that I was not able to verify the exact default behavior on the actual device. I learned about undocumented features from a Japanese article written by the distributor. https://www.idaten.ne.jp/portal/page/out/secolumn/cisco/meraki/072.html * Japanese > ちなみにこのハブ間接続を禁止する設定はサポートへの依頼で解除することも可能ですので、実は要検証という条件付きであればハブ拠点をUmbrellaと接続することも可能です。 * Translate to English Incidentally, this setting that prohibits hub-to-hub connections can be removed by requesting it from support, so it is actually possible to connect hub locations to Umbrella with the condition that verification is required. [Overview] * Slide with comments * Slide without comments [Perspectives on each one] * Umbrella SIGs do not establish VPN tunnels with each other * When "Umbrella SIG Connector" and "Meraki MX in Hub" are mixed * Exit Hubs settings cannot be tunneled to the Umbrella SIG * "Spoke of MX" that does not tunnel VPN to "Umbrella SIG Connector" can tunnel VPN to "MX of Hub". Thanks to the support staff for their kindness! As a request, I would like the documentation to be detailed so that misunderstandings do not occur.

MyHomeNWLab · ‎Sep 20 2022

The SNMP Trap feature is a Beta feature. SNMP Overview and Configuration - Cisco Meraki https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/SNMP_Overview_and_Configuration#SNMP_Traps > Enabling Traps > Contact Meraki Support to have the feature enabled on the desired organization However, it appears to have recently been opened to the public. Therefore, it is additionally displayed in Firewall Info. In my Org1 environment, I activated it when it was Beta. However, in my Org2 environment, it appears without activation.

MyHomeNWLab · ‎Sep 17 2022

I think you should organize the information. My understanding is that the current situation is as follows If you want Meraki to do something similar to FortiGate, the question arises. how does it connect to the Internet? Without information on the entire network, the optimum cannot be found.

MyHomeNWLab · ‎Sep 15 2022

I also checked in my environment. Magnetic Design System (new Web UI) displays the MSP Portal even if the account belongs to only one Organization. It is not displayed in the old Web UI.

MyHomeNWLab · ‎Sep 13 2022

My environment (shard: n240) is working too!

MyHomeNWLab · ‎Sep 7 2022

Is it possible that Source NAT was configured in ForiGate? I think FortiGate had a Source NAT (LAN-to-WAN) setting in the default configuration depending on the model. For LAN-to-LAN communication, Meraki MX does not Source NAT. So, if routing is not configured, communication may not be possible.

About MyHomeNWLab

MyHomeNWLab

Community Record

Badges