Ad Widget

Collapse

Template Net Arista SNMP Voltage/Fan/Temperature Trigger Thresholds

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • burnsy29
    Junior Member
    • Oct 2020
    • 7

    #1

    Template Net Arista SNMP Voltage/Fan/Temperature Trigger Thresholds

    Wondering if anyone has experience with Template Net Arista SNMP Fan/Temperature/Voltage Trigger Thresholds, specifically, my problem is that the trigger prototypes are creating triggers with thresholds that appear to be incorrect as per below?
  • markfree
    Senior Member
    • Apr 2019
    • 868

    #2
    What is your Zabbix version?
    Are you using an out-of-box template?

    Your Arista template might use overrides for its thresholds. Maybe you could check that in your temperature/power discovery.

    Comment

    • burnsy29
      Junior Member
      • Oct 2020
      • 7

      #3
      Hello, Zabbix version is Zabbix 5.0.14 and Template Net Arista SNMP is an out of the box template. In the voltage discovery:

      Under "Filters" there is a macro called {#SENSOR_TYPE} set to "matches" regular expression 3|4.

      Under the "Overrides" tab:
      Overrides

      Comment

      • burnsy29
        Junior Member
        • Oct 2020
        • 7

        #4
        Fan Discovery:

        Macro {#SENSOR_TYPE} set to "matches" regular expression "10"

        Overrides What I don't want to do is have to hard code triggers etc at the host level. I want everything done at the template level so that it is uniform across all Arista switches (approximately 30 devices)

        Thank you for your time.

        Comment

        • markfree
          Senior Member
          • Apr 2019
          • 868

          #5
          I'm not familiar with Arista devices, but I'm trying to understand the logic behind Arista discovery.

          With Arista template, Voltage and temperature comes from "Get Sensors" item.

          So, "Get sensors" item returns a list of discovered entities and their raw values, all in JSON format. Acccording to doc, "the returned value contains a list of macro → value pairs":
          In Arista template they are:
          {#SENSOR_TYPE}, (...), {#THRESHOLD_LO_WARN}, {#THRESHOLD_LO_CRIT}, {#THRESHOLD_HI_WARN} and {#THRESHOLD_HI_CRIT}

          If you use "snmpget", what values do you get by querying the above items (OIDs are in template's item)?

          After you link your template to your host, what kind of raw values are you getting from these items "sensor.temp.value[entPhySensorValue.100006015]" and "{sensor.voltage.value[entPhySensorValue.100006101]"?
          What does the Arista switch documentation says about temperature and voltage values?

          Comment

          • burnsy29
            Junior Member
            • Oct 2020
            • 7

            #6
            This is interesting........doing an SNMP walk reveals the following:

            iso.3.6.1.2.1.99.1.1.1.1.100006101 = INTEGER: 3
            iso.3.6.1.2.1.47.1.1.1.1.2.100006101 = STRING: "CpucardPwrCon Rail1 12V"
            iso.3.6.1.2.1.47.1.1.1.1.3.100006101 = OID: ccitt.0
            iso.3.6.1.2.1.47.1.1.1.1.4.100006101 = INTEGER: 1100006000
            iso.3.6.1.2.1.47.1.1.1.1.5.100006101 = INTEGER: 8
            iso.3.6.1.2.1.47.1.1.1.1.6.100006101 = INTEGER: 101
            iso.3.6.1.2.1.47.1.1.1.1.7.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.8.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.9.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.10.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.11.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.12.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.13.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.14.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.15.100006101 = ""
            iso.3.6.1.2.1.47.1.1.1.1.16.100006101 = INTEGER: 2
            iso.3.6.1.2.1.47.1.1.1.1.17.100006101 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00
            iso.3.6.1.2.1.47.1.1.1.1.18.100006101 = ""
            iso.3.6.1.2.1.99.1.1.1.1.100006101 = INTEGER: 3
            iso.3.6.1.2.1.99.1.1.1.2.100006101 = INTEGER: 9
            iso.3.6.1.2.1.99.1.1.1.3.100006101 = INTEGER: 2
            iso.3.6.1.2.1.99.1.1.1.4.100006101 = INTEGER: 1192
            iso.3.6.1.2.1.99.1.1.1.5.100006101 = INTEGER: 1
            iso.3.6.1.2.1.99.1.1.1.6.100006101 = STRING: "Volts"
            iso.3.6.1.2.1.99.1.1.1.7.100006101 = Timeticks: (242941648) 28 days, 2:50:16.48
            iso.3.6.1.2.1.99.1.1.1.8.100006101 = Gauge32: 60000
            iso.3.6.1.4.1.30065.3.12.1.1.1.1.100006101 = INTEGER: -1000000000
            iso.3.6.1.4.1.30065.3.12.1.1.1.2.100006101 = INTEGER: -1000000000
            iso.3.6.1.4.1.30065.3.12.1.1.1.3.100006101 = INTEGER: 1000000000
            iso.3.6.1.4.1.30065.3.12.1.1.1.4.100006101 = INTEGER: 1000000000
            iso.3.6.1.4.1.30065.3.12.1.1.1.5.100006101 = STRING: "No thresholds are defined"

            Here is an example of voltage from the host's latest data.
            Voltage (36 Items)
            CpucardPwrCon Rail1 12V: Voltage 2021-08-10 17:10:02 1.19 KV -1 V
            CpucardPwrCon Rail2 5V ALW: Voltage 2021-08-10 17:10:02 507 V
            CpucardPwrCon Rail3 3.3V ALW: Voltage 2021-08-10 17:10:02 329 V
            CpucardPwrCon Rail4 1.8V ALW: Voltage 2021-08-10 17:10:02 179 V
            Example for temperature:
            Temperature (60 Items)
            Back-panel temp sensor: Temperature 2021-08-10 17:12:02 28.6 °C
            Back-panel temp sensor: Temperature status 2021-08-10 17:12:02 ok (1)
            CPU board temp sensor: Temperature 2021-08-10 17:12:02 31.5 °C +0.1 °C
            CPU board temp sensor: Temperature status 2021-08-10 17:12:02 ok (1)

            So it appears that there is no issue with the actual data, the issue lies in the trigger prototypes and the triggers themselves.


            Comment

            • markfree
              Senior Member
              • Apr 2019
              • 868

              #7
              It seems the trigger thresholds are defined by switch itself.
              Arista template only collects that threshold and use it for the triggers.

              The OID bellow suggests that no threshold was configured in your device. Maybe that is why previews OIDs show strange values.
              iso.3.6.1.4.1.30065.3.12.1.1.1.5.100006101 = STRING: "No thresholds are defined"
              Maybe you can change the threshold at the switch configuration.

              Comment

              • burnsy29
                Junior Member
                • Oct 2020
                • 7

                #8
                And that was my thought exactly. I have reached out to the Arista switch admin to investigate. If you'd like, I will let you know the results. Again, thank you for your time and feedback.

                Comment

                • polakos
                  Junior Member
                  • Sep 2021
                  • 2

                  #9
                  Hello burnsy29, Did you have any luck getting the switches to report correct Thresholds? We are running EOS 4.23.0F and are having the same problem. I am planning on upgrading to latest but I'm curious if that will fix it and if there is an alternate method as I will have to request downtime to upgrade. Thanks!

                  Comment

                  • polakos
                    Junior Member
                    • Sep 2021
                    • 2

                    #10
                    So I cloned the Arista SNMP template and removed the Triggers for the voltages as they were being reported incorrectly. Applied that template to my 7050s and now I don't have to worry about the incorrect threshold values. Not the best but c'est la vie

                    Comment

                    • Phillip7833
                      Junior Member
                      • Oct 2021
                      • 1

                      #11
                      Originally posted by burnsy29
                      This is interesting........doing an SNMP walk reveals the following:

                      iso.3.6.1.2.1.99.1.1.1.1.100006101 = INTEGER: 3
                      iso.3.6.1.2.1.47.1.1.1.1.2.100006101 = STRING: "CpucardPwrCon Rail1 12V"
                      iso.3.6.1.2.1.47.1.1.1.1.3.100006101 = OID: ccitt.0
                      iso.3.6.1.2.1.47.1.1.1.1.4.100006101 = INTEGER: 1100006000
                      iso.3.6.1.2.1.47.1.1.1.1.5.100006101 = INTEGER: 8
                      iso.3.6.1.2.1.47.1.1.1.1.6.100006101 = INTEGER: 101
                      iso.3.6.1.2.1.47.1.1.1.1.7.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.8.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.9.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.10.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.11.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.12.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.13.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.14.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.15.100006101 = ""
                      iso.3.6.1.2.1.47.1.1.1.1.16.100006101 = INTEGER: 2
                      iso.3.6.1.2.1.47.1.1.1.1.17.100006101 = Hex-STRING: 00 00 00 00 00 00 00 00 00 00 00
                      iso.3.6.1.2.1.47.1.1.1.1.18.100006101 = ""
                      iso.3.6.1.2.1.99.1.1.1.1.100006101 = INTEGER: 3
                      iso.3.6.1.2.1.99.1.1.1.2.100006101 = INTEGER: 9
                      iso.3.6.1.2.1.99.1.1.1.3.100006101 = INTEGER: 2
                      iso.3.6.1.2.1.99.1.1.1.4.100006101 = INTEGER: 1192
                      iso.3.6.1.2.1.99.1.1.1.5.100006101 = INTEGER: 1
                      iso.3.6.1.2.1.99.1.1.1.6.100006101 = STRING: "Volts"
                      iso.3.6.1.2.1.99.1.1.1.7.100006101 = Timeticks: (242941648) 28 days, 2:50:16.48
                      iso.3.6.1.2.1.99.1.1.1.8.100006101 = Gauge32: 60000
                      iso.3.6.1.4.1.30065.3.12.1.1.1.1.100006101 = INTEGER: -1000000000
                      iso.3.6.1.4.1.30065.3.12.1.1.1.2.100006101 = INTEGER: -1000000000
                      iso.3.6.1.4.1.30065.3.12.1.1.1.3.100006101 = INTEGER: 1000000000
                      iso.3.6.1.4.1.30065.3.12.1.1.1.4.100006101 = INTEGER: 1000000000
                      iso.3.6.1.4.1.30065.3.12.1.1.1.5.100006101 = STRING: "No thresholds are defined"

                      Here is an example of voltage from the host's latest data. Upsers
                      Voltage (36 Items)
                      CpucardPwrCon Rail1 12V: Voltage 2021-08-10 17:10:02 1.19 KV -1 V
                      CpucardPwrCon Rail2 5V ALW: Voltage 2021-08-10 17:10:02 507 V
                      CpucardPwrCon Rail3 3.3V ALW: Voltage 2021-08-10 17:10:02 329 V
                      CpucardPwrCon Rail4 1.8V ALW: Voltage 2021-08-10 17:10:02 179 V
                      Example for temperature:
                      Temperature (60 Items)
                      Back-panel temp sensor: Temperature 2021-08-10 17:12:02 28.6 °C
                      Back-panel temp sensor: Temperature status 2021-08-10 17:12:02 ok (1)
                      CPU board temp sensor: Temperature 2021-08-10 17:12:02 31.5 °C +0.1 °C
                      CPU board temp sensor: Temperature status 2021-08-10 17:12:02 ok (1)
                      So it appears that there is no issue with the actual data, the issue lies in the trigger prototypes and the triggers themselves.

                      Everything is very open with a clear description of the issues. It was truly informative. Your website is very helpful. Many thanks for sharing!
                      Last edited by Phillip7833; 05-10-2021, 06:34.

                      Comment

                      Working...