Re: How to fix?
The only solution here - if the CLI or other management tools aren't able to access devices to add filters on the fly (if it's even possible on this equipment type) - would be to take down ALL THE DEVICES that take part in the broadcast mayhem AT THE SAME TIME to ensure that the bad packets are gone.
Yup.. Which even if one can convince management, can be easier said than done. So lots of nodes, many of which would probbably be in transmission huts & unmanned sites. So just use your remote power management system to do an emergency shutdown.. But that assumes you've got working OOB access to the power systems, and enough field engineers to deal with nodes that don't power back up. Which should be possible on a good network, but then there's pressure to cut costs..
But it's an inherent risk with using Ethernet for anything, especially when it's deployed on systems that would naturally be physical or virtualised rings. So it's going to loop, and it will result in broadcast storms, unless you have a way to mitigate those built-in, or contingency plans for when they happen.
Biting the hand that feeds IT
