Prerequisites
Your Gateways will come pre-provisioned with everything they need in order to automatically collect data from your supported sensors, and they will be configured to connect to your designated cloud endpoint. Network connectivity specific to the installation site will need to be configured by customers as described in Configuration, or by working with the Rigado Solutions Engineering team.
Cascade 500-W cellular gateways will come pre-configured for cellular connectivity based on your prior coordination with the Rigado Solutions Engineering team.
Gateway Network Requirements
If you are installing a gateway on a network which has a firewall restricting access to the Internet, you may need to work with the local network administrator to configure the firewall to allow the gateway to communicate with the remote hosts it needs.
The Cascade Gateway needs access to the following internet services:
Gateway operating system - Ubuntu Core
| Ubuntu Core Required Hosts | Protocol | Port | Notes |
|---|---|---|---|
| 0.ubuntu.pool.ntp.org ntp.ubuntu.com | UDP | 123 | Time Server (configurable) |
| geoip.ubuntu.com | TCP/HTTPS | 443 | Determine local timezone |
| login.ubuntu.com api.snapcraft.io dashboard.snapcraft.io storage.snapcraftcontent.com canonical-lgw01.cdn.snapcraftcontent.com canonical-lcy01.cdn.snapcraftcontent.com canonical-lcy02.cdn.snapcraftcontent.com canonical-bos01.cdn.snapcraftcontent.com | TCP/HTTPS | 443 | Software updates |
Table 2.1 Ubuntu Core Required Hosts
Rigado Edge Direct
Rigado has two connectivity options for Gateway cloud management: Microsoft Azure or Amazon Web Services. All Gateways are pre-configured to use one set of hosts by default, this is displayed in Edge Direct, along with configuration to change between the two. Only one set of hosts is used at a time.
| Edge Direct Azure Required Hosts | Protocol | Port | Notes |
|---|---|---|---|
| provision.rigado.com | TCP/HTTPS | 443 | Hosted at AWS and Azure IPs |
| serial-vault.rigado.io | TCP/HTTPS | 443 | Hosted at AWS and Azure IPs |
| api.azure.rigado.com | TCP/HTTPS | 443 | Posting Logs |
| diagnostics.azure.rigado.com | TCP/HTTPS | 443,80 | Error Reporting |
| mqtt.azure.rigado.com | TCP/MQTT | 8883 | Metrics and diagnostics |
Table 2.2 Rigado Azure Required Hosts
OR
| Edge Direct AWS Required Hosts | Protocol | Port | Notes |
|---|---|---|---|
| provision.rigado.com | TCP/HTTPS | 443 | Hosted at AWS and Azure IPs |
| serial-vault.rigado.io | TCP/HTTPS | 443 | Hosted at AWS and Azure IPs |
| api.rigado.com | TCP/HTTPS | 443 | Posting Logs |
| diagnostics.rigado.com | TCP/HTTPS | 443,80 | Error Reporting |
| a2fyo1pewinh1f.iot.us-west-2.amazonaws.com a2fyo1pewinh1f-ats.iot.us-west-2.amazonaws.com | TCP/MQTT | 8883 | Metrics and diagnostics |
Table 2.3 Rigado AWS Required Hosts
IoT Solution Data
Rigado utilizes a direct edge-to-cloud architecture for all IoT Device data. Please consult individual IoT Solution service providers for required remote host details.
| IoT Solution Data endpoints | Protocol | Port | Notes |
|---|---|---|---|
| IoT Solution defined host | TCP/MQTT/HTTPS | 8883/443 | Hosted at AWS and Azure IPs |
Table 2.4 Rigado IoT Solution Data
Network Connectivity Notes
This list of Internet services would also be applicable for cellular providers which require whitelisting for the sites that can be accessed over a cellular network connection. The gateway uses DHCP to configure its IP address, default gateway, and DNS servers. If DHCP is not available, please see Configure Ethernet for instructions on how to setup a static IP.
The gateway must have access to a time server to function correctly. If the default time server is not available, please see Configure NTP Time Server for instructions on how to setup an NTP server.
Be aware that many of these hosts resolve to multiple IP addresses which may change at any time. System administrators should not rely on whitelisting individual IP addresses for these services.
Updated 11 months ago