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

ATEN PDUs with per-outlet metering

Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery

    Description

      Hi

      The ATEN-PE-CFG MIB already exists but for some reason the device is categorised as "Allied Telesis" and gets the Allied logo instead of the ATEN one

      Also, our model (PE8108G) has per-outlet metering and it would be good to get those sensors detected. The MIB distributed by Observium has these sensors described, I will attach a walk to this shortly.

      Attachments

        1. aten-discovery-debug.txt
          8 kB
          Phillip Baker
        2. aten-display.png
          34 kB
          Phillip Baker
        3. aten-overview.png
          25 kB
          Phillip Baker

        Activity

          [OBS-3468] ATEN PDUs with per-outlet metering
          philb Phillip Baker added a comment - - edited

          At some point in May 2022 the individual outlet entities appeared.

          This case should probably be closed as resolved.

          philb Phillip Baker added a comment - - edited At some point in May 2022 the individual outlet entities appeared. This case should probably be closed as resolved.
          philb Phillip Baker added a comment -

          Yup, now showing as ATEN with correct logo. Thanks!

          I dunno if this is something you are interested in suppressing/patching from observium but there isn't anywhere to actually configure sysContact on this device - what shows when you query that OID is in fact the "PDU Name". sysName, which you might expect to contain "PDU Name" instead appears to always be the manufacturer name "aten".

          Anyway: all I really care about now are the outlets when you have the time and motivation, thanks

          philb Phillip Baker added a comment - Yup, now showing as ATEN with correct logo. Thanks! I dunno if this is something you are interested in suppressing/patching from observium but there isn't anywhere to actually configure sysContact on this device - what shows when you query that OID is in fact the "PDU Name". sysName, which you might expect to contain "PDU Name" instead appears to always be the manufacturer name "aten". Anyway: all I really care about now are the outlets when you have the time and motivation, thanks
          landy Mike Stupalov added a comment -

          This is incorrect Vendor detection, fixed in r10698.

          landy Mike Stupalov added a comment - This is incorrect Vendor detection, fixed in r10698.
          philb Phillip Baker added a comment -

          It's not a one-off, either:

          philb Phillip Baker added a comment - It's not a one-off, either:
          philb Phillip Baker added a comment -

          Done, it does seem to think it's Aten, but attached screengrab of what it looks like in Observium.

          I might be imagining this but I am sure while they originally appeared as Allied, I thought they changed to Aten a while ago but if they did do that they have gone back to Allied again....

          philb Phillip Baker added a comment - Done, it does seem to think it's Aten, but attached screengrab of what it looks like in Observium. I might be imagining this but I am sure while they originally appeared as Allied, I thought they changed to Aten a while ago but if they did do that they have gone back to Allied again....
          landy Mike Stupalov added a comment -

          Hrm, I'm not see reasons for incorrectly detect this device (should be detected as Aten).
          Please attach discovery debug for it:

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

          landy Mike Stupalov added a comment - Hrm, I'm not see reasons for incorrectly detect this device (should be detected as Aten). Please attach discovery debug for it: ./discovery.php -d -m os -h <device>

          People

            landy Mike Stupalov
            philb Phillip Baker
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: