Re: Open case with Cisco: Intermapper high CPU polling

[Jeje]

--On Tuesday, November 12, 2002 08:24:42 PM -0500 "William W. Fisher" <[EMAIL PROTECTED]> wrote:

The only difference between SNMPv1 and SNMPv2c polling in InterMapper 3.6
and later is that SNMPv2c polls include variables from ifXTable. If you
do not need the 64bit counters (ifHCInOctets, ifHCOutOctets) to monitor
extremely fast links, you should get by with SNMPv1 polling.  In effect,
using SNMPv1 will implement their suggestion of refraining from accessing
the ifXTable.

A longer term solution would be for InterMapper to honor their capability
MIB statements with respect to ifInMulticastPkts, ifInBroadcastPkts,
ifOutMulticastPkts, ifOutBroadcastPkts.

Unfortunately I need those 64 bits counters to monitor gigabit ports on my 7400 boxes. These interfaces are really busy and they counter wrap quickly. I hope you'll quickly provide a fix for this.

Thanks.

jeje.

____________________________________________________________________
Note: To unsubscribe from this mailing list, please send email to:
<mailto:InterMapper-Talk-off@;list.dartware.com> Thanks!