[c-nsp] EOBC0/0 ifInErrors

Jim Getker (getker) getker at cisco.com
Tue Oct 13 07:26:47 EDT 2020

The EOBC is a proprietary shared bus, and full duplex doesn't exist.  Collisions are going to occur, and they can result in receive errors.  Overall I wouldn't worry about it unless there are other symptoms.  That being said I haven't worked on the Cat6K for a long time and can't speak for TAC, take it for what it is worth.


-----Original Message-----
From: cisco-nsp <cisco-nsp-bounces at puck.nether.net> On Behalf Of Nick Hilliard
Sent: Tuesday, October 13, 2020 7:04 AM
To: Tim Rayner <Tim.Rayner at aarnet.edu.au>
Cc: cisco-nsp <cisco-nsp at puck.nether.net>
Subject: Re: [c-nsp] EOBC0/0 ifInErrors

Tim Rayner wrote on 13/10/2020 10:48:
> If the EOBC0/0 interface that you're seeing runts on is running as 
> full duplex, and the interface that it connects to is running at half 
> duplex,

that would do it, but EOBC is an internal interface which is h/d by default. I'm not sure if it's even possible to configure the interface discipline on the CLI, but maybe it is.

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/

More information about the cisco-nsp mailing list