Cisco Bug ID CSCtn29349

Similar Questions

• Is there a breakdown for Cisco bug ids?

  I'm curious to know what are the values of the id of the bug.  For example.  All bug IDS begin with the CSC followed by two letters and a series of numbers.  The two letters represent something beyond the unique values randomly?  I was hoping that by looking at the release notes for a new version of the code, I could easily identify what kind of bugs have been fixed.  More specifically, in my case, I want to identify easily if security vulnerabilities have been fixed in a version of particular code without having to maintain an exhaustive list of all security bugs.

  Hi Dave,.

  I'm not aware anyway to easily accomplish what you want.  Here are the options I can think of:

  Bug ToolKit (known affected Version)
  Note of support for the SW version (OPEN / closed caveats)
  Notice of security itself.

  Not much can be taken from the id of the bug itself.

  Best regards

  Ben Solero

• Bug CSCta93305 not visible to me

  Bug tool provided the following details, I received the support of reference Bug ID by RIM, which relates to the RIM Blackberry MVS customers and Cisco IOS H323 PSTN gateways.

  Can you provide details on what is the bug number and if/when it is fixed?

  CSCta93305 Details of bug

  Dear Dear customer of Cisco Bug Toolkit, you are looking for the bug ID CSCta93305 contains proprietary information which cannot be disclosed at this time. so we can't display the details of the bug. Please note that it is our policy that all external bugs available in Bug Toolkit to help our customers. Therefore, system administrators have automatically been sensitized to the problem.

  While we work to resolve this issue, we invite you to join the experts on the Bug Toolkit support community. You can find here answers to your questions Bug Toolkit, or send your comments on our forum as well. Thank you.

  Note: Some requests for documentation bugs and product improvements are not available in the Bug Toolkit

  / * Style definitions * / table. MsoNormalTable {mso-style-name: "Table Normal" "; mso-knew-rowband-size: 0; mso-knew-colband-size: 0; mso-style - noshow:yes; mso-style-priority: 99; mso-style - qformat:yes; mso-style-parent:" ";" mso-padding-alt: 0 to 5.4pt 0 to 5.4pt; mso-para-margin: 0; mso-para-margin-bottom: .0001pt; mso-pagination: widow-orphan; do-size: 10.0pt; do-family: "Times New Roman", "serif" ;} "}

  Hi Darmstrong,

  The reason there is no information for the bug id "CSCtf98962" is that this bug was filed as new feature enhancement and is not in the external customer environment. Sorry for the inconvenience.

  If you have 8.0.X and 7.1.5 versions running on your product, these bug - id CSCsr03120 and CSCtd07904 can help you.

  Also you can save this bug and you will be informed when more information is added to the bug or published on the external environment. More details on how to save the bug, and to receive notifications is available in the link help on the upper right part of BTK.

  Kind regards

  Gibot.

• "" Cisco ASA multiple defects remote control let users deny Service and bypass the security controls ".

  Recently we have heard people talk of "Cisco ASA several flaws let users deny remote Service and bypass the security controls" under the securitytracker. However, as everyone knew, ASA 8.3 need a lot more resources on ASA HW to run. I checked that the bugs associated to above problem "CSCtg69742, CSCth36592, CSCtg61810, CSCte53635, CSCte46460, CSCte20030, CSCtf29867, CSCte14901, CSCsz80777, CSCsz36816" in the Cisco Bug Toolkit. None of them show any information if there is a fix for ASA 8.2 (x).

  This means that Cisco starts to stop supporting 8.2 (x) and to push customers to their "so-called" best image 8.3 version (x) as a strategy of "marketing?

  Cisco is best to find a solution for this problem on 8.2 (x) rather than push customers to something Cisco "love." It may not be the best interest of the customers AT ALL. Instead of pushing customers to ASA 8.3 (x), Cisco likely to push customers to its big competitor Juniper:)

  Sean,

  I did a quick search on the Bug Toolkit for CSCtg69742 and found the following result.

  Fixed in
  8.2 (3)
  8.3 (1.5)
  8.3 (2)
  8.2 (2.15)
  8.2 (2.107)
  100,7 (0.17) M
  100.5 (5.16) M
  8.3 (1,100)
  100.7 (6.1) M
  8.4 (0.99)

  This was posted in the column on the left side of the search results page.

  I recommend you research each ID of Bug Bug Toolkit (http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs) for the version name (number) that contains the fix for this bug.

  HTH

  Amol

• Can not find information about CSCtf98962 in Bug Toolkit

  Hi all

  We found the CSCtf98962 in the Release Notes for Cisco Unified CCX and Cisco Unified IP IVR 8.0 (2) SU1 in the section warnings resolved. However we have found no information on Bug Toolkit. It shows below when we tried to find CSCtf98962:

  Dear Dear customer of Cisco Bug Toolkit, you are looking for the bug ID CSCtf98962 contains proprietary information which cannot be disclosed at this time. so we can't display the details of the bug. Please note that it is our policy that all external bugs available in Bug Toolkit to help our customers. Therefore, system administrators have automatically been sensitized to the problem.

  While we work to resolve this issue, we invite you to join the experts on the Bug Toolkit support community.  You can find here answers to your questions Bug Toolkit, or send your comments on our forum as well.  Thank you

  We are currently conducting unwanted and would like to know the symptom and the workaround for this bug. Any help would be much appreciate.

  Thanks in advance.

  Hi Queen,

  The reason there is no information for the bug id "CSCtf98962" is that this bug was filed as new feature enhancement and is not in the external customer environment.

  Currently, the bug is changed and it should be available in the Bug Toolkit within 24 hours.

  Kind regards

  Gibot.

• Misfiring ID 2200 (invalid IGMP header)

  I get that alarm a lot. When I discovered the captured packet the header value is 22. only<11 is="" supposed="" to="" fire.="" can="" anyone="">

  This problem is resolved in the update S149. For reference, she was assigned Cisco bug ID CSCeh26783.

• ISE v1.4: "WARNING: Profiler Queue size limit is reached.

  Hi all

  We have improved our nodes 10 v1.2.1 Patch v1.4 ISE 6 weekends. Since then, we have been doing the above alarm message very frequently (often every five minutes) and it's really annoying.

  Six of the ten nodes have the character of PSN and they seem not to be under any large load (less than 10,000 active endpoint points shared between them) and the readings of CPU and memory and latency are all very low.

  I wonder if I ran into the following Cisco Bug:

  https://BST.cloudapps.Cisco.com/bugsearch/bug/CSCuw93839

  Unfortunately, Cisco provide little information on the bug above, I can't be sure.

  Has anyone encountered this?

  Thank you.

  rgrds,

  Inayat

  I think that maybe it's actually the following problem

  CSCuy20317 Error "profile tail limit reached" in the patch 1.3/4 5 +.

  If that is the question, the good news is that 1.4 patch 7 has been posted and includes a fix for this problem

  Curious to know how you go

• E-mail manager webview

  I am trying to install the e-mail Manager option 5.0 and integrating it with icm 7.0. When I try to access my webview for email I get error like "http 404 page not found". I tried all the troubleshooting solutions listed in the cisco bug Toolkit but even so iam not able to solve. kindly help me out in this issue. Also, I'm getting an error of connection for t server failed.could log someone help me in this.

  Oh. Problem.

  Problem. Problem. Big problem. I don't know if this can be resolved.

  I know that it is never mentioned in CEM 5.0 installed, but when you install a version of service and you read the release notes, it is written here:

  Create an instance of CEM 5.0 (0) with the name of the instance? CEM? or? CEM? causes a malfunction of the server of the user interface. Use of the name? CEM? or? CEM? is reserved and should never be used for example name in any form.

  http://www.Cisco.com/Web/ccbu/Cem/5/0/0/8/0/0/CEM5.0.0_SR8_Release_Notes.PDF

  I've seen this problem before: just webview wouldn't start upward if the instance name is CEM.

  It's totally weird, if you go to the formation of the ICM multi-channel Option, you install an EMC instance named "EMC". Funny, right?

  G.

• TMS not related loss of package codecs C series

  Hello

  I have a TMS system (13.0) and a mixture of C20, C40 and older MXP endpoints. While trying to track down a video problem I had, I noticed that the TMS is not presenting the any of the conferences on the C Series codecs in conferences of packet loss. I see several entries for the older MXP endpoints but nothing involving endpoints of series C. I looked at the logs on the codec itself, and he showed that packet loss was produced on the Conference in question. Example from eventlog/all journal entry the below:

  Jul 10 19:44:13 arm4 video4: 410097.85 i DEC_FSM-4: decode Err: 76836 framework: (lost packets) ERROR 0x00000a40 | Corrupt data. Concealment applied | H264D_ERR_COPROCESSOR_STREAM_BUFFER_ERROR

  Anyone know if I need to enable something different on codes of series C for reports using the TMS packet loss or what I'm missing here?

  Thank you

  Steven

  Hello Steven

  C-series, MX and EX relate not to TMS packet losses. This option works only with MXP.

  You should check on the endpoints itself, as TMS will never show that.

  There were enhencment CSCtq54891 open there for that and you can watch it via Cisco Bug Toolkit:

  http://Tools.Cisco.com/support/BugToolKit/search/getBugDetails.domethod=fetchBugDetails&bugId=CSCtq54891

  Thank you

  Rafal

• CSCtg84350?

  I downloaded a bug for code 3750 scrub 12.2 (53) SE1 sometime.  In reviewing some of the bugs that interests us, CSCtg84350 is now more visible.  It is said:

  "Dear Dear customer of Cisco Bug Toolkit, the bug ID CSCtg84350 you are looking for has not received correctly to a Cisco product; so we can't display the details of the bug. Please note that it is our policy that all external bugs available in Bug Toolkit to help our customers.  Therefore, system administrators have automatically been sensitized to the problem. »

  If I understand the original description, it was related to the SLA/RTR.  Execution 'ip SLAs enable timestamp' caused active and reserve HSRP nodes become active.

  Updates on this please?  Thank you!

  This is a bug in the documentation, and the accompanying note were displayed.  Not sure why it has not been the case.

  The release note is:
  
  The HSRP both active after exec "ip sla enable timestamp".
  To work around, Increase hello timer values
  
  e.g. standby timers 15 16
  The explanation is that when low level timstamping gets enabled, the hsrp hello timers need to be increased as well since there is a greater delay between when the packet arrives at the interface and time it is handed to the application.
  
  

• display of packets on WS-SVC-IDS2-BUN-K9 module

  Hi all!

  I try to use CLI command 'package display' WS-SVC-IDS2-BUN-K9 module.

  If I put only the name of the interface as an argument to the command:

  display packages gigabitEthernet0/7

  I'm having a lot of packages. It is ok.

  But if I add expression argument I get nothing even with necessary traffic on the wire:

  package display expression gigabitEthernet0/7 ip proto \icmp

  package display gigabitEthernet0/7 expression verbose dst host IP

  package display gigabitEthernet0/7 expression verbose dst port SOME PORT

  I tested the problem on 5.0 (2) and 1.0000 E3. Results were almost the same.

  On IPS-4255. all mentioned above command produces the expected results.

  I searched Cisco bug-tool and found nothing.

  Can someone check to reproduce? Has anyone seen it?

  Or maybe it is not a bug, but a feature. But I wasn't able to find his description.

  Wait for a response.

  Kind regards

  Maxim

  The order of packages use tpcdump under the covers. Thus, the expression must be a valid expression for that tcpdump will understand.

  If packets are standard IP packets, then the expression can be applied directly (which is probably what you see on your IPS-4255).

  BUT if the packages have a 802. 1 q header (header of vlan), then a special statement should be added in the expression for tcpdump to find out how to apply the rest of the expression. With the JOINT-2 he found in most JOINT-2 deployment packages will have 802. 1 q headers. The same problem will be seen on devices running inline vlan pair configurations.

  The key word "vlan" must be added to the expression, so he knows he has to analyze the 802. 1 q header before seeking the rest of the expression.

  If you want to try something like:

  package display gigabitethernet0/7 expression vlan ip proto \icmp

  NOTE: Several VLANs can also be added after the key word of VLANs to restrict the output of tcpdump for traffic to a single VLAN.

• What is a ring of ring/tx rx in router?

  Hi all

  picture below describes a process routes of routers/switches package.

  

  first router receives a packet

  interface processor stores private packet buffer or public buffer memory.

  above market.

  What is a role of RX ring?

  ring is a common memory (buffer) or a memory (buffer) dedicated to interface?

  is there anyone which is a rx ring (ring of tx)?

  Hello

  I would add a little more.

  As well as public and private swimming pools interface, Cisco IOS creates special buffer called rings control structures. Cisco IOS and controllers interface using these rings to control what pads are used to receive and transmit packets to the media. The rings themselves are made up of media-controller-specific elements that point to the individual package also buffers in memory of I/O.

  Each interface has a pair of rings - a ring of reception for receipt of packages and a ring of transmission for the transmission of packets. The size of the rings varies with the interface controller. In general, the size of the ring of the show is based on the bandwidth of the interface or the VC and is a power of two (Cisco Bug ID CSCdk17210).

  Kind regards

  Kevin

• understanding version fixed in IOS (e.g. CSCtn74228)

  Hi all! Please explain what it means (for example the bug No. CSCtn74228)

  1 found-In
  M4 15.0 (1)

  Fixed in
  M5.4 15.0 (1)

  I do not understand fixed version. Do does it say that this bug is fixed in 15.0 (1) M5? How can that be if 15.0 (1) M5 was released before the bug was discovered?

  Thanks in advance.

  First found in tells that release the bug was discovered in.  It may or may not exist in older versions.

  Fixed in indicates the version number of internal Cisco where the patch was applied.  All future versions of the ORC will transport the fix.  In this case, 15.0 (1) M5.4, 15.0 (1) M6 and later will be the fix.

  The 'Known the affected Versions' link is useful to check if the bug is known to affect a specific version.

  15.0 (1 M) is the basic version.  Reconstruction numbers after that

  Thus, the sequence would be 15.0 (1) M1, M2 15.0 (1): 15.0 (1) M3, etc..

  Between you would see internal, not released "rebuilt" as 15.0 (1) M1.3, M2.5 15.0 (1), M3.2 15.0 (1).  They appear in bug toolkit which is just a reflection of the internal Cisco bug tracking system.  The next "integer" is released (public) software which has the fix.

  Make sense?

• Radio0-802. 11A address MAc indicated but not enable ROOT - AP

  Hello

  I have a ROOT access point and 2 NO ROOT APs does not work well, sometimes NO roots lost connection with ROOT. I need to change everything for the new.

  After the associated parameter config in each of them, NO ROOT with the ROOT AP, so far everything looks very good.

  When I type sh dot11 association on ROOT, the other is shown.

  ROOT >
  ROOT > sh dot11 associations

  802.11 client Stations on Dot11Radio0:

  SSID [link]:

  MAC address IP Device Name Parent State
  003A.9922.1f20 0.0.0.0 Br-client - Assoc 003a.9924.2ba0---> 802.11 has
  Bridge of 003a.9924.2ba0 192.168.1.249 NON-ROOT2 self Assoc
  Bridge of 003a.9933.e070 192.168.1.251 NON-ROOT1 self Assoc
  003A.9935.1BA0 0.0.0.0 Br-client - Assoc 003a.9933.e070---> 802. 11A

  ROOT >

  with the old ROOT AP only showed info related to NON-ROOT2 and NON-ROOT1 Radio0 802 mac address. 11 g; I do not understand why is indicated as much info on the other interface, in College, they are disabled.

  is there something wrong with the PA? is a bug?

  This reach the operation?

  on NON-ROOT is the info shown

  NON-ROOT1 >sh dot11 ASSociations

  802.11 client Stations on Dot11Radio0:

  SSID [link]:

  MAC address IP Device Name Parent State
  003A.9933.eb30 192.168.1.250 ROOT 11 g-bridge - Assoc

  NON-ROOT2 >sh dot11 associations

  802.11 client Stations on Dot11Radio0:

  SSID [link]:

  MAC address IP Device Name Parent State
  003A.9933.eb30 192.168.1.250 ROOT 11 g-bridge - Assoc

  NON-ROOT2 >

  Concerning

  Hello

  There was an internal bug filed for what you see. The bug will be marked as external, so it can be viewed with the Cisco Bug tool in the following days.

  For bug summary:

  CSCti72291    Root watch non-pont bridge another radio as a client bridge.

  Everything associated with Dual radio AP root and non-root bridge mode bridge
  Watch radio nonroot bridge disabled as br-client root bridge.

  1. set up a dual radio ap as a root bridge and another ap non-root Bridge.
  2 combine the two AP
  3. link to the root bridge table indicates nonroot bridge another mac-address client-br radio.

  Also if the bridge root partner nonroot bridge via interface d0/d1.
  The bridge root configure d0 as root bridge triggers radio reset in vice versa and d1 interface

  This bug has been closed for the time being and there is no solution as this is added as part of the fixed CSCsj68025 bug.
  So in summary all the time that NRB associated root bridge, it updates the root on the two radio stations (point 0 and point 1).
  This happens regardless of the State of radio (upwards or downwards).  It has no side effects because of this behavior.

  Please let us know if none is more on that.

  Kind regards

  Alex

• PuTTY and password change issue ACS server

  When a new user is created with the checkbox 'Must change the password at the next logon' checked, ACS does not allow the user to change the password.  The password prompt displays a message access denied. Could someone point me in the right direction to solve this problem?

  I created a new account on cisco ACS server and check the box "user must change password at the next logon". I then used ssh to test the newly created using PuTTY user account. When I ssh to the cisco devices [switch or router] password prompt appears and ask me to type the new password. Once I did this I get a message access denied.

  It worked well with secure CRT. But users do not have secure CRT, they are supposed to use PuTTY. Users can connect in devices using PuTTY. The problem is that when we try to change the password.

  ACS Version: ACS 4.0

  Thank you

  Nachi

  When a user connects in SSH to the system and uses an expired password GANYMEDE, he is prompted to change their password. However, this password change does not work correctly.

  To resolve this problem, you must have the SSH v2 with "Keyboard interactive" authentication for SSH v2 game. Cisco bug ID CSCin91851 addresses this problem.

  Symptom:

  When you use the router as a ssh server is authenticating with a normal SDI/RADIUS, work of authentication backend. However, neither the new BUGS mode or mode next token dialogues completes successfully.

  Conditions:

  Problem only occurs in mode again PIN or next token dialogue mode.
  Specific SSHv2

  Workaround solution:

  Use telnet for authentication or to define vty lines to authenticate against RADIUS
  (non - SDI) server instead.

  Other Description of the problem:

  Not all ssh clients are supported the dialogue for the new PIN mode or next token to work.