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.

IXON's general allowlist contains a list of all servers that can possibly be used by an IXON edge gateway. For privacy reasons, it will not include your M2M Cloud Cluster's hostname. As such, whenever you're in contact with a local IT to grant an IXON edge gateway the necessary access to the IXON Cloud, make sure to also share your M2M Cloud Cluster's hostname. This will be shared with you upon delivery.

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.

With an M2M Cloud Cluster, on the topic of BACnet/IP, distinction is made between users that connect through the IXON Cloud, which is possible with and without an M2M Cloud Cluster, and connections that are only possible with the M2M Cloud Cluster.

For users connecting through the IXON Cloud, BACnet/IP communication over VPN is possible by following these instructions: Connect to your machine using BACnet/IP.

For connections that are only possible with the M2M Cloud Cluster (Server to machine, Machine to server, and Machine to machine), you have the following options available to you:

• Routing in combination with BBMD.
  • Requirement: This option requires routing. Check the support article for your use case to see whether routing is explained. If it isn't, this option isn't possible for your use case.
  • Instructions: See Connect to your machine using BACnet/IP.
• VPN 1:1 NAT in combination with direct IP communication.
  • Requirement: This option requires VPN 1:1 NAT. Check the support article for your use case to see whether VPN 1:1 NAT is explained. If it isn't, this option isn't possible for your use case.
  • Instructions: Set up VPN 1:1 NAT as explained in the support article for your use case. Open your BACnet/IP software and connect to the IP address of your machine. BACnet's broadcast functionality (BBMD) will not work with VPN 1:1 NAT, because that BACnet functionality requires routing to function. Note that not all BACnet/IP software allows for direct IP communication.