{#SNMPINDEX} being truncated

XMLWordPrintable

    • Type: Problem report
    • Resolution: Cannot Reproduce
    • Priority: Trivial
    • None
    • Affects Version/s: 4.2.0
    • Component/s: Server (S)
    • None

      OIDs I'm using in this example

       

      .1.3.6.1.4.1.5454.1.80.4 =
         .iso.org.dod.internet.private.enterprises.trango.tbw.ptp.gige
       or
         GIGA-PLUS-MIB::gige
      .1.3.6.1.4.1.5454.1.80.4.1.1.3.0 =
          .iso.org.dod.internet.private.enterprises.trango.tbw.ptp.gige.eth1.config1.gigeEth1Enable.0
       or
         GIGA-PLUS-MIB::gigeEth1Enable.0
      

       

      I am attempting to discover a complex OID
      My discovery rule specifies .1.3.6.1.4.1.5454.1.80.4

      I am attempting to discover (among others) .1.3.6.1.4.1.5454.1.80.4.1.1.3.0
      When discovery occurs, {#SNMPINDEX} is set to 'th1Enable.0'

      This is not helpful. Either of the following would be correct
      1.1.3.0
      eth1.config1.gigeEth1Enable.0

       

        1. Configuration.png
          129 kB
          Omni Flux
        2. DiscoveryFilters.png
          32 kB
          Omni Flux
        3. DiscoveryMacros.png
          31 kB
          Omni Flux
        4. DiscoveryPreprocessing.png
          23 kB
          Omni Flux
        5. DiscoveryRule.png
          37 kB
          Omni Flux
        6. ItemPreprocessing.png
          29 kB
          Omni Flux
        7. ItemPrototype.png
          49 kB
          Omni Flux
        8. snmpwalk.txt
          17 kB
          Omni Flux
        9. snmpwalk-Of.txt
          38 kB
          Omni Flux
        10. snmpwalk-On.txt
          19 kB
          Omni Flux

            Assignee:
            Alexey Pustovalov
            Reporter:
            Omni Flux
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: