> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:juniper-nsp- > [EMAIL PROTECTED] On Behalf Of Paul Goyette > Sent: Friday, June 13, 2008 10:12 AM > To: Lakshminarayanan P; juniper-nsp@puck.nether.net > Subject: Re: [j-nsp] L3 incompletes > > > My 2 cents - > > > > The most common reason for this problem is some protocol that > > is disabled on > > the interface in question being enabled on the other to which > > the interface > > connects. For example, OSPF might be disabled on this > > interface but enabled > > on the other end to which this interface connects. As a result, the > > multicast updates reaching this interface would then be > > discarded as L3 > > incompletes! > > No, that should result in "policed discards", not "L3 incompletes". > This commonly shows up when the neighbor is from Brand-C and has > cdp enabled. :) >
I'm hesitant to attempt to correct anyone with a "juniper.net" address, but I'm not sure this is entirely true. Discarded OSPF packets should show up as layer 3, not layer 2, so I don't believe policed discards counts in this situation. It is correct that CDP/LLDP/VTP/etc. will show up as policed discards. -evt _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
