Guest

Preview Tool

Cisco Bug: CSCte98535 - MSC Resets after some logging some diag errors

Last Modified

Jan 09, 2017

Products (1)

  • Cisco Carrier Routing System

Known Affected Releases

3.9.0.BASE

Description (partial)

Symptom:

A line card reloaded as a result of an error condition detected within the Metro ASIC, which resulted in the collection of ASIC SCAN information.

The following messages were observed immediately preceding the card reload:

RP/0/RP0/CPU0::Feb 11 05:08:57.976 : online_diag_rp[340]: %DIAG-XR_DIAG-3-ERROR : (U) Fabric Ping Failure, 1 of 10 nodes failed: node0_3_CPU0 
RP/0/RP0/CPU0::Feb 11 05:11:02.146 : online_diag_rp[340]: %DIAG-XR_DIAG-3-ERROR : (U) Fabric Ping Failure, 1 of 10 nodes failed: node0_3_CPU0 
RP/0/RP0/CPU0::Feb 11 05:13:07.048 : online_diag_rp[340]: %DIAG-XR_DIAG-3-ERROR : (U) Fabric Ping Failure, 1 of 10 nodes failed: node0_3_CPU0 
RP/0/RP0/CPU0::Feb 11 05:15:10.624 : online_diag_rp[340]: %DIAG-XR_DIAG-3-ERROR : (U) Fabric Ping Failure, 1 of 10 nodes failed: node0_3_CPU0 
RP/0/RP0/CPU0::Feb 11 05:17:15.012 : online_diag_rp[340]: %DIAG-XR_DIAG-3-ERROR : (U) Fabric Ping Failure, 1 of 10 nodes failed: node0_3_CPU0 
LC/0/3/CPU0::Feb 11 05:17:53.597 : cpuctrl[305]: %PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_LINK : Cpuctrl PORT LINK error, intID = 2000, port = 8 (PSE), port_link_error = 0x1:     Cpuctrl CRC errors, CRC counter = 3  
LC/0/3/CPU0::Feb 11 05:17:53.599 : egressq[151]: %L2-EGRESSQ_HW_DLL-3-HW_ERROR : Sharq MIF CRC error occurred. 
LC/0/3/CPU0::Feb 11 05:17:53.601 : cpuctrl[305]: %PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PORT : Cpuctrl Port iSN error, IntID = 2001, reg = 0x80000001, port = 8 (PSE), cause = 0x2, last_req = 00020020 80041001         timeout detected  
LC/0/3/CPU0::Feb 11 05:17:53.601 : cpuctrl[305]: %PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_SN : PCI SN error READ operation, IntID 2001, pci_snerr_status = 0x80000046  PIO failure, Addr = 00000000 00020020 port sn 8 (PSE) real 8  


Conditions:

The Metro ASIC experienced a watchdog timeout due to backpressure being applied by the Egressq ASIC.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.