Cisco Bug Discussions

ASA5500-X Chassis Serial Number Not Visible from CLI

For the above query adclient application services stopped and resarted again,but the application acs status shows the error "Execution failed".Kindly suggest the end solution for this bug.

                   Hi Experts,How I can solve this problem?BR,

Originally posted:  2012-Nov-18Bug tracker:  CSCuc48084A complete list of the issues and updated patterns to fix those problems is listed here:https://supportforums.cisco.com/thread/2171992Thanks!

I dont know!

Hi,Has anybody experienced this issue?Probably we are in the same situation.Vsan recreation is the only option?Thanks in advance.Krisztian

Since I have lost a full day with this bug I think that it is worth to publish it on the community for better visiblity.I was doing a refresh upgrade during the Jump Upgrade procedure (7.1.5 --> 9.1.2) when I hit the bug.I was lucky that I was workin...

What should we do to fix this bug except upgrading the VISM SW / FW ?

Seems that this bug should be corrected in ASA version 9.0(3.5)wait and see ;o)

                  Has there been any workaround or OS fix available for this bug?

                   Has software version 7.6(1.70) been made available to the public?Downloads Home Products Wireless Wireless LAN Controller Standalone Controllers Cisco 5500 Series Wireless Controllers Cisco 5508 Wireless Controller Wireless LAN Con...

We recently upgraded our C7609-S routers to 12.2(33)SRE8 version. Post a month of these upgrades, I am continuously getting the SIP-200 related alarms on one of my routers which matches with bug id CSCsm80678.Only IOS version 12.2(33)SRB1 is mentione...

The impacted version is IOS XE 02.02.02 and not 03.02.02 as listed in the bug description.

Start and stop ise application resolve the problem or only the reload command resolve this issue. Thanks

I have experienced this issue in NXOS 6.0(4) 7009I resolved this issue by removing the standby IP in GLBP on the standby CoreI then readded the standby IP and no longer saw the error relating to that Vlan in the log