Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4711

PoE alerts reported on Netgear GS728TPS(B) and GS752TPS(B)

Details

    • Help
    • Resolution: Not A Bug
    • Minor
    • None
    • CE-22.5
    • Alerting, Ports

    Description

      Observium reports alerts about PoE ports on Netgear GS728TPS(B) and GS752TPS(B) when the power/current/voltage delivered is below 3W/3A/3V.

      It is normal for these PoE devices (include phones and cameras) to power/current below  consumption 3W/3A.

      How can I get rid of these alerts ?

       

      Attachments

        Activity

          [OBS-4711] PoE alerts reported on Netgear GS728TPS(B) and GS752TPS(B)

          It wasn't easy to figure out how to do this, but I finally managed to disable the sensors.

          Thanks for your time Adam !

          Pierre-Yves Pierre-Yves added a comment - It wasn't easy to figure out how to do this, but I finally managed to disable the sensors. Thanks for your time Adam !

          This is just because sensor thresholds are auto-generated where not provided by the device +/- a certain %age from the initial value.

          You can manually set the thresholds, they should probably just be disabled for these sensors.

          adama Adam Armstrong added a comment - This is just because sensor thresholds are auto-generated where not provided by the device +/- a certain %age from the initial value. You can manually set the thresholds, they should probably just be disabled for these sensors.
          Pierre-Yves Pierre-Yves added a comment - - edited

          I can't go any further than .1.3.6.1.4.1.4526.11.1.1.4.1.1.1.* because * is huge [0..2147483647] as show in MIB fastpathswitching.my , and the snmpwalk command is not fast enough to parse this OID entirely.

          agentEventLogIndex OBJECT-TYPE
                   SYNTAX      Integer32 (0..2147483647)
                   MAX-ACCESS  read-only
                   STATUS      current
                   DESCRIPTION
                               "Unique index of Event log entry."
                   ::= { agentEventLogEntry 1 } 

          Is there a way to exclude this OID so that snmpwalk ends within a reasonable time ?

          SNMP dump and Netgear MIBS are attached to this reply.

          [^gs7xxts_tps-v5.3.0.36-mibs.zip]

          Pierre-Yves Pierre-Yves added a comment - - edited I can't go any further than .1.3.6.1.4.1.4526.11.1.1.4.1.1.1. * because * is huge [0..2147483647]  as show in MIB fastpathswitching.my , and the snmpwalk command is not fast enough to parse this OID entirely. agentEventLogIndex OBJECT-TYPE          SYNTAX      Integer32 ( 0 .. 2147483647 )          MAX-ACCESS  read-only          STATUS      current          DESCRIPTION                       "Unique index of Event log entry."          ::= { agentEventLogEntry 1 } Is there a way to exclude this OID so that snmpwalk ends within a reasonable time ? SNMP dump and Netgear MIBS are attached to this reply. [^gs7xxts_tps-v5.3.0.36-mibs.zip]

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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

            adama Adam Armstrong
            Pierre-Yves Pierre-Yves
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: