Cisco Bug Discussions

Hello Community We have multicast streams between the FW cluster (layer 3) and the N7706 (two Nodes), because of the BUG we Implemented an non redundant work ork arround (GRE Tunnel).   ::::: Topolgy :::::   N7706  ----------  N7706     |            ...

Does this bug affect Meraki switches?

How to disable MGCP detection on FMC version 6.2.0.2 (build 51). 

Garry Cross, I owe you a six pack! Thank you for posting this, you ended my exhaustive efforts to figure out wtf was going on with my OSPF adjacencies! Frank

does anyone know why the device-sensor accounting command was removed from the 15.0(2) train for catalyst 2000 switches? just updated a few 2960S switches to 15.0(2a)SE9 and suddenly i'm not getting my CDP information sent in my radius device trackin...

is there a fix for this yet? it does not work in asa 9.6.3 either or using TLSV1.1

Just to update anyone else, we had to run these CLI commands even after we uploaded the reportfix10 cop file that was suppose to resolve this issue.   Thanks, Rafael

This also affects other service policy operations such as configuring QoS rules, netflow, etc. Basically, selecting any tab other than 'Protocol Inspection' in the rule actions dialog will fail.

https://community.cisco.com/t5/identity-services-engine-ise/cisco-ise-2-4-0-357-patch-5-cve-2018-15459-cscvi44041/td-p/3796619

I am planning to upgrade my ASA cluster to 9.9(2) code and need more details of CSCvk29685 bug. Is this caused  by running captures? I have Cisco ASA 5585 cluster.

We are having an issue similar.  When the customer pushed the transfer button, dials the number, and then pushes "end call" it puts the person on a permanent hold without a ring back notification.

Hi All -   I'm receiving "%SMART_LIC-3-EVAL_EXPIRED_WARNING: Evaluation period expire.." in my log messages on my Cisco 4431 router.  We aren't using a Smart Cloud manager.   Will it cause any issues if I just run  "no license smart enable" and reboo...

Can anyone confirm the fixed release in 16.3.x? The DDTS Bug notes state 16.3.1, but also say 16.3.1 is affected. The release notes state 16.3.1 and 16.3.2 resolve this caveat.  However, I think I'm seeing this caveat in 16.3.3.   Thanks in advance.

We upgraded a FirePower 7120 from 6.2.2.1 to 6.2.3.7 and it too suffered from this bug.  The bug should be edited so line This only affects the following device series: "70xx (not 71xx)" reads as "7xxx".  On a side note, we have FirePower 8250's upgr...