Network Usage issue

[alehal]

Hello

Past few week our school has been getting daily network usage Warning emails

The 20 minute usage on the network from 10:20 AM to 10:40 AM EDT on May 20 was 111.75 GB

The usage number changes from little lower then this or higher

I checked our summary report and top items are coming from our Avigilon camera server the rest top ten are also camera related

Avigilon		27.33%
N88386		21.61%

Has anyone ever delt with issue like this before and what could we do to resolve this issue. Is this cabling issue or something else

[Philip D'Ath]

It is not a cabling issue. This is simple data transfer.

Try clicking on the client, then on the right hand side under the pie chart click on "Show Details", and look at the type of traffic it says it is generating.

[alehal]

This is what I am seeing when go into details for appliccations. UDP items all from camera softwares we have. Thinking might need to talk security to see if they made some changes might be causing this

[CMR]

This is likely the camera video streams. Are you saying that the traffic was no there before? Look at the source and destination IP addresses, I'd expect that they are the cameras and the NVRs. If not then can you work out what they are?

[parameswaran]

Hi Everyone,

We've been facing this issue for sometimes our network will receive this alerts very frequently like 4 times a day, when we reviewed the communities most of the answers that we got was it from MV, but however in order to confirm this we have raised a meraki support case and support has mentioned that this is actually a well known case in meraki and it is caused by a bug in the MX firmware which incorrectly counting the traffic flows which results in an erroneous usage data alerts and we can’t perform any configuration change to resolve the issue we just have to wait for the new firmware to rollout to fix this which doesn't have a ETA, in the meantime for a workaround solution we can disable the alert until the newer firmware is made available.

Thanks

[CMR]

Indeed, the 18.x firmwares in particular have had this problem. The 19.x firmwares had apparently fixed it, but I see that in the 9th December update it is back... 🤦🏻‍♂️