4900M - %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR:

[david.hunt.2]

Hi All

We have recently upgraded  a number of these model switches to cat4500e-ipbasek9-mz.122-54.SG1.bin ... about 12 weeks ago. Of the 6 that we upgraded, one has had the following triggered on it.

Nov  1 13:54:54.049 ACDT: %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR: VFE IC iccErr interrupt. valid: 1 errStatus: 0x2000000 replyBusParity: 0xBD replyBusLog.rep: 0x8000000 0x180000C7400 log.rep: 0xF8082600000000 0x0 0x0 0x101035A extLog.rep: 0xFF00000000 0x0 0x0 0x0 tcamIfRxErrStatus.rep: 0x2000000 IC CAM stsReg.rep: 0x0 0

Nov  1 14:04:56.113 ACDT: %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR: VFE IC iccErr interrupt. valid: 1 errStatus: 0x2000000 replyBusParity: 0xBD replyBusLog.rep: 0x8000000 0x180000C7400 log.rep: 0xF8082600000000 0x0 0x0 0x101035A extLog.rep: 0xFF00000000 0x0 0x0 0x0 tcamIfRxErrStatus.rep: 0x2000000 IC CAM stsReg.rep: 0x0 0

Nov  1 14:14:58.173 ACDT: %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR: VFE IC iccErr interrupt. valid: 1 errStatus: 0x2000000 replyBusParity: 0xBD replyBusLog.rep: 0x8000000 0x180000C7400 log.rep: 0xF8082600000000 0x0 0x0 0x101035A extLog.rep: 0xFF00000000 0x0 0x0 0x0 tcamIfRxErrStatus.rep: 0x2000000 IC CAM stsReg.rep: 0x0 0

Nov  1 14:25:00.237 ACDT: %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR: VFE IC iccErr interrupt. valid: 1 errStatus: 0x2000000 replyBusParity: 0xBD replyBusLog.rep: 0x8000000 0x180000C7400 log.rep: 0xF8082600000000 0x0 0x0 0x101035A extLog.rep: 0xFF00000000 0x0 0x0 0x0 tcamIfRxErrStatus.rep: 0x2000000 IC CAM stsReg.rep: 0x0 0

Nov  1 14:35:02.305 ACDT: %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR: VFE IC iccErr interrupt. valid: 1 errStatus: 0x2000000 replyBusParity: 0xBD replyBusLog.rep: 0x8000000 0x180000C7400 log.rep: 0xF8082600000000 0x0 0x0 0x101035A extLog.rep: 0xFF00000000 0x0 0x0 0x0 tcamIfRxErrStatus.rep: 0x2000000 IC CAM stsReg.rep: 0x0 0

Nov  1 14:45:04.373 ACDT: %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR: VFE IC iccErr interrupt. valid: 1 errStatus: 0x2000000 replyBusParity: 0xBD replyBusLog.rep: 0x8000000 0x180000C7400 log.rep: 0xF8082600000000 0x0 0x0 0x101035A extLog.rep: 0xFF00000000 0x0 0x0 0x0 tcamIfRxErrStatus.rep: 0x2000000 IC CAM stsReg.rep: 0x0 0

Nov  1 14:55:06.417 ACDT: %C4K_SWITCHINGENGINEMAN-4-VFEICINTERRUPTICCERR: VFE IC iccErr interrupt. valid: 1 errStatus: 0x2000000 replyBusParity: 0xBD replyBusLog.rep: 0x8000000 0x180000C7400 log.rep: 0xF8082600000000 0x0 0x0 0x101035A extLog.rep: 0xFF00000000 0x0 0x0 0x0 tcamIfRxErrStatus.rep: 0x2000000 IC CAM stsReg.rep: 0x0 0

What concerns me is that there was nothing in the logs preceeding this alarm .. documentation reflects that it's an informative message and no action is required ... but why would it keep repeating on a 10 minute cycle since it was first triggered?  Sniffs of a bug to me.

I don't see this issue on any of the other switches that we upgraded.  All of the switches run in the same operational role.

Ta

Dave

[nkarpysh]

Hi David,

What you have seen are the correctable parity errors.

To learn more about Parity Errors please check the following CCO documentations:

https://www.cisco.com/en/US/products/hw/routers/ps341/products_tech_note09186a0080094793.shtml

http://www.cisco.com/en/US/products/hw/routers/ps167/products_tech_note09186a0080094340.shtml

In general that is usually transient if seen once - or HW problem in case of mulitple occurrencies. So if that is still scrolling - please consider the replacement of Supervisor (RMA).

Hope this helps,

Nik

[david.hunt.2]

Hi Nik,

What concerns me is that it triggered at one point and consistnetly puts this error in the log every 10 minutes since it was triggered, which sniffs of a bug to me.  If we are hitting a correctable error, why do they not appear randomly instead of every 10 minutes??

Dave

[nkarpysh]

Hi David,

I agree this message scrolling is confusing and possibly should be addressed in SW. But I did not find any opene DDTS for a same in 12.2(54)SG1. However the root cause for it is HW parity error. I guess reload should stop this error - on reoccurrence replace it.

Nik

[david.hunt.2]

Does the switching team believe this is a hardware issue, or a new bug ... TAC case??

Ta

David

[nkarpysh]

I'm from LANSW team and Root Cause - indeed HW.

In regards to scrolling message It can be both - DE actually need to look into the code. SO if that parity error stays there as not correctable and switch is doing regular routine and finds that again and again - thus the continious logs. I guess nothing can be changed in the way it handles that.

But can be be just some process reporting of that parity stuck - than that would be abug - however did not find any so far.

Nik