This document will describe the Initial setup of Site Controller in a IR910 device.
Please read the official device installation guide: Overview Documentation from Cisco.com for IR910 before you proceed installing the azeti Software. |
The All in One installer packages is used to install all neccesary components of the Site controller, including Mosquitto and third party libraries at the same time. It cannot be used for upgrading an installed system as it will overwrite any previous configuration. |
You will need to know the IP of the system and to have access via ssh.
You have the installation files:
Before you begin the installation, make sure that you have the system with the right time configuration and a timezone configured in your system. Please read the file /etc/timezone to check that it is including your location. This file should contain a pair (Example: Europe/Berlin), that corresponds to the names that you can find in /usr/share/zoneinfo. |
Once the system is installed, you will need to do a basic configuration of the system in order to connect to the cloud server. You should have received all the credentials beforehand, contact your provider in case you miss some information. |
Uncompress the file with the command
# tar -xvf nameoffile (Example: tar xvzf SC_all_in_one_installer-armv5tel-62bf7d4) |
The installation script prepares the system to start every time your device is rebooted. In case you want to change this behavior, the installation script is located in /mnt/apps/etc/init.d, with a prefix and the name SiteController. |
If the system was not set to autostart, it should be started after installation. To do that follow this procedure:
Start SiteController and Mosquitto
#/mnt/data/azeti/SiteController/run_SiteController.py start |
SiteController Status, note that required modules should be marked green and running
# /mnt/data/azeti/SiteController/run_SiteController.py status WARNING: section SiteController.conf not contained in SiteController.cfg. Time zone set to: Etc/UTC Serial of this installation: cisco-sbsa-demo001 Main version of this installation: 1.1.0_(Build:1228_c300ebc) OK: Integrity check passed. OK: Module Watchdog.py is running with PID (29410) OK: Module cloudConnector.py is running with PID (29457) OK: Module HD2CloudExporter.py is running with PID (29495) OK: Module ConfigProvider.py is running with PID (29557) OK: Module RawResultsDeMux.py is running with PID (29663) OK: Module CalibResultsEvaluator.py is running with PID (29702) OK: Module JobProcessor.py is running with PID (29736) OK: Module AutomationController.py is running with PID (29760) OK: Module VirtualSensorProvider.py is running with PID (29799) OK: Module ModbusDaemon/ModbusMaster.py is running with PID (29828) OK: Module UDPserver_AdvantechAdam60xx.py is running with PID (29882) OK: Module trapd.py is running with PID (29910) OK: Module snmpgetd.py is running with PID (30021) OK: Module http_server.py is running with PID (30096) OK: Module persistord.py is running with PID (30140) WARNING: Module VS_fill_quantity.py is not running. WARNING: Module VS_flow_rate.py is not running. WARNING: Module VS_tank_simulator.py is not running. WARNING: Module VS_access_control.py is not running. WARNING: Module VS_battery_details.py is not running. WARNING: Module VS_HistoryAnalyser.py is not running. WARNING: Module VS_filesize.py is not running. OK: Module mosquitto daemon is running with PID (29365) |
Once you finish the installation process, you have a basic Site Controller system installed. The system has to be configured in order to do the necessary tasks. You can adjust some configuration, from deciding which modules will run in Site Controller to select some parameters of the different modules. Please read carefully the guides about Site Controller before proceeding to change any configuration of the system. A wrong configuration may cause a failure in the monitoring/actuation system that can affect the overall solution.
Configuration needed:
[ExternalBroker]
host=10.0.0.72
organizationShortName = Test
sub_topics=cloud/%SYSID%/#
user_id=cvd.cisco@azeti.net
password=india.89
After you have performed your initial tests on the system, it is time to prepare it for production. It is advisable that you perform the following steps for a production system:
Step | Description |
---|---|
Block incoming access to the local SC Mosquitto MQTT broker | The broker is initially open to external connections, as there are some tests that have to be done after installation that normally need a technician to connect to the broker. After the installation is done, you may want to block the access to the Mosquitto broker from the outside. This is done in the configuration file of Mosquitto, adding the parameter bind_ address localhost. Please refer to the Mosquitto documentation in http://www.mosquitto.org. In the IR910 the mosquitto configuration file is in /mnt/apps/etc/mosquitto/mosquitto.conf. |
Securing the communications with the cloud | The default installation does not contain certificates. In order to have a secure communication, you will need TLS certificates provided by azeti. Please see the section "Activating TLS connections" below. |
[ExternalBroker] #azetibroker02 azeti organization tls_enable=True host=azetibroker02.azeti.net organizationShortName = Test user_id=user.just.test@azeti.net password=doNotTryIsFake port=8883 |
Make sure that enough disk space is available in the IR910 linux environment.
|
If you receive errors during the first start of the Site Controller regarding non existing modules, it might be that you run out of space during the installation and that the necessary python modules are not installed. Please check the space in the directory where you put the installation files to be sure it has still free space. If not, search for a different suitable directory and repeat the installation process.
You may want to remove the backups from previous installations that are in /mnt/data/SiteController-install. |
It may happen that you have restrictions in your network regarding ports and IPs. Contact your system administration department with the following information in order that they solve it:
Access given to the PC that manages the cloud server: |
---|
|
Access given to the IR910: |
|
If you have a site controller but you do not know which version is installed, look in the root folder of Site Controller. There is a file called SiteController-rev-info.txt, which include the version and build of the software. This information will be useful in case you contact support and cannot provide direct access to the system.
Contact our support service (support@azeti.net) in case you do not manage to proceed with the installation. Be prepared to give our technicians direct or remote ssh access to the system. |