Rx Drops and Rx Filtered - High Counts on Mimosa C5?

[uberdome]

I have a Mimosa C5 powered by a Netonix WS-6-MINI. It has very high counts of Rx Drops and Rx Filtered errors.

I thought this was a physical problem, so I tested many changes. I replaced the Mimosa C5, I replaced the network cable, I used a shorter network cable, I replaced the WS-6-MINI, I replaced the power... and all of these efforts still showed high error counts. I have other locations without these error counts. I have other sites with the same configuration that do not have this problem.

These are the error totals for the past 6 days:

Screenshot 2022-07-21 154800.jpg (13.77 KiB) Viewed 3376 times

What would cause such high error counts?

What is unique about Rx Drops and Rx Filtered that they are listed under "Receive Errors" but they are not counted on the "Status" page under "Errors"?

Thank you, Chris

[KBrownConsulting]

RX Filtered aren't anything to worry about. viewtopic.php?f=6&t=747&p=5516&hilit=rx+filter#p5516

I believe one example of a scenario that would result in a filtered packet is a packet arriving at the port on a VLAN not assigned to the port.


As far as RX Drops go:
viewtopic.php?f=17&t=3030&p=20440&hilit=+rx+drops#p20440
viewtopic.php?t=1682&p=12562
https://forums.netonix.com/viewtopic.php?f=6&t=1163

[uberdome]

...I believe one example of a scenario that would result in a filtered packet is a packet arriving at the port on a VLAN not assigned to the port...

Actually, it turned out untagged packets were hitting the port - but no untagged VLAN was assigned to the port in the Netonix. This was causing the high Rx Drop errors. I believe it was just broadcast traffic in that particular broadcast domain. I added a VLAN, and untagged it on that port in the Netonix. Then, all Rx Drop errors stopped.