I think it should be possible, at least was with Eaton metered ePDU's.
Although looking at code, maybe that was only about ePDUs (at least for the
load, a few more devices might give apparent or real power consumption):
$ git grep -E 'outlet\..*\.((real)?power|load)"'
drivers/apc-ats-mib.c: snmp_info_default("outlet.group.%i.realpower", 0,
1, ".1.3.6.1.4.1.318.1.1.8.5.4.5.1.15.%i", NULL, SU_FLAG_NEGINVALID |
SU_OUTLET_GROUP, NULL),
drivers/eaton-pdu-marlin-mib.c: snmp_info_default("outlet.%i.realpower", 0,
1.0,
drivers/eaton-pdu-marlin-mib.c: snmp_info_default("outlet.%i.power", 0, 1.0,
drivers/eaton-pdu-marlin-mib.c: snmp_info_default("outlet.group.%i.load",
0, 1.0,
drivers/eaton-pdu-marlin-mib.c:
snmp_info_default("outlet.group.%i.realpower", 0, 1.0,
drivers/eaton-pdu-marlin-mib.c: snmp_info_default("outlet.group.%i.power",
0, 1.0,
drivers/eaton-pdu-nlogic-mib.c: snmp_info_default("outlet.%i.load", 0, 1,
drivers/eaton-pdu-nlogic-mib.c: snmp_info_default("outlet.%i.power", 0, 1,
drivers/eaton-pdu-nlogic-mib.c: snmp_info_default("outlet.%i.realpower", 0,
1,
drivers/eaton-pdu-revelation-mib.c:
snmp_info_default("outlet.%i.realpower", 0, 1.0, AR_OID_OUTLET_ACTIVEPOWER
".%i", NULL, SU_OUTLET, NULL),
drivers/eaton-pdu-revelation-mib.c:
snmp_info_default("outlet.%i.power", 0, 1.0, AR_OID_OUTLET_APPARENTPOWER
".%i", NULL, SU_OUTLET, NULL),
drivers/emerson-avocent-pdu-mib.c:
snmp_info_default("outlet.%i.realpower", 0, 0.1,
drivers/hpe-pdu-mib.c: snmp_info_default("outlet.%i.realpower", 0, 1.0,
drivers/hpe-pdu-mib.c: snmp_info_default("outlet.%i.power", 0, 1.0,
drivers/hpe-pdu-mib.c: snmp_info_default("outlet.group.%i.load", 0, 1.0,
drivers/hpe-pdu-mib.c: snmp_info_default("outlet.group.%i.realpower", 0,
1.0,
drivers/hpe-pdu-mib.c: snmp_info_default("outlet.group.%i.power", 0, 1.0,
drivers/hpe-pdu3-cis-mib.c: snmp_info_default("outlet.group.%i.load",
0, 1.0,
drivers/hpe-pdu3-cis-mib.c: snmp_info_default("outlet.%i.load", 0, 1,
drivers/hpe-pdu3-cis-mib.c: snmp_info_default("outlet.%i.power", 0, 1,
drivers/hpe-pdu3-cis-mib.c: snmp_info_default("outlet.%i.realpower", 0,
1,
drivers/mge-hid.c: { "outlet.1.power", 0, 0,
"UPS.OutletSystem.Outlet.[2].ApparentPower", NULL, "%.0f", 0, NULL },
drivers/mge-hid.c: { "outlet.1.realpower", 0, 0,
"UPS.OutletSystem.Outlet.[2].ActivePower", NULL, "%.0f", 0, NULL },
drivers/mge-hid.c: { "outlet.2.power", 0, 0,
"UPS.OutletSystem.Outlet.[3].ApparentPower", NULL, "%.0f", 0, NULL },
drivers/mge-hid.c: { "outlet.2.realpower", 0, 0,
"UPS.OutletSystem.Outlet.[3].ActivePower", NULL, "%.0f", 0, NULL },
drivers/mge-hid.c: { "outlet.3.power", 0, 0,
"UPS.OutletSystem.Outlet.[4].ApparentPower", NULL, "%.0f", 0, NULL },
drivers/mge-hid.c: { "outlet.3.realpower", 0, 0,
"UPS.OutletSystem.Outlet.[4].ActivePower", NULL, "%.0f", 0, NULL },
drivers/raritan-pdu-mib.c: snmp_info_default("outlet.%i.realpower", 0,
1.0, ".1.3.6.1.4.1.13742.1.2.2.1.7.%i", NULL, SU_OUTLET, NULL),
drivers/raritan-pdu-mib.c: snmp_info_default("outlet.%i.power", 0,
1.0, ".1.3.6.1.4.1.13742.1.2.2.1.8.%i", NULL, SU_OUTLET, NULL),
drivers/raritan-px2-mib.c: snmp_info_default("outlet.%i.power", 0, 1,
".1.3.6.1.4.1.13742.6.5.4.3.1.4.1.%i.5", "%i", SU_OUTLET | SU_FLAG_OK,
NULL),
drivers/raritan-px2-mib.c: snmp_info_default("outlet.%i.realpower", 0,
1, ".1.3.6.1.4.1.13742.6.5.4.3.1.4.1.%i.6", "%i", SU_OUTLET | SU_FLAG_OK,
NULL),
Hope this helps,
Jim
On Thu, Mar 19, 2026 at 1:17 AM John Klimek via Nut-upsuser <
[email protected]> wrote:
> I'm using an Eaton 9PX2200GRT which has a primary (or main) and two
> individual load segments.
>
> Is it possible to view the real time power consumption of the individual
> load segments? I believe this is available with the Eaton M2/M3 network
> card web interface.
> _______________________________________________
> Nut-upsuser mailing list
> [email protected]
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
