I do not have the same problem in my environment (MX64, MX67, vMX-S).   However, there is a topic that may be relevant.   AutoVPN Connectivity Issues - The Meraki Community https://community.meraki.com/t5/Meraki-Service-Notices/AutoVPN-Connectivity-Issues/ba-p/149812 ... View more

Related Topic   VMX with client VPN or AnyConnect - The Meraki Community https://community.meraki.com/t5/Documentation-Feedback-Beta/VMX-with-client-VPN-or-AnyConnect/m-p/149090#M51 ... View more

I contacted support last month. I inquired whether the following matter is a bug or a specification.   vMX and Client VPN on Microsoft Azure - The Meraki Community https://community.meraki.com/t5/Security-SD-WAN/vMX-and-Client-VPN-on-Microsoft-Azure/m-p/103379   [Topic Summary] The value of the Meraki vMX AZ setting determines whether the Client VPN (L2TP, AnyConnect) can work or not.   * 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.     This matter appears to be undetermined / undefined.   Therefore,... It is not a bug, as it is not yet determined / undefined. It is not a specification, as it is not yet determined / undefined.   I would like to see just the current information clearly stated in the document. If not documented, more customers may be affected. Furthermore, the quality of Meraki vMX products is suspect.   It will be the Meraki MX on Azure rather than AnyConnect-specific, but I'm including it here because there is no topic for it.   vMX Setup Guide for Microsoft Azure - Cisco Meraki https://documentation.meraki.com/MX/MX_Installation_Guides/vMX_Setup_Guide_for_Microsoft_Azure ... View more

I contacted support last month. I inquired whether the following matter is a bug or a specification.   [Topic Summary] * 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.   This matter appears to be undetermined / undefined.   Therefore,... It is not a bug, as it is not yet determined / undefined. It is not a specification, as it is not yet determined / undefined.   Since it is neither a bug nor a specification, it does not appear to be documented. I have provided feedback to be documented, but I don't know what will happen. ... View more

I think the most readily available is DevNet Sandbox's Meraki Always On. However, it is a read-only environment. There is also DevNet Sandbox's Meraki Enterprise, which is a bit more flexible, but reservations are required.   Cisco DevNet Sandbox - try out online developer environments - Cisco DevNet https://developer.cisco.com/site/sandbox/   Cisco dCloud also has several Meraki environments. ... View more

改めて画面を見てたのですが、サポートの方が仰られてたのは 「Help > Get help」の画面で「Still need help?」をクリック後に、 さらに「Call the Meraki Support team」をクリックした状態を指してたようです。 ※備考: 英語メニューです。   ... View more

補足的な情報を共有させて頂きます。   仕様的に上限数がない場合であっても、 過剰なほど設定をしすぎるとMeraki DashboardのWeb UI上での表示に時間がかかってしまい、 実質的な上限数が発生する可能性があります。   以前、試しにVPN exclusion rulesに1000件ほど設定した際は、Web UIのレスポンスが少なからず鈍くなっておりました。 そのため、Web UIで管理に向かないほどの設定数がある場合はご注意ください。 ... View more

基本的に各製品の仕様はData Sheetの情報が正になるので、 代理店やSIerの営業される方々が販促資料として用意していないと日本語の情報は無いかと存じます。   また、仮にあったとしても正確な情報としてData Sheetも確認するのが好ましいです。 何故かと言いますと、パフォーマンスのような情報として理論値と推奨値や実測値があった場合は、 営業資料には性能の良い方が記載されているパターンがあります。 ... View more

For your information.   I contacted Meraki Technical Support because I could not see the documentation. The HTTPS Inspection document has been intentionally de-published.   There are the following reasons.   HTTPS Inspection is BETA version and the specifications are subject to change at any time. HTTP Inspection could lead to a significant impact on existing functionality and network stability.   In addition, the public release of the document was cancelled due to the high risk involved in operating the system for general users.   I contacted support in Japanese, so the nuances may be slightly different when translated into English.   In my opinion, I don't consider it a serious matter because there are ways to offload to Cisco Umbrella. ... View more

I have intentionally run out of licenses in Co-Term for verification purposes. My environment at the time was Meraki MX, MS, MR.   In that case, splash page was displayed when accessing the Internet. Presumably, this is a mitigation measure to allow Meraki to renew its license. It is not explicitly stated, so I don't think it is a guaranteed behavior. Also, as expected, the file server in the LAN is no longer accessible.   One thing I can say for sure is that the service impact is certain to occur after the grace period. ... View more

To put it another way, "Why can't vMX (Virtual MX) be in Routed Mode (NAT Mode)?".   It is related to DC-DC Failover. To make Meraki vMX redundant, it must be DC-DC Failover. Because Meraki vMX does not support Warm-Spare (VRRP). The implementation is different from on-premises because the public cloud's infrastructure manages IP addresses and Route Tables.   Redundant vMX Hub in DC-DC Failover must be in Concentrator Mode, not Routed Mode (NAT Mode). Because, duplicate subnets are not allowed in Routed Mode (NAT Mode). MX in Routed Mode (NAT Mode) that join Auto VPN must be unique subnets.   Auto VPN Routes are statically configured and there must not be more than one route. For example, Packet says: "Where do I go if I have duplicate routes in Routed Mode (NAT Mode)?" However. with DC-DC Failover topology, there is redundancy between the DCs, so there is a possibility of reaching the destination via either DC.   Concentrator Mode allows duplicate routes to be advertised to Auto VPN. It is only with that duplicated route that DC-DC Failover is possible.   For these reasons, it makes virtually no sense to put vMX in Routed Mode (NAT Mode) in the production environment, even if it was possible.   If you ask why we chose such specifications, that is another topic. This product characteristic is very difficult. ... View more

状況の共有ありがとうございます。 伺った内容を聞く限りではアナウンスされた内容が誤ってる可能性があるので、 "正規のサポート"を受けるためにDashboardからケースをオープンした方が好ましい状況かなと思います。   勿論、ここで解答を待つ方法もありますが確実性はないので、平行してケースをオープンしておくのが確実だと思います。 ... View more

また本人確認などのためにパスコードが必要になる場合は、 アカウントをクリックしてポップアップした時の My profile のページを開くと、 Your support passcode for today に情報が表示されます。 日替わりなので問い合わせるタイミングに留意してください。 ... View more

仕様確認で問い合わせが必要な状況だと思いますが、サポート契約があるのであればMeraki Dashboardからケースを上げれます。電話連絡は必ずしも必要ないです。   補足ですが、 本コミュニティはあくまでも有志によるコミュニティなので、サービス レベルが保証されてるものとはまた違います。 実際、私もコミュニティに登録してるユーザー サイドの者になります。 なので確実に回答がつくのが保証されてるわけではないので、サポートとコミュニティを混同しないようにご注意ください。   また、その電話番号が検索してもヒットしないようなので Merakiの個別担当宛なのか、SIerの営業の方へ質問してるのかなど背景が分かりかねますが、 最初はMeraki Dashboardからケースを開いてCase Numberを発行して、 その上で電話した方がトラッキングしやすいですし、サポートの方にも話が通じやすくなると存じます。 ... View more

Meraki Dashboardにログインして右上のアカウントをクリックすると、ポップアップしたときに CUSTOMER の項目に XXX-XXXX のようなCustomer Numberが表示されます。 ドキュメントだと下記に画面キャプチャがあります。   Locating the Meraki Customer Number or Support Passcode - Cisco Meraki https://documentation.meraki.com/General_Administration/Support/Locating_the_Meraki_Customer_Number_or_Support_Passcode > Meraki Customer Number (MCN) ... View more