Sounds similar to an issue we just had on site with produced/Consumed tags. Our network team traced it to how some of the managed switches handled multicast traffic. in this case the switches were required to have an IP address in the Multicast vLan to ensure correct handling of Multicast traffic. So could be worth checking how your switches handle Multicast and check their config against that information. Or if possible replace with unmanaged switches and see if the error goes away.