Placing customers first, Cisco led the management of an industry-wide issue with certain memory components manufactured between 2005 and 2010 that could affect specific products. (February 2014)
Cisco has been working with individual customers on an issue related to memory components manufactured by a single supplier between 2005 and 2010. These components are widely used across the industry, and have been included in some Cisco products.
Although the majority of Cisco products using these components are experiencing field failure rates below expected levels, the components are known to slowly degrade over time. A handful of our customers have recently experienced a higher number of failures, leading us to change our approach to managing this issue.
Cisco has decided to take a charge of $655 million related to the expected cost of managing these issues, including supporting our fix-on-fail and technology migration programs. We are taking this action to support our customers and partners.
Q: What is the issue?
A: Cisco has been working with individual customers on an issue related to memory components manufactured by a single supplier between 2005 and 2010. These components are widely used across the industry. The majority of affected Cisco products are experiencing field failure rates below expected levels:
Q: How are these components used?
A: These components are commonly used as the main memory of the processor for the operating system. They include memory modules and discrete on-board memory (individual components soldered on a line card or similar printed circuit board assembly).
Q: What causes the issue?
A: Typically, the memory components are more than 2-3 years old and suffer a functional failure when subjected to a power cycle event (turned off and on). The memory failure is attributed to a degradation mechanism in a specific memory circuit design.
Q: Is this a hard failure that causes a device to fail or a transient failure that could temporarily disrupt normal operations?
A: We know that the components slowly degrade over time, but they require a power cycle to exhibit a hard failure. What we've seen is that within the population of components affected by this problem, some components may fail earlier than anticipated, while others will not exhibit failure within the component’s expected lifetime.
Component Supplier
Q: Who supplies the impacted memory components?
A: As a matter of policy, Cisco stands behind the reputation of our products. We do not intend to publicly name the supplier.
Q: What makes you say this is an industry-wide issue?
A: This issue relates to memory components manufactured by a single supplier between 2005 and 2010. The components are used across the industry and not just in Cisco devices.
Q: How are others in the industry handling this issue?
A: While different systems vendors have chosen to address this issue in different ways, Cisco believes its approach is the best course of action for its customers. Despite the cost, we are demonstrating that we always make customer satisfaction a top priority.
Cisco Response
Q: Does this issue impact all memory components used in Cisco products?
A: No, this issue is confined to memory components from specific lots from a specific supplier.
Q: What will happen to the inventory supply of these components? Will they be used in other products?
A: Product using these components has not been shipped new since ~2012. The Service Depots have been purged of Focus List products, with exception of the SPA cards. Service Depot removal of exposed Non-Focus products is in progress and may take 12-18 months to complete.
Q: How long has Cisco been selling products with this component?
A: Cisco products with the suspected memory components began shipping in 2005, and this continued until the final component was identified and removed from our inventory in 2012.
Q: How should a customer determine if this memory issue impacts products in their network?
A: We are providing information on affected product families at www.cisco.com/go/memory, including a list of Focus Products and links to product-specific Field Notices (click on the tabs above for more information).
Q: What failure rates is Cisco seeing?
A: We continue to closely monitor the data for Cisco products that have experienced field failures or customer escalations. The majority of our products using these components are experiencing field failure rates below expected levels. However a handful of our customers have recently experienced a higher number of failures in their networks, which is why we are changing our approach in managing this issue.
Q: Are these failure rates getting worse?
A: The current data does not show a significant increase in failure rates, but we do know that the components are known to slowly degrade over time.
Timeline
Q: How and when did Cisco find out about this issue?
A: Cisco first became aware of this issue in December 2010.
Q: What did Cisco do as a result?
A: When Cisco first became aware of this issue in December 2010, we:
Only in late 2012 did field failures and supplier review data point to a potential customer impact. Based on the information available at the time, Cisco created and managed an active inventory management of replacement line cards, and implements a "fix-on-fail" escalation process to support customers.
Advice to Customers
Q: How do I determine if this memory issue impacts products in my network?
A: As always, customers should contact the Cisco Technical Assistance Center (TAC) if they experience a failure in a Cisco product. Cisco has established a process to help analyze a customer's installed base for exposure. We recommend reviewing the Focus Product list and Field Notices that are available through the above tabs.
Q: Do normal SmartNet and warranty entitlement rules apply?
A: Yes. Normal SmartNet and warranty entitlement rules remain in place and will be applied by the Cisco TAC if you experience a failure in one of the products listed in the Field Notices. In other circumstances (eg. out of warranty or out or contract), we'd encourage you to raise your concern directly with your Cisco account team.
Q: What are Focus Products?
A: Cisco has divided the relevant PIDs (orderable Product IDs) into two categories – Focus Products and All Other Products. The categories are based on the use of affected memory components (circuitry, number of components), observed field failure rates (including customer experience), and product replacements since 2012. Focus Products require careful management, while All Other Products have lower than expected failure rates.
Q: What action does Cisco recommend for Focus Products?
A: Cisco recommends careful management of these devices, including:
Cisco's recommendation is fix-on-fail for both product categories to minimize network disruption.
Q: What action does Cisco recommend for All Other Products?
A: These products have lower than expected failure rates. Cisco's recommendation is fix-on-fail for both product categories to minimize network disruption
Q: Does this issue cause any security-related concerns?
A: No. Although there are no known security implications associated with this issue, Cisco does recommends customers review the latest Security Advisories at www.cisco.com/go/psirt before making upgrade decisions.
Q: Will you be replacing products, repairing products, or offering discounted upgrades?
A: Any currently available and covered products that experience an issue will be addressed through fix-on-fail, using normal support processes, or technology migration programs. End of Sale products will only be managed through a fix-on-fail, return-to-factory, or technology migration program. End of Support products will be managed through a technology migration program only.
The Issue
Cisco has been working with individual customers on an issue related to memory components manufactured by a single supplier between 2005 and 2010. These components are widely used across the industry, and have been included in some Cisco products. The majority of affected Cisco products are experiencing field failure rates below expected levels:
Cisco's Response
Product-by-Product Assessment
Cisco has assessed 105 impacted product families that use the impacted memory component. 95 of these product families have demonstrated lower than expected failure rates.
Cisco has divided the relevant PIDs (orderable Product IDs) into two categories:
The categories are based on:
Cisco recommends careful management of the Focus Products, including:
Click here to see a list of the 124 PIDs in the Focus Products category. Cisco's recommendation is fix-on-fail for both product categories to minimize network disruption.
Although Field Notices are normally issued for products with greater than expected failure rates, Cisco is providing updates for every product family that includes an impacted memory component. To minimize network disruption, Cisco recommends fix-on-fail for all related products.
Although there are no known security implications associated with this issue, Cisco also recommends customers review the latest Security Advisories at www.cisco.com/go/psirt before making upgrade decisions.
Collaboration Endpoints
Title | Field Notice | |
---|---|---|
FN#63772 – IP Phones – May Fail To Boot-Up After A Power Cycle – Fix-on-Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63772.html | |
FN#63768: CTS TelePresence Systems might fail to boot-up after a power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63768.html |
Interfaces and Modules
Title | Field Notice | |
---|---|---|
FN#63782 ACE10, ACE20, and ACE30 module may fail to boot-up after a software upgrade or power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63782.html | |
FN#63522 - Catalyst 6500/Cisco 7600 Series Router – Firewall Service Module (FWSM) – Some Service Modules may fail to boot-up after a software upgrade or power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/635/fn63522.html | |
FN#63755 - Catalyst 6500/Cisco 7600 Series Router – Anomaly Detector Module and Anomaly Guard Module – Some modules may fail to boot-up after a software upgrade or power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63755.html |
|
FN#63779: Service Application Module for IP may fail to boot-up after a software upgrade or power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63779.html | |
FN#63762: EHWIC-3G-XXX, EMV-IPVS-16A, HWIC-3G-XXX, NME-XXX & SM-XXX may fail to boot-up after a power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63762.html | |
FN#63773 – SPA Modules Might Fail to Boot After a Software Upgrade or Power Cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63773.html |
Optical Networking
Title | Field Notice | |
---|---|---|
FN#63771 – ONS 15310 and ONS 15454 – Products Affected Might Fail to Boot After Power Cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63771.html |
Routing
Title | Field Notice | |
---|---|---|
FN#63764 – Some ASR1000 products may fail to boot-up after a power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63764.html | |
FN#63765 – Some 7200/7300 Products Might Fail to Boot Up After a Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63765.html | |
FN#63493 – CRS – Products Affected Might Fail to Boot Up After a Software Upgrade or Power Cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/634/fn63493.html |
|
FN#63553 – C7600 may fail to boot-up after a software upgrade or power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/635/fn63553.html | |
FN#63405: CISCO18XX & CISCO28XX may fail to boot-up after a power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/634/fn63405.html | |
FN#63760: CISCO3825 & CISCO3845 may fail to boot-up after a power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63760.html | |
FN#63761 - CISCO8XX & IAD8XX May Fail to Boot-up after a Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63761.html | |
FN#63781 - ESR10K - Products Affected Might Fail to Boot Up After a Software Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63781.html |
Security
Title | Field Notice | |
---|---|---|
FN#63740 – IPS-4240 and IPS-4255 Sensor Appliances – Some appliances may fail to boot-up after a software upgrade or power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63740.html | |
FN#63742 – ASA 5505 Series Appliances – Some appliances may fail to boot-up after a power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63742.html | |
FN#63741 – ASA 5500 Series Appliances – Some Appliances May Fail to Boot-up after a Power Cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63741.html |
Storage Networking
Title | Field Notice | |
---|---|---|
FN#63752: MDS 9000 may fail to boot-up after a software upgrade or power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63752.html |
Switching
Title | Field Notice | |
---|---|---|
FN#63748 – Catalyst Express 500 may fail to boot-up after a power cycle – Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63748.html | |
FN#63743 - Catalyst 6500 - Might Fail to Boot Up After a Software Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63743.html | |
FN#X63751 - Nexus 7000 may fail to boot-up after a software upgrade or power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63751.html |
|
FN#63746 - Catalyst C4500 and Catalyst 49xx may fail to boot-up after a software upgrade or power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63746.html | |
FN#63745 - Cat3K may fail to boot-up after a power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63745.html | |
FN#63744 - Cat2K may fail to boot-up after a power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63744.html | |
FN#63756: ME3400/E Switches may fail to boot-up after a software upgrade or power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63756.html | |
FN#63774: MGX Switches may fail to boot-up after a software upgrade or power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63774.html | |
FN#63747 - IE3000 - Products Affected Might Fail to Boot Up After a Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63747.html |
Unified Communications
Title | Field Notice | |
---|---|---|
FN#63769: AS5400XM & AS5350XM may fail to boot-up after a power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63769.html | |
FN#63777 - UC520/UC540 Might Fail to Boot After a Software Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63777.html |
Video
Title | Field Notice | |
---|---|---|
FN#63750 - UBR10K Cards Might Fail to Boot After Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63750.html | |
FN#63753 - RFGW10 Cards Might Fail to Boot After Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63753.html | |
FN#63754 - UBR7200 Cards May Fail to Boot after Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63754.html |
|
FN#64010 - RFGW-1 Might Fail to Boot Up After a Software Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/640/fn64010.html | |
FN#64034 - DCM Might Fail to Boot After Software Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/640/fn64034.html | |
FN#64035 - ROSA EM Might Fail to Boot After a Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/640/fn64035.html | |
FN#64059 - D9054, D9858, D9865, D9887, and D9887B Might Fail to Boot After a Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/640/fn64059.html | |
FN#64060 - Phoenix HMTS and Phoenix AC Receivers Might Fail to Boot After a Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/640/fn64060.html | |
FN#64066 - Cisco AnyRes Live Might Fail to Boot After a Software Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/640/fn64066.html |
Wireless
Title | Field Notice | |
---|---|---|
FN#63758 - ASR5000 and ARS5500 products may fail to boot-up after a software upgrade or power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63758.html | |
FN#63763 - AP1250, AP1140, AP1520, AP1130 may fail to boot-up after a software upgrade or power cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63763.html | |
FN#63770 - WLC21XX, WLC44XX, WiSM Might Fail to Boot Up After a Software Upgrade or Power Cycle - Fix on Failure | //www.cisco.com/c/en/us/support/docs/field-notices/637/fn63770.html |