cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements

8768
Views
20
Helpful
12
Replies
Beginner

Cisco 6880-X DFC1-1-EXCESSIVE_PARITY_ERROR

Hello

For the last couple of days, I'm getting these errors in a dual chassis 6880 environment (VSS) 

469486: Mar 22 13:57:45.235: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469487: Mar 22 13:57:47.975: %EARL-SW2_DFC1-3-NF_PARITY_ERROR: EARL 0 NF ASIC: Uncorrectable Parity error in Netflow Table.
469488: Mar 22 13:57:52.459: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469489: Mar 22 13:57:52.687: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469490: Mar22 13:57:55.975: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM

469491: Mar 22 13:58:01.143: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469492: Mar 22 13:58:07.975: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469493: Mar 22 13:58:08.599: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469494: Mar 22 13:58:09.187: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469495: Mar 22 13:58:15.968: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469496: Mar 22 13:58:17.228: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469497: Mar 22 13:58:24.452: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469498: Mar 22 13:58:24.688: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469499: Mar 22 13:58:27.968: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469500: Mar 22 13:58:33.136: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469501: Mar 22 13:58:39.968: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469502: Mar 22 13:58:40.592: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469503: Mar 22 13:58:41.180: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
469504: Mar 22 13:58:47.972: %EARL-SW2_DFC1-3-NF_PARITY_ERROR: EARL 0 NF ASIC: Uncorrectable Parity error in Netflow Table.
469505: Mar 22 13:58:48.016: %EARL-SW2_DFC1-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM

I've seen that there is a bug in some versions (CSCus64795) but it shows as corrected in the version that I'm running - I'm running 15.2(1)SY1 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCus64795/?referring_site=bugquickviewredir

I'm considering to plan a reload to the chassis, but i'd like to know what's the problem origin...

Has anyone had this issue?

Thank you very much

1 ACCEPTED SOLUTION

Accepted Solutions
Participant

There has been no bug to fix

There has been no bug to fix the parity error. parity error means, you will have to reload the respective component. here, its Sw2-DFC1.. so, switch-2 module-1.

The excessive logging of this message used to create memory leak and that what being fixed via this bug.

as you have the bug fix integrated, your system did not crash!!

View solution in original post

12 REPLIES 12
Beginner

Hi Tiago,

Hi Tiago,

I'm facing exactly the same within the same environment but we're running IOS 15.1.2.SY4.

I opened a TAC-case

Greetings

Roman

VIP Mentor

Its a known bug

Its a known bug

Excessive logging/Memory leak due to a parity error in the Netflow VRAM.
CSCus64795

Description
Symptom:
A Catalyst 6500 or 6800 may generate a lot of syslog messages and leak memory due to a parity error in the NetFlow table. A sample of these messages are:
%EARL-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
and
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

Conditions:
These messages are printed as a result of a parity error. This bug is not to address the parity error which has occurred in the system. Instead this bug was raised to overcome two issues:
1) The excessive debug logs that are produced by the system. From lab testing after a parity error the system will generate over 200,000 debug messages in a day.
2) The repeated misleading EXCESSIVE_PARITY_ERROR messages that get generated. From previous cases a single one time error will get flagged repeated by the system causing this misleading messages.
3) A memory leak that occurs as a result of the parity error. Each time the system flags the one bit error an entry into a table is created without bound. A single error will cause of a leak of roughly 30MB per day in the process named NF ISR Intr Task.

To stop the messages and leak schedule a window to reload the supervisor or linecard where the parity error was seen.

Workaround:
There is no workaround. The corrective action to clear the parity error is to perform a reload on the affected component in a maintenance window.

Further Problem Description:
Refer to CSCut56929 which addresses parity error in the VRAM.
Beginner

Hi Marc,

Hi Marc,

I know this bug but according to the TAC engineer it should be resolved in our running release

VIP Mentor

Ahye didn't see they had a

Ahye didn't see they had a bug id in first post , don't like to say it but if your still getting those errors the bug must have carried over to your version as well unfortunately

Beginner

Hi Mark,

Hi Mark,

that's exactly the case; I just received an answer from TAC saying the same; the bug was not fixed and therefore carried over to the release we're running.

I'm adviced to upgrade to 15.1.2-SY7

Best regards

Roman

Participant

There has been no bug to fix

There has been no bug to fix the parity error. parity error means, you will have to reload the respective component. here, its Sw2-DFC1.. so, switch-2 module-1.

The excessive logging of this message used to create memory leak and that what being fixed via this bug.

as you have the bug fix integrated, your system did not crash!!

View solution in original post

Beginner

I'm fully aware of the bug

I'm fully aware of the bug and parity errors. According to TAC the bug has not been fixed in our running release.

We re-seated the linecard in question and it's ok now.

Beginner

Re: I'm fully aware of the bug

Hi rhub,

 

Did you need to reload the chassis when re-seated the Line card ?

 

Thanks,

Nohfendi

Beginner

I received the error messages

I received the error messages using version 15.1.2-SY7 on a 6509E chassis.

Re: Hi Mark,

Seems to me that it never got fixed as i'm seeing it right now on a 6880 running 15.1(2)SY11...

 

Reloading the affected module fixed it actually but still it's annoying,

 

Regards,

 

Stefan

Highlighted
Beginner

I am also seeing this on a

I am also seeing this on a 6807-XL in VSS mode running IOS version 15.1(2)SY4a:

Mar 15 11:49:40: %EARL-SW2_STBY-1-EXCESSIVE_PARITY_ERROR: EARL 0: Parity error detected in VRAM
Mar 15 11:49:40: SW2_STBY: Warning: Uncorrectable Parity error is seen in the Netflow Table.

Beginner

Re: Cisco 6880-X DFC1-1-EXCESSIVE_PARITY_ERROR

I can see that there is a bug CSCus64795 in the answers around the site, but the bug description has been removed from cisco.com, why is that?

At least there should be other bug references to the problem.

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards