2.1. 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 Configure Network , 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.

2.1.1. 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 these Internet services:

Table 2.1 Remote Services
Remote Host Protocol Port Notes
UDP 123 Time server
geoip.ubuntu.com TCP/HTTPS 443 Determine local timezone
TCP/HTTPS 443 Software updates
api.rigado.com TCP/HTTPS 443 Posting logs
diagnostics.rigado.com TCP/HTTPS 443,80 Error Reporting
a2fyo1pewinh1f.iot.us-west-2.amazonaws.com TCP/MQTT 8883 Metrics and control
Customer-defined remote host      

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.

Note that the following remote hosts have been used previously, however they have been recently depreciated:

Table 2.2 Depreciated Remote Services
Remote Host Protocol Port Notes
TCP/HTTPS 443 Provisioning Software updates

They continue to operate as of October 2020 but are expected to be no longer used in the future.