Cisco Bug Discussions

BootROM 1.41Booting from SPI flash General initialization - Version: 1.0.0Serdes initialization - Version: 1.0.2mvCtrlPexPolaritySet: TWSI Write skipped, leaving PEX polarity in EP modePEX: pexIdx 0, detected no linkDDR3 Training Sequence - Ver TIP-1...

Hi , Could anyone help me to fix the issue, Leaf switch 93216TC-FX2 keep on reloading, it has ACI version: 14.2(7v)  Logs: version 14.2(7v Reason: reset-triggered-due-to-ha-policy-of-resetSystem version: 14.2(7v)Service: sdkhal hap reset   Thanks Mar...

I found this bug CSCwn07392   ，but no way to fix，what can i do to fix this problem?

It is not listed as effecting 17.06.03, but I have two C9300-48UXM switches where this is affecting.  Very infrequent. Switch#sho log | inc temp Apr 15 2023 19:46:28.305: %THERMAL-2-THERMAL_YELLOW_THRESHOLD: Switch 3 R0/0: cmand: Hotspot temperature ...

I have reviewed this open bug.  First of all, I would like to ask the question, Is Cisco going to fix it?  It does not appear as such being that they have not attempted to fix it over multiple versions for the at least couple years or more they have ...

The message in the title does not disappear (appears only in the PCisco Bug Discussions, Cisco Bugsublisher) after upgrading my entire cluster.Only until I ran a post upgrade check on the Publisher and then a reboot made that disappear.Why do these m...

Same Problem..I hope there is a fix soon

Hello,Currently I'm trying to update my CISCO account to partner, as my current company belongs to this kind of role. Everytime that I've tried to do it, different web browswer, cleaning cookies, etc etc always have the same error that im enclosin. P...

Upgrading from 17.09.05 to 17.12.04 corrupted the PAC key on a C9300-48P switch stack, thus breaking RADIUS authentication with ISE.After re-applying the original PAC Key to the stack, RADIUS authentication started working.

Is this bug still active? 

CVE-2016-6409 - this vulnerability affects cisco IOS & IOSXE. In the cisco advisory IOS mentioned as - 15.6(1)T but IOSXE version not mentioned. Can someone Help to check  

In CUCM v12.5 SU3, we have stopped this service, although we try to start it manually, it always returns to NOT RUNNING.As data we only have one node in this case CUCM PUB.any idea how to start the service? 

Could we add functionality to the rehoming process so that if rehoming fails the agent falls back to the original on-prem cluster and the UI reports the agents that failed to rehome? Otherwise, there are several manual steps that require a server adm...

Recommended workaround is to use firmware from 2022?