New Feature - Assurance

[B33b5]

This new feature I've been believe looking at I feel there is something wrong.

We have majority of our MXs whether MX67, MX250 showing maxed out on Utilization and CPU 24/7 even when they aren't in use overnight they are still maxed out.

Clearly there is a floor in this.

I've raised a support ticket but want to make sure other Meraki users don't read too much into the figures/data if wrong.

Thanks

B33B5

[RaphaelL]

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 ?

[ww]

That sounds like a bug from 18.211.2 firmware

You could try the .4 upgrade

[Beebs]

The stable MX 18.211.2 firmware version

[NFL0NR]

On the other hand, for us it was a problem.  our mx450's were showing 100% utilization and we were killing it.  It even caused it to reboot until we offloaded dns traffic.   I wouldn't say they're 100% accurate but I wouldn't say they should be ignored either.  Kinda like the lights on your vehicles dash.  

Many factors go into your utilization and cpu score is driven by packet processing (ids/ips) and anything the mx is routing.  Most important is not to exceed your maximum number of flows.. (thus why we had to offload dns)

[Beebs]

It is with Support to review as like I've said to them site is non-operational between 6pm to 9AM but it does not show any drop in utilisation.

Hence want to know what the crack is that it's not a red herring. 

@RaphaelL @ww I've checked MX 18.211.4 change log not showing MX67 100% utilization so either they are unaware or unrelated issue.

[jimmyt234]

We have noticed something similar across a dozen or so MX67 devices - CPU will remain constantly > 80% even during low/no traffic periods (ie. overnight). Running a mixture of 18.211.2/3/4

Meraki support have said:

"Following an investigation of backend logs, we have confirmed that the MXs are being affected by an unexpected behaviour which causes the device to run at 100% CPU usage when one of the LAN ports is converted to WAN2, IDP/IDS is enabled, and a WAN change is made.

The behaviour was already raised to our development team who are actively investigating and looking to produce a fix as soon as possible.
Unfortunately, there is no ETA for when the fix is going to become available, at this moment in time.

The workaround to reduce the CPU usage is to either restart the MX or disable IDP/IPS for around 5 minutes and re-enable it."

We are in the process of scheduling reboots for these devices to see if it fixes it.

[Beebs]

UPDATE

I've been asked by Support to upgrade to MX 18.211.4 so they can take a look at the MX backend.