System requirements

  Operating system   A server or PC that is always on with the most current version of:   English install of Microsoft® Windows® 10 and 11 64-bit, Server 2016, Server 2019, Server 2022, Server 2025 Windows release information   Rocky Linux 8 and 9 (recommended) Rocky Linux release information   Red Hat Enterprise Linux 8 and 9 (recommended) RHEL release information     RHEL 7 and CentOS are not supported on Gateway 1.23 and newer. How to replace your EcoStruxure IT Gateway with a new installation EcoStruxure IT Gateway 1.23 release notes    It is recommended that operating systems and browsers are kept up to date and patched regularly in accordance to vendor recommendations.   User permissions   Windows Local administrator permissions for clean install or manual update   The “Local System” account and “Network Services” account need permissions for running the Gateway software and performing an auto-update or an update initiated from ITE.   Linux root or sudo capable user required for clean install or manual update   The root user and the non-login gateway user need permissions for running the Gateway software and performing an auto-update or an update initiated from ITE.   /etc/default/useradd must use the default /home directory. Otherwise, the install will fail.   The user running the Gateway installer must have file system privileges set to umask 0022 or 0002. Otherwise, the installer cannot initialize the database.     CPU and Memory The required CPU and memory depends on the number of monitored devices and the protocol. The following guidelines are based on our testing. Your actual results may vary due to differences in hardware, network, and device responsiveness.   The Gateway service (OpenJDK Platform binary) allocates up to half the total system memory for its use.   Recommended minimum CPU and memory The number of SNMPv3 devices the Gateway can monitor is about 25% of what is possible with SNMPv1 and Modbus TCP.    SNMPv1 and Modbus TCP   Size Number of devices Number of sensors RAM CPU Small 250 34,000 4GB 4 Medium 2000 270,000 8GB 8 Large 5000 540,000 16GB 24     SNMPv3   Size Number of devices Number of sensors RAM CPU Small 60 8,500 4GB 4 Medium 500 65,000 8GB 8 Large 1,200 130,000 16GB 24   One Minute Polling A maximum of 25 devices can be configured to poll at 1 minute.   When you use the small Gateway configuration to discover SNMPv3 devices, only about 10 out of the 60 SNMPv3 devices can be polled at 1 minute.  More than 10 devices may cause the Gateway to become overloaded and not keep up with the configured poll rate. See Configure 1 minute polling in EcoStruxure IT Gateway   Alarms If the combination of number of devices, poll rate, and protocol is more than the Gateway can handle, you may get a device communication alert alarm.   Disk Space 800MB of disk space is required for the application itself, plus additional space for a maximum of 8 days of sensor data.   Additional disk space required   Size Additional disk space Total disk space Small 128MB per day 2GB Medium 512MB per day 5GB Large 1.1GB per day 10GB   Firewall Port 443 TCP outbound To connect using static IP addresses, add: 40.84.62.190 23.99.90.28 52.230.227.202 52.177.161.233 52.154.163.222   If your firewall blocks the Gateway default ports, or any non-default ports you specified, you must add firewall exceptions for these ports. See Gateway default ports   DNS A DNS server must be defined for the network that connects to EcoStruxure IT.   Make sure your Gateway can resolve us.ecostruxureit.com via DNS.   Make sure Gateway versions older than 1.10.0 can resolve us.struxureon.com via DNS.   Supported browsers Microsoft Edge® Mozilla® Firefox® Google Chrome™ Safari Set the screen resolution to at least 1024 x 768.   Smartphone iPhone 6S and newer iOS 13.0 and newer Android 10 and newer   Connected devices Intelligent Network Management Card Modbus TCP or SNMP V1 and V3 enabled Gateway versions older than 1.15 do not allow discovery of SNMPv3 devices with the Authentication type and Encryption type set to None. See Discover devices Connected to a TCP/IP network that the Gateway has access to Note: Firmware update and mass configuration with APC NMC 4 (AP9644) devices are not yet supported. Redfish server protocol support HP Proliant with iLO 4, 5 Note: iLO 4 requires ManagerFirmwareVersion 2.55 or greater. Dell PowerEdge with iDRAC 7, 8, 9 NetBotz support Rack Monitor 570, 250, 750/755   Security certificate When you launch the EcoStruxure IT Gateway, the browser might display a message that the connection is not secure. Since the application is installed on the local machine, the security certificate used by localhost is a self signed certificate. It is safe to add an exception to your browser for https://localhost.   See How to replace the self-signed SSL certificate in EcoStruxure IT Gateway

If your firewall blocks the Gateway default ports listed here, or any non-default ports you specified, you must add firewall exceptions for these ports. The information in this article pertains to the latest version of EcoStruxure IT Gateway. Web server Communication between the Gateway and your web browser on the intranet uses the following port: Name Port Direction Type Description Web server 443 INBOUND TCP Web browser access to Gateway interface You can specify the ports used by the Gateway web server when you install the Gateway software.   Device communication Communication between the Gateway and your devices on the intranet uses the following ports: Name Port Direction Type Description FTP 21 OUTBOUND TCP Transfer device configurations, firmware binaries, and logs SCP 22 OUTBOUND TCP Transfer device configurations, firmware binaries, and logs SNMP 161 OUTBOUND UDP SNMP device polling and discovery   1062 INBOUND UDP SNMP traps   162 INBOUND UDP SNMP traps (default for most third party devices)   8011 INBOUND TCP HTTP Service log capture (available on select devices) NetBotz HTTPS 443 OUTBOUND TCP HTTPS NetBotz device polling and discovery   8453 INBOUND TCP HTTPS NetBotz traps NetBotz HTTP 80 OUTBOUND TCP HTTP NetBotz device polling and discovery   8010 INBOUND TCP HTTP NetBotz traps Modbus TCP 502 OUTBOUND TCP Modbus TCP device polling and discovery Redfish 443 OUTBOUND TCP Redfish server polling and discovery See Configure SNMP trap ports EcoStruxure IT communication Communication between the Gateway and EcoStruxure IT over the internet uses the following port. Name Port Direction Type Description EcoStruxure IT 443 OUTBOUND TCP EcoStruxure IT Gateway communication with EcoStruxure IT cloud.   Local system only Firewalls do NOT need to open external access to these ports. This information is provided to help avoid port conflicts.  Name Port Direction Type Description Database port 5432 INBOUND TCP Local System ONLY - Used by the Gateway software to communicate with its database. Note: The database port is subject to change on software update. A free port is automatically selected for the database during the update process.   Gateway appliance specific Gateway appliance version 1.10 and newer Name Port Direction Type Description Gateway 22 INBOUND TCP Gateway application command line interface access Gateway 2222 INBOUND TCP For support use only  Gateway appliance OS command line interface access via SSH Note: You must first access the Gateway CLI from the appliance private network on port 22 to enable the SSHD service, and then follow the instructions provided by support. See Gateway appliance command line interface (CLI) - version 1.10 and newer See EcoStruxure IT Gateway appliance installation and setup - version 1.10 and newer for more information.   Gateway appliance version 1.9 and older Communication between the Gateway appliance's Webmin interface and your web browser. Note: Webmin is only accessible from the private network of the Gateway appliance. Name Port Direction Type Description Webmin 10000 INBOUND TCP Web browser access to the Gateway appliance's Webmin setup and configuration interface. See EcoStruxure IT Gateway appliance installation - version 1.9.0 and older for more information. More information In addition to the firewall of your host system, your IT department might have firewalls and proxies in place that could prevent Gateway from communicating with EcoStruxure IT or your devices.  Contact your IT department if they are running firewalls that are blocking required ports. If your organization uses a proxy, see the instructions in these articles for configuring the Gateway: System requirements for EcoStruxure IT Gateway Installing and setting up EcoStruxure IT Gateway