Skip to main content

Halo IoT Networking Requirements

The following table defines the network topology, ports, and protocols required to support an Augury system installation.

Updated over 5 months ago

WiFi (AP) configuration

Setting

Supported configuration

Comments

WiFi type

WPA2 Personal

WPA Open System (no password)

SSID

Visible or Hidden network

Preferably isolated dedicated network for IoT

Authentication

PSK

No other authentication steps to gain access (e.g captive portal)

Password should remain static

Password may include 94 special characters, as detailed in the Printable Characters Table

Band

2.4Ghz, 5Ghz

5Ghz is supported under a new Node FCC ID

IP Addressing

IPv4 DHCP

A dedicated network is recommended (DMZ, VLAN, etc…)

RSSI

-75dBm

Minimal Wifi RX signal strength

DNS server

Should be provided by the network

Wired configuration

Setting

Supported configuration

Comments

Connector

RJ-45

Speed & Duplex

Automatic

The device supports 10/100/1000M

IP Addressing

IPv4 DHCP

POE

802.3af

DNS server

Should be provided by the network

Outbound Connections

The following ports must be open to enable Halo 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 8883 (443 on customer request)*

production-iothub.azure-devices.net

20.80.227.212

IoT Data Transfer

TCP/UDP 655

35.227.38.87

35.227.23.164

35.197.254.125

35.197.217.254

35.189.119.102

35.196.166.158

34.139.202.40 - only for Cassia

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

*Some customers may prefer to use TCP 443 instead of TCP 8883 for IOT data transfer. Augury Nodes (Node 2.0 and Cassia) are configured to use either TCP 8883 or TCP 443 for MQTT data transfer. If TCP 8883 is blocked, the Node will automatically fall back to using TCP 443.

System & Network Characteristics

System Overview

The following is a common setup:

  • 4 Endpoints per machine

  • Up to 8 machines per Node

Data Transfer

  • Augury's best practice is to sample once an hour

  • The machine transfers up to 640KB of data per hour

  • In the case of 4 endpoints per machine

  • Data transfers are spread randomly over the hour

  • Minimum bandwidth:

  • Download 2Mbps

  • Upload 2Mbps

IoT Security

  • All data from the Node to the cloud is encrypted.

  • Device-to-cloud authentication with asymmetric cryptography algorithms

  • Device-level ACL and monitoring

  • Periodic penetration tests

Document Number: PB00012
Revision: H

Printable PDF

Did this answer your question?