Re: [j-nsp] packet checksum error in input fab_stream

Hey, Over fabric you have 1 stream per NPU_ingress to NPU_egress per QoS. Usually just 2 QoS classes, I think maybe in ICHIP just 1 class. At any rate as the stream numbers are so small, these are low priority streams even in Trio. It is telling you that traffic coming to egress ICHIPs in those

Re: [j-nsp] packet checksum error in input fab_stream

> I raised the same point to Joerg in another forum and suggested JTAC, > if I had to venture a guess, perhaps PFE_ID 128 is actually RE > injected packet? > > I though of this, but it shouldn't come through the fabric. JTAC is always an option but, as it is I-chip, it might be not supported.

Re: [j-nsp] packet checksum error in input fab_stream

+1 to Saku. This means your egress PFE, identified by FPC and ICHIP(), receives corrupted cells from the fabric. It might be caused by ingress PFE or fabric chips or even backplane lines. In this case you see it on different fabric streams, so it means that this is not caused by a single faulty

Re: [j-nsp] packet checksum error in input fab_stream

On 1 August 2017 at 14:48, Pavel Lunin wrote: > Some strange thing here is PFE_ID 128. This should be a kind of dummy ID > (MX960 max PFE_ID is 47), I don't know what it means. Maybe some I-CHIP > specificity, e. g., as I remember, they looped packets, switched between > two