|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
Hi Peter, all,
There are two things that I would like to discuss at Monday's Ad Hoc please:
(1) I would like to discuss the interface statistics a bit
+--ro in-error-fcs-pkts? // 64 <= pkt <= 1518, bad FCS or alignment
+--ro in-error-runt-pkts? // pkt < 64, good or bad FCS
+--ro in-error-giant-pkts? // pkt > MRU, good or bad FCS.
The problems that I'm trying to work around in Clause 30 is that there don't appear to be separate registers for:
in-pkts-errors-runt counter64, // pkt < 64, good frame
in-pkts-errors-fragment counter64, // pkt < 64, bad frame
in-pkts-errors-giant counter64, // pkt > MRU, good frame
in-pkts-errors-jabber counter64, // pkt > MRU, bad frame
There are separate registers in clause 30 for bad FCS vs bad alignment. However, from "22.214.171.124.7 aAlignmentErrors": "This counter will not increment for group encoding schemes encoding greater than 4 bits per group.". Does this imply that this counter will be 0 for all speeds at 1GB/s or faster?
(2) The IETF/IEEE liaison meeting is on Monday, a couple of hours after the Task Force Ad Hoc. I will email them to give them a heads up that I want to speak about RMON MIB vs Ethernet 802.3 YANG. But it would be good to confirm what I say for that meeting.
On 27/01/2017 01:24, Peter Jones (petejone) wrote: