As an FYI - We're on 10.6.1.11002-15 and experiencing the same behavior. Nice to know there's at least nothing to worry about. We did a cluster reboot, and it did not change the presentation, so it's apparently just that way.
These alerts also being observed on 9.3(12). Anyone having the same issue? CISCO claims that the bug was fixed on this version but apparently it has become too common on 9.3(12). 2023 Dec 6 15:34:38.498 ny5-dedge-mgt-acc83a %PLATFORM-5-PS_STATUS: Pow...
Dear All,Recently, there is a vulnerability found called cross-site scripting(CVE-2024-20251) in ISE and as per cisco article fixed release is mentioned below which is little confusing about the fixed version. For instance, who has 2.7 version so whi...
it's really crappy stuff. we recently hit it ending on one cluster only to our luck. only able to login with maglev. internal 'maglev login -u admin' expectedly fails. so, something to be done via root shell with involvement of CTAC. known fixed rele...
I ran into this bug recently. Upgraded a UCM 11.5 cluster to UCM 14 SU2. The upgrade went smoothly and the certificates migrated normally. This bug came into play when the tomcat certificate was recycled. The existing tomcat certificate was signed...
CSCwf98780 - macOS: Xcode 15 device discovery not working with IPv6 tunnel-all VPN@cisco @support Do you have an ETA on a bug fix for this issue? Sean Batson
Hello Cisco,
we are running a Deployment with 18 ISE nodes; every node is joined to 4 Domainsresulting in totally 72 domain joins ! It is running for more than 5 years now without major issues.
As you do not give any details,neither about the node no...
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi80849/?rfs=iqvred Does anyone know what versions of FTD code fix this issue? The bug article only lists FXOS and ASA versions.
I upgraded the Cisco utility from Any connect to Cisco Security Client, it has version: 5.1.1.27 and after the update, to connect to the former Wi Fi network was impossible. The wi fi network has WPA3 SAE enabled...
My security team has asked us to verify that this vulnerability was not exploited before we installed the update. Are there any known ways of verifying this was not already exploited on a system before the fix was installed?
