I'll try to restate this in a way that makes sense, but the text you
quoted says it pretty well. The MIB data you are accessing is stored as
a counter that increments for each byte transmitted and received. Let's
say you polled the router and got this information:
InOctets: 543980
OutOctets: 234095
Does that tell you anything? Not really. However if you wait a minute
and poll it again you could see the amount of traffic in and out of that
interface over a period of time, which gives you a rate. A single poll
will not give you any usefull information. To get a rate, you need to
sample the data over time. In this case the data is stored in bytes so
you multiply times eight to get the rate in bits per second.
Does that help? If not, I'll try again later after some more coffee.
<g>
John
>>> "Luong, David" <[EMAIL PROTECTED]> 4/2/01 8:50:40 AM >>>
Hi Techies,
I have recenty been reading Cisco Press' new book called "Peformance
and
Fault Management" and they stated to measure utilization on a WAN
interface
(full-duplex); it is recommended to use the following formula:
max ( delta(ifInOctets), delta(ifOutOctets) x 8 x 100)
------------------------------------------------------
(number of seconds in delta) x ifSpeed
They state because of "MIB II variables are stored as counters, you
must
take two poll cycles and figure the difference between the two" hence
the
delta number. I don't understand why two poll cycles are needed and why
is
using "counters" attributed to this?
Thanks,
David
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
