Forum Discussion
boczon_108037
Nimbostratus
NimbostratusCacti LTM 10.2 n opool data returned
Anyone experience any issues with Cacti not logging pool data correctly for LTM 10.2?
Here is the error.
+ Running data query [14]. + Found type = '3' [snmp query].
+ Found data query XML file at 'E:/cacti/resource/snmp_queries/f5_bigip_pool.xml'
+ XML file parsed ok. + Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.3375.2.2.5.2.3.1.1'
+ No SNMP data returned
+ Found data query XML file at 'E:/cacti/resource/snmp_queries/f5_bigip_pool.xml'
+ Found data query XML file at 'E:/cacti/resource/snmp_queries/f5_bigip_pool.xml'
+ Found data query XML file at 'E:/cacti/resource/snmp_queries/f5_bigip_pool.xml'
manual snmp walk is working
snmpwalk -v 2c -c mycummunity myf5host .1.3.6.1.4.1.3375.2.2.5.2.3.1.1
Running that brings back data a full list of all pools
Same Cacti installation is working for other hosts.
A wireshark trace shows the snmpbulkwalk stops on the 20th pool. I can recreate the same issue on two different LTMs (not an HA pair)
Communication is through a FW but can verify FW rule is OK
LTMs that are not working are 10.2HF1 6900's I can collect and graph interface stats but can not do the same for pools or VS.
3 Replies
- JRahm
Admin
I have not tried this, but if you have repeatable results just from a snmpwalk, then I'd get a case open. If found to be a bug, can you post the CR back here? 
Wilfried_113615Hi,having the same problem with LTM 8900, v10.2 for the pool connection snmp queries. the snmpwalk f5_bigip_pool.xml for the working 6400 show many values. the snmpwalk f5_bigip_pool.xml for the not working 8900 shows: No Such Object available on this agent at this OID. So I think there must be a difference in the OIDs between both machine types.
So I've done 2 snmpwalk on different LTM machine types but same v10.2, first the working LTM 6400:
[a2590172@cdcacp01 ~]$ snmpwalk -v2c -c public loadbal6400 .1.3.6.1.4.1.3375.2.2.5.2.3.1.1
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.7.99.111.98.105.100.101.118 = STRING: "cobidev"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.7.99.111.98.105.105.110.116 = STRING: "cobiint"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.8.99.111.98.105.100.101.118.97 = STRING: "cobideva"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.8.99.111.98.105.100.101.118.98 = STRING: "cobidevb"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.8.99.111.98.105.100.101.118.99 = STRING: "cobidevc"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.8.99.111.98.105.100.101.118.100 = STRING: "cobidevd"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.8.99.111.98.105.116.101.115.116 = STRING: "cobitest"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.8.109.111.98.105.108.100.101.118 = STRING: "mobildev"
:
:
and now the LTM 8900:
[a2590172@cdcacp01 ~]$ snmpwalk -v2c -c public loadbal8900 .1.3.6.1.4.1.3375.2.2.5.2.3.1.1
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1 = No Such Object available on this agent at this OID
This means that there must be a difference between the pool MIB's. I would like to know if I have to find a workaround for this and build new cacti definitions, or I can wait for a patch.- Wilfried_113615Have a case open: C899543
Greets
Wilfried
...and solution is to bigstart restart the application.
![\"F5](\"https://www.f5.com/content/dam/f5/f5-logo.svg\"){kind=logo}
