Idea ID: 1654115

NNMi Support for MIB OID Type CounterBasedGauge64

Status : Under Consideration
Under Consideration
See status update history
over 3 years ago

Currently, the MIB Object type CounterBasedGauge64 is not strictly supported by RFC:

From  RFC 2856:

           Note that this TC is not strictly supported in SMIv2,
           because the 'always increasing' and 'counter wrap' semantics
           associated with the Counter64 base type are not preserved.
           It is possible that management applications which rely
           solely upon the (Counter64) ASN.1 tag to determine object
           semantics will mistakenly operate upon objects of this type
           as they would for Counter64 objects.

Even with NNMi, we cannot cast it as Big Integer.  It will result in an error in the nnm.log files.

NNMi can cast as a Gauge, but it will not support values greater than 32 bit.

The Idea is to get real support for this OID

Labels:

Content - Integrations
Parents
  • Though no strictly a standard the RFC has been around since 2000 and the extended type is commonly used by many vendors today including F5, Cisco, Juniper, etc. In the specific case of F5 there are key metrics I can not monitor with NNM due to this limitation including things like memory and connections. This type is already supported today by other competing products such as SolarWindows.

Comment
  • Though no strictly a standard the RFC has been around since 2000 and the extended type is commonly used by many vendors today including F5, Cisco, Juniper, etc. In the specific case of F5 there are key metrics I can not monitor with NNM due to this limitation including things like memory and connections. This type is already supported today by other competing products such as SolarWindows.

Children
No Data