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 |
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
Comments
0 comments
Please sign in to leave a comment.