Meraki

RaphaelL · ‎Dec 2 2024

Hi , Where is the root bridge of your topology ? I would look at logs on that device and start from there.

RaphaelL · ‎Dec 2 2024

Hi , DNS requests must be seen by the MX. So they can't be encrypted and can't be intra-vlan DNS requests. DNS requests over Auto-VPN/NMVPN is fine. DNS requests over Internet is fine. DNS requests inter-vlan is fine.

RaphaelL · ‎Nov 30 2024

Wow cool ! I didn't expect this book to be found in a library ! lucky you !

RaphaelL · ‎Nov 28 2024

Hi everyone , I just saw a new book published for Securing Meraki Networks : https://www.ciscopress.com/store/securing-enterprise-networks-with-cisco-meraki-9780138298180 I haven't read it nor bought it yet but it looks well made according to the reviews ! I didn't know where to post this , but this might help people ! Cheers ,

RaphaelL · ‎Nov 28 2024

This is one of the lowest priority case between all our active cases (20-30). They will get there , but geting concrete answers has been a hard task lately.

RaphaelL · ‎Nov 27 2024

I would be curious to know if you are using Umbrella. I have an open case ( from 2022... ) that all my MX450s in Concentrator mode are sourcing that type of trafic and we are not using umbrella. I wasn't able to get an answer from Meraki since then.

RaphaelL · ‎Nov 26 2024

Re-tested this behavior this morning and with MS 17.1.3 I still do have this problem of random packets dropping every x packets on a span port.

RaphaelL · ‎Nov 26 2024

I just tested a Span port on a MS120 , it is much more reliable , but I'm still dropping packets out of the blue. This is a bit annoying when you want to do a proper troubleshooting.

RaphaelL · ‎Nov 24 2024

Lowest physical port(s) of "Active" stack member switch become root port(s), port(s) on the member switch in the stack would be in STP blocking under normal conditions Is there a proper way to provision a stack without placing the "Active" stack member on top ? In your example MS425-16-1 has to have a lower MAC than MS425-16-2 if you want to have the "correct" ports in blocking. It is a bit annoying because even if you place the lowest switch MAC on top , after a RMA you have to rebuild the stack according to the MAC. Selecting the "Active" stack member from dashboard would solve that , but no idea if there are any plans for that

RaphaelL · ‎Nov 22 2024

Yep pretty sure I also have experienced this behavior on a small MS.

RaphaelL · ‎Nov 22 2024

No. It is my MX at home. Directly plugged into my ONT. My PC is a client behind the MX. My PC is bulding a VPN tunnel to a VPN appliance somewhere else. The MX is displaying the packets in the wrong sequence but are received in the right sequence.

RaphaelL · ‎Nov 22 2024

I can't quite find the exact answer I got months ago. It was something that the packet capture engine is not prioritized by the CPU. So It can miss packets or show them in the incorrect order.

RaphaelL · ‎Nov 22 2024

Hi , Just encountered once again a very special behavior on the MX plateform ( running 19.1.5 ). Testing scenario : I'm capturing IPSec ( VPN tunnel from my computer to a VPN gateway ) trafic on my PC and on my MX which performs L3 routing for my LAN. My goal is to capture all ESP packets and compare the ESP Sequence to quantify the number of ESP packets inbound that are out of order. To my biggest surprise the 2 traces are way different. As you can see the exact same packet with the same IP ID and the same ESP sequence appears out of order only on the pcap taken on a MX. Conclusion : The packet capture engine on the MX is way to unpredictable. Packets are routed and forwarded in the correct order , but they will be scrambled in the captures making troubleshoot harder. Yes. I had a case opened in the past. Yes they said this is expected. Reason #34591 that I dislike MXs.

RaphaelL · ‎Nov 22 2024

Might be far fetch but can you capture the beacons to confirm that 802.11r is not enabled ?

RaphaelL · ‎Nov 19 2024

Hi , Have you tested this with a more recent MS firmware ? MS 17.1.4 is stable RC.

RaphaelL · ‎Nov 18 2024

No since the frames will be forwarded and not routed. ( L2 vs L3 )

RaphaelL · ‎Nov 18 2024

Hi , Where are you reading this info ? Also there is a firmware bug related to Device utilization stuck at 100%. What firmware are you running ?

RaphaelL · ‎Nov 18 2024

Hi , https://documentation.meraki.com/General_Administration/Monitoring_and_Reporting/Device_Uptime Requirements and Limitations Device uptime is supported on all Cisco Meraki switch models and most access points. Support for other products is planned for future availability.

RaphaelL · ‎Nov 17 2024

Bonjour , Peux-tu nous partager les configurations du wifi qui est sous Meraki ? Est-ce que la TV supporte seulement 2.4ghz ?

RaphaelL · ‎Nov 15 2024

Forgot to reply to my own post lol. Support told me this is a known issue that won't be fixed since this will be replaced by Assurance Endpoints

RaphaelL · ‎Nov 14 2024

Easiest way to troubleshoot those issues would be to take packet captures. 1- Capture on LAN side of the MX Spoke 2- Capture on the Site-To-Site VPN interface of the VPN spoke 3- Capture on the Site-To-Site VPN interface of the VPN Hub if you see the DHCP requests on all 3 , the problem is not on your Meraki environnement

RaphaelL · ‎Nov 14 2024

THIS is what I like to read ! I will speak for the rest of the group but we dedicate a lot of our time on the dashboard and also here on the community. To see that someone from Meraki reads our suggestions / critics is good way to tell us that we have a voice and can influence Meraki and hopefully make the experience even better ! - Raphael & and the rest.

RaphaelL · ‎Nov 13 2024

6 or 7 ( who is counting ) The scaling of the timeline is super odd. Increments of 16-17 minutes and doesn't line up with the graph below.

RaphaelL · ‎Nov 13 2024

5 - This is what I was refering to.

RaphaelL · ‎Nov 13 2024

It is not as bad as I expected , however they need to re-organize the info on the left. It is scattered. 1- I would put in a block all SSID / radio related info. 2- Put the notes right below the address 3- Group uptime and firmware in the same section. 4-I have the same 'bug' , SSID id '0' is displayed instead of the name of the SSID. Odd text wrapping for long client names ( you know these damn client names that are created with mDNS instead of DHCP that people have requested for years to change the processing order of a client name xxxxxxxx-4a0c-4148-a1ee-cf390578ab3c 🙃 ) 5-Centering of the client info is also messed up. Some collums are centered and some are not. The info shouldn't take 1/2 of my screen. Put all that text in a small (!) icon. Need help with your UI ? 1-800-Raphael

About RaphaelL

RaphaelL

Raphael Letourneau

Community Record

Badges