Contents
Cirrus Link Resources
Cirrus Link Website
Contact Us (Sales/Support)
Forum
Cirrus Link Modules Docs for Ignition 7.9.x
Inductive Resources
Ignition User Manual
Knowledge Base Articles
Inductive University
Forum
Before being able to access the virtual machine you must have completed the installation process **** here *****. Once the virtual machine in the Azure Marketplace has been used to create an EC2 instance in Azure it is possible to access the filesystem of the EC2 instance via SSH.
The only access to the IoT Bridge system is via SSH. As part of of the EC2 instance provisioning process a 'keypair' is associated with the instance. This is something that available during the keypair creation process and can not be retrieved after the initial creation so make sure to save it. To access the instance, you will need the following pieces of information.
Username: ubuntu
Private key: (as created during the EC2 instance provisioning process)
SSH port: 22
In addition to the above information, you must make sure the SSH port (22) is open for inbound connections in the security group you have associated with the IoT Bridge EC2 instance you have created.
There is nothing unique about connecting to a IoT Bridge instance over any other other Microsoft Ubuntu based instance. Microsoft provides detailed instructions on this process of connecting via SSH and SCP ***here*** if you are unfamiliar with it.
The following shows the files that are likely of most interest with regard to IoT Bridge functionality.
This is the core configuration file where Azure SiteWise and MQTT Server configuration is performed - details can be found here
/opt/ibas/conf/ibas.properties
This is the log file directory. Cirrus Link support may ask for these files to resolve configuration, connectivity, or other issues.
/opt/ibaz/log
For support tickets and debugging purposes Cirrus Link support may ask you to make modifications to this file on occasion
/opt/ibaz/conf/logback.xml
This starts the IoT Bridge service - not the service starts automatically on boot so using this script directly is only generally need for debugging
sudo /etc/init.d/ibaz start
This stops the IoT Bridge service
sudo /etc/init.d/ibaz stop