forked from networkupstools/nut
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsnmp.txt
50 lines (32 loc) · 1.44 KB
/
snmp.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
Desc: Information about SNMP and Network UPS Tools
File: snmp.txt
Date: 16 March 2003
Auth: Arnaud Quette <[email protected]> or <[email protected]>
This document presents interactions between SNMP and Network UPS Tools.
This work is mostly sponsored by:
MGE UPS SYSTEMS <http://www.mgeups.com/opensource/>
There are two part in NUT for SNMP support:
1) the agent or server side
An SNMP agent provides information for its hardware.
In general, agents are embedded in SNMP card.
This part has to be implemented as a Net-SNMP sub agent, acting
as a NUT middleware (upsd level). Such software make a bridge
between NUT data and SNMP, thus allowing to monitor, through
SNMP, standard point to point UPSs (serial and USB).
This is part of the "UPS Sub-Agent" project with Net-SNMP team.
2) the client side
* Introduction
An SNMP client communicates with an agent to acquire data.
This part, which has to be a NUT driver, is implemented by snmp-ups.
snmp-ups acts as a bridge from SNMP to NUT, thus allowing to monitor
in NUT any SNMP Agent (embedded or on a host).
The new snmp-ups driver now support multiple MIBS (SNMP structures
declaration). For more information on snmp-ups, have a look at its
manpage (man 8 snmp-ups).
* Extending existing mib2nut information
To be written...
* Adding new mib2nut information
To be written...
References:
- NUT SNMP Protocols Library Available at:
http://www.networkupstools.org/ups-protocols.html#_snmp