l2_vm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
l2_vm [2022/10/20 15:22] – [Level2 cloud running virtual image] emozolyak | l2_vm [2023/10/04 13:29] (current) – [Virtual node peculiarities] emozolyak | ||
---|---|---|---|
Line 2: | Line 2: | ||
====== Level2 cloud running virtual image ====== | ====== Level2 cloud running virtual image ====== | ||
- | In this scenario, your WebHMI image is running on a cloud virtualization platform. To add a virtual node, press the respective button in the Level2 node list: | + | ===== About ===== |
+ | |||
+ | In this scenario, your WebHMI image is running on a cloud virtualization platform. | ||
+ | * connecting the devices to the Level2 IoT with MQTT protocol | ||
+ | * use Level2 VPN and NAT method | ||
+ | |||
+ | ===== Adding virtual cloud node ===== | ||
+ | |||
+ | To add a virtual node, press the respective button in the Level2 node list: | ||
{{ : | {{ : | ||
Line 17: | Line 25: | ||
| {{ : | | {{ : | ||
- | ***Version** - select either the latest version, or some of previous versions. | + | ***Version** - select either the latest version, or some previous versions. |
- | ***TimeZone** - | + | ***TimeZone** - sets the timezone for the virtual node. With this setting the node will log the data with the respective timestamps in UTC, so that you'll get right times for data when viewing node graphs/ |
- | {{ : | + | Then a progress window will come: |
+ | {{ : | ||
- | and | + | and final message: |
- | {{ : | + | {{ : |
Virtual nodes are basically the same as for hw WebHMI or Virtual Box image except for minor details (like VPN + HTTP proxy service control, which are enabled by default for that kind of nodes). Further node configuration is only performed on the Level2. | Virtual nodes are basically the same as for hw WebHMI or Virtual Box image except for minor details (like VPN + HTTP proxy service control, which are enabled by default for that kind of nodes). Further node configuration is only performed on the Level2. | ||
- | <WRAP center round important 60%> | + | ===== Connecting virtual cloud node to your hardware ===== |
- | Please note, that the virtual node will be created with the " | + | |
+ | You can connect your virtual node to real equipment with either ways: | ||
+ | |||
+ | ==== MQTT protocol ==== | ||
+ | Please refer to the [[connect_iot_device_to_l2 | article]] on connecting MQTT devices to Level2 | ||
+ | |||
+ | ==== TCP/IP based protocols using NAT technique==== | ||
+ | |||
+ | In this scenario, you arrange your system like this: | ||
+ | {{ : | ||
+ | |||
+ | Below is the example of NAT settings for Mikrotik router: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | And you also have to enable routing to the L2 node for your router: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Virtual node peculiarities ===== | ||
+ | |||
+ | Please note, that the virtual node will be created with the " | ||
+ | |||
+ | <WRAP center round important 50%> | ||
+ | Please note that licensed cloud image will be **stopped** after account balance becomes zero, then after 2 weeks of stopped state this image **will be deleted**. | ||
</ | </ | ||
l2_vm.txt · Last modified: 2023/10/04 13:29 by emozolyak