Cisco Bug Discussions

Hello!Did anybody try to upgrade your OpenSSL on Cisco to 1.0.2zg because of the bug? Or is there another way to solve this? TY and BR

This bug CSCwa45730 [Known Fixed Releases] contains 5.0(1c) as fixed. This is incorrect. I opened a Cisco HXDP support case to clarify and indeed, 5.0(1c) is vulnerable.  Only HXDP containing ESXi 7.0U3i or later with an upgrade to HXDP 5.0(2a) or la...

happens in 11.5(1)SU2 also

Does version 9.3.(12) have a cosmetic issue as its previous version for power supplies? 

Hello @cisco Team,We recently upgrading the cisco Switch stack WS-C3650-48PD to version 16.12.07 and unfortunately switch 3 didn't came up post upgrade. We encounter the following error messages.Front-end Microcode IMG MGR: found 1 microcode images f...

When I click save and deploy I get the following error for one of the CVP call serverAn Unknown Error occurred while working on Save&Deploy Unified CVP Call Server, please consult your Administrator for more details.The logs read below37284: 172.21.1...

The workaround on listed on this bug may be somewhat misleading and unnecessary for a couple reasons. The bug details seem to lead to the understanding that Ekahau v11.3 project files are not supported, but as noted in the bug details, the cause is d...

I have the RV340W setup on two different offices/locations. Both have the same issue: After 25-35 leases no more DHCP leases are being issued. I can use static IPs just fine over the 25-35 limit, so the problem seems to be related to DHCP.I'm using t...

We use logs for forensic information and expect the data to be accurate.  For logs to contain incorrect information is worse than not containing any information.  FMC has correlation rules / traffic profiles that use this data but the data is not cor...

We recently hit this bug in UCCE 11.6.1 / CUIC 11.6.1.10000-44.  Our client reported that some users were getting the following error when trying to view live data report gadgets in Finesse. "Request to Server returned Forbidden".   We traced the iss...

DNAC2.3.5&ISE 3.2.0.401&IOS-XE 17.10.01 affected. W/a is to reload of entire stack 

Bug status is "fixed", but no "Known Fixed Releases" and no Workaround available.Is there a new COP coming and if yes, when can we expect that?

This is a problem we cannot connect to our ISE server with a ".i" TLD...cant believe they have a regex validation on this field...like we wont know what FQDN we have...

Once connected to a port  with Spanning tree it was easy to clear the error by disabling both ports on the FI and then enabling the ports.  Doing this on both FIs caused the error to be cleared on both Fabric Interconnects This was the alert we recie...