Cisco Bug Discussions

I've started an IDEA (feature request to modify this behaviour. Vote up if you are interested: https://ciscocollaboration.ideas.aha.io/ideas/COLLAB-I-5609

This bug shows it is fixed, however there is no workaround defined, and there is no Fixed release shown.

For anybody with this issue, rather than downgrading from Java 8/latest ASDM version, follow these steps: Control Panel > Java > Network Settings. Change the option to 'Direct Connect', this will resolve the issue of it just sitting at connecting. An...

Hello Team, Two questions: 1. is version 7.0(3)I4(1) impacted by this bug too? 2. is this bug fixed in version 7.0(3)I7(1)? Thank you

use caution when applying the 400 ms workaround. While this Did stop the failed echo and BFD bouncing, it caused massive instability with our OTV AED with dual site adjacency. the OTV Join interface was using BFD for OSPF. Both 7k's were not AED Auth...

My ASA version 9.8 (1) Show version Cisco Adaptive Security Appliance Software Version 9.8(1) Show processes | include Unicorn Mwe 0x00007f8ecb3a2f38 0x00007f8eac36b688 0x00007f8ed0bb0a80 2272 0x00007f8e994a3030 30528/32768 Unicorn Proxy Thread 223 P...

I don't think this is a "logging issue only" - since based on this logging, the appliance sends alert emails that are the only valid way of monitoring the health of the system. And if the monitoring of a system is generating constant false positives,...

Any update on the fix? Why is it taking so long to resolve this issue? 

Does anyone know if Cisco is looking to get this fixed?  It doesn't make sense that the data is available and on box, but can't be viewed in a readily accessible dashboard widget when in flexconnect mode.  Fells like someone missed something.

Ok so is anyone else seing problems with the supposedly fixed versions of ASA code Advisory says if Unicorn Proxy Thread iexists you are vulnerable   Our ASA-5525-X is running 9.9(2.1) and we get the following Show processes | include Unicorn Mwe 0x...

It is not fixed in 6.4.0.4. We had a real similar issue.

Please help us understand whether this bug is introduced with UCCE 12.0 and above. Is there any work around for this?  When is this going to be fixed?

Is there any resolution available for the above bug from cisco.Latest update from cisco states work around is still not available

I hit the same issue on 4.0(4d).