Ad Widget

Collapse

SNMP Dynamic indexes

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jponeill125
    Junior Member
    • May 2011
    • 4

    #1

    SNMP Dynamic indexes

    Hi All,
    I was just wondering has anyone ever encountered this problem or even better found a solution.
    I have a 2-level index, and Zabbix finds the indexed item correctly, but does not correctly append the full difference between the indexed item you're searching for, and the item you want to find the value for.

    Example (from CISCO VPDN MIB):

    .1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898 = STRING: "[email protected]"
    .1.3.6.1.4.1.9.10.24.1.3.2.1.3.2.24196.60898 = INTEGER: 10
    .1.3.6.1.4.1.9.10.24.1.3.2.1.4.2.24196.60898 = Timeticks: (52950267) 6 days, 3:05:02.67
    .1.3.6.1.4.1.9.10.24.1.3.2.1.5.2.24196.60898 = Counter32: 3685231
    .1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898 = Counter32: 349105822
    .1.3.6.1.4.1.9.10.24.1.3.2.1.7.2.24196.60898 = Counter32: 6645606
    .1.3.6.1.4.1.9.10.24.1.3.2.1.8.2.24196.60898 = Counter32: 3877033828
    .1.3.6.1.4.1.9.10.24.1.3.2.1.9.2.24196.60898 = INTEGER: 1
    .1.3.6.1.4.1.9.10.24.1.3.2.1.10.2.24196.60898 = ""
    .1.3.6.1.4.1.9.10.24.1.3.2.1.11.2.24196.60898 = INTEGER: 0
    .1.3.6.1.4.1.9.10.24.1.3.2.1.12.2.24196.60898 = INTEGER: 2
    .1.3.6.1.4.1.9.10.24.1.3.2.1.20.2.24196.60898 = Gauge32: 0
    .1.3.6.1.4.1.9.10.24.1.3.2.1.21.2.24196.60898 = Counter32: 0
    .1.3.6.1.4.1.9.10.24.1.3.2.1.22.2.24196.60898 = Counter32: 0
    .1.3.6.1.4.1.9.10.24.1.3.2.1.23.2.24196.60898 = ""
    .1.3.6.1.4.1.9.10.24.1.3.2.1.24.2.24196.60898 = INTEGER: 0

    The item I'm using as my search is "[email protected]", but the base of the index is (according to the MIB) ".1.3.6.1.4.1.9.10.24.1.3.2.1.2". Therefore "2.24196.60898" is the index number. I'm trying to retrieve the value for ".1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898" , of which the base should be ".1.3.6.1.4.1.9.10.24.1.3.2.1.6".

    Zabbix is reporting the following: "OID [1.3.6.1.4.1.9.10.24.1.3.2.1.6.60898] value has unknow type [0x81]". Does Zabbix have the ability to compare the difference between the the matched index ".1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898" , and the search base index we supply, and then append it to the index we're looking for the value for ".1.3.6.1.4.1.9.10.24.1.3.2.1.6"



    Thanks
  • netmon
    Member
    • Feb 2012
    • 30

    #2
    What Zabbix Version are you using?

    LLD (Low Level Discovery) in Zabbix 2.0 is probably what you are looking for.

    Just to clarify: You are only interested in the user email string?
    So basically only OID .1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898.
    Or better:
    .1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.nnn.mmm

    Is that correct?

    Comment

    • jponeill125
      Junior Member
      • May 2011
      • 4

      #3
      Hi Netmon,

      Thanks for the quick reply.

      The [email protected] the this active-id of a user on an L2TP session (DSL user). The active-id is always the same. Every time a user re authenticates he receives a new active-number(60898). So far so good. I can use the [email protected] to find the active-number each time a user connects and I can use this index to get the bandwidth usage of a DSL customer even though the last portion of the OID is different each time they connect. Bandwidth usage OID is 1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898. which is my base OID.

      However, 24196 or nnn is the tunnel-id of the L2TP tunnel over which the DSL user travels. If the L2TP tunnel over which the user is connecting drops the (24196 or nnn) portion of the OID also changes. This means zabbix is handing 60898 to the bandwidth OID instead of 24196.60898.

      So the short answer to your question is no. I need the resulting index from [email protected] to feed nnn.mmm into my base OID instead of just mmmm.

      Any help on this would be greatly appreciated.

      Comment

      • netmon
        Member
        • Feb 2012
        • 30

        #4
        Hi,

        check:

        My Addons to the Zabbix Monitoring Solution. Contribute to simonkowallik/Zabbix-Addons development by creating an account on GitHub.



        .1.3.6.1.4.1.9.10.24.1.3.2.1.2.2.24196.60898 = STRING: "[email protected]"
        .1.3.6.1.4.1.9.10.24.1.3.2.1.3.2.24196.60898 = INTEGER: 10
        .1.3.6.1.4.1.9.10.24.1.3.2.1.4.2.24196.60898 = Timeticks: (52950267) 6 days, 3:05:02.67
        .1.3.6.1.4.1.9.10.24.1.3.2.1.5.2.24196.60898 = Counter32: 3685231
        .1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898 = Counter32: 349105822
        .1.3.6.1.4.1.9.10.24.1.3.2.1.7.2.24196.60898 = Counter32: 6645606
        .1.3.6.1.4.1.9.10.24.1.3.2.1.8.2.24196.60898 = Counter32: 3877033828
        .1.3.6.1.4.1.9.10.24.1.3.2.1.9.2.24196.60898 = INTEGER: 1
        .1.3.6.1.4.1.9.10.24.1.3.2.1.10.2.24196.60898 = ""
        .1.3.6.1.4.1.9.10.24.1.3.2.1.11.2.24196.60898 = INTEGER: 0
        .1.3.6.1.4.1.9.10.24.1.3.2.1.12.2.24196.60898 = INTEGER: 2
        .1.3.6.1.4.1.9.10.24.1.3.2.1.20.2.24196.60898 = Gauge32: 0
        .1.3.6.1.4.1.9.10.24.1.3.2.1.21.2.24196.60898 = Counter32: 0
        .1.3.6.1.4.1.9.10.24.1.3.2.1.22.2.24196.60898 = Counter32: 0
        .1.3.6.1.4.1.9.10.24.1.3.2.1.23.2.24196.60898 = ""
        .1.3.6.1.4.1.9.10.24.1.3.2.1.24.2.24196.60898 = INTEGER: 0

        The item I'm using as my search is "[email protected]", but the base of the index is (according to the MIB) ".1.3.6.1.4.1.9.10.24.1.3.2.1.2". Therefore "2.24196.60898" is the index number. I'm trying to retrieve the value for ".1.3.6.1.4.1.9.10.24.1.3.2.1.6.2.24196.60898" , of which the base should be ".1.3.6.1.4.1.9.10.24.1.3.2.1.6".

        Base OID Relative OID
        .1.3.6.1.4.1.9.10.24.1.3.2.1 .2.2.24196.60898 = STRING: "[email protected]"
        . . .
        .1.3.6.1.4.1.9.10.24.1.3.2.1 .6.2.24196.60898 = Counter32: 349105822

        discovery rule type:"external check"
        key:
        advsnmp.discovery[{HOST.IP},"-v2c -cpublic",.1.3.6.1.4.1.9.10.24.1.3.2.1,1.1,3.2]

        advsnmp.discovery will extract:

        {#ADVSNMPINDEX1} => 2
        {#ADVSNMPINDEX1} => 6
        {#ADVSNMPINDEX2} => 24196.60898
        {#ADVSNMPINDEX2} => 24196.60898


        alternative 1:
        advsnmp.discovery[{HOST.IP},"-v2c -cpublic",.1.3.6.1.4.1.9.10.24.1.3.2.1,1.4]

        in this case advsnmp.discovery will extract:

        {#ADVSNMPINDEX1} => 2.2.24196.60898
        {#ADVSNMPINDEX1} => 6.2.24196.60898


        alternative 2:
        advsnmp.discovery[{HOST.IP},"-v2c -cpublic",.1.3.6.1.4.1.9.10.24.1.3.2.1,2.3]

        in this case advsnmp.discovery will extract:

        {#ADVSNMPINDEX1} => 2.24196.60898
        {#ADVSNMPINDEX1} => 2.24196.60898



        Hope that helps!

        Comment

        • jponeill125
          Junior Member
          • May 2011
          • 4

          #5
          Thanks for you help netmon

          Comment

          Working...