Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member



The problem you encountered someone

%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

Cisco Employee

Hi Yang,Please ask this

Hi Yang,

Please ask this question in community "Network Infrastructure"---->LAN, Switching and Routing for quick and correct answers. This is a forum for ACE, CSS, CSM devices etc.



Note: Please mark answers if they are helpful.

Cisco Employee

I am taking this thread now

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
c14531.shtml > regarding parity errors, that might be of use to you, as it goes more in
depth about these evenets.






New Member

hi insharieYesterday, this

hi insharie

Yesterday, this switch in question is restarted , and now it seems everything is normal.

Thank you very much for your help.





Cisco Employee

Glad to know the same.Could

Glad to know the same.

Could you please mark the thread as answered if you dont require any further help on th same.




New Member

Thanks for this Inayath

Thanks for this Inayath really helpfull.

New Member

CreatePlease to create content