Our two 6509s got struck by this bug a week ago and we had an entire day of outtage before managing to get the workaround implemented. We have analyzed the Netflow-data we have and see no sign of repeated or consistent mDNS traffic, neither unicast nor multicast in the seconds before the 12-13 crashes, and no sign of any targetted traffic or general multicast DNS after we applied the workaround.
The number of registered support cases on this bug has more than doubled in one week, indicating *something* is happening to trigger this, so I am hereby reaching out the community for more information and knowledge. Is it possible that this can be triggered by legitimate mDNS-traffic? Has anyone else managed to capture or observe targetting traffic?
Bergen municipal government, Norway.