About JDomagala

JDomagala · ‎03-29-2022

Now that is just ridiculous. No matter how many years it will be supported or sold for, what matters is amount of that devices in production. This is most heavily used MX in my organization of 2k+ networks. So yes, Meraki should spend a couple of days of testing to measure the VPN throughput limitation, probably the meaning of VPN peers/clients has on that limitation too. Can that be arranged?

JDomagala · ‎03-24-2022

Do you monitor perfscore on that MX? I assume it was MX100. Known 17.6 bug is "significant" VPN throughput capabilities decrease for MX100 and MX84. I wonder what that means - how much is significant 🙂 Asked Meraki but no response for now.

JDomagala · ‎03-22-2022

"MX84 and MX100 appliances have significantly reduced VPN throughput." What does significantly mean? 5%, 35%? Please test and provide specific information on VPN throughput limit for those platforms on this firmware.

JDomagala · ‎03-03-2022

What is the support take on that? @Meraki was the issue debugged or reproduced in lab? 16.16 was supposed to be a solution for major issues we have in a vast global network, I think community needs details fast.

JDomagala · ‎03-14-2020

Sorry, but this is unacceptable. Everyone wants to know the root cause for lack of connectivity. On smartphone when I loose connectivity when needed badly, I am very much interested if my gear is the problem or is it the network issue. If my home fiber connection went down, I want to know if that has to do something with power or is it an ISP problem. When I administer thousands of Meraki sites, knowing if connection loss is power related is quite important. This is a simple function to write, probably only change would be for the dashboard. This thread does handles the matter more seriously: https://community.meraki.com/t5/Security-SD-WAN/Uptime-command-in-Meraki/td-p/49260

JDomagala · ‎11-13-2019

Thanks Nolan, I guess advanced alarm suppression logic can be done outside of Meraki and those traps should suffice. The other subject: this is what meraki forum adds to my posts: <div class="mceNonEditable lia-copypaste-placeholder"> <div class="mceNonEditable lia-copypaste-placeholder"> </div> </div> <div> </div> <div> </div> <div id="vidyowebrtcscreenshare_is_installed"> </div> I had Vidyo extension installed and for some reason that info was attached, causing problems with posting too 🙂

JDomagala · ‎11-13-2019

Sure I made a wish, just thought that this should be spoken about on the forum if someone would look for a solution 🙂 yeah, there probably is some > or / put where it shouldn't be 😉

JDomagala · ‎11-13-2019

Hi, I would very much appreciate if Meraki created new type of trap/alert - for x cellular connecting failures in y time, where x and y would be configurable. This failures happening once in a while probably wouldn't affect user experience since cellular is mainly backup, right now we don't have alerting at all for cellular backup not working at all if its trying to connect all the time. Also, every time I post something on Meraki Community, I get this: "Correct the highlighted errors and try again." "Your post has been changed because invalid HTML was found in the message body. The invalid HTML has been removed. Please review the message and submit the message when you are satisfied." And I'm really just typing to create that invalid HTML 🙂

JDomagala · ‎10-24-2019

I made a wish for alerts on 95th percentile threshold crossing per link and alert for all thresholds like that crossed in network. It does fall under performance monitoring rather than fault management though. Traditionally that's done by external monitoring systems. SD-WAN solutions should have that threshold alerts though... Maybe the only way is to make more and more wishes.

JDomagala

Community Record

Badges

Re: New MX 17.6 stable release candidate firmware - no longer a beta, many ...

Re: Meraki Firmware MX 16.16 problems - MX 100 and MX 64

Re: New MX 17.6 stable release candidate firmware - no longer a beta, many ...

Re: Meraki Firmware MX 16.16 problems - MX 100 and MX 64

Re: How to show uptime on meraki switch?

Re: Alerting for notorious cellular connecting status

Re: Alerting for notorious cellular connecting status

Alerting for notorious cellular connecting status

Re: Network saturation, high latency, high loss; why can't I get an alert f...

Re: New MX 17.6 stable release candidate firmware - no longer a beta, many ...

Re: Meraki Firmware MX 16.16 problems - MX 100 and MX 64

Re: New MX 17.6 stable release candidate firmware - no longer a beta, many ...

Re: Meraki Firmware MX 16.16 problems - MX 100 and MX 64

Alerting for notorious cellular connecting status