Forum Discussion
nik_65678
Nimbostratus
Nimbostratuscacti - no snmp data returned
i've been banging my head against this for a while now. i installed cacti, all is working well. i import the f5 templates version 2. i add four load balancers, all with identical software versions and snmp configurations. i setup data sources and graphs. a little while goes by and i can't figure out why three of the four load balancers aren't able to fetch pool/vip data.
i can run successful snmpwalks from the command line of my cacti server however it seems that cacti/php is not having such good luck. only one of the three servers can pull vip/pool data however they can all pull memory/interface/cpu/etc data. here's an example of the debug output on a non-working server:
+ Running data query [14].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/usr/local/share/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 '/usr/local/share/cacti/resource/snmp_queries/f5_bigip_pool.xml'
+ Found data query XML file at '/usr/local/share/cacti/resource/snmp_queries/f5_bigip_pool.xml'
here's the debug output of a working query (i snipped out lots of redundant data, there's actually a whole lot more):
+ Running data query [10].
+ Found type = '3' [snmp query].
+ Found data query XML file at '/usr/local/share/cacti/resource/snmp_queries/f5_bigip_vs.xml'
+ XML file parsed ok.
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.3375.2.2.10.2.3.1.1'
+ Index found at OID: '1.3.6.1.4.1.3375.2.2.10.2.3.1.1.8.110.105.107.95.116.101.115.116' value: 'XXXXX'
+ Inserting index data for field 'vsIndex' [value='8.110.105.107.95.116.101.115.116']
+ Located input field 'vsName' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.3375.2.2.10.2.3.1.1'
+ Found item [vsName='XXXXX'] index: 8.110.105.107.95.116.101.115.116 [from value]
+ Located input field 'vsIPAddress' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.3375.2.2.10.1.2.1.3'
+ Found item [vsIPAddress='Hex- CC 08 F2 C7'] index: 8.110.105.107.95.116.101.115.116 [from value]
+ Located input field 'vsServicePort' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.3375.2.2.10.1.2.1.6'
+ Found item [vsServicePort='80'] index: 8.110.105.107.95.116.101.115.116 [from value]
+ Found data query XML file at '/usr/local/share/cacti/resource/snmp_queries/f5_bigip_vs.xml'
any ideas why i might be able to reach the big-ip via snmpwalk on the command line but not via cacti?
HamishCirrocumulus
OK, so you've checked all the usual bits like correct community name etc by the fact that some stats come back and it's just VS ones that dont, I suggest starting at the middle of the problem... Take a tcpdump of the traffic between the cacti server and the F5.
Then use wireshark or similar to load the tcpdump and see what queries and responses are going back & forth between the two boxes.
Also, if you do an snmp walk for the specific OID that's failing (.1.3.6.1.4.1.3375.2.2.5.2.3.1.1) what do you get back?
H
nik_65678i can do some snmp queries to the non-working hosts but not all (pool/vs do not work while cpu memory etc do). for example, here is an snmpwalk to the "working" machine i listed above:
snmpwalk -c public -v2c f5loadbalancer1.com .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.8.110.105.107.95.116.101.115.116 = STRING: "XXXXX"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.11.119.119.119.46.102.120.99.109.46.100.101 = STRING: "XXXXX"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.11.119.119.119.46.102.120.99.109.46.105.116 = STRING: "XXXXX"
and here is the "non-working" machine:
snmpwalk -c public -v2c f5loadbalancer2.com .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.8.110.105.107.95.116.101.115.116 = STRING: "XXXXX"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.11.119.119.119.46.102.120.99.109.46.100.101 = STRING: "XXXXX"
SNMPv2-SMI::enterprises.3375.2.2.5.2.3.1.1.11.119.119.119.46.102.120.99.109.46.105.116 = STRING: "XXXXX"
as you can see they're exactly the same. my cacti server can reach both of them just fine from the command line however through cacti i can only reach *some* of the oids. i'm going to do some packet captures later but i have double-checked my cacti settings about two-dozen times :]- HamishPosted By nik on 07 Apr 2010 10:09 AM my cacti server can reach both of them just fine from the command line however through cacti i can only reach *some* of the oids. i'm going to do some packet captures later but i have double-checked my cacti settings about two-dozen times :]
Yep... That's why the packet captures are necessary. To see where the problem lies. Divide and conquer. (It's how I solve problems. When you don't know what's going wrong, pick a bit in the middle and PROVE what's happening there. That will tell you if it's a problem at Cacti or the F5. My money is on the cacti end BTW). H H