Ad Widget

Collapse

Problem with Discovered Temperature Trigger for HP iLO.

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cb0n3y
    Member
    • Feb 2021
    • 32

    #1

    Problem with Discovered Temperature Trigger for HP iLO.

    Hello everyone,

    i set up a ProLiant DL20 Gen10 server using the provided "Template Server HP iLO SNMPv2". I get all i need with that template but
    i am experincing some issues with the temperature triggers. On Zabbix i get the System-0.8 Sensor Temperature is bove the threshold
    but when i look in the iLO Frontend everything is fine. The trigger itself has a macro named {$TEMP_WARN:"Device"} but i cannot find
    that macro anywhere. I only get {$TEMP_WARN}, {$TEMP_WARN:"Ambient"}. I'm getting crazy whith it. If you take a look at the pictures,
    System-0.8 has at the moment 85 °C on Zabbix and 86°C on iLO frontend, that is not bad, i just need a reload.

    So, the Caution for System-0.8 is 110 °C and Critical is 115 °C. Why the Template trigger fires on 85°C? Thank you very much.
    Attached Files
  • Hamardaban
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • May 2019
    • 2713

    #2


    • If a macro with its context is not found on host, linked templates or globally, then the macro without context is searched for.

    Comment

    • cb0n3y
      Member
      • Feb 2021
      • 32

      #3
      Godd Morning Hamardaban,

      thanks for your answer but i still do not get it. Where will the macro without context searched for? Sorry but i am new to all this.
      Last edited by cb0n3y; 20-04-2021, 15:42.

      Comment

      • cb0n3y
        Member
        • Feb 2021
        • 32

        #4
        Hello cyber,

        that make sense for me but i'm afraid is not the solution. The trigger will be created as a prototype trigger an the device is just the last numbers of the OID (e.g.: SNMPv2-SMI::enterprises.232.6.2.6.8.1.3.0.8, the created Item get the name System-0.8). I tried another thing
        and it works now, even though is not the final solution. What i made was to change the the Macro from {$TEMP_WARN:"Device"} to {$TEMP_WARN:"{#SNMPINDEX}"} in the Trigger prototype. Then a i added the Macros for each device
        (e.g.: {$TEMP_WARN:"0.8"} = 100 and {$TEMP_CRIT:"0.8"} = 105) in the Template and it works.

        That is not the solution, then we have some HP Device Generation and the OID are not standard for all of them. I thought there's way to read the threshold in the discovery rule and use the values. I have no idea. Thank you again for your answer and time. Have a nice day.

        Comment

        • cb0n3y
          Member
          • Feb 2021
          • 32

          #5
          Hi cyber,

          again, thank you very much. I'm going to let the things like they are right now (with the changes a mentioned before) and i'm gonna tune the values for each host. Thanx to everyone of you.

          Comment

          • cyber
            Senior Member
            Zabbix Certified SpecialistZabbix Certified Professional
            • Dec 2006
            • 4806

            #6
            if {$TEMP_WARN:"Device"} is not found, then Zabbix will look for {$TEMP_WARN}. That one is present in that template (macros) ...So change that one or add {$TEMP_WARN:"Device"} macro there with your desired value.

            Comment

            • cyber
              Senior Member
              Zabbix Certified SpecialistZabbix Certified Professional
              • Dec 2006
              • 4806

              #7
              Nonono.... triggers are created based on prototype... all (LLD) macros found in prototype will be replaced with discovered data.
              You could have just added {$TEMP_WARN:"Device"} with a value of 100 and {$TEMP_CRIT:"Device"} with value 105, it would have applied to all created triggers. Only need one macro not for each discovered one...Later, if you really want to "tune" per host, you can override those macros on host level (host->macros-> inherited -> change)


              Last edited by cyber; 24-12-2021, 12:22.

              Comment

              Working...