%EARL-DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM Sep 2 07:02:00.952: DFC1: Warning: Uncorrectable Parity error is seen in the Netflow Table. If any error is seen in Netflow flow creation or Netflow Data export, it is advised to reboot the card in a maintenance window
I am taking this thread now and will move to lan/switching soon.
Answer to your question:
Based on the above error seen on the device refers to the parity error.
Parity errors are events where a bit's original value is changed to the opposite one (0 to 1, or vice versa). These can happen in one of two different types, soft parity errors or hard parity errors.
With soft parity errors, the bit's value is changed due to an external influence on the switch, for example the most common reasons are voltage variations, radiation of the environment, etc. While these types of problems are rare, they can happen and are transient that will not reoccur.
A hard parity error on the other hand are caused by an actual hardware failure and reoccur quite often.
It is worth mentioning that parity errors are not bound to Cisco products, these can happen to any piece of electronics.
What happened in this situation was that the module detected an incorrect value in NetFlow's TCAM. At first the module was sending messages advising to manually reload the module to clear the memory, as only "read" functions were being made at this incorrect memory address.
The module ended reloading itself, because a function/feature attempted to perform a "write" function on said memory address, that pointed to an invalid region of memory; And in order to clear the corrupted value, the module had to reload itself. Stack trace decodes confirm this further.
Action Plan: To determine if we are dealing with a soft or hard parity error, we need to monitor the device for another crash. The recommendation is 48 hours, I suggest we do it until Thursday just to be sure.
If the linecard remains stable, it will confirm the soft parity error. If it crashes again, we will proceed with a linecard replacement. If for some reason it crashes again after the monitoring period, we can always reopen the case and proceed with the RMA.
I'd like to share with you a reference link<http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080 c14531.shtml > regarding parity errors, that might be of use to you, as it goes more in depth about these evenets.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...