The following table defines the network topology, ports, and protocols required to support an Augury system installation.
WiFi (AP) configuration
Setting | Supported configuration | Comments |
WiFi type | WEP WPA-PSK [TKIP], Personal WPA2-PSK [AES], Personal |
|
SSID | Visible (Not Hidden) | Preferably isolated dedicated network for IoT |
Encryption | TKIP AES |
|
Authentication | PSK | ● No other authentication steps to gain access (e.g captive portal) ● The password should be 8-63 characters long ● Password may include 94 special characters, as detailed in thePrintable Characters Table ● In case of a Wi-Fi password change, the user needs to configure the Gateway with the new credentials |
Band | 2.4Ghz | IEEE 802.11 b/g/n |
IP Addressing | IPv4 DHCP or Static IP | A dedicated network (DMZ, VLAN, etc.) is recommended. |
RSSI | -70dBm | Minimal Wifi RX signal strength |
DNS server |
| Should be provided by the network |
Cellular configuration
Setting | Supported configuration | Comments |
SIM | Standard size SIM (large) |
|
APN | As required by the network operator | 4G (LTE) only |
Outbound Connections
The following ports must be open to enable Ranger Pro systems to communicate with Augury servers.
Port / Protocol | Destination | Description |
TCP 443 | iot.augury.com (52.177.239.125) api.augury.com | IoT services |
TCP/UDP 655 Upon customer request | 35.227.38.87 35.227.23.164 35.197.254.125 35.197.217.254 35.189.119.102 35.196.166.158
| Support,Service |
UDP/TCP 123 | 0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org 3.pool.ntp.org or
Customer provided (local NTP server or time.google.com | NTP |
TCP 80 | 13.107.246.55 13.107.246.56 | Required, IoT Data Transfer |
TCP 8883 | solace-prod.mhaas.bakerhughes.com divigraph-iothub.azure-devices.net production-iothub.azure-devices.net 20.80.227.212 20.44.17.101 20.253.108.228 20.253.108.230 | Required, IoT Data Transfer, MQTT |
TCP 22 | divi-prod-reverse.westeurope.cloudapp.azure.com 20.13.122.0 | Optional, Support Service |
TCP/UDP 53 | 8.8.8.8 8.8.4.4 | Required, DNS |
TCP 4901 | RPCS client node | Optional, only add if RPCS configuration software is used on site. |
|
|
|
TCP 502 | Modbus client node | Optional, only add if Modbus connection is used on site. |
Document Number: PB00039
Revision: A