On 6 April 2012 14:49, Per Jessen <[email protected]> wrote:
> I'm looking for the "overruns:" number as in the ifconfig display:
>
> # ifconfig eth5
> eth5 Link encap:Ethernet HWaddr 00:02:B3:8D:CF:F6
> RX packets:2799 errors:0 dropped:0 overruns:0 frame:0
> TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:168911 (164.9 Kb) TX bytes:1697 (1.6 Kb)
>
>
> I'll double check if that is what I get in Discards, thanks.
I don't think it is, no.
Looking at the /proc/net/dev format, this looks as follows:
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed
multicast|bytes packets errs drop fifo colls carrier compressed
lo:27538514 310470 0 0 0 0 0 0
27538514 310470 0 0 0 0 0 0
eth0:2762421755 80087525 0 0 0 0 0 7286360
3905086444 50271882 0 0 0 0 0 0
It's a little difficult to be sure which zero corresponds with which,
but I strongly suspect that "overruns" in the ifconfig output
corresponds to the "fifo" field in /proc/net/dev
Certainly with the old interface table implementation, this field is skipped.
(Look at the definition of "scan_line_2_2" in mibgroup/mibII/interface.c)
I'm less familiar with the code for the newer re-write, but it looks as
if it's more-or-less the same (see _parse_stats() in
mibgroup/if-mib/data_access/interface_linux.c)
So no - my suspicion is that this particular value is not being reported.
Dave
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
