Meraki

RaphaelL

I have AI-RRM , FRA , AI Channel planning and Busy hour configured on 15 networks to do a PoC. Each network has between 6-22 APs in normal open office environnement. FRA seems to be super agressive on some sites. More than 1/3 of the radios are disabled on this network. The stats ( made by the tool ) looks okay , but you do see a big swing in score everyday. There are a lot of channel changes and Tx power changes. Way more frequently than before. I'm still in the 14 days training period , I hope it will become less agressive in the future.

RaphaelL

Have you looked at your AI-RRM Insight stats ? Wireless -> Radio Settings :

RaphaelL

Hi , So VRFs are finaly here on MX. I just deployed MX 26.1.2 on my C8121 What's new Added support for configuring Virtual Router Forwarding domains (VRF) through the Early Access feature program. So that's true , I can configure the VRFs from the page Organization -> VRFs But according to my dashboard and documentation : https://documentation.meraki.com/SASE_and_SD-WAN/MX/Design_and_Configure/Configuration_Guides/Networks_and_Routing/VRF_for_WAN_Appliances VRFs are supported on MX 26.1.3+ in Routed Mode. 7 VRFs can be configured within a dashboard organization to be used in addition to the Default VRF. So TL;DR , I can configure VRFs but not use VRFs at the moment , am I missing something ? Is the limit 7 custom VRFs + default = 8 or 6 custom VRFs + default = 7 ? The messages are misleading for a non-native english speaker.

RaphaelL

If I'm not mistaken you could in theory use a ThousandEye agent on your MX. A bit overkill imo

RaphaelL

Can we take a moment to appreciate Ryan's work ? Took his time to respond with an animated tutorial on how to achieve what Dunky is requesting. That's some dedication. 👏

RaphaelL

That's right , but it doesn't scale well. Also the "status" ( green , red ) is per PEER and not per uplink which doesn't make any sense.

RaphaelL

Maybe the Meraki team could expose per-uplink AutoVPN tunnel status (established / not established) so we can detect this condition. This is something that I have requested for years and have requested this year with the BU. It doesn't make sense that we don't already have this

RaphaelL

Hi , This documentation button is a redirect to Cisco's internal documentation platform : https://documentation.meraki.com/CiscoPlusSecureConnect/Cisco__Secure_Connect_Now_-_Policies/Organization-wide_Group_Policy It should redirect to : https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Design_and_Configure/Configuration_Guides/Organization-wide_Group_Policy

RaphaelL

From what I have heard , there are already improvements to performance in 26.1 and more coming in 26.2. I would expect 700-800Mbps in IPS mode

RaphaelL

AI-RRM would be a great start.

RaphaelL

Regarding DHCP you are pretty much limited to DAI , mandatory DHCP and DHCP server blacklist / whitelist

RaphaelL

No 😞 not at the moment , but some nice QoL are coming in 26.2 and ++

RaphaelL

They do !

RaphaelL

I'm pretty sure it doesn't at the moment !

RaphaelL

Usualy more than that ! Those 3288 networks are MX 19.1.9 which got flagged around Jan 27-28 as critical since 19.1.12 is out. I'm not really a fan of that feature tbh. The version is stable and secure

RaphaelL

Hi , The new view for firmware upgrade is out on my shard : Would it be possible to set a static window size for the release notes ? It's annoying to cycle versions and having to follow up and down the Previous / Next version button. One windows is 200px in height the next one is 400 and so on. The position of the buttons changes on every page. Not sure if my explanation is clear or not Yes I did leave a feedback 😉

RaphaelL

Yeah I think you are right. I'm always a bit hesitant when I see changes to AutoVPN , we have suffered so much in the past. But tbh MX19 has been SO much stable. Kudos to Meraki

RaphaelL

Quite curious about this one : Added support for Diffie-Hellman Groups 15 (3072-bit ECDH) and 21 (521-bit ECDH encryption) in IPsec and AutoVPN configurations, ensuring interoperability with modern cryptographic standards and enhances security postures for sensitive communications. Pretty sure we are going to see a hit in performance

RaphaelL

I took thousands of pcaps on MX and they all behave like that and even from old to recent firmware including MX 15.44 , 16.16 , 17.X , 18.107 , 19.1.7 , 19.1.12 It's very odd and I never found out why

RaphaelL

Hi , That would be nice indeed ! In the mean time you can search it via Organization -> Overview :

RaphaelL

I would open a case , not so much we can look / do at this point

RaphaelL

You migrated from what version ? It seems like your device is unable to install the firmware and is stuck in a upgrade firmware loop

RaphaelL

That SSID is probably going to be unusable

RaphaelL · Re: MX 19.1.12 - Last update for 19.1 - Couple fixes

Ahh that's why !

RaphaelL · Re: MX 19.1.12 - Last update for 19.1 - Couple fixes

This version doesn't seem to be out yet , but I'm able to see the changelog

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges