Fwd: Need information to retrieve etherStatsTable parameters from the linux kernel.

Hi All,

I am trying to implement etherStatsTable of the Rmon mib. I am using
Net-SNMP 5.4.2.1. I am implementing it on linux kernel. I can get the values
of some parameters from /proc/net/dev. The following are the parameters for
which I could not find from where to get the values from the system. Can you
guys help me out in this. I would be very greatfull. Thank you in advance.

   1. etherStatsDropEvents: The total number of events in which packets were
   dropped by the probe due to lack of resources. Note that this number is not
   necessarily the number of packets dropped; it is just the number of times
   this condition has been detected.
   2. etherStatsOctets: The total number of octets of data (including those
   in bad packets) received on the network (excluding framing bits but
   including FCS octets).
   3. etherStatsBroadcastPkts: The total number of good packets received
   that were directed to the broadcast address.  Note that this does not
   include multicast packets.
   4. etherStatsCRCAlignErrors: The total number of packets received
   that had a length (excluding framing bits, but including FCS octets) of
   between 64 and 1518 octets, inclusive, but but had either a bad Frame Check
   Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS
   with a non-integral number of octets (Alignment Error).
   5. etherStatsUndersizePkts: The total number of packets received that
   were less than 64 octets long (excluding framing bits, but including FCS
   octets) and were otherwise well formed.
   6. etherStatsOversizePkts: The total number of packets received that
   were longer than 1518 octets (excluding framing bits, but including FCS
   octets) and were otherwise well formed.
   7. etherStatsFragments: The total number of packets received that were
   less than 64 octets in length (excluding framing bits but including FCS
   octets) and had either a bad Frame Check Sequence (FCS) with an integral
   number of octets (FCS Error) or a bad FCS with a non-integral number of
   octets (Alignment Error).
   8. etherStatsJabbers: The total number of packets received that
   were longer than 1518 octets (excluding framing bits, but including FCS
   octets), and had either a bad Frame Check Sequence (FCS) with an integral
   number of octets (FCS Error) or a bad FCS with a non-integral number of
   octets (Alignment Error).
   9. etherStatsPkts64Octets: The total number of packets (including
   bad packets) received that were 64 octets in length (excluding framing bits
   but including FCS octets).
   10. etherStatsPkts65to127Octets: The total number of packets (including
   bad packets) received that were between 65 and 127 octets in length
   inclusive (excluding framing bits but including FCS octets).
   11. etherStatsPkts128to255Octets: The total number of packets (including
   bad packets) received that were between 128 and 255 octets in length
   inclusive (excluding framing bits but including FCS octets).
   12. etherStatsPkts256to511Octets:
   13. etherStatsPkts512to1023Octets:
   14. etherStatsPkts1024to1518Octets:

Thank you in advance.

Srivardhan

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july

_______________________________________________
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