We got a new Eaton 9PX 8K G2 at site, and the UPS agent doesn't read any of the OIDs successfully.
2026-03-17T14:15:27+0000 startup-op: launching acq
2026-03-17T14:15:27+0000 start called for acq
2026-03-17T14:15:27+0000 acq:0 Status is now "starting".
2026-03-17T14:15:27+0000 acq:0 Status is now "running".
2026-03-17T14:15:28+0000 UdpTwistedTransport starting on 34949
2026-03-17T14:15:28+0000 Starting protocol <pysnmp.carrier.twisted.dgram.udp.UdpTwistedTransport object at 0x7f263a21acb0>
2026-03-17T14:15:28+0000 192.168.2.162: noSuchName at 1.3.6.1.2.1.33.1.2.7.0
2026-03-17T14:15:28+0000 192.168.2.162: noSuchName at 1.3.6.1.2.1.33.1.3.3.1.5.1
2026-03-17T14:15:28+0000 192.168.2.162: noSuchName at 1.3.6.1.2.1.33.1.3.3.1.5.1
And all the fields typically displayed in ocs-web show either "No Such Object currently exists at this OID" or "NaN".
We probably need to import new MIBs from the device for support in the agent.
socs version: v0.6.0
We got a new Eaton 9PX 8K G2 at site, and the UPS agent doesn't read any of the OIDs successfully.
And all the fields typically displayed in ocs-web show either "No Such Object currently exists at this OID" or "NaN".
We probably need to import new MIBs from the device for support in the agent.
socs version:
v0.6.0