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?
Introduction to Essential Utility for Optical Network ProfessionalsSnapshot of utilityFeature SupportedComposite Power calculatorNet Composite power Change when some channels are added/removedDirect Conversion for multiple parametersUse CasesSupported Tec...
There are few interoperability issues between 2960x and other vendors. In this article we will go over the steps on how to debug these issues.
Check the phy id from “show controllers ethernet-controller phy” output.
<snip from show controllers ethe...
It appears that you are trying to access end of life information from Cisco search. We have detected a problem with your script ("eol...) and would like to help. Please contact email@example.com if you would like support.