|
Convert those values to binary:
6103148527616 = 1011000110100000000000000000000000000000000
12652973654016 = 10111000001000000000000000000000000000000000
19426137079808 = 100011010101100000000000000000000000000000000
and shift right 32 bits and back to decimal:
1421, 2946, 4523
So they're about right, just padded with extra zeroes. You can
probably convert those values with whatever software package you're
using to retrieve the SNMP data.
Note that the two words may just be swapped - try making the counter
wrap by sending more than 2**32 packets, and see what happens. Or it
may just be a counter32 value being reported as a counter64. Either
way, the right numbers are there, you just need to convert.
On 11/20/06, Malcolm <lists@xxxxxxxxxxxxxxxx> wrote:
Having got over the excitement of getting SNMP data out of LVS...
Everything looks great except that the InBytes counter seems out of whack?
If I clear the packet counters then:
snmpwalk -c public -v 2c -m LVS-MIB localhost 1.3.6.1.4.1.8225.4711
Returns zero for everything as expected.
But if I test access one html page through the LVS I get:
LVS-MIB::lvsRealStatsInBytes.2.4 = Counter64: 6103148527616
But ipvsadm correctly shows 1525
Grab another page and I get:
LVS-MIB::lvsRealStatsInBytes.2.4 = Counter64: 12652973654016
ipvsadm shows: 3050
Do you need to do something special with the output from 64bit counters?
(divide by a billion?)
and then...
4471
19426137079808
It also shows both configured virtual servers to have the same traffic
(inBytes) even though one is in active.
I'm going to try installing from scratch again to see if that makes a
difference (current ipvsadm had ops patch will try a vanilla one.)
_______________________________________________
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://www.in-addr.de/mailman/listinfo/lvs-users
|
