Pchip Error

[thekotaksampah]

Hello Guys,
I wanna ask you with this problem..

Code: Select all

Complex 0 (parity error): Trap raised 1625 times; Last Trap 09/14/2008 12:04:05

Please tell me.. how come this happen.. and what impact for the network..

Thank you so much

[mivens]

The P chip is the packet processor on the IOM/IMM which does the classification and forwarding.

Reload the IOM/IMM during a maintenance window (use the command “tools perform card <slot> power-cycle") and if the errors are still being reported, get the IOM/IMM replaced.

Whether or not the parity errors are service-affecting depends on where in memory the error is occurring, how often it's happening as well as whether they are correctable or uncorrectable errors.

The SNMP traps/syslogs associated with that error are suppressed by default but can be re-enabled (configure log event-control chassis tmnxEqCardPChipMemoryEvent enable) to help you identify when this issue is happening.

Alcatel support have Pchip Parity Error Troubleshooting Guide they can give you.

[rifster]

Hi Guys,
Do you know how to obtain this Pchip Parity Error Troubleshooting Guide? Is it something they charge you for?
Today I found the following commands but I'm not sure whether they trigger a log event. Maybe you can comment on that.

A:SR12# show log event-control "chassis" | match hip
2059 tmnxEqCardPChipError MI gen 0 0
2063 tmnxEqCardPChipMemoryEvent MI gen 0 0
2076 tmnxEqCardPChipCamEvent CR thr 0 0

A:SR12# configure log event-control "chassis" 2059 generate
A:SR12# configure log event-control "chassis" 2063 generate
A:SR12# configure log event-control "chassis" 2076 generate

mivens
The line you mentioned "configure log event-control chassis tmnxEqCardPChipMemoryEvent enable" is not working for me on SR12 timos 9.

[mivens]

Sorry you're quite right - the last argument should be "generate" not "enable". My mistake. From the "show log event-control" output you've got it right - your system will now generate traps for tmnxEqCardPChipMemoryEvent .

If you open an Alcatel Assistance Request about P Chip errors they will often supply you with the troubleshooting guide without asking for it so you can diagnose the problem yourself without bothering them next time. However, some Alcatel customers choose to have a field engineer with a replacement card on-site before the remote power cycle in case the card doesn't come back (which means you open an Assistance Request anyway).

The short answer from the troubleshooting guide is that as long as you're running TiMOS release 8 or above and using an IOM 3 and the PChip errors are incrementing then the recommendation is to power cycle the card with "tools perform card <slot> power cycle" then replace the card if they continue to increase.

[thekotaksampah]

Dear All,

I found this problem on my router

Code: Select all

FCS Errors Detected
Complex 0 (egress): Trap raised 5 times; Last Trap 04/02/2014 15:59:42
Sources of egress err'd packets (from last trap): Card(s) 2

What is the second line means?

Code: Select all

Sources of egress err'd packets (from last trap): Card(s) 2

Is it mean the suspect Pchip problem from other cards or what? And Why it's happened then how to solve this kind of problem.

I need your hel guys,

Thanks

[mivens]

Egress FCS errors will result in packets being discarded by the system due to a failed CRC. The severity of the service impact will vary depending on the type of packets being corrupted e.g. control or data packets, as well as the rate of discard, etc.

See this DTS #113862 from the SR OS Release Notes:

Egress Pchip FCS errors are reported when corrupt packets enter an egress forwarding complex. They are difficult to debug because the card that detects and reports the corrupt packets may not be the actual source of corruption. Egress FCS error log events and egress FCS error output under “show card” have been enhanced to provide information about the source of the corrupt packets.

The enhanced information aids in the isolation of faults by narrowing down the possible defect to the following cards:
- The card that is reported as source of the corrupted packets. This is usually the case if only one such source is reported by multiple egress complexes.
- Any of the SF/CPM cards. In this case, one or more egress complexes will report egress Pchip FCS errors from multiple sources.
- The card that reported the errors. In this case, one egress complex will report egress Pchip FCS errors from multiple sources.

If there is any doubt, Alcatel-Lucent support should be contacted to determine which, if any, piece of equipment is causing the issue.

Is there only one card reporting these egress FCS errors from card 2? If multiple cards are reporting errors from card 2 then that is most likely the problem.

The timestamp of your last error is a long time ago so maybe you should just continue to monitor.

The command: “configure log event-control chassis 2059 generate” can be used to enable Ingress / Egress Error traps for these events.

[Dearis]

test in diferent ISP (internet provider), or condition net (hot spot, university, ....)



บาคาร่าออนไลน์