Introducing IOhubTM networks

With IOhubTM you can create a network of instances (devices) that can communicate and transfer messages among themself.

Two or more EZ VPNTM devices, located in different places, that run IOhubTM applications, even if they are not interconnected with a VPN or using other complex infrastructure, can exchange MQTT data among themself using the IOhubTM network.

An IOhubTM network does not require configuring infrastructural information such as IP, subnets, interfaces, firewall or security aspects. The IOhubTM network is configured in one simple step and is ready to use.

How to use the networks

  • you can take advantage of IOhubTM networks by using the Data Field Exchanger EXCH scripting language.
  • With the EXCH scripting language, you can write or publish a value on any MQTT internal broker application belong to the same network.

If you need more information on configuring your IOhubTM applications to let them communicate using the IOhubTM network please visit the EXCH Language Remote destinations section.

Use cases

You can take advantage of IOhubTM networks in several different scenarios. Here is a non-exhaustive list of examples:

  • Make different machines communicate with each other regardless of where they are in the world.
  • Multiple, geographically distributed IOhubTM applications that collect data from the local machines and send it into one centralized IOhubTM application that contains the database and the charting module.
  • Multiple, geographically distributed IOhubTM applications that collect data from the local machines and one main IOhubTM application that act as an orchestrator of the others and increase or decrease production values of each IOhubTM node.
  • Use an IOhubTM node as a dispatcher of communications from an ERP or MES to automatically distribute messages to other IOhubTM nodes within the company and different geographic sites.
  • Configuring an iohub node to act as a single centralized notification application.
  • Simplify and lighten the tasks of every IOhubTM node by centralizing the logic in a single data orchestrator.
  • Use IOhubTM networks to enable bi-directional communications among sites that are not publicly reachable (such as mobile / satellite connectivity or network that use carrier-grade NAT).

The IOhubTM network rules

An IOhubTM network is a high-security level network and is bound to the following rules:

  • A network must have its unique name

    There is no limit on how many networks you can create, but every network must have its unique lower case name.

  • The name of a network cannot be changed.

    When the network has been created there is no way to change its name. In case you need to change the name of the network we recommend you create a new network and move the instances in the new network.

When you move the instances to the new network, no other modifications are required.

  • A network can be removed if does not contains instances.

    Unassign first the network from any instance if you want the network can be removed.

  • Networks are isolated and cannot communicate with each other.

  • IOhubTM istances (devices), that are not assigned to a network, are defined as isolated and cannot communicate with other instances or networks.

    By default all new IOhubTM instances are defined as isolated.

  • Each IOhubTM instance has its own unique ID used to identify the instance within the network.

    The ID must be unique within the same network and can be changed later.

  • Network can be only assigned to an instance belongs to the same EZ VPNTM account.

    IOhubTM instances that belongs to different accounts cannot be configured to the same network.

Security aspects

The IOhubTM network is automatically configured and managed when set. Communications are strongly encrypted and authentication is protected with a regularly automatically renewed 1024bit token.

The instances within the same network cannot communicate with other networks, isolated instances or instances in other networks.

IOhubTM instances configured as isolated cannot communicate with other IOhubTM istances or other networks.

The devices and machines with which IOhubTM communicate cannot use the IOhubTM network to independently communicate or exchange information.

Manage IOhubTM networks

To define an IOhubTM network you need to:

  • Add a new IOhubTM network name.
  • Assign the network to one or more IOhubTM instances (devices).

Add a new network

To add a new network:

  1. Click IOhubTM menu.
  2. Click Networks.
  3. Type the name of the new network.
  4. Click Add Network button to create the new network.
<iohub></iohub> networks add

Remove a network

To remove an existing network:

  1. Click IOhubTM menu.
  2. Click Networks.
  3. Click Remove button to remove the network.

Please note that the Remove button is only available if the network is not assigned to any IOhubTM instance.

<iohub></iohub> networks remove

Show networks

To show what networks are configured in the EZ VPNTM account:

  1. Click IOhubTM menu.
  2. Click Networks.
<iohub></iohub> networks show

Please note that the IOhubTM instances showed in orange are set in edit mode. Please be sure to leave edit mode to be sure the devices have received the network configuration correctly.

<iohub></iohub> networks orange

Assign network to an IOhubTM instance

To assign a network to an IOhubTM instance:

  1. Click IOhubTM menu.
  2. Click Instances.
  3. Click Manage button to manage the instance.
<iohub></iohub> networks manage

In order to manage IOhubTM network configuration the EZ BoxTM device must be set in Edit Mode.

  1. click Enter Edit Mode to activate the edit mode.
<iohub></iohub> networks edit mode

To assign the network:

  1. Select the Network.
  2. Type the IOhubTM ID.
  3. Click Update EZ Box button to assign the network.
<iohub></iohub> networks update id

The legend of the EZ BoxTM device is updated accordingly:

<iohub></iohub> networks legenda

Leave edit mode to apply the network configuration:

  1. Click Leave Edit Mode button to leave edit mode and apply the new settings.
<iohub></iohub> networks leave edit mode

Please note the EZ BoxTM device will restart:

<iohub></iohub> networks restart ezbox