Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • None
    • Default
    • None

    Description

      Hello Team,

      I added my PDUs AVOCENT PM3000 to Observium and they are not seen as PDUs but juste Servers, so we don't have any consumption information about Inlet and Outlet electrical ports.

      Could you add this please ?

      Thank you
       

      Attachments

        1. debug_result_05.02.2024.txt
          130 kB
        2. debug_result_07.02.2024_2.txt
          183 kB
        3. debug_result_07.02.2024.txt
          32 kB
        4. debug_result.txt
          135 kB
        5. image-2024-01-05-12-46-15-249.png
          image-2024-01-05-12-46-15-249.png
          247 kB
        6. image-2024-01-31-10-46-34-252.png
          image-2024-01-31-10-46-34-252.png
          280 kB

        Activity

          [OBS-4713] Add PDU AVOCENT PM3000

          Here the debug result on copy.debug_result.txt
           

          Yolf Yassine ATOUI added a comment - Here the debug result on copy. debug_result.txt  

          do not show me just screenshots.
          you need make discovery debug (as bot written early):

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

          support was added based on your snmpdump, for troubleshooting on device discovery need your debug.

          landy Mike Stupalov added a comment - do not show me just screenshots. you need make discovery debug (as bot written early): ./discovery.php -d -h <device> support was added based on your snmpdump, for troubleshooting on device discovery need your debug.

          Hello Mike,

          Not talking about Stable and Rolling version, I'm under v24.1.13288 (rolling) and have you latest updates on this topic.

          Just saying that the dev is not having on consideration the outlet consumptions as it is possible to do normally throught the MIB.

          Yolf Yassine ATOUI added a comment - Hello Mike, Not talking about Stable and Rolling version, I'm under v24.1.13288 (rolling) and have you latest updates on this topic. Just saying that the dev is not having on consideration the outlet consumptions as it is possible to do normally throught the MIB.

          This changes not in stable branch,you need wait for stable update or switch to trunk temporary:
          https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          landy Mike Stupalov added a comment - This changes not in stable branch,you need wait for stable update or switch to trunk temporary: https://docs.observium.org/updating/#switch-between-rolling-and-stable-trains

          Hello, 
          Thank you for the add but I don't have the graphs of consumption by outlet as it is possible to see on the GUI.
          Could you add this part please ?
          I join the requested snmpdump

           

          Yolf Yassine ATOUI added a comment - Hello,  Thank you for the add but I don't have the graphs of consumption by outlet as it is possible to see on the GUI. Could you add this part please ? I join the requested snmpdump  

          Added in r13246.

          landy Mike Stupalov added a comment - Added in r13246.

          Please make snmpdump as Bot requested (below).

          Or in latest Observium revisions we have script for make snmpdump as:

          /opt/observium/scripts/snmpdump.php -h <device>
          

          landy Mike Stupalov added a comment - Please make snmpdump as Bot requested (below). Or in latest Observium revisions we have script for make snmpdump as: /opt/observium/scripts/snmpdump.php -h <device>

          MIB added

          Yolf Yassine ATOUI added a comment - MIB added

          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

            landy Mike Stupalov
            Yolf Yassine ATOUI
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: