Hello -

If it has not already been suggested and/or implemented, I'd like to propose 64-bit counters, at least for octets in/out of interfaces and VLANs. I monitor that traffic by fetching it via SNMP with a tool like MRTG. Apparently the counters in ROS 3.x are 32-bit, which means that 5-minute sample intervals are too infrequent for traffic above 100Mbps, and 1-minute sample intervals are too infrequent for traffic approaching the mid-500Mbps mark (counters start to rollover multiple times between reads and data errors result). 64-bit counters would give greater flexibility on read intervals, and on a device like the RB1000 which is Gig-capable, 64-bits really should be standard.

Thanks!

Ed

it would be great =(

interface counters are 64bit for a long time already

where can we get HC OIDs? /interface print oid returns only 32-bit counters...

Yeah, you do send 64bit counters, but you send them in SNMPv1, which is actually not allowed, and my management system complains about that...

interface counters are 64bit for a long time already

When I try to query the RB1000 in SNMPv2c with MRTG, it does not respond:

--base: Get Device Info on public@r1.0:::::2
SNMP Error:
no response received
SNMPv2c_Session (remote host: "r1.0" [xxx.xxx.xxx.xxx].161)
community: "public"
request ID: 1806897419
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/local/mrtg-2/bin/../lib/mrtg2/SNMP_util.pm line 627
SNMPWALK Problem for 1.3.6.1.2.1.1 on public@r1.0:::::2:v4only
at /usr/local/mrtg-2/bin/cfgmaker line 915
WARNING: Skipping public@r1.0:::::2 as no info could be retrieved

It works fine using SNMPv1, which is the default with MRTG. The MRTG config example in the Mikrotik docs here appears to be SNMPv1: http://www.mikrotik.com/documentation/m ... 1028300036

I am able to query my mananged switches using SNMPv2 from this same station, so I know that it works. MRTG only reads 64-bit data in SNMPv2 and I *think* that this is the standard. Has anyone else been able to query ROS with SNMPv2?

Ed

We do it with MRTG now. Just query with v1, and then change MaxBytes to 125000000 and it should work. I think : )

We do it with MRTG now. Just query with v1, and then change MaxBytes to 125000000 and it should work. I think : )

Changing MaxBytes will not help if MRTG does not fetch a 64-bit value in v1 mode - the following is from the MRTG docs:

SNMPv2c
If you have a fast router you might want to try to poll the ifHC* counters. This feature gets activated by switching to SNMPv2c. Unfortunately not all devices support SNMPv2c yet. If it works, this will prevent your counters from wraping within the 5 minute polling interval, since we now use 64 bit instead of the normal 32 bit.

Example:

Target[myrouter]: 2:public@router1:::::2

Ehm, MikroTik, if you could please support SNMPv2C and only return Counter64 varbinds in SNMPv2C. A lot of SNMP monitors don't like receiving 64-bit counters in SNMPv1. Essentially, you are breaking the RFC's here...

A little proof of what I'm talking about:
Funny thing is, that this happens when specifying SNMPv2C mode too, which could mean that you don't properly identify Counter64 when you send 64-bit values?

Ehm, MikroTik, if you could please support SNMPv2C and only return Counter64 varbinds in SNMPv2C. A lot of SNMP monitors don't like receiving 64-bit counters in SNMPv1. Essentially, you are breaking the RFC's here...

The other thing I discovered when investigating this is that I can't even query ROS on a RB1000 with MRTG in SNMPc2C mode - I get errors like this:

SNMP Error:
no response received
SNMPv2c_Session (remote host: "r1.0" [xxx.xxx.xxx.xxx].161)
community: "public"
request ID: 1430634338
PDU bufsize: 8000 bytes
timeout: 2s
retries: 5
backoff: 1)
at /usr/local/mrtg-2/bin/../lib/mrtg2/SNMP_util.pm line 627
SNMPWALK Problem for 1.3.6.1.2.1.1 on public@r1.0:::::2:v4only
at /usr/local/mrtg-2/bin/cfgmaker line 915
WARNING: Skipping public@r1.0:::::2 as no info could be retrieved

This appears to be an MRTG issue, not a ROS issue, and it persists even with the latest MRTG version. This is a bit off-topic, but has anyone else tried this?

Further tests indicated that SNMPv2C support in ROS is pseudo at best; you can get a response to some queries, but it does not support important features over v2C like getbulk and 64-bit counter value returns. One of the developers of the venerable MRTG was kindly working with me on this, and he said:

...for most queries, the only difference between SNMPv1 and SNMPv2c is one bit in the version field. But get-bulk is NOT OPTIONAL in SNMPv2c, in fact it is the MAJOR
advantage of SNMPv2c over SNMPv1 - the only other changes that come to my mind are better diagnostic returns and support for 64-bit integers.

I've started a feature-request thread for this here: http://forum.mikrotik.com/viewtopic.php?f=1&t=32647. All those who are interested in seeing v2C support in ROS, please post your support.

Thanks!
Ed