Mailing List Archive

1 2  View All
Re: EOBC0/0 ifInErrors [ In reply to ]
12.10.2020 23:12, Nick Hilliard wrote:

> Eugene Grosbein wrote on 12/10/2020 10:07:
>> Forgot show show that moment:
>>
>> http://www.grosbein.net/cisco/eobc0_0-inc.png
>>
>> Both graps show same value, upper graph shows maximum over an hour, lower (blue) is an average over an hour.
>>
>>> Today at 12:16 another one (now inactive) RSP module was ejected physically and error rate decreases again but not ceased:
>>>
>>> http://www.grosbein.net/cisco/eobc0_0-day2.png
>>>
>>> What does it mean?
>
> if errs-in matches runts-in, then this may be a backplane failure. You need to get an opinion from TAC on this.

I'm not sure how and where I can get counters for errs-in/runts-in of EOBC0/0.

Also, I have another similar 7606 box with two excactly same RSP modules and its SNMP counters for EOBC0/0 show very similar picture.
I doubt this is hardware failure because both routers experience no other visible problems while forming core of the network and carrying its traffic.

We have no active support contract.

_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: EOBC0/0 ifInErrors [ In reply to ]
Eugene Grosbein wrote on 12/10/2020 20:11:
> I'm not sure how and where I can get counters for errs-in/runts-in of
> EOBC0/0.

"show platform eobc all" - see the "Giants / Runts" counters.

> Also, I have another similar 7606 box with two excactly same RSP
> modules and its SNMP counters for EOBC0/0 show very similar picture.
> I doubt this is hardware failure because both routers experience no
> other visible problems while forming core of the network and carrying
> its traffic.

the EOBC interface is half-duplex which means that collisions can
happen. It may be that these "errors" are simply collisions, in which
case they are harmless.

Nick
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: EOBC0/0 ifInErrors [ In reply to ]
13.10.2020 2:18, Nick Hilliard wrote:

> Eugene Grosbein wrote on 12/10/2020 20:11:
>> I'm not sure how and where I can get counters for errs-in/runts-in of
>> EOBC0/0.
>
> "show platform eobc all" - see the "Giants / Runts" counters.
>
>> Also, I have another similar 7606 box with two excactly same RSP
>> modules and its SNMP counters for EOBC0/0 show very similar picture.
>> I doubt this is hardware failure because both routers experience no
>> other visible problems while forming core of the network and carrying
>> its traffic.
>
> the EOBC interface is half-duplex which means that collisions can happen. It may be that these "errors" are simply collisions, in which case they are harmless.

It seems so:

#show platform eobc all
Driver Level Counters: (Cumulative, Zeroed only at Reset)
Frames Bytes
Rx(0) 83287913 683355380
Tx(0) 76687181 3083105928

Input Drop Frame Count
Rx0 = 0 Rx-replacement0 = 0
Per Queue Receive Errors:
FRME OFLW BUFE NOENP DISCRD DISABLE BADCOUNT
Rx0 0 0 0 0 0 0 0

Rx Last bit not set = 0 Rx First bit not set = 0
Ring Reset = 0

Tx Errors/State:
One Collision Error = 306656 More Collisions = 1209541
No Encap Error = 0 Deferred Error = 2009836
Loss Carrier Error = 0 Late Collision Error = 0
Excessive Collisions = 1 Buffer Error = 0
Tx Freeze Count = 0 Tx Intrpt Serv timeout= 1
Tx Flow State = FLOW_ON
Tx Flow Off Count = 0 Tx Flow On Count = 0

Counters collected at Idb:
Is input throttled = 0 Throttle Count = 0
Rx Resource Errors = 0 Input Drops = 0
Input Errors = 28517
Output Drops = 0 Giants/Runts = 0/28517
Dma Mem Error = 0 Input Overrun = 0

Hash match table for multicast (in use 1, maximum 64 entries):
Entry 0 MAC Addr = 0100.8300.0000

Dev_Instance=0x1D13A06C 487825516
Receive/Transmit Buffer Descriptors
RingSz Shadow StartBD LastBD Head Tail Pend
Rx0 512 1D13AA2C 79CF7C80 79CF8C78 361 0 0
Tx0 512 0 79CF8CC0 79CF9CB8 333 333 0

Rx Drop On Busy Disabled
Hash match table for multicast (in use 1, maximum 64 entries):
Entry 0 MAC Addr = 0100.8300.0000

ETSEC IPC/RPC/SCP Counters

IPC Rx Count = 100450718
IPC RxFrag Count = 12547529
IPC RPC Request Rx Count = 11260149
IPC RPC Request RxFrag Count = 9414646
IPC RPC Response Rx Count = 14647969
IPC RPC Response RxFrag Count = 1562930
IPC Unreliable Rx Count = 452764
SCP Rx Count = 28688164

IPC Tx Count = 91846030
IPC TxFrag Count = 104057
IPC RPC Request Tx Count = 13189443
IPC RPC Request TxFrag Count = 3899
IPC RPC Response Tx Count = 5032168
IPC RPC Response TxFrag Count = 68319
IPC Unreliable Tx Count = 452792
SCP Tx Count = 28696645


ETSEC counters in Hardware

64b = 122344316 64b-127b = 138902198 128b-255b = 43473726
256b-511b = 11325757 512b-1023b = 8774625 1024b-1518b = 160146925
1519b-1522b = 0 RxBytes = 3933761960 RxPkt = 420739417
RxFCSErr = 0 RxMCast = 9871009 RxBCast = 17
RxCntrlFr = 0 RxPauseFR = 0 RxUnkop = 0
RxAlignErr = 0 RxLenErr = 0 RxCodeErr = 0
RxSenseErr = 0 RxUnder = 76 RxOver = 0
RxFrag = 12458974 RxJab = 0 RxDrop = 0
RxFilerRej = 0 Txbytes = 3420175598 TxPkt = 76687181
TxMCast = 244991 TxBCast = 2 TxPause = 0
TxDef = 1421065 TxCol = 306656 TxMCol = 321360
TxLateCol = 0 TxExCol = 1 TxTotCol = 1516203
TxDrop = 0 TxJab = 0 TxFCS = 0
TxOver = 0 TxUnder = 0 TxFrg = 0
TxIllegalTxDrops = 0


_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: EOBC0/0 ifInErrors [ In reply to ]
13.10.2020 2:18, Nick Hilliard wrote:

> Eugene Grosbein wrote on 12/10/2020 20:11:
>> I'm not sure how and where I can get counters for errs-in/runts-in of
>> EOBC0/0.
>
> "show platform eobc all" - see the "Giants / Runts" counters.

Another box show similar picture:

Counters collected at Idb:
Is input throttled = 0 Throttle Count = 0
Rx Resource Errors = 0 Input Drops = 0
Input Errors = 4306877
Output Drops = 0 Giants/Runts = 0/4306877
Dma Mem Error = 0 Input Overrun = 0

_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: EOBC0/0 ifInErrors [ In reply to ]
Eugene Grosbein wrote on 12/10/2020 20:28:
> It seems so:
[...]
> Tx Errors/State:
> One Collision Error = 306656 More Collisions = 1209541
[...]
> Input Errors = 28517
> Output Drops = 0 Giants/Runts = 0/28517

uh, obviously collisions are a transmit phenomenon, but you're seeing rx
errors, so this isn't collisions. I don't know what the root cause is
here, but runts are not good on ethernet and usually indicate physical
cabling problems. As the EOBC interface is "cabled" via the crossbar at
the rear of the chassis, there are relatively few failure points.

Nick
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: EOBC0/0 ifInErrors [ In reply to ]
Eugene Grosbein wrote on 12/10/2020 20:28:
> It seems so:
[...]
> Tx Errors/State:
> One Collision Error = 306656 More Collisions = 1209541
[...]
> Input Errors = 28517
> Output Drops = 0 Giants/Runts = 0/28517

> uh, obviously collisions are a transmit phenomenon, but you're seeing rx
> errors, so this isn't collisions. I don't know what the root cause is
> here, but runts are not good on ethernet and usually indicate physical
> cabling problems. As the EOBC interface is "cabled" via the crossbar at
> the rear of the chassis, there are relatively few failure points.

> Nick

One possibility that springs to mind here is a duplex mis-match. 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, then the half-duplex interface will record a collision and stop transmitting when it receives a frame overlapping with one that it is transmitting. Your full-duplex interface will only see the part of that frame that is transmitted before the collision is detected - which the full-duplex interface may record as a runt.

It would be interesting to know what happens to the runt and collision stats if you can force both ends to full duplex, or both ends to half duplex.

Tim
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: EOBC0/0 ifInErrors [ In reply to ]
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.

Nick
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
Re: EOBC0/0 ifInErrors [ In reply to ]
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

1 2  View All