Seneca Cloud BOX User Manual

Page 1

MI003790

MI004560_100-EN

SENECA s.r.l.

Via Austria, 26 – 35127 –PADOVA – ITALY
Tel. [phone] Fax. [phone]
Web site: www.seneca.it
Technical assistance: [e-mail] (IT), [e-mail] (Other)
Commercial reference: [e-mail] (IT), [e-mail] (Other)

This document is property of SENECA srl. Duplication and reproduction are forbidden, if not authorized. Contents of the present

documentation refers to products and technologies described in it. All technical data contained in the document may be modified
without prior notice Content of this documentation is subject to periodical revision.

To use the product safely and effectively, read carefully the following instructions before use. The product must be used only for the use

for which it was designed and built. Any other use must be considered with full responsibility of the user. The installation,
implementation and set-up is allowed only for authorized operators; these ones must be people physically and intellectually suitable.
Set up must be performed only after a correct installation and the user must perform every operation described in the installation
manual carefully. Seneca is not considered liable of failure, breakdown, accident caused for ignorance or failure to apply the indicated
requirements. Seneca is not considered liable of any unauthorized changes. Seneca reserves the right to modify the device, for any
commercial or construction requirements, without the obligation to promptly update the reference manuals.

No liability for the contents of this documents can be accepted. Use the concepts, examples and other content at your own risk. There
may be errors and inaccuracies in this document, that may of course be damaging to your system. Proceed with caution, and although
this is highly unlikely, the author(s) do not take any responsibility for that. Technical features subject to change without notice.

USER MANUAL

Cloud BOX

Remote Connector

and

micro WebSCADA

USER MANUAL – Cloud BOX

2

Date

Revision

Notes

06/10/2016

01

First revision.

USER MANUAL – Cloud BOX

3

Table of contents

1. SOFTWARE OPEN SOURCE ...................................................................................... 6

2. INTRODUCTION ........................................................................................................... 6

2.1. Compatible Devices ........................................................................................................................................ 6

2.2. Hardware specifications ................................................................................................................................. 7

3. CLOUD BOX INSTALLATION...................................................................................... 7

4. CONFIGURATION ........................................................................................................ 8

4.1. Default Network Address ............................................................................................................................... 8

4.2. Access to the administration section .............................................................................................................. 8

5. CLOUDBOX ADMINISTRATION SECTION ................................................................. 9

5.1. Configuration ................................................................................................................................................. 9

5.2. Users .............................................................................................................................................................13

5.3. Groups ..........................................................................................................................................................14

5.4. Logs ...............................................................................................................................................................14

5.5. Devices ..........................................................................................................................................................14

5.6. Statistics .......................................................................................................................................................19

6. EDIT PROJECT .......................................................................................................... 20

6.1. Edit Page .......................................................................................................................................................20

6.2. "Dashboard with widgets” page ....................................................................................................................22

6.3. "Events" page ...............................................................................................................................................23

6.4. "CSV Export" page .........................................................................................................................................25

6.5. "Trace Map" page, Log Trace on Map ...........................................................................................................25

7. STORAGE OF DATA AND PERFORMANCE ............................................................ 25

8. ROUTER CONFIGURATION ...................................................................................... 26

USER MANUAL – Cloud BOX

4

9. DATA COLLECTION (COLLECTOR) ........................................................................ 26

10. CLOUD BOX MAINTENANCE ................................................................................ 28

10.1. Resetting the Cloud BOX hardware ...............................................................................................................28

10.2. Firmware upgrade .........................................................................................................................................35

10.3. Backup ..........................................................................................................................................................35

10.4. Restore .........................................................................................................................................................36

10.5. Use of an external disk ..................................................................................................................................36

11. ADVANCED CUSTOMIZATION .............................................................................. 36

USER MANUAL – Cloud BOX

5

Seneca Cloud BOX

CAUTION!

UNDER ANY CIRCUMSTANCES, SENECA S.R.L. OR ITS SUPPLIERS SHALL NOT BE RESPONSIBLE FOR
LOSS OF RECORDING DATA/INCOMES OR FOR CONSEQUENTIAL OR INCIDENTAL DAMAGE DUE
TO NEGLECT OR RECKLESS MISHANDLING OF Cloud BOX, EVEN THOUGH SENECA IS WELL AWARE
OF THESE POSSIBLE DAMAGES.

SENECA, ITS SUBSIDIARIES, AFFILIATES, COMPANIES OF THE GROUP, ITS SUPPLIERS AND
RETAILERS SHALL NOT GUARANTEE THAT THE FUNCTIONS WILL SATISFY COMPLETELY
CUSTOMER’S EXPECTATIONS OR THAT Cloud BOX, THE FIRMWARE AND THE SOFTWARE SHALL
HAVE NO ERRORS OR WORK CONTINUOUSLY.

USER MANUAL – Cloud BOX

6

1. Software Open Source

The Cloud Box software and firmware contain open source software. You can get the source code of such
software by requesting them via email to [e-mail].

2. Introduction

Cloud BOX is a server that allows you to:

 Receive, store on a database and display the RTU events and data
 View real-time and historical data on web pages in graphic mode
 View the realtime and historical events / alarms on web pages in graphic mode
 Send commands to the RTU even if these do not have a static IP

2.1. Compatible Devices

Compatible devices are:

Device

Z-GPRS3

MyAlarm2

Z-KEY

Z-LOGGER3

Z-UMTS

USER MANUAL – Cloud BOX

7

2.2. Hardware specifications

Device Type

Industrial Server

Motherboard Form Factor

Mini-ITX

Cooling

Passive (fanless)

Frontal I/O

2 x USB 2.0

Back I/O

2 USB 2.0 high current
2 USB 2.0
1 VGA
1 HDMI
1 Gb LAN
1 Jack DC (8 V to 19 V)

Processor

Intel Atom N2800

Processor Speed

1.86 GHz

Socket

Onboard (BGA)

Core Number

2

Chipset

Intel NM10

Memory

DDR3 SO-DIMM (non-ECC)

Memory Type

2 GB (minimum)

LAN Controller

Intel 82579L GbE

Supply voltage (AC Adapter)

8~19 V

AC Adapter Socket

Jack DC Onboard

Operating temperature

0°C ~ 40°C

Dimensions (WxHxD)

185.14 x 32 x 205 mm

Certifications

CE, FCC, RoHS

Storage

32 GB SSD Drive

3. Cloud BOX Installation

USER MANUAL – Cloud BOX

8

To install Cloud BOX proceed as follows:

Place the server horizontally, resting it on a flat surface or with the brackets that make it attachable to a wall
(supplied in the package).

Connect the power supply (on the round plug of the back) and the network cable. The device has no keyboard
or mouse, these are only necessary in case of maintenance and can therefore be left unconnected.

Boot the device with the front power button, no further settings are needed to the device.

CAUTION: CloudBox is a server device, so it is necessary that the switch off it’s make in a correct way, without
lifting the power when the server is turned on. It’s recommended, therefore, to connect an electrical device
such as a UPS rescue to prevent surges and / or power blackout.

Shutdown it’s make through the front button that must be pressed once briefly, the long press of the button
makes the immediate shutdown without possibility, for the operating system, to shut down their processes
and could make CloudBox unusable.

4. Configuration

4.1. Default Network Address

The Cloud Box is configured by default with the network settings obtained by DHCP, then, when connected
to a network Cloud Box will try to autonomatically acquire an IP address from the DHCP Server (very often
the Router).

If this operation is not successful, the following network parameters are set:

IP Address 192.168.90.101

subnet-mask 255.255.255.0

gateway 192.168.90.1

4.2. Access to the administration section

The first IP address acquired is viewable through Seneca Device Discovery software (available in the
CloudBox section at www.seneca.it).

You can then access the administration section via a PC with a browser using the following credentials:

USER MANUAL – Cloud BOX

9

Name

Parameter

USERNAME

[e-mail]

PASSWORD

seneca

URL

https://<<INDIRIZZO>>/admin/

5. CloudBox Administration Section

The administration section presents a navigation menu of this kind::

5.1. Configuration

For the first configuration, you must go to the "Configuration" section:

USER MANUAL – Cloud BOX

10

The first tab is for the network configuration parameters: classic IP address, netmask, gateway and DNS.

The "Service" tab, allows you to configure:

HTTP Port: The communication port that the device can be used for not encrypted communication, the
default is 80.

HTTPS Port: The communication port protected by SSL certificate (self-signed), the default is 443.

Log rotation time is the number of days after which the data logs are deleted; attention to the fact that the

logs instead of system (not visible from the panel) does not come influenced by this parameter.

Device Authentication Key: This parameter is the authentication key that they will use the device to send
data. It can be generated by the system or manually written. Pay attention to the value that you set because,
being in fact a password, you must choose it with a safety criteria. The surest way is to randomly generate it
with the appropriate button.

Allow device registration: if checked, the system allows new devices to self-register, or they will be discarded
instead.

USER MANUAL – Cloud BOX

11

The third section covers all configuration and data backup parameters.

backup device: the system automatically identifies a local device (the main disk) and any connected USB
devices. If you press "Mount to" the system will hook them to the filesystem making them available; on the
contrary if you press "Unmounting all" the device will be dropped. From a drop down you can select on which
device you want to make the backup and then the restore.

Backup schedule: here you can set the system to automatically start a backup at the expiration of a certain
time (0-23) and, in certain days of the week.

Beware that this operation can be heavy for the server (depending on the data present in the system). This
operation, if the server is running, it will block other batch like the csv exports until the completion.

The FTP section contains the configuration parameters of two accesses that allow the following functions:

USER MANUAL – Cloud BOX

12

Updates: is a simple ftp access that you need to update devices remotely. RTU devices such as Z-GPRS3 may,
in fact, update the firmware or a SEAL program from an FTP server.

System account: With this access you have visibility of the root of all FTP folders (including access updates).
Here you can load a remotely restore or upgrade an application for Cloud BOX (this if you use the local disk,
see section Backup and Restore for more information). In addition there is a custom folder where you can
upload a custom logo (named logo.png or logo.jpg, in lower case). This logo will be applied to both the login
to the dashboard (replacing the title in text format). It’s also possible to upload a file custom.css with which
modify the dashboard style, see the personalization chapter for more info.

The general section, however, allows you to modify the operating parameters not strictly connected to the
system:

Station title: this parameter is the name of the station, useful if you have more than one Cloud Box.

Language: the default language to be assigned to each user

Use CDN: This flag enables the use of an external Content Delivery Network, allowing the browser to

download the libraries from internet without using the CloudBox bandwidth

Google map key: for tracking functions and GPS maps display was based on Google Maps technology.

For use this feature you must register and get a key that gives you access to a number of views (under the
contract). This parameter is required if you want to benefit from the maps, you can also get more information
about the terms of use of the maps in the link next to the key.

USER MANUAL – Cloud BOX

13

When you go to save the Cloud BOX recognize whether they were or not modified system parameters that
require a reboot. In this case the machine will restart within 30 seconds; This behavior is also possible in the
absence of changes by checking the option at the bottom of the page. The restart is possible only if there

are no pending batch, in this case the system will wait until the processing is complete to avoid failure or
data loss.

5.2. Users

Cloud Box provides a user management panel (Users link on the left); each user can be freely configured with
these parameters:

Active: Indicates whether the user is on or off.

Name: is the user name, an abbreviation that allows only letters and numbers.

Email is the email address linked to the user, will be used for the login.

Password: This is the credential that you will use with the email or name to access the resources allocated.

There are no limits or specific constraints, it is recommended to follow the basic safety rules.

Time Zone is the time zone where the user is located and is a fundamental parameter. When you view the
times, in fact, the system will adjust the displayed time taking account of this time zone and not that of the
server or device.

Role: User roles can be of three types, the first is the administrative which allows you to have access to the
Administration section. The user role is only used to access the dashboard. It’s also possible to configure if
the user can or not edit the dashboard.

Group: it’s the group of users that belongs to this credential access, for more details see the group
management.

Language: is the language that will be set as the default for this user.

USER MANUAL – Cloud BOX

14

5.3. Groups

When you create pages for displaying the data (dashboard) you want to restrict their access.

To provide this functionality, there are user groups.

A group may contain one or more users, and each page can be connected to a group.

The administrator automatically is inside all groups so, therefore, he can access to all pages.

For example you have 3 users and an administrator.

You want that user1 can only access the dashboard 1 and 2, while user2 and 3 can only access the dashboard
3 and 4.

You will have a scheme like:

5.4. Logs

The screen shows in a descending time order the Cloud Box application logs, here we show the notifications,
and errors. Each line can contain a navigable detail through its right button. This log can be manually cleared
or will be cleared automatically as configured.

Warning! Cloud BOX is a server machine, so the log section must be monitored to become aware of any
problems.

5.5. Devices

The programmed devices must point to the Cloud BOX using a device credential making using this type of
URL:

HTTP://<<IP ADDRESS>>/collector/1/<<KEY>>

OR (if availbale):

USER MANUAL – Cloud BOX

15

HTTPS://<<IP ADDRESS>>/collector/1/<<KEY>>

On Seal this url must be inserted in the Cloud section:

Once configured and started the device will make a first send that will provide data on the beginning of the
Cloud BOX datalogging session. This recording operation is automatic, but linked to the flag of the new
registrations (as seen in the basic configuration paragraph);

this flag can be changed on the fly from this screen with the right button. The device management shows in
tabular form all devices registered successfully.

A registered device is stored with a generic name linked to its own unique identifier, for example devices
such as Z-GPRS3 will arise with the modem IMEI. Of each device you can change the configuration in the
device tab.

USER MANUAL – Cloud BOX

16

The first tab manages the description, here you can see the time stamp of the last time the Cloud BOX
recorded data from this device.

The device name is set automatically, then you can customize it. You must then go to assign the device model
that is sending data, this parameter is very important because the editor will put or not a set of commands
that the device can execute.

The timezone, like for the user, specify the time zone of the device.

When the device is programmed from scratch a new session is initiated, these parameters are then sent
along with the new sampling time and are recorded by Cloud BOX. For convenience, on the left, are shown
the last log line and the last recorded event.

USER MANUAL – Cloud BOX

17

The tag data is the configuration of the variables sent from the device to Cloud BOX. Initially, this table is
empty or can vary due to a reprogramming.

Pressing the "import from data" button the system analyzes the last log line and, based on this, the tags are
populated.

This tag set is always updated in additive way, this to preserve the integrity of the data. One thing to watch
out is that a tag that changes the data type from integer to floating point does not lose the previous, but any
widgets will be updated in floating point mode.

The tab of each tag can be changed by writing a variable name and a data type to be set in accordance with
this project in the device. The data types are general and are needed from the editor in order to enable a
better choice based on the type. Internally, however, the data is always stored as a 64-bit float.

Name

Type

Integer

Integer with or without sign

Boolean

True / False

USER MANUAL – Cloud BOX

18

Floating Point

It’s a floating point type

Latitude

GPS Latitude

Longitude

GPS Longitude

The aggregate function is essential for the representation of historical graphs (trend).

When you want to view long periods of time on a graph you run into the problem that the number of points
is huge.

To overcome this drawback, is used the operation of decimation (downsampling). The system automatically
understands what is the minimum resolution displayed on the selected time window.

If we want to see a full week of a device sampling once a minute we will have 1440 samples for 7 days (10080
samples).

To allow a view not too dense (and therefore difficult to read) are imposed for example up to 300 samples;
it follows that we will have to group data in the sections of about 34 minutes. By grouping the data for this
resolution there is the need to choose how to represent with a single sample this group of samples.

It’s therefore necessary to take these groups of samples (groups of 34 samples) and translate them into one
sample to represent all of them.

If it were an analog value as a temperature, the aggregate function could be for example an average.

Case studies can be very different as the needs. For this it is possible, in addition to the data type, also
describe the function that aggregates them when necessary. These functions are coded as follows:

USER MANUAL – Cloud BOX

19

Function

Description

Count

Number of samples in the time interval

Min

Minimum value in the time interval

Max

Maximum value in the time interval

Mean

Average value in the time interval

Sum

The Sum of values in the time interval

Stddev

Standard Deviation in the time interval

First

First value in the time interval

Last

Last value in the time interval

In the last tab, logs, are a subset of the general log, here are visible only the rows of logs related to the specific
device.

5.6. Statistics

This screen provides an overview of the server status, offers a number of indexes to be monitored. The upper
part is made up of several panels that show static data such as network and firmware version of Cloud BOX.

Other indicators provide for example the load of the machine RAM and hard always represent the
consumption of server resources; If the RAM gets too close to the upper limit it is likely that the server can
freeze or slow down dramatically. The disc is critical if approaches to filling, in this case it is likely to have
inconsistent data in the system and subsequently the block of all applications.

USER MANUAL – Cloud BOX

20

6. Edit Project

The project configuration can only be modified by users with authority to modify the pages:

The dashboard has been tested using the following browsers

Chrome 50 or later for

Windows, Android, Ios, OSx

Each project may contain several pages of different types. The different types of pages do not require
configuration of the contents, have specific uses and do not required further parameters in addition to the
basic parameters.

Click to create, remove and move the pages:

6.1. Edit Page

Click Edit to change the page parameters:

USER MANUAL – Cloud BOX

21

The parameters of the page are first of all the title that appears in the link and as label in the page itself. The
refresh time is only useful for dashboard with widgets type pages (grid) where it is possible to include
components that display data in real time. Here, it is possible to set the refresh time for the data displayed.
This parameter applies to the whole page, and the widgets will therefore all be updated based on this
parameter.

Type indicates the type of page to create. Pages can be of the following types:

Dashboard with widgets

Events page

CSV export page

Trace map page

The tick at the end indicates that the page is the home page for the previously specified group. It is important
to remember that it is possible to have several home pages for different groups. This is because during the
login process, the system checks what group the user belongs to and directs him/her to the correct page.

Once configured, the page is empty and ready to be populated with widgets

USER MANUAL – Cloud BOX

22

6.2. "Dashboard with widgets” page

Only authorised users may add and edit widgets:

By clicking Edit, it is possible to add widgets, selecting them among those available.

Click to add a Widget

Click to change the page grid

Click to save the changes to the page

Click to cancel the changes to the page

Once a widget had been added to the grid, it can be moved by clicking and dragging it to the desired
position:

USER MANUAL – Cloud BOX

23

From the left to the right container:

Each widget has its own configuration, which can be accessed using the icon

Each widget must be aware of the variable it is associated to, and where to recover it from.

6.3. "Events" page

The events page consists of a filter and a table display of events/alarms received from the RTUs.

In SeAL, these events correspond to MSG (message) type blocks:

USER MANUAL – Cloud BOX

24

Also the execution of commands appears in this page.

Data, type and content filters can be applied. The date filter can be set as absolute, meaning that precise
dates are selected. As an alternative, the relative real time filter can also be selected, in which case the end
date will be the current date, going back for a selected time period.

USER MANUAL – Cloud BOX

25

6.4. "CSV Export" page

This page can be used to export the data of a device in csv format, so that they may be edited using and
external software (e.g. excel).

It includes a device and a time filter, through which a group of data can be selected. It is possible to calculate
in advance the amount of data that will be selected with the set filter. This gives an idea of the final size. This
operation is extremely important, as it gives the idea of how much time will be needed for the export
procedure, and the required CPU for supplying the required data. This operation is completed in batch mode.
This means that the request is included in a queue of tasks to complete in the system that will carry out the
operation and return the data at a later stage. It is possible to queue several requests. These will be
completed one at the time, and can be cancelled. As they are not of fundamental importance for the
operation of the server, export batch tasks may be paused if the CPU load exceeds the alarm levels. Backup
tasks have priority over batch tasks.

6.5. "Trace Map" page, Log Trace on Map

This particular page offers to the user a full page map, and a time filter like for the events page. By selecting
the device, it is possible to follow the path completed.

7. Storage of data and performance

The important parameters to consider when talking about the capabilities of the server are the number of
devices, the sample time, the number of tags, and the time during which they must be maintained. The server
resources to monitor are CPU, disk space and ram.

Parameter

Resources

Description

Number of devices

CPU, DISK

It affects how many requests are made every minute to the
server (CPU), and how much disk space will be required.

Sample time

CPU, DISK

The more sending operations and the more requests are
made to the server, the more samples and disk space are
required.

Number of Tags

CPU, DISK

It has a strong effect on disk space; less during data
processing.

Holding time

DISK, RAM

The main factor is disk space; performance levels decrease
with the increase of data, as it becomes more demanding to
carry out researches, and therefore display the data on the
dashboard.

USER MANUAL – Cloud BOX

26

SUMMATION (SAMPLE TIME) / (60 * 24)

This is the calculation required for the number of daily records where the sample time is expressed in
seconds. The calculation provides the daily records received from the RTUs. This is a neutral parameter in
relation to the number of Tags, as the time series database creates a unique data table, in which the columns
consist of all the Tags collected from each device.

8. Router Configuration

When connecting Cloud BOX to a Router, for example an ADSL router, to make it visible through the internet
it will be necessary to open some ports and set them to the Cloud BOX internal IP address.

Port

Description

Compulsory

HTTP

Needed for devices that do not support SSL. Default is 80, but it can be
changed.

Yes

HTTPS

Needed for administration purposes. Default is 443, but it can be changed.

Yes

SSH

Port 22 is only necessary if access from Seneca support is required.

No

FTP

Port 21 is required for access to the devices, for downloading firmware, or
a new program.

No

The server must also be able to communicate with the outside in order to synchronize with the clock. Check
that this is possible and that the time is correct, otherwise malfunctioning might occur.

9. Data collection (Collector)

This component is "invisible" to the user. It's the section of the software that receives data from the devices
and saves them on the database. When it receives the data, it checks if the device is authorized and already
present. Otherwise, it saves it and starts recording the data. During normal operation, each record is tagged
with its timestamp, which is received directly from the RTU. The server timestamp will only be tagged if the
RTU does not have an internal clock (see the specific device manual). If this timestamp received is in the
future (as far as Cloud BOX), the system will generate an error, and data saving will not be possible. In this
case, the log will contain an error, to indicate that the server or the device clock is not synchronized correctly.
Other specific cases can be "recovery" cases (when supported by the RTU). These occur when for any reason

USER MANUAL – Cloud BOX

27

whatsoever the device is unable to reach the server, for example if the mobile phone line is disconnected.
The device that supports this function will store the data locally for a certain amount of time, and upload will
resume once connection is re-established. In this case, the server will consider the device "in recovery". In
this condition, the device is not off line, but the data themselves are, and therefore marked in orange until
alignment is re-established. Lastly, the device is considered offline if it does not reconnect to Cloud BOX for
a period of time exceeding its sampling time.

The devices don't just send data to Cloud BOX, but also alarm messages, which are asynchronous in relation
to the sampling time, and arrive when they occur, rather than during the next data upload window (polling).
During each connection, Cloud BOX can send commands to the device based on the needs of the user and
how the dashboard was programmed. The Dashboard

The dashboard is a web application that can be opened from a desktop or smartphone and can be fully
configured by the user. The pages that can be configured on the server are arranged into a grid with cells
containing elements called widgets. Each of them performs a specific function, such as for example a chart,
or a needle indicator. The editor gives the possibility of arranging these elements from left to right, grouping
them by rows, in a grid format. Each row may contain a certain number of widgets. It is not necessary for all
rows to have the same number of columns.

When creating a new page, it is possible to include an arbitrary number of rows, and a preset number of
columns. This system ensures automatic adaptation of the display based on the platform being used (Desktop
or Smartphone). In case of Desktop, the format will be as shown on the editor. With the display getting
smaller, form a PC to a Tablet, or a Smartphone, the system moves the widgets one on top of the other, with
the ones on the left in the uppermost positions.

USER MANUAL – Cloud BOX

28

10. Cloud BOX maintenance

10.1. Resetting the Cloud BOX hardware

Factory resets are performed by resetting a factory image. In both cases, do a configuration backup first, to
be used for the reset. To perform these operations, the following is required:

- USB keyboard and Monitor with HDMI socket (ATTENTION!! The monitor must

support HD 1920 x 1080 resolutions and 72Hz minimum refresh frequency)

- 1 x 2Gb minimum USB stick for the UPDATE software

- 1 x 2Gb minimum USB stick for the firmware

We recommend that you connect to VPN Box Manager first and complete a backup, as the procedure will
erase the whole disk, including the configuration data. The software required for the update is Clonezilla,
which can be downloaded from http://clonezilla.org/downloads.php; make sure to download the Debian
version in ISO 64bit format. To prepare the first USB stick with the Clonezilla reset program, download the
program for the creation of the stick from http://sourceforge.net/projects/usbwriter/. Now insert the USB
stick, open the previously downloaded USBWriter program, select the ISO image and underneath the unit
the stick is connected to. ATTENTION! All the data on the stick will be erased.

USER MANUAL – Cloud BOX

29

When writing is complete, close the program, disconnect the Clonezilla stick and insert the second stick. The
firmware must be saved on this stick, and it can be obtained from the Seneca support site or server. The
firmware packet must be unpacked in root, where there must be just one folder containing a series of files
as per the following figure: ATTENTION! The folder must not be renamed, its name must not contain any

spaces, and it must be of the CLOUDBOX-1.0.0.0 type. Once the second stick is disconnected, reset can be

performed.

Connect Cloud BOX to a monitor and to a keyboard and insert the first stick with the Clonezilla reset program
in the front left port. Start Cloud BOX and wait for the stick to boot, a selection screen will be displayed, select
“Clonezilla live (default settings , VGA 800x600)”.

USER MANUAL – Cloud BOX

30

Press Enter and wait for the operating system to boot, which might take a few minutes depending on the
speed of the stick used. A selection screen for the keyboard layout will be displayed first.

Select “en_US.UTF-8 English”, press Enter and continue with the English configuration; the system will
continue by asking for the keyboard to be remapped; press Enter again and continue.

USER MANUAL – Cloud BOX

31

The system is now ready and will ask if you want to start with the wizard program or enter the shell, select
the first option as in the figure.

The reset is image based, so proceed with the selection of the first item as per the following figure.

USER MANUAL – Cloud BOX

32

The operation carried out is a reset from local device, which means from the USB peripheral; for this reason,
"local_dev" must be selected in the screen shown below. After pressing Enter (bottom yellow), the system
will ask to insert the peripheral to use for the reset. Insert the stick with the firmware into the second front
right USB port, wait 5 seconds and press Enter. The connected devices will be assessed, wait for the
procedure to complete.

When scanning is completed, a window appears where you are asked to select the device containing the
firmware. The situation should be as follows: SDA1 is the fixed disk of Cloud Box, SDB1 is the Clonezilla update
program and SDC1 is the firmware. Choose the last one to carry out the reset.

USER MANUAL – Cloud BOX

33

A window will then appear, as per the following picture, asking what folder must be used; since everything

is in root, select “Top directory_in_the_local_device”. Once selected, press Enter and its contents will be

shown, continue by pressing Enter again.

You are then asked for the level of details of the options, which in this case must be left as "Beginner". Press
Enter and continue.

USER MANUAL – Cloud BOX

34

Having to reset the firmware, proceed by selecting "restoredisk" followed by the unit to reset.

The system is now ready to be reset and will ask what unit to carry it out on: the disks compatible with the
restore will be displayed, as shown in the figure below; only one compatible disk should be displayed, the
32Gb system disk, the main VPN Box disk, an SSD that should take the name SDA.

USER MANUAL – Cloud BOX

35

Once the disk has been selected, the procedure starts and further confirmation to proceed will be requested
(by pressing Y or Enter), as the operation causes the complete loss of all stored data. At the end you will be
asked how you want to proceed, select "poweroff" and then take the USB sticks out. Restart the VPN Box
and wait for the machine to reboot. Once the operating system has been reloaded, the encryption keys will
be created: this is a long operation, so leave the VPN Box switched on until it restarts automatically.

ATTENTION! The machine must not be switched off and restarted during this configuration operation.

10.2. Firmware upgrade

This operation only updates the Cloud BOX server application, leaving the system and the data intact. For a
full formatting use the reset procedure. Firmware upgrade is carried out remotely by FTP connection to Cloud
BOX through the system. After login, in the root load the zip packet called upgrade.zip. After this, send the
configuration restart command, which will complete the operation in a few minutes. Once all the services
have restarted, the upgraded log is stored in the server log. During the operation, all the services are stopped.
The update of the operation status is performed on the physical console of the server.

10.3. Backup

Backups can be scheduled or forced using the panel as indicated in the basic configuration section. If the
destination of the backup is a local destination, make sure that it does not fail due to lack of sufficient space.

Attention! When selecting a backup peripheral, especially if the amount of data is significant, it will be
necessary to ensure that the storage disk is of good quality. For this reason, a USB key, even if 3.0 and/or of
large size, is not recommended. A slow backup activity will last for a long time, with possible freezing of the
server during the backup period, making it impossible to display data, or for them to be saved by the RTUs.

USER MANUAL – Cloud BOX

36

Attention! When doing backups, keep several copies of data and regularly check their content. The backup
file is a zip file.

10.4. Restore

Restore is performed in the same way as the upgrade, by uploading a previously created backup zip file called
restore.zip in the root, followed by the restart command. The process will start automatically 15 seconds
after restart has been completed. In case of positive outcome, a row will be added to the logs, with the results
of the operation. If this operation is performed from an external hard disk (see relevant section), upload the
zip file in the root of the USB hard disk. During the operation, all the services are stopped. The update of the
operation status is performed on the physical console of the server, and the final result is then recorded in
the logs.

10.5. Use of an external disk

It is possible to connect a USB hard disk and use it to store backups. In this case the whole disk will be used.
To use an external hard disk, go to the configuration section and select service. This will show the USB hard
disk units recognised by the system. Select the desired one from the menu and press use. From this moment
on, all backups will be performed on that unit.

11. Advanced customization

The section that can be customized is the Dashboard, or the appearance of the user panel. The title and the
footer that appear at the top and bottom of the panel are strings that can be customized from the project
options in the editor. The title may be replaced by a PNG or JPEG logo (to be loaded through the FTP server
to the Custom folder). Its size depends on the top bar, which by default is 64 pixels. For page setup, the
dashboard uses the Version 3 CSS Bootstrap framework. In addition to the basic style page, it also uses a
default theme, which is only loaded if there is no custom style page that can be loaded. It is possible to load
a custom style page with the name custom.css to the Custom folder, which can be reached through the FTP
server using the System account. In this page it is possible to override the style. Each widget has the following
appearance:

<widgetNAME class=”widget widgetNAME”>

<div class="widget-heading">

<h3 class="widget-title">WIDGET TITLE</h3>

</div>

<div class="widget-body">

USER MANUAL – Cloud BOX

37

……

</div>

</widget>

The widget has a different HTML tag depending on the type, and is connected to a general style called widget.
A specific class is applied in cascade with the same name of the tag, so that the style can be customized. For
the main container with the tag name, an in-line style is applied, which regulates the minimum height. This
allows the widget to expand, but maintain a minimum space requirement in terms of height. The height
parameter reflects in fact the row height, set by the editor. The content is split in two sections: heading and
body. The heading may not be present in two cases: if the title is empty, or if the widget is a label widget,
which being in itself a title does not need a heading. The body of the widget is the content, which represents
the widget itself. The editor also contains a box that makes it possible to change the unique widget ID, which
can then be sent with the CSS.