Gateway Installation Precheck

Prior to installing your gateway, whether it’s our on-prem hardware option or our virtualized software gateway, we will need to know a little bit about your network. These questions help ensure the gateway can connect to the cloud and access devices on your network without requiring changes after deployment. For a more detailed questionnaire covering full deployment requirements, download the Deployment Readiness Guide.

Gateway to Cloud

• Will you use DHCP (dynamic or reserved) for the gateway’s WAN/cloud facing port or will you need a static IP assigned to the gateway?
• Is outbound port 443 open on your network?
• Does your firewall have destination IP/hostname restrictions, and if so, are you able to allow our destination hostnames? (FQDN ACLs)
• Do you have any custom DNS servers, or NTP servers?

Gateway to On-Premises Devices (OT Network)

• Do you plan to deploy a physical (Mapped provided) gateway or make use of a virtualized gateway (View Secure Edge [IoTium], Azure Stack Edge, Kubernetes, Docker, VMWare ESXi, etc)?
• Does the BMS network have access to the Internet, or is it isolated?
• Will you use DHCP (dynamic or reserved) for the gateway’s LAN/devices facing port or will you need a static IP assigned to the gateway?
• Are all devices and controllers reachable on a single network, either directly or through VLAN trunking at the switch? If not, multiple gateways may be required to cover different network segments.
• Do you use custom ports for any on-premises control network protocols? For example, BACnet on a port other than 47808, C-Bus (CNI) on a port other than 10001, KNX on a port other than 3671, etc.
• Do you have any port filtering or port authentication in place, such as Dot1q?
• If using BACnet protocol, do you make use of BACnet/IP Broadcast Management Devices (BBMDs)?
• Can you provide a network diagram showing IP and serial devices?
• If using a hardware gateway, will the gateway be housed in close proximity to the network switches/routers?

Based on your answers, Mapped will configure the gateway and coordinate any additional requirements before deployment.

Common Blockers

• Internet access from the gateway is restricted (firewall rules)
• The gateway cannot reach external services needed to connect and send data (DNS issues)
• Some devices cannot be accessed by the gateway (network restrictions)
• Some systems may not be discoverable across the network (subnet limitations)
• Devices may appear visible but are not actually reachable (segmentation limits)

Additional Notes:

Once deployed, the gateway will:

• Establish a secure outbound connection to the Mapped Cloud over HTTPS (TCP 443)
• Discover and read data from accessible devices on the network
• Begin streaming normalized data without requiring inbound firewall changes

However, the gateway can only discover devices that are both reachable over IP from its network location, and are not restricted by firewall or network segmentation.