[j-nsp] Strange RX issue w/ GE PIC

[Masood Ahmad Shah]

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.



-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Eric Van Tol
Sent: Monday, August 25, 2008 8:05 PM
To: 'juniper-nsp at puck.nether.net'
Subject: [j-nsp] Strange RX issue w/ GE PIC

Hi all,
I'm experiencing a strange RX issue on a link and I need some more ideas on
where to look.  Two routers, an M7i and M20, are connected back-to-back,
sort-of (there's optical gear between them, obviously), over a WDM link.
Ping tests work perfectly from one to the other, using various packet sizes.
When enabling traffic from the M7i to the M20 by lowering an OSPF metric,
the link works fine.  When enabling traffic in the opposite direction, M20
to M7i, I begin to get massive input errors on the M20 GE PIC.  I see no
errors at all on the M7i side, ever.  Errors only start to accrue when
traffic reaches a certain as-yet-undetermined level, when bi-directional
traffic is enabled.

Done so far:
 - Cleaned every connector in the path.
 - Replaced both patch cables at either end of the link.
 - Installed intermediary switch to rule out PIC/SFP problems.
 - Failed over to redundant light path to rule out primary path problems.

In what situation would one see input errors accrue on one side, but only
when bi-directional traffic is enabled?

Thanks,
evt
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp