You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: examples/standalone/snmp-eaton-ups/README.md
+58-39Lines changed: 58 additions & 39 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,43 +1,59 @@
1
-
# Eaton UPS Standalone UCM (SNMP)
1
+
# Eaton UPS Standalone Device (SNMP)
2
2
3
-
This example describes the implementation of the [Standalone UCM](https://handbook.enapter.com/software/virtual_ucm/) concept using the opensource [Enapter python-sdk](https://github.com/Enapter/python-sdk) for monitoring Eaton UPS using SNMP protocol.
3
+
This example describes the implementation of the Standalone Device concept
4
+
using the opensource [Enapter
5
+
python-sdk](https://github.com/Enapter/python-sdk) for monitoring Eaton UPS
6
+
using SNMP protocol.
4
7
5
-
In order to use this UCM you need to enable SNMPv1 protocol in the Web Interface of your UPS and set unique community name for the read only access. The default port for SNMP is 161 but also can be changed.
8
+
In order to use this standalone device you need to enable SNMPv1 protocol in
9
+
the Web Interface of your UPS and set unique community name for the read only
10
+
access. The default port for SNMP is 161 but also can be changed.
6
11
7
-
As an example in this guide we will use the following dummy settings for configuration:
12
+
As an example in this guide we will use the following dummy settings for
13
+
configuration:
8
14
9
-
UPS IP Address: 192.168.192.192
10
-
11
-
Community Name: public
12
-
13
-
SNMP Port: 161
15
+
- UPS IP Address: 192.168.192.192
16
+
- Community Name: public
17
+
- SNMP Port: 161
14
18
15
19
## Requirements
16
20
17
-
It is recommended to run this UCM using Docker and Docker Compose. This will ensure that environment is correct.
21
+
It is recommended to run this standalone device using Docker and Docker
22
+
Compose. This will ensure that environment is correct.
18
23
19
-
The UPS must be reachable from the computer where the Docker Container will be running. You can check availability and settings with `snmpget` command on Linux or Mac:
24
+
The UPS must be reachable from the computer where the Docker Container will be
25
+
running. You can check availability and settings with `snmpget` command on
26
+
Linux or Mac:
20
27
21
28
```bash
22
29
user@pc snmp-eaton-ups % snmpget -v1 -c public 192.168.192.192:161 1.3.6.1.2.1.33.1.1.1.0
23
30
SNMPv2-SMI::mib-2.33.1.1.1.0 = STRING: "EATON"
24
31
```
25
32
26
-
## Step 1. Create Standalone UCM in Enapter Cloud
27
-
28
-
Log in to the Enapter Cloud, navigate to the Site where you want to create Standalone UCM and click on `Add new` button in the Standalone Device section.
33
+
## Step 1. Create Standalone Device in Enapter Cloud
29
34
30
-
After creating Standalone UCM, you need to Generate and save Configuration string also known as ENAPTER_VUCM_BLOB as well as save UCM ID which will be needed for the next step
35
+
Log in to the Enapter Cloud, navigate to the Site where you want to create a
36
+
Standalone Device and click on `Add new` button in the Standalone Device
37
+
section.
31
38
32
-
More information you can find on [this page](https://developers.enapter.com/docs/tutorial/software-ucms/standalone).
39
+
After creating Standalone Device, you need to Generate and save Configuration
40
+
string also known as `ENAPTER_STANDALONE_COMMUNICATION_CONFIG` as well as save
41
+
UCM ID which will be needed for the next step.
33
42
34
43
## Step 2. Upload Blueprint into the Cloud
35
44
36
-
The general case [Enapter Blueprint](https://marketplace.enapter.com/about) consists of two files - declaration in YAML format (manifest.yaml) and logic written in Lua. Howerver for this case the logic is written in Python as Lua implementation doesn't have SNMP integration.
45
+
The general case [Enapter Blueprint](https://marketplace.enapter.com/about)
46
+
consists of two files - declaration in YAML format (manifest.yaml) and logic
47
+
written in Lua. Howerver for this case the logic is written in Python as Lua
48
+
implementation doesn't have SNMP integration.
37
49
38
-
But for both cases we need to tell Enapter Cloud which telemetry we are going to send and store and how to name it.
50
+
But for both cases we need to tell Enapter Cloud which telemetry we are going
51
+
to send and store and how to name it.
39
52
40
-
The easiest way to do that - using [Enapter CLI](https://github.com/Enapter/enapter-cli) to upload manifest.yaml into Cloud. The other option is to use [Web IDE](https://developers.enapter.com/docs/tutorial/uploading-blueprint).
53
+
The easiest way to do that - using [Enapter
54
+
CLI](https://github.com/Enapter/enapter-cli) to upload manifest.yaml into
0 commit comments