This article explains the meaning of the error: SLCHIP(0): 1 new SLin XIF ins eope errors that is reported on the FPC in T Series devices.

The error indicates that the SLCHIP has already started processing the header of a packet but for some reason it has not received the full packet.

This can be triggered by a link flap or by taking a PIC offline.

From the logs it can be seen that the SONET interface went down just before the error was reported:

Mar 12 14:04:48  rpd[3462]: RPD_LDP_NBRDOWN: LDP neighbor 192.0.2.1 (so-12/0/0.0) is down
Mar 12 14:04:48  rpd[3462]: RPD_ISIS_ADJDOWN: IS-IS lost L2 adjacency to AA-R1 on so-12/0/0.0, reason: Interface Down
Mar 12 14:04:48  mib2d[3461]: SNMP_TRAP_LINK_DOWN: ifIndex 169, ifAdminStatus up(1), ifOperStatus down(2), ifName so-12/0/0
Mar 12 14:04:49  lcc1-master eventd: sendto: Network is down
Mar 12 14:04:49  lcc1-master lcc1-fpc4 SLCHIP(0): 1 new SLin XIF ins eope errors
Mar 12 14:04:49  lcc1-master lcc1-fpc4 SLout(0): stream 0 2691193 cells dropped at the cif
Mar 12 14:04:49  lcc1-master lcc1-fpc4 SLout(0): stream 0 438173 first cells dropped at cif
Mar 12 14:04:51  lcc1-master lcc1-fpc4 SLout(0): stream 0 347758 cells dropped at the cif
Mar 12 14:04:51  lcc1-master lcc1-fpc4 SLout(0): stream 0 71556 first cells dropped at cif
Mar 12 14:04:54  /kernel: so-12/0/0 link 0: Asserting SDH alarm(s) LOF
Mar 12 14:05:24  lcc0-master lcc0-fpc0 NFAB(0/1): RODR offset overflow count incremented (1)
Mar 12 14:05:24  lcc0-master lcc0-fpc0 CMALARM: Error (code: 542, type:Minor) encountered, cmalarm_passive_alarm_signal
Mar 12 14:05:28  /kernel: so-12/0/0 link 0: Clearing SDH alarm(s) LOF

This is expected behavior and does not indicate any hardware problem with the FPC. No action is required.

2022-03-06 - IP address changed per RFC 5737