ETB Controller™ Installation Instructions: Section 4 - Socomec Site Internet Configuration

4.0 Networking Installation and Configuration

The ETB Controller™ provides multiple methods for connectivity to obtain internet access and to connect to ETB Monitor. Most importantly the installer/developer must make sure a network drop is ready to use for the EMS system based on the information below. The network drop provided should be configured for DHCP, and when a firewall is present, the below ports should be opened for outbound traffic.

ETB Controller™ requires an internet connection for the following reasons:

• • Send telemetry data regarding system performance
    • Time series data such as power, current voltage etc.
    • Status data such as inverter modes
    • Alerts and events
  • Receive software updates
    • Platform, OS and application updates
    • New ML models
    • Bill date ranges and utility rate information relevant to the performance of the site

4.1 Wired Ethernet

To use wired ethernet, network access must be made available by the site IT administrator to ensure that an active network port is available.

The local ruggedized computer does NOT need access to any of the host customers local area network.  It is requested that the device be placed on a separate VLAN with internet ports enabled as defined within this document.  

4.2 LTE / Cellular

If connecting using LTE, a SIM card and LTE modem can be provided by the Energy Toolbase, Inc. support team prior to site commissioning and installation. If you have determined the LTE service will be required for a site, please reach out to ETB support for a quote for the hardware and LTE service.

4.3 Ports

To ensure proper EMS connectivity, the following network outbound ports must be enabled if connecting to a local site network:

• • TCP 22 – Remote connection
  • TCP/UDP 52 - DNS
  • TCP 80 – Failover remote connection
  • UDP 123 – Time synchronization
  • TCP 443 – Cloud services
  • TCP 3022 – Remote diagnostic connection
  • TCP 3024 – Remote diagnostic connection
  • TCP 4505 – Remote device management
  • TCP 4506 – Remote device management
  • TCP 8443 – Cloud services
  • TCP 8883 – Cloud MQTT traffic
  • UDP 40000 – Secure private network access

  • TCP 18264 *

  • TCP 257 *

  • TCP 18191 *

  • TCP 18192 *

  • UDP 500 **

  • UDP 1701 **

  • UDP 4500 **

  • UDP 259 **

    * Outbound traffic on these ports will be destined toward public IP 194.169.203.20
    ** Outbound traffic on these ports will be destined toward public IP 194.169.203.21

4.4 Connection Validation

Once the network connection drop has been installed, to test the connection, the installer should plug the ethernet cable into a laptop and attempt to reach an external webpage to confirm the outbound connection is valid. If the connection fails to reach the web, please review the required outbound ports with the site IT administrator to ensure the proper ports have been opened.