Cisco publishes Field Notices to notify customers and partners about significant issues in Cisco products that typically require an upgrade, workaround or other user action. Field Notices are posted to the Product Support pages on www.cisco.com. Notifications are sent via email to the users who have opted in via the the Cisco Notification Service, which allows users to customize the notifications they wish to receive.
Note: Field Notices do not contain security vulnerability-related issues. Security vulnerability notifications are addressed by Cisco PSIRT in accordance with the Security Vulnerability Policy. Users can view the latest Cisco security advisories and alerts on our website, and can subscribe to one or more notification options.
|•||What information is shared in Field Notices?|
|•||How does Cisco generate Field Notices?|
|•||What should you do if you experience an issue highlighted in a Field Notice?|
|•||How do Field Notices differ from other Cisco product and product issue notifications?|
Field Notices are officially published in English only and provide information that includes, but is not limited to, products affected, defect identification numbers, problem symptoms, workarounds and solutions. More specifically, the primary components of a Field Notice are:
|•||Title – A structured line that indicates the Field Notice number, a high level description of the issue and the recommended actions.|
|•||Products Affected – List of Affected Product IDs that are impacted by this issue.|
|•||Problem Description – A brief description of the issue.|
|•||DDTS (Bug ID) – Bug ID that can be used to look up the bug via the www.cisco.com Bug Toolkit.|
|•||Background – History of the issue and possible derivations.|
|•||Problem Symptom – A description of what may occur with the system and any behaviors or indicators that you are experiencing the problem.|
|•||Workaround – An expanded next step description to avoid the problem or to correct the situation.|
|•||How to identify hardware levels (optional) – If appropriate, a description of steps to take to identify if your hardware is exposed to the problem.|
A Field Notice can also include several optional fields which help users understand additional information about the problem and how to find the technical information for the affected products.
When Cisco identifies a product issue, we analyze the issue, evaluate corrective actions if necessary, and if urgent action is needed from the users, we develop and publish a Field Notice to communicate the information.
Cisco uses the following process to publish Field Notices:
|1||We classify newly identified product issues based on functional, operational or product impact.|
|2||We assess the potential scope and impact to our customer install base and service inventory.|
|3||We ensure Cisco is ready to deploy and implement the required workaround or solution.|
|4||We use a consistent methodology to draft, approve and publish Field Notice.|
Customers should follow the recommended actions in the “Workaround/Solution” section in the Field Notice. This will offer the best way to recover from an issue they are experiencing or mitigate risk of an issue. Often, the recommended actions may include solution approaches to avoid hardware replacement (RMA) or hardware upgrades. Recommended actions that involve these approaches include, but are not limited to:
Some Field Notice solutions guide customers to perform hardware replacements as the best way to resolve an issue. Recommended actions that involve these approaches include actions such as hardware replacements. Customers can request replacements through an upgrade form available at the end of the Field Notice when it applies.
When considering configuration changes, software and/or firmware upgrades, customers must make their own determinations regarding implementing any recommendations in Field Notices. In all cases, customers should ensure that the devices to be upgraded contain sufficient memory and confirm that current hardware and software configurations will continue to be supported properly by the new release or solution. If the information is not clear, customers are advised to contact the Cisco Technical Assistance Center (TAC) or their contracted maintenance providers.
Cisco uses several methods to deliver product and issue related information to our Customers and Partners, such as Security Advisories, Software Advisories, End of Life Notices, etc. Each form of communication serves a specific purpose, but may overlap from time-to-time. Field Notices are structured so that they can be used as a stand-alone document and/or in conjunction with other customer-facing documents.
|•||End of Life Notices|
View a listing of all current Field Notices by product category, most viewed, and most recent.
Get notified when new Field Notices are published.
Receive notifications via Cisco Notification Service when new Field Notices are released.
Learn how Cisco is addressing an issue related to memory components manufactured by a single supplier between 2005 and 2010.