Pchip Egress Error & Fail-on-error Feature

[gargoyle]

Hi All,

i had several cases with pchip Egress Error in IMM Module, the symptoms from this errors are:
- an/some NE(s) which 2 hops from impacted node geeting unmanaged
- if there is network interface under the error card, some sdp from other NE which transit/traverse this interface will be in oper state down.

This error give a huge impact in the network.
i read about fail-on-error feature, but somehow this feature doesnt included Pchip Egress Error (only Pchip ingress error and ethernet modules).
i need a feature for automatically shutdown a modules (card, mda or port) when there is Pchip Egress error detected,
can anyone give me suggestion what feature for that or other recommendation for this problem?

thanks anyway,

[mivens]

Is it egress XPL errors you're concerned about?

The troubleshooting guide for that suggests "config>port>ethernet>down-on-internal-error" will help.

[gargoyle]

Hi Mivens,

thank you for the answer,
whether egress XPL errors and Egress PChip FCS Error are similar?

I've checked about down-on-internal-error in router config guide, i will test it in the lab, hope it will works and minimize the impact from PChip FCS egress Error.

[mivens]

They are not the same thing.

The problem with egress PChip FCS errors is that the source of the problem is often not the card reporting the errors. So it is not a good idea to automatically shutdown the card reporting the problem. XPL errors are between the IOM and the MDA so they are isolated to one linecard.

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.