Ad Widget

Collapse

help with template oid issue UPS-MIB / MikroTik

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • zabbix@citylinkfiber.com
    Junior Member
    • Aug 2016
    • 3

    #1

    help with template oid issue UPS-MIB / MikroTik

    Hi,
    I'm trying to build a general template to monitor the UPS values I can get from a mikrotik router. The routers have a USB port that can talk to certain UPS's and report back data via UPS-MIB.

    My challenge is that if I do a query on tik-a with the following OID, it works.
    OID: .1.3.6.1.2.1.33.1.4.4.1.5.6
    I get a valid result.

    if I send the same OID to tik-b, i get an error
    "No Such Instance currently exists at this OID"

    If i remove the .6 at the end (go up one level) and run a manual cli
    snmpwalk on either tik-a or tik-b it works.

    I'm trying to figure out how to build a template that will work on any tik that supports the UPS values without having to be specific on the last level.

    thoughts ??

    thank you
  • peatb
    Zabbix Certified Trainer
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Aug 2016
    • 36

    #2
    some options you could try:

    set the oid in the template to for instance: .1.3.6.1.2.1.33.1.4.4.1.{$FINALPART} and on a host level, define the {$FINALPART} macro with the correct value.

    or, create a discovery rule that finds the correct oid and build your items with that.

    Not really elegant, but if devices behave inconsistent, you'll need to be creative
    Last edited by peatb; 06-09-2016, 11:37. Reason: typo

    Comment

    • zabbix@citylinkfiber.com
      Junior Member
      • Aug 2016
      • 3

      #3
      Hi

      Thanks for the ideas. Any pointers on how to create a discovery rule for this ?

      Comment

      • peatb
        Zabbix Certified Trainer
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Aug 2016
        • 36

        #4
        Make a discoveryrule on the part of the tree that's always the same. So try for instance on .1.3.6.1.2.1.33.1.4.4.1

        if I understand your issue correctly, this would discover:
        .1.3.6.1.2.1.33.1.4.4.1.5.6 on tik-a
        .1.3.6.1.2.1.33.1.4.4.1.5 on tik-b

        and then the item prototype can be .1.3.6.1.2.1.33.1.4.4.1.{#SNMPINDEX}

        or something like that. You'll need to play around a bit probably to find the correct setting (or it may not work after all)

        Comment

        Working...