Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • CE-21.10
    • Default
    • Ubuntu 20.04

    Description

      I'm polling a few NetApp boxes (ONTAP 9.9.1P4)

      I get some alerts on over current on one of the shelfs' four current sensors.

      The maximum on the sensor in OB is set to 0.585A

      But where does this maximum come from?

      On this NetApp system I have three identical shelfs with the same type disks, and only one of the shelfs are reporting this.. and the OB sensors maximum is not the same??

      When I look into the NetApp with "environmential staus" it also does not report any issues... and there isn't even a min/max values for the current sensors as there is for the fans for example...

      So this leads be to believe that OB somehow derives this maximum current value of 0.585 from past measurements?    I have tried to reset the sensor in OB, and it is now showing a blank values...

      I may have similar issues on another shelf where it reports the fans running at a too slow speed...

       

      Maybe I just need to reset the sensors and they will find their own min/max values eventually?

       

      /Beardmann

      Attachments

        Activity

          [OBS-3932] False NetApp current alerts

          Hi Heino Walther, we have not received the additional information requested earlier from you in this issue 'I'm polling a few NetApp boxes (ONTAP 9.9.1P4)

          I get some alerts on over current on one of the shelfs' four current sensors.

          The maximum on the sensor in OB is set to 0.585A

          But where does this maximum come from?

          On this NetApp system I have three identical shelfs with the same type disks, and only one of the shelfs are reporting this.. and the OB sensors maximum is not the same??

          When I look into the NetApp with "environmential staus" it also does not report any issues... and there isn't even a min/max values for the current sensors as there is for the fans for example...

          So this leads be to believe that OB somehow derives this maximum current value of 0.585 from past measurements?    I have tried to reset the sensor in OB, and it is now showing a blank values...

          I may have similar issues on another shelf where it reports the fans running at a too slow speed...

           

          Maybe I just need to reset the sensors and they will find their own min/max values eventually?

           

          /Beardmann'!

          Issues without your response will be closed within 2 weeks.

          landy Mike Stupalov added a comment - Hi Heino Walther, we have not received the additional information requested earlier from you in this issue 'I'm polling a few NetApp boxes (ONTAP 9.9.1P4) I get some alerts on over current on one of the shelfs' four current sensors. The maximum on the sensor in OB is set to 0.585A But where does this maximum come from? On this NetApp system I have three identical shelfs with the same type disks, and only one of the shelfs are reporting this.. and the OB sensors maximum is not the same?? When I look into the NetApp with "environmential staus" it also does not report any issues... and there isn't even a min/max values for the current sensors as there is for the fans for example... So this leads be to believe that OB somehow derives this maximum current value of 0.585 from past measurements?    I have tried to reset the sensor in OB, and it is now showing a blank values... I may have similar issues on another shelf where it reports the fans running at a too slow speed...   Maybe I just need to reset the sensors and they will find their own min/max values eventually?   /Beardmann'! Issues without your response will be closed within 2 weeks.

          General questions and device support you always can discuss in our Discord channel, click here for connect.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support you always can discuss in our Discord channel, click here for connect . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            Beardmann Heino Walther
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: