> -----Original Message----- > From: Masood Ahmad Shah [mailto:[EMAIL PROTECTED] > Sent: Monday, August 25, 2008 12:51 PM > To: Eric Van Tol; juniper-nsp@puck.nether.net > Subject: RE: [j-nsp] Strange RX issue w/ GE PIC > > There can be multiple reasons for these input errors. > > Policed Discards > Frames that the incoming packet match code discarded because they were not > recognized or of interest. Usually, this field reports protocols that the > JUNOS software does not handle, such as CDP. > > L3 incompletes > This counter is incremented when the incoming packet fails Layer 3 > (usually > IPv4) sanity checks of the header. For example, a frame with less than 20 > bytes of available IP header would be discarded and this counter would be > incremented. > > L2 mismatch timeouts > Count of malformed or short packets that cause the incoming packet handler > to discard the frame as unreadable. > > HS link CRC errors > Count of errors on the high-speed links between the ASICs responsible for > handling the router interfaces. >
Thanks for the response, but unfortunately, it's not quite what I'm looking for help on. I know what each of the errors are and why they are generated. The puzzling thing is why I wouldn't see them constantly upon any input traffic to one side. I only see the errors occur when both input/output traffic is enabled. -evt _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
