-
-
Notifications
You must be signed in to change notification settings - Fork 351
Which SNMP options are supported by your build?
For NUT v2.8.0 and later you can query supported MIBs with a special mibs=--list
driver option. Note that generally the driver requires other options to basically start and pass sanity checks, so you may have to dummy them out (e.g. in a build workspace without a real NUT deployment). Also note that some mappings have several aliases, to be detected at different OIDs used by the respective vendor over time and across the model line-up.
Example output:
:; NUT_STATEPATH=/tmp snmp-ups -x mibs=--list -s test -x port=x
Network UPS Tools - Generic SNMP UPS driver 1.30 (2.8.0-2245-g9476ed20c)
The 'mibs' argument is '--list', so just listing the mappings this driver knows,
and for 'mibs=auto' these mappings will be tried in the following order until
the first one matches your device
NUMBER MAPPING NAME VERSION ENTRY POINT OID AUTO CHECK OID
1 apc_ats 0.6 .1.3.6.1.4.1.318.1.3.11 .1.3.6.1.4.1.318.1.1.8.1.5.0
2 apc_pdu 0.4 .1.3.6.1.4.1.318.1.3.4.4 .1.3.6.1.4.1.318.1.1.4.1.4.0
3 apc_pdu 0.4 .1.3.6.1.4.1.318.1.3.4.5 .1.3.6.1.4.1.318.1.1.4.1.4.0
4 apc_pdu 0.4 .1.3.6.1.4.1.318.1.3.4.6 .1.3.6.1.4.1.318.1.1.4.1.4.0
5 apc 0.1 .1.3.6.1.4.1.318.1.3.4.9 <NULL>
6 apcc 1.6 .1.3.6.1.4.1.318.1.1.1.1.1.1.0 .1.3.6.1.4.1.318.1.1.1.1.1.1.0
7 baytech 0.4035 .1.3.6.1.4.1.4779 .1.3.6.1.4.1.4779.1.3.5.2.1.24.1
8 bestpower 0.4 .1.3.6.1.4.1.2947.1.1.2.0 .1.3.6.1.4.1.2947.1.1.2.0
9 cpqpower 1.66 .1.3.6.1.4.1.232.165.3 .1.3.6.1.4.1.232.165.3.1.1.0
10 cyberpower 0.53 .1.3.6.1.4.1.3808.1.1.1 .1.3.6.1.4.1.3808.1.1.1.1.1.1.0
11 cyberpower 0.53 .1.3.6.1.4.1.3808 .1.3.6.1.4.1.3808.1.1.1.1.1.1.0
12 delta_ups 0.5 .1.3.6.1.4.1.2254.2.4 <NULL>
13 eaton_ats16_nmc 0.21 .1.3.6.1.4.1.705.1 .1.3.6.1.4.1.534.10.2.1.2.0
14 eaton_ats16_nm2 0.22 .1.3.6.1.4.1.534.10.2 .1.3.6.1.4.1.534.10.2.1.2.0
15 eaton_ats30 0.03 .1.3.6.1.4.1.534.10.1 .1.3.6.1.4.1.534.10.1.2.1.0
16 eaton_epdu 0.69 .1.3.6.1.4.1.534.6.6.7 .1.3.6.1.4.1.534.6.6.7.1.2.1.2.0
17 eaton_pdu_nlogic 0.1 .1.3.6.1.4.1.534.7.1 <NULL>
18 eaton_pxg_ups 0.105 .1.3.6.1.4.1.534.2.12 1.3.6.1.4.1.534.1.1.2.0
19 eaton_pw_nm2 0.105 .1.3.6.1.4.1.534.1 1.3.6.1.4.1.534.1.1.2.0
20 emerson_avocent_pdu 1.3 .1.3.6.1.4.1.10418.17.1.7 .1.3.6.1.4.1.10418.17.2.1.2.0
21 aphel_revelation 0.52 .1.3.6.1.4.1.534.6.6.6 .1.3.6.1.4.1.534.6.6.6.1.1.12.0
22 aphel_genesisII 0.52 .1.3.6.1.4.1.17373 .1.3.6.1.4.1.17373.3.1.1.0
23 pulizzi_switched1 0.5 .1.3.6.1.4.1.20677.1 .1.3.6.1.4.1.20677.1
24 pulizzi_switched2 0.5 .1.3.6.1.4.1.20677.2 .1.3.6.1.4.1.20677.1
25 hpe_epdu 0.33 .1.3.6.1.4.1.232.165.7 .1.3.6.1.4.1.232.165.7.1.2.1.3.0
26 hpe_pdu3_cis 0.1 .1.3.6.1.4.1.232.165.11 .1.3.6.1.4.1.232.165.11.1.2.1.3.1
27 huawei 0.4 .1.3.6.1.4.1.8072.3.2.10 .1.3.6.1.4.1.2011.6.174.1.2.100.1.2.1
28 mge 0.55 .1.3.6.1.4.1.705.1 .1.3.6.1.4.1.705.1.1.1.0
29 netvision 0.44 .1.3.6.1.4.1.4555.1.1.1 .1.3.6.1.4.1.4555.1.1.1.1.1.1.0
30 raritan 0.8 .1.3.6.1.4.1.13742 .1.3.6.1.4.1.13742.1.1.12.0
31 raritan-px2 0.4 .1.3.6.1.4.1.13742.6 .1.3.6.1.4.1.13742.6.3.2.1.1.3.1
32 xppc 0.4 .1.3.6.1.4.1.935 <NULL>
33 tripplite 1.55 .1.3.6.1.4.1.850.1 <NULL>
34 ietf 1.55 .1.3.6.1.2.1.33 1.3.6.1.2.1.33.1.1.1.0
Overall this driver has loaded 34 MIB-to-NUT mapping tables
Various authentication and encoding options are available generally in the NUT codebase, but may be constrained practically by the net-snmp
or ucd-snmp
library used during the build. The codepaths not supported by the backend library are not built, and in particular not reflected in the common help text for supported options and/or their values.
For example, compare this output:
:; snmp-ups -h
...
Set the securityLevel used for SNMPv3 messages (default=noAuthNoPriv, allowed: authNoPriv,authPriv) : -x secLevel=<value>
Set the securityName used for authenticated SNMPv3 messages (no default) : -x secName
Set the authentication pass phrase used for authenticated SNMPv3 messages (no default) : -x authPassword
Set the privacy pass phrase used for encrypted SNMPv3 messages (no default) : -x privPassword
Set the authentication protocol (MD5, SHA, SHA256, SHA384, SHA512) used for authenticated SNMPv3 messages (default=MD5 if available) : -x authProtocol=<value>
Set the privacy protocol (DES, AES) used for encrypted SNMPv3 messages (default=DES if available) : -x privProtocol=<value>
...
...to this on another platform:
...
Set the authentication protocol (MD5, SHA, SHA256, SHA384, SHA512) used for authenticated SNMPv3 messages (default=MD5 if available) : -x authProtocol=<value>
Set the privacy protocol (DES, AES, AES192, AES256) used for encrypted SNMPv3 messages (default=DES if available) : -x privProtocol=<value>
...
Welcome to the Network UPS Tools (NUT) project Wiki, and feel free to contribute tricks and insights.
While there are several good entries in the menu, ones referenced most frequently in issue discussions include:
- Building NUT for in-place upgrades or non-disruptive tests and Using NIT (NUT Integration Test suite) sandbox
- Technicalities: Customizing (NUT) config files and scripts delivered by packaging
- Links to distribution packaging recipes and repository sections
- Troubleshooting
upsdrvctl
drivers not starting ("insufficient permissions on everything" or "Can't claim USB device [VVVV:PPPP]@0/0: Entity not found") possibly due to nut-driver-enumerator (NDE) services having been there before you with NUT 2.8.x - Changing NUT daemon debug verbosity
- Building NUT integration for Home Assistant
- Running NUT in an LXC container
- Troubleshooting eventual disconnections (Data stale) and CyberPower Systems (CPS) know-how
- NUT for Windows
- NUT HCL and DDL
- Code contributions, PRs, PGP and DCO
- NUT CI farm
Also keep in mind the documentation links from NUT website and the FAQ in particular.