You have reached the Help and FAQ page for Cisco Bug Search Tool (BST). For more assistance with Cisco.com, refer to global help. In order to visit the Japanese translation of the FAQ, refer to our Japanese version of the Help page.
The Cisco bug tracking system maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. Bug Search is a web-based tool that acts as a gateway to the bug tracking system and provides you with detailed defect information about your products and software.
Each bug has a unique identifier (ID). Cisco bug IDs use a pattern of CSCxxNNNNN, where x is any letter (a-z) and N is any number (0-9). These bug IDs are referenced in Software Release Notes, Security Advisories, Field Notices and other Cisco support documents. Technical Assistance Center (TAC) engineers or other Cisco staff can also provide you with bug IDs.
Bug Search can assist you with:
Anyone who has a valid Cisco.com account can access Bug Search online, but only customers and partners can utilize its advanced features. As a guest, you can search for specific bugs, access and rate them (future release). Guest users are limited to query a maximum of two hundred bugs per month. If you log in with a customer or partner service level ID, additional functionality, such as Keyword Search, Product (Model or Series) and Product (PID) based searching is available.
Note: If you do not have a profile on Cisco.com, you can obtain a login and create a user profile at the Cisco.com Registration page. After you register a Cisco.com account, you must associate a Service Contract to your Cisco.com login profile.
The feedback link is located in the upper right-hand corner of Bug Search. This form allows you to report general feedback or problems with Bug Search. Every feedback submission is reviewed by the Bug Search Support Team. We can only contact you if your information is provided in the form. If you provide your contact information, this gives us permission to contact you about the feedback submission.
There are two main search options available in Bug Search:
You have one or more Cisco bug IDs and want to obtain details on those bugs.
Complete these steps:
You experience a specific problem or issue and want to look for known bugs and fixes related to it.
Complete these steps:
In order to increase your search relevancy, Bug Search supports these Search Syntax options.
|Implicit synonym support||Crash||Matches any bug with crash, crashed, or crashing|
|Support for multiple strings||"Ethernet interface" or Ethernet Interface||Matches anything that has the exact phrase Ethernet interface|
You have a product that runs specific software and want to research the bugs related to that device.
Choose Product Name, Product Series or Product ID from the Product Family drop-down list.
Choose a Software Type and Release (as shown below) in order to further refine your search.
Note: Bugs at Cisco are not always tracked at the Cisco product model level. In these instances, all bugs at the series level impact all the models in the series. By selecting a model, Bug Search will find the correct bugs for you.
In order to search for bugs related to a specific software release, complete these steps:
Note: By default, your search results include bugs with all severity levels and statuses, and bugs that were modified any time in the bug life cycle. After you perform a search, you can filter your search results to display those with a particular Status, Severity, etc. This behavior is different than Bug Toolkit.
After you perform a search, the search results are listed below your search criteria. A preview of the bug information is shown and you can mouse over bugs to see more content about a specific bug.
You can click on any one bug title to open the Bug Details page for that bug. Before you choose the bug or bugs you want to view, there are multiple options available to browse and filter your search results table.
Bug Search offers powerful filtering options. You can filter your search results based on Bug Severity, Bug Status, Bug Rating, Bug Modified Date, and number of support cases.
For example, the below filter selection would load all bugs that contain the keyword "router crash" which are fixed and have a severity of 1.
To remove a particular filter, simply click the appropriate filter and choose the empty box from the drop-down list as shown:
The initial set of 25 search results is shown in the bottom pane. Drag the scroll bar to display the next set of 25 results. Pagination of search results is not supported in this version of Bug Search. This functionality will be available in a future release. Because pagination is not supported, table refresh rates can be slower if the scroll bar is adjusted too quickly.
Before you click a specific bug ID to view the Bug Details Page, you can view key bug details on the Search Results page itself. Roll your mouse over a specific bug to see more information about that bug.
The default sort order for your search results is dependent upon the search method you use. By default, the bugs are displayed in the order most closely related to your search criteria.
In order to change the order your results are sorted, choose a value in the Sort by drop-down list as shown here.
You can export all the bug details from your search to a Microsoft Excel spreadsheet so you can view them later at your convenience. Presently, up to 10000 bugs can be exported at a time to an Excel spreadsheet.
When you click a linked bug ID in your search results list, you are taken to the Bug Details page for that bug. The Bug Details page contains information in detail about the bug.
In order to assist in improving the bug description of individual bugs, Bug Search has a provision for quality ratings. Each bug will be associated with content quality information which will be an average of all rating information provided by customers. Cisco recommends that our customers provide ratings for all the bugs viewed based on bug description (for example. symptom, condition, and workaround). Bug Quality ratings are tracked at five different levels:
Content quality information is available in the search results table and also in the Bug Details page below the RNE of the bug. On the bug details page, along with overall average quality information, the number of users who submitted the feedback is made available next to the rating within parenthesis. For example, in the case below, two users have rated the bug based on bug description details. You can select the star rating and provide any optional comments before you submit ratings information.
The details section contains information related to the bug status, severity, product, fixed/affected releases of the bug, option to download software for the fixed release and the number of support cases associated with the bug.
You can also view the existing community discussions on that bug or have an option to initiate a new discussion.
Bug Severity is usually defined from the development managers' point of view and gives the product teams ways to focus on bug fixes for their next releases. Severity is also impacted by customer priority and other details not displayed within Bug Search. This table defines bug severity levels.
|Bug Severity Level||Description|
Reasonably common circumstances cause the entire system to fail, or a major subsystem to stop working, or other devices on the network to be disrupted. There is no workaround.Example: Router crashes when you enter the isdn bind-l3
iua-backhaul dpnss command.
Important functions are unusable, and there is no workaround, but the other functions and the rest of the network operates normally.Example: IP helper addresses are ignored.
Things fail under unusual circumstances, or minor features do not work at all, or things fail but there is a low-impact workaround. This is the highest level for documentation bugs.Example: LAT does not work unless you have an IP address on the interface.
Things fail under very unusual circumstances, but operation essentially recovers without intervention. Users do not need to install any workarounds, and performance impact is tolerable.Example: The first segment for each TCP connection is always
The defect causes no real detrimental effect on system functionality.Example: The word "connection" is incorrectly spelled "conection" in a display.
|6||Enhancement||This represents a request for new functionality or for an improvement to a feature that is currently offered.|
Important Note: Status can change frequently throughout the lifecycle of a bug. For example, if the status is Fixed, the bug is most likely fixed in a new release of the software, as represented in the Known fixed Releases.
|Open||The bug has not been fixed.|
|Fixed||The bug has been fixed.|
|Other||The bug is a duplicate of another bug.|
|Terminated||A decision was made not to fix the bug.|
This field displays the last time the bug details were changed.
This represents the Cisco Product name or Software in which the bug occurs.
This field displays the software releases known to be impacted by this bug.
This field displays the software releases known to contain a fix for this bug.
Saved Searches are an aspect of personalization in Cisco Bug Search that enables you to save individual bugs or search criteria that is important and required to monitor future needs. You also have the capability to set up e-mail notifications for them if required. Users who have Cisco.com Customer or Partner privileges will be able to use this functionality. All saved criteria are organized into groups and notifications that can be set for each group. There will be a default group created if the user does not give a name when creating for the first time then the service will keep on adding to this group if the group name is not specified. The default group name will be the Cisco login User ID. A group will remain active for a year beginning from the last updated date. The Notification frequency currently supported:
All previously stored individual bugs or search criteria present in Bug Toolkit will be ported into Cisco Bug Search. Listed here are the steps being taken for the smooth transition of your information:
A single bug can be saved in two ways - from the “Save bug” option in bug details page or from bug flyout on search results page. Mentioned below is the procedure to save a bug from bug details page:
Complete these steps in order to save searches:
Choose the specific bug/search you want to load from the Load Saved Search drop-down list on the home page. You can also clear/email a specific search by using the appropriate buttons beside the Load Saved Search drop-down list.
Choose Edit saved searches from the Load Saved Search drop-down list to access your watch list.