The user must have privilege-level 15 for the setup. If you are unsure about the credentials, please check the config of the host-OS on the router in question.
In your running router-configuration, there should be a line, similar to:
username cisco privilege 15 password 0 cisco
Deleting an existing LXC-Container
If you do already have an SiteController-LXC installed on the system, you have to delete that container. It is currently not supported to have two instances of the SiteController running on the same system. To delete the container, simply bring it to the state "DEPLOYED". The approach is very straight forward. The states of the LXC-Container can be triggered from the Web console by the corresponding links under the column "Actions" (red box on screenshot).
To delete and container, it has to be in the "Deployed"-State. So if your old container is running, please stop it; then deactivate it at last delete it, by clicking on the corresponding link in the "Actions"-column in the WebFE.
Different states for LXC-Containers
User uploads the Container → Deployed
User activates and configures the resources for the container → Activated
User configures the "package_config.ini" → still Activated
User starts the LXC → Running state
Deploying the new Site Controller LXC
Login and make sure no other LXC container is currently present.
Open Applications and choose Add/Deploy
Choose the Site Controller LXC package (e.g. SiteController-1.3.5-...tar.gz) and enter an application id
Now your LXC-Container is in the DEPLOYED state. Click Manage to activate the container and allocate resources appropriately.
Select a monitoring sensor in the Serial Access Configuration, choose any if you are unsure. It is important that one is selected as otherwise the container execution will fail.
Depending on your configuration and environment, it might be also necessary to modify the Network Configuration on the right side. When you are done, please click on the "activate"-button, to activate the container.
In Applications choose the Actions column and click manage to reach the App-Config where you can configure the mandatory Azure login credentials
Locate the [dc_azure] section and enter your credentials like in below example.
logger = azeti_file
module_specific_log_level = DEBUG
host = azeti-hub.azure-devices.net
device = azeti-Azure
SAStoken = SharedAccessSignature sr=azeti-hub.azure-devices.net%2Fdevice%[Rest redacted]
# upload interval to server in seconds
upload_interval = 15
Please change this section corresponding to your environment. Important sections (like the name of the device) have been marked in the screenshot. SASToken has been redacted for security reasons.
Click Save to persist the changes
Finally start the container, or restart if it was already running
You should see your new device appear in the Microsoft Azure ioT Hub.
Check out these articles to explore next steps such as importing a configuration from an existing installation.