Cisco Bug Discussions

I attached 6 Rack mounts c200 to my FI 6120. UCSM was able to discover and acknowledge 2 out of 6. the remain 4 are stuck on discovery state of the following:checking CIMC of server4(FSM-Stage:sam:dme:ComputeRackUnitDiscover:BmcPresence).Can anyone h...

I found this log with version 4.2.1 on CRS-8-LCC-B. And restart wdsysmon, will it impact to any service?

I found this log on 4.2.1 on CRS-8-LCC-B. And restart wdsysmon, will it impact to any service?

Wouldn't it be a workaround to disable name resolution by configuring: no ip domain-lookup ?

Wouldn't it be a workaround disabling name resolution by configuring no ip domain-lookup  ?

Hi,It contains proprietary information that cannot be disclosed at this time.Why ....?!?!?!?!-Sergio

It appears there's a problem with these forums. I am trying to post a message with screenshots to better explain the issue, but when I click submit, the forum rejects my message and pops up an error that says "You must complete the word verification....

Hello,I have not found the firmware version 1.4(5)SR1.1, to resolve this bug. the last version that I have found at Cisco website is  1.4(5.3)RegardsJ.Ortiz

Dear SupportI would like to know in which release this enhancement will be embedded, and if it can be delivered in a patch.Regards 

Hi,I see the status for this bug as Fixed, however on CDETS it shows more state (i.e under investigation). So can we get clarity on this?RgdsManish

As of June 9th, the status of this bug is "Fixed" with "Known Affected Releases" being 1.2(0.899), which is the one we are running.Known Fixed Releases is (0) and then there is a link to the download area where I can download an update to 1.2.1. The ...

Hi Cisco Dev Team,do you intend to implement this feature in the near future?I had several use cases for such a feature and freeradius supports this right now. Greetings,Simon 

Which are Known Fixed Releases? I understand all hw and releases are vulnerable (but bug is not clear in Known Affected Releases section)

I have a suspicion that I have a similar problem. Where can I see the details of a bug? - Bug search tool does not produce results.

Are the messages %IP-4-DUPADDR: Duplicate address expected with HA NAT?  With Stateful NAT they were seen if the "redundancy GROUP_NAME" was not added to the static NAT.  I am seeing them with a correctly configured HA NAT Box to Box set up and there...