Ad Widget

Collapse

Low level discovery with external script

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • atavius
    Junior Member
    • Apr 2015
    • 8

    #1

    Low level discovery with external script

    Hi,
    I am trying to automatically generate graphs and items for device WalkAIR3000.
    This device has somehow really stupid MIB that contains data that I need in 3 separate tables that have no visible reference point.

    In first table I have names of clients:
    Code:
    snmpwalk 10.5.xxx.xxx  -cpublic  -v1 .1.3.6.1.4.1.2933.1.2.3.1.13.2
    SNMPv2-SMI::enterprises.2933.1.2.3.1.13.2.1 = STRING: "CL1_Rofa"
    SNMPv2-SMI::enterprises.2933.1.2.3.1.13.2.3 = STRING: "CL3_OP_Fedinova"
    SNMPv2-SMI::enterprises.2933.1.2.3.1.13.2.4 = STRING: "CL4_Soitron"
    SNMPv2-SMI::enterprises.2933.1.2.3.1.13.2.5 = STRING: "CL5_Stavoindustria"
    Then in second table I have data about perfomance
    Code:
    snmpwalk 10.5.xxx.xx  -cpublic  -v1 1.3.6.1.4.1.2933.1.2.17.1.1.1.1.7
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.66049 = Counter32: 240 // this is value Downlink_minSNR about signal of first client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.66051 = Counter32: 240 // this is value Downlink_minSNR about signal of second client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.66052 = Counter32: 310 // etc
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.66053 = Counter32: 280 //etc
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.131585 = Counter32: 280 // this is value Uplink_minSNR about signal of first client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.131587 = Counter32: 270 // this is value Uplink_minSNR about signal of second client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.131588 = Counter32: 320 //etc
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.7.131589 = Counter32: 250 //etc
    And then in third table I have another data of the perfomance:
    Code:
    snmpwalk 10.5.xxx.xx  -cpublic  -v1  1.3.6.1.4.1.2933.1.2.17.1.1.1.1.16
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.66049 = Counter32: 0 // this is value Uplink_FER about signal of first client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.66051 = Counter32: 0 // this is value Uplink_FER about signal of second client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.66052 = Counter32: 0 //etc
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.66053 = Counter32: 0 //etc
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.131585 = Counter32: 0 // this is value Downlink_FER about signal of first client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.131587 = Counter32: 0 // this is value Downlink_FER about signal of second client 
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.131588 = Counter32: 0 //etc
    SNMPv2-SMI::enterprises.2933.1.2.17.1.1.1.1.16.131589 = Counter32: 0 // etc
    So after some looking around I figured out that this cant be done with low level discovery out of the box. Nevertheless, after reading http://honglus.blogspot.sk/2013/01/z...lications.html I think that external script might do the trick here.

    My idea is that I will get all data formatted to table like:
    1. Client name, Downlink_minSNR, Uplink_minSNR, Downlink_FER, Uplink_FER
    2. Client name, Downlink_minSNR, Uplink_minSNR, Downlink_FER, Uplink_FER
    3. Client name, Downlink_minSNR, Uplink_minSNR, Downlink_FER, Uplink_FER
    4. Client name, Downlink_minSNR, Uplink_minSNR, Downlink_FER, Uplink_FER

    What I am not sure about is how to hook this up to low level discovery to create items based on number of rows in my table. So could someone explain me how something like this works in Zabbix?
    Last edited by atavius; 21-09-2015, 11:56.
Working...