On 5/13/19 12:10 PM, Vijay, Anjali wrote:
Thanks for the help. Meanwhile, I had changed the buffer size back to
1472 and it seems to be working fine like the previous version, net-snmp
5.7.3. Do you think this can cause any serious impact?
Hi Anjali,
I think that approach is risky. It's easy
Hi Bart,
Thanks for the help. Meanwhile, I had changed the buffer size back to 1472 and
it seems to be working fine like the previous version, net-snmp 5.7.3. Do you
think this can cause any serious impact?
Regards,
Anjali Vijay
From: Bart Van Assche
Sent: Sunday, April 28, 2019 3:39 AM
To:
On Mon, May 13, 2019 at 10:08:58AM +0200, Ilya Etingof wrote:
>
> > The currelt 5.8 release (and unreleased 5.7 update) should already
> > contain objects like memTotalRealX which are defined as
> > CounterBasedGauge64
> >
> > Unfortunately I don't have hardware to test it :-)
>
> Just in case
> The currelt 5.8 release (and unreleased 5.7 update) should already
> contain objects like memTotalRealX which are defined as
> CounterBasedGauge64
>
> Unfortunately I don't have hardware to test it :-)
Just in case on-line agent emulation [1] could be helpful:
$ snmpget -v2c -c
On Mon, May 13, 2019 at 02:56:46AM -0400, Josef Ridky wrote:
> Hi folks,
>
> I would like to know your opinion on following issue.
>
> UCD-SNMP-MIB [1] uses INTEGER32 instead of COUNTER64 for memory OIDs which
> limits the reporting to 2 TiB (using KiB as the base).
> Large modern servers often
Hi folks,
I would like to know your opinion on following issue.
UCD-SNMP-MIB [1] uses INTEGER32 instead of COUNTER64 for memory OIDs which
limits the reporting to 2 TiB (using KiB as the base).
Large modern servers often contain more than 2 TiB of memory leading to the
OIDs rolling over and
