[c-nsp] Input error from Cisco Switch and Juniper Router

[Frances Albemuth]

 IIRC, the L3 incomplete counter will increment on the jnx side for
dot1q tags which you haven't configured, as well.  So, if the Cisco
port isn't configured to limit which VIDs are allowed on the port
there's a high likelihood the jnx is going to hear frames with dot1q
tags which aren't configured on the interface.  If this is a situation
one doesn't plan to remedy in the near term one can prevent every L3
incomplete from being counted as an input error by using
'ignore-l3-incompletes' in the
interface/(fastether-options|gigether-options) context.  This will
also cause the interface to stop counting the L3 incomplete packets
themselves.  I believe this knob was introduced in JunOS 9.0.

 -FC


On Fri, Jan 16, 2009 at 9:48 AM, Eric Van Tol <eric at atlantech.net> wrote:
>> -----Original Message-----
>> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
>> bounces at puck.nether.net] On Behalf Of Kelvin Goei
>> Sent: Thursday, January 15, 2009 11:17 PM
>> To: cisco-nsp at puck.nether.net
>> Subject: [c-nsp] Input error from Cisco Switch and Juniper Router
>>
>> Hi All,
>>
>> We are experiencing issue with connectivity between Cisco Switch to
>> Juniper Router. We are seeing the input error keep increasing in our Cisco
>> Switch.
>>
>
> CRC errors are normally caused by a physical issue such as a bad cable, port, or light levels.  You mentioned that you changed the cable on the Cisco side, what about the Juniper side?  Check to make sure that the fiber connectors are clean along the entire path of the RX cable to the Cisco and that your light levels are within spec.  Do you know the distance of the cable between the two?
>
> Policed discards and L3 incompletes wouldn't cause CRC errors, but as a previous poster mentioned, you'll want to disable CDP/LLDP/STP on the Cisco side to prevent policed discards from accruing.  L3 incompletes are an annoying counter on Juniper that are normally impossible to figure out without a packet sniffer, but in my experience have not been service affecting.
>
> -evt
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>