Forum Discussion

JosephT's avatar
JosephT
Icon for Nimbostratus rankNimbostratus
Dec 10, 2007

Help finding OID for GTM Performance Graph

I'm trying to add the "GTM Performance" graph to Cacti. Cacti doesn't have a pre-defined OID for it so I need to add it manually. FYI, on the GTM, the "GTM Performace" graphs displays the number of DNS requests and responses/sec.

 

 

I've snmpwalked the GTM and the closest OID's I could find were:

 

 

F5-BIGIP-GLOBAL-MIB::gtmStatRequests.0 = Counter64: 20175638

 

F5-BIGIP-GLOBAL-MIB::gtmStatResolutions.0 = Counter64: 19866984

 

 

But those counters don't come anywhere close to the numbers we see on the graphs. The graphs show about 30 DNS requests & responses/sec.

 

 

Any ideas? TIA

3 Replies

  • Funny you should post, I started looking at GTM today for inclusion in the F5 Cacti templates. These are counters, not gauges, and represent the total number, not the current number. If you build your graph template similar to the traffic_in data point on an interface, you should get the results you are looking for.

     

     

    BTW, if you get the bones of a GTM template, please share! I'll post when I get there, I'm just now evaluating the mibs.
  • Have either of you had any luck getting Cacti and the GTM's setup together?
  • Posted By citizen_elah on 12/10/2007 12:40 PM

     

    Funny you should post, I started looking at GTM today for inclusion in the F5 Cacti templates. These are counters, not gauges, and represent the total number, not the current number. If you build your graph template similar to the traffic_in data point on an interface, you should get the results you are looking for.

     

    BTW, if you get the bones of a GTM template, please share! I'll post when I get there, I'm just now evaluating the mibs.

     

     

    I decided to revisit this today and actually got it to work! Thanks for pointing out the need to use "counter" instead of "guage" for the data source type in the data template.

     

    In anycase, here are the OID's should anyone need them:

     

    requests: .1.3.6.1.4.1.3375.2.3.1.2.1.2.0

     

    resolutions: .1.3.6.1.4.1.3375.2.3.1.2.1.3.0