Ad Widget

Collapse

Problem polling F5 vservers

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cpaterson
    Junior Member
    • Feb 2011
    • 2

    #1

    Problem polling F5 vservers

    I'm currently configuring a pair of Zabbix servers on v1.8.4 and am having problems with polling F5 virtual server stats, I think its to do with the length of the oid as the pollers for Cisco and Junipers work fine.
    An example oid for inbound bytes:
    .1.3.6.1.4.1.3375.2.2.10.2.3.1.7.25.97.112.105.46. 109.117.115.105.99.46.111.118.105.46.99.111.109.95 .50.55.56.56.95.118.115

    I get an 0x81 error back when I try these polls and Zabbix shows an error in the item configuration.

    The oid works fine using snmpget from the cli.

    Anyone had this before and know how to get it working?

    Thanks in advance
  • untergeek
    Senior Member
    Zabbix Certified Specialist
    • Jun 2009
    • 512

    #2
    I have found that OIDs are more trouble than MIBs in many cases.

    I know, that sounds completely antithetical, but it is what our experience has been.

    We've installed the F5 MIBs and the Cisco MIBs and had great experience using MIBs instead of OIDs.

    Comment

    • cpaterson
      Junior Member
      • Feb 2011
      • 2

      #3
      Problem polling F5 vservers

      Thanks for your reply untergeek,
      I've tried using the mibs unfortunately it still not working.

      Tested from snmpget and returns data
      Still getting the same response from Zabbix.

      My snmp oid entry in zabbix is :

      F5-BIGIP-LOCAL-MIB::ltmVirtualServStatClientBytesIn.30.97.99.99.1 11.117.110.116.46.109.117.115.105.99.46.111.118.10 5.46.99.111.109.95.104.116.116.112.115.95.118.115


      This is the results of a traffic capture for this query

      17.084520 1.2.3.4 -> 9.8.7.6 SNMP get-request IF-MIB::ifOutDiscards.17.1.1.6.7.0.97.108.108.101.116 .46.109.117.115.105.99.46.111.118.105.46.99.111.10 9.95.104.116.0.4004014544.3100775837.3100775837.0. 3099866431.113.4004014480.95.4004013232.109.95.104 .4004014912.0.4004014656.3154654200.3154654200.0.3 099866431.4294967295.4004014592.0.4004013344.95.0. 0.4004014976.3154654187.4004014672.0.0.32.0.429496 7295.3154654193.0.4004014344.0.0.0.0.0.0.1.0.32.0. 1962934272.3.13.3.3100775836.0.0.0.0.0.0.0.0.31000 41908.0.3.24.3.3154654199.3099866431.0.4004014976. 0.4004013728.0.0.0.4004015424.4576705.4004015056.0 .0.0.0.4294967295.4576705.0.4004014728.6.0.0.0

      17.086652 9.8.7.6 -> 1.2.3.4 SNMP get-response IF-MIB::ifOutDiscards.17.1.1.6.7.0.97.108.108.101.116 .46.109.117.115.105.99.46.111.118.105.46.99.111.10 9.95.104.116.0.4004014544.3100775837.3100775837.0. 3099866431.113.4004014480.95.4004013232.109.95.104 .4004014912.0.4004014656.3154654200.3154654200.0.3 099866431.4294967295.4004014592.0.4004013344.95.0. 0.4004014976.3154654187.4004014672.0.0.32.0.429496 7295.3154654193.0.4004014344.0.0.0.0.0.0.1.0.32.0. 1962934272.3.13.3.3100775836.0.0.0.0.0.0.0.0.31000 41908.0.3.24.3.3154654199.3099866431.0.4004014976. 0.4004013728.0.0.0.4004015424.4576705.4004015056.0 .0.0.0.4294967295.4576705.0.4004014728.6.0.0.0

      Looks like the command string is getting corrupted somehow But checking directly in the DB it all looks good.

      Comment

      Working...