32bit and 64 but counters ( RFC2233 support)

[shadowcaster]

Hello.
I got into a problem with choosing counter size in cacti. I have 1G ether interfaces, which can operate at 10, 100 and 1000 mbit.
Per RFC2233:
3.1.6. Counter Size

For interfaces that operate at 20,000,000 (20 million) bits per
second or less, 32-bit byte and packet counters MUST be used. For
interfaces that operate faster than 20,000,000 bits/second, and
slower than 650,000,000 bits/second, 32-bit packet counters MUST
be used and 64-bit octet counters MUST be used. For interfaces
that operate at 650,000,000 bits/second or faster, 64-bit packet
counters AND 64-bit octet counters MUST be used.

So, in order to plot interface traffic correctly, software must:
1) Get list of interfaces (let's say ifIndex 1-5)
2) Get 64 bit counters - they exist ONLY for interfaces with speed over 650,000,000 bits/second (let's say with ifindex 2 and 3)
3) Get the rest of ifIndex from 32 bit counters -they exist only for interfaces lower than 650,000,000 bits/second (it will be 1,4 and 5)
4) populate RRDs

Can this be done in cacti?

[BSOD2600]

Yes.

Cacti comes with default interface templates either using the standard or 64bit sizes.

[shadowcaster]

But I can't select 64 OR 32 bit - in any point in time interface can be 10 mbit/32bit and next time - 1000 mbit/64bit counter. It's impossible to select manually.

[BorisL]

I monitor all my 20k ports using 64bit counters. Works nice.
Do not bother with 32bit ones, they are subject to be used only when 64bit counters are unavailable. Most modern equipment do support 64bit counters.

[Howie]

Hello.
I got into a problem with choosing counter size in cacti. I have 1G ether interfaces, which can operate at 10, 100 and 1000 mbit.
Per RFC2233:
3.1.6. Counter Size

For interfaces that operate at 20,000,000 (20 million) bits per
second or less, 32-bit byte and packet counters MUST be used. For
interfaces that operate faster than 20,000,000 bits/second, and
slower than 650,000,000 bits/second, 32-bit packet counters MUST
be used and 64-bit octet counters MUST be used. For interfaces
that operate at 650,000,000 bits/second or faster, 64-bit packet
counters AND 64-bit octet counters MUST be used.

So, in order to plot interface traffic correctly, software must:
1) Get list of interfaces (let's say ifIndex 1-5)
2) Get 64 bit counters - they exist ONLY for interfaces with speed over 650,000,000 bits/second (let's say with ifindex 2 and 3)
3) Get the rest of ifIndex from 32 bit counters -they exist only for interfaces lower than 650,000,000 bits/second (it will be 1,4 and 5)
4) populate RRDs

Can this be done in cacti?

What equipment behaves this way?

I think you are imagining an extra line in that RFC quote that says 'and MUST NOT use 32-bit'. What you usually get in kit that supports 64-bit counters is two tables, ifTable (the old SNMPv1 one) and ifXTable (all the bits added later, including the ifHC* counters). They would be an entry in both tables for all interfaces, but the 32-bit counters aren't really useful for >100Mbit interfaces.

The only exception I know of is Windows' SNMP agent, which doesn't do 64-bit counters on any speed interfaces (isn't that right, BSOD2600?)

[peecee]

Would having a 32-bit counter result in the weirdness I'm seeing in this graph?

[Howie]

No, it results in a drop to lower levels where you would expect a peak, but still with a 'traffic shaped curve'. Like this:

http://forums.cacti.net/about24526.html

[peecee]

I was afraid you were going to say that. So I'm guessing this indicates that the host simply isn't responding?

[Howie]

I was afraid you were going to say that. So I'm guessing this indicates that the host simply isn't responding?

Possibly. Check the cacti logs for errors related to that DS number.

[BSOD2600]

The only exception I know of is Windows' SNMP agent, which doesn't do 64-bit counters on any speed interfaces (isn't that right, BSOD2600?)

Correct.