Preview Tool

Cisco Bug: CSCun71685 - False NP parity errors reported on ASR9000 Ethernet Line Cards

Last Modified

Jul 20, 2018

Products (1)

  • Cisco ASR 9000 Series Aggregation Services Routers

Known Affected Releases

4.1.0.BASE 4.2.0.BASE 4.3.0.BASE 5.1.0.BASE

Description (partial)

When checking the PRM error logs via the show prm server trace error CLI command, false indications of parity errors may be observed. Here is an example:

Mar 11 10:21:53.749 prm_server/error 0/1/CPU0 t3  prm_process_parity_common : Transient parity Error corrected on NP1, cause=47, memId=0, errorMask=0
Mar 11 10:21:55.091 prm_server/error 0/1/CPU0 t3  prm_process_parity_common 0: Parity Err: NP1-MemId(0) errorMask 0x0, Recov 0 Rewrite 0 parityMask 0x0 SramLine 0 bErrorDetected 0

show controllers np interrupts reports a PARSE_CLUSTER_PARITY error. Here is an example:

 2                               PARSE_CLUSTER_PARITY   47      24      4

This issue can occur on any Trident linecard.   No particular configuration or network conditions are necessary.
Bug details contain sensitive information and therefore require a 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.