Required module
The M2M Cloud Cluster is an IXON product that can be used to solve the following secure remote communication use cases:
| Server to machine | Machine to machine | |
|---|---|---|
|
Communication from a central computer or server to multiple machines at the same time. Example: A BMS or SCADA system that needs to control, manage, and monitor various machines simultaneously at different locations. |
Communication from machine to machine. Example: Machines at different locations that are dependent on inter-machine communication to operate accordingly. |
More information:
Server to machine
Use case: Communication from a central computer or server to multiple machines at the same time. Example: A BMS or SCADA system that needs to control, manage, and monitor various machines simultaneously at different locations.
How does it work?
The M2M Cloud Cluster is basically a VPN server with modified rules. This is completely set up and maintained by IXON. These modified rules enable simultaneous access to all of your machines from one or more systems.
All IXrouters and IXagents in your IXON Cloud company will automatically connect to the M2M Cloud Cluster. For reliable long-term communication between your system and the machines it is generally recommended to configure a static VPN address for each IXrouter. This is easily configured in the IXON Cloud.
Your system will connect to the M2M Cloud Cluster by using the publicly available OpenVPN Client together with the OVPN file provided by IXON. The OpenVPN client can be configured to automatically connect upon system startup and will automatically reconnect if the VPN connection is ever lost.
With everything connected to the M2M Cloud Cluster, all that remains is to make sure that your system can communicate with your machines. There are several methods to achieve this, depending on your exact use case: routing, 1:1 NAT, and port forwarding. Please contact your IXON Account Manager or IXON distributor to discuss your use case.
System requirements
VPN-compatible traffic
All network traffic sent to your machines needs to be compatible with our VPN connection. Rule of thumb is that if the communication works over a regular IXON VPN connection, it will also work with the M2M Cloud Cluster.
In more technical terms, compatible traffic over IXON VPN to an IXrouter includes unicast layer 3 traffic, UDP broadcast traffic, and select layer 2 traffic like Siemens’ PROFINET and B&R’s SNMP. Compatible traffic to an IXagent includes all layer 3 and layer 2 traffic. If you’re unsure about the compatibility, please contact us.
OpenVPN-compatible system
Your system (central computer or server) needs to be able to run the OpenVPN client. Windows, Linux, and macOS are supported.
Does anything change for me?
Nearly everything in the IXON Cloud remains unchanged for you. However, to allow communication between your system and all machines at the same time, please note that:
- Everything with an active VPN connection to the M2M Cloud Cluster will be able to access your system that has an active VPN connection to the M2M Cloud Cluster. This includes connected IXrouters, IXagents, and users.
Continue to Frequenty Asked Questions
Machine to machine
Use case: Communication from machine to machine. Example: Machines at different locations that are dependent on inter-machine communication to operate accordingly.
How does it work?
The M2M Cloud Cluster is basically a VPN server with modified rules. This is completely set up and maintained by IXON. These modified rules enable communication between all of your machines.
All IXrouters and IXagents in your IXON Cloud company will automatically connect to the M2M Cloud Cluster. For reliable long-term communication between machines it is recommended to configure a static VPN address for each IXrouter. This is easily configured in the IXON Cloud.
With everything connected to the M2M Cloud Cluster, all that remains is to make sure that your machines can communicate with each other. There are two methods to achieve this, depending on your exact use case: 1:1 NAT and port forwarding. Please contact your IXON Account Manager or IXON distributor to discuss your use case.
System requirements
VPN-compatible traffic
All network traffic sent to your machines needs to be compatible with our VPN connection. Rule of thumb is that if the communication works over a regular IXON VPN connection, it will also work with the M2M Cloud Cluster.
In more technical terms, compatible traffic over IXON VPN to an IXrouter includes unicast layer 3 traffic, UDP broadcast traffic, and select layer 2 traffic like Siemens’ PROFINET and B&R’s SNMP. Compatible traffic to an IXagent includes all layer 3 and layer 2 traffic. If you’re unsure about the compatibility, please contact us.
Custom port-compatible system
If you need to communicate with multiple devices behind a single IXrouter, then your system needs to be able to use custom ports. For example, if your system uses Modbus TCP for communication to your machine, then it will use port 502 (default Modbus port). However, your system should allow you to change this port somewhere in its settings. This requirement does not apply to you if you only need to communicate to a maximum of one device per IXrouter.
Testing is required
The technical details of each machine to machine use case are different. To make sure your exact use case is compatible with the M2M Cloud Cluster, testing is required.
Does anything change for me?
Most things in the IXON Cloud remain unchanged for you. However, to allow communication between machines, please note that:
- Everything that has an active VPN connection to the M2M Cloud Cluster will be able to access everything else that has an active VPN connection to the M2M Cloud Cluster. This includes connected IXrouters, IXagents, and users.
Continue to Frequenty Asked Questions
FAQ
How many IXrouters can I connect to the M2M Cloud Cluster?
Up to 1500 IXrouters or IXagents can be connected.
Can I only connect some of my IXrouters to the M2M Cloud Cluster?
Yes. All IXrouters and IXagents in your IXON Cloud company will connect to the M2M Cloud Cluster. You can transfer IXrouters to another IXON Cloud company to exclude them from your M2M Cloud Cluster.
When will maintenance take place on the M2M Cloud Cluster?
Occasionally, server maintenance is necessary on your M2M Cloud Cluster to make sure everything keeps running smoothly. Generally at most once a year. When maintenance is scheduled, IXON will inform you one week in advance. IXON will perform the maintenance and during this period the M2M Cloud Cluster may be unavailable. If the date/time is not suitable for you, please let us know so we can reschedule.
What is the delivery time of the M2M Cloud Cluster?
The delivery time of the M2M Cloud Cluster can be up to 3 weeks. This is necessary to schedule sufficient time to make sure everything is set up and working correctly.
Where can I get the M2M Cloud Cluster?
If you’re interested in the M2M Cloud Cluster, please contact your IXON Account Manager or IXON distributor to discuss your use case.