[rrd-users] Re: gigabit interfaces

[Gellatly, Laurie]

Using my OverTime application that uses HP OpenView as its collector
and RRDTool as its database and graphing facility I don't think I 
will have too many trobles about my SNMP framework
not understanding the various versions of SNMP. If the agent on the
switch/hardware has a problem then that is a manufacturer problem.
My comment still stands, from machines I've seen that DO NOT SUPPORT
ifHC... under ANY SNMP version and yet have interfaces that support
>100Mb. The fact that some switches do is great and those companies
certainly make our lives in network management easier. So, you can
see that using OpenView as my frontend certainly has its advantages.
Just need the various polled agents to provide the data.

BTW from the recent discussion about counter wrapping and machine
restarts, Openview checks on sysUptime and calculates the differences
for me (allowing for counter wraps - provided you poll frequently
enough still) so all the data is collected as "GAUGE" and eliminates
a lot issues in recent discussions.


			...Laurie :{)

-----Original Message-----
From: Simon Leinen [mailto:simon at limmat.switch.ch]
Sent: Thursday, 6 July 2000 23:25
To: Gellatly, Laurie
Cc: 'Todd Caine'; Michael Smith; rrd-users at list.ee.ethz.ch
Subject: Re: [rrd-users] Re: gigabit interfaces


>>>>> "gl" == Gellatly, Laurie <Laurie.Gellatly at vodafone.com.au> writes:
> All we need to do now is have the manufacturers with Gig interfaces
> always provide IfHCInOctets etc and the world will be simple.  In my
> experience, too many machines have higher speed interfaces without
> providing the 64bit counters to support them!

Don't be so quick to blame the vendors... as I said, SNMP agents that
let you access Counter64 variables using SNMPv1 are buggy.  This is
stated quite clearly in RFC2576, section 4.1.2.1:

  "[...]
   The impact on multi-lingual command responders is that they MUST NOT
   ever return a variable binding containing a Counter64 value in a
   response to a request that was received using the SNMPv1 message
   version.
   [...]"

So you have to use SNMPv2 or SNMPv3 to access the 64-bit counters.  As
long as Cricket doesn't have a supported way to select SNMPv2 (which
is implemented in the underlying Perl SNMP library), it's not easy to
make use of Counter64 variables which are implemented correctly (such
as those in Cisco's SNMP agents).

Regards,
-- 
Simon.


---------------------------------------------------------------------
This correspondence is for the named person's use only.  It may 
contain confidential or legally privileged information or both. 
No confidentiality or privilege is waived or lost by any 
mistransmission.  If you receive this correspondence in error, please
immediately delete it from your system and notify the sender.  You 
must not disclose, copy or rely on any part of this correspondence 
if you are not the intended recipient. 

Any views expressed in this message are those of the individual sender,
except where the sender expressly, and with authority, states them to
be the views of Vodafone.

This email has been checked for viruses.

--
Unsubscribe mailto:rrd-users-request at list.ee.ethz.ch?subject=unsubscribe
Help        mailto:rrd-users-request at list.ee.ethz.ch?subject=help
Archive     http://www.ee.ethz.ch/~slist/rrd-users
WebAdmin    http://www.ee.ethz.ch/~slist/lsg2.cgi