Download PDF
Download page UMS Communication Ports.
UMS Communication Ports
Which ports are used by the components of IGEL UMS and the other components of a UMS infrastructure?
The following table shows the ports used by the components that play a role in a UMS infrastructure.
Port (Protocol) | Who is Listening? Applications/Service Binding to Port | Who is Talking? Applications/Services Initiating Communications | Description | Required by UMS Feature |
---|---|---|---|---|
9 (UDP) | Device | UMS Server | The UMS Server sends magic packets to the devices. | Core (Wake on LAN) |
80 (TCP) | IGEL download server (HTTP server at fwu.igel.com) | UMS Server | The UMS Server requests the connection details required for connecting to the IGEL license server (at susi.igel.com). | Automatic License Deployment (ALD) |
80 (TCP) | IGEL download server (HTTP server at fwu.igel.com) | UMS Server | See UMS Contacting the Download Server to Check for New Updates. | Core (Universal Firmware Update) |
88 (TCP/UDP) | MS Active Directory Service | UMS Server | The UMS Server sends a Kerberos request to MS Active Directory. | Core (if Active Directory is used), Shared Workplace |
389 (TCP) | MS Active Directory Service | UMS Server | The UMS Server sends an LDAP request to MS Active Directory. | Core (if Active Directory is used), Shared Workplace |
443 (TCP) | IGEL licensing server (at susi.igel.com) | UMS Server | The UMS Server requests licenses; see UMS Contacting the Licensing Server. | Automatic License Deployment (ALD) |
636 (TCP) | LDAPS server (other than MS Active Directory) | UMS Server | The UMS Server sends an LDAP request over SSL. | Core (if LDAPS server is used) |
1433 (TCP) | Microsoft SQL Server database | UMS Server | Core (if MS SQL Server is used) | |
1521 (TCP) | Oracle database | UMS Server | Core (if Oracle is used) | |
1527 (TCP) | Apache Derby database (Derby Network Server) | UMS Server | Core (if Apache Derby is used) | |
5432 (TCP) | PostgreSQL database | UMS Server | Core (if PostgreSQL is used) | |
5900 (TCP) | Device (UMS agent) | UMS Console | The UMS Console initiates a VNC session for shadowing; see UMS and Devices: Shadowing. | Core (shadowing) |
6155 (UDP) | HA Load Balancer UMS Server | HA Load Balancer UMS Server | Both HA Load Balancer and UMS Server listen on port 6155 and use it for communication. | High Availability (HA) |
8443 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | UMS Console | See UMS with Internal Database or UMS with External Database. | Core |
8443 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | Device | The device requests a file from the UMS; see UMS and Devices: File Transfer. | Core (file transfer) |
8443 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | Device | In the course of a Universal Firmware Update, the device requests a file from the UMS; see UMS and Devices: File Transfer. | Core (Universal Firmware Update) |
8443 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | Device | The UMS provides files for customizing the look and feel of the device's GUI; see UMS and Devices: File Transfer. | Core (firmware customization) |
8443 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | Device | The UMS provides license files for the devices; see UMS and Devices: File Transfer. | Core (licenses) |
8443 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | 3rd party component using IMI (IGEL Management Interface) | IMI | |
8443 (TCP) | ICG (IGEL Cloud Gateway) | UMS Server | Core (with ICG) | |
8443 (TCP) | ICG (IGEL Cloud Gateway) | Device | Core (with ICG) | |
8443 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | File synchronization between UMS Servers | High Availability (HA) |
9080 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | Device | The device requests a file from the UMS (regular file transfer or Universal Firmware Update). This port is only used if Allow SSL Connections only is deactivated in the UMS Administrator. If Allow SSL Connections only is activated, port 8443 is used for firmware updates and file transfer. | Core (unencrypted, no SSL) |
Auto ("high port") | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | UMS Console | The GUI is started via Java Webstart console. This port is only used if Allow SSL Connections only is deactivated in the UMS Administrator. If Allow SSL Connections only is activated, port 8443 is used for firmware updates and file transfer. | Core (unencrypted, no SSL) |
30001 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | Device | Core (direct device communication, not used with communication via ICG) | |
30002 (TCP) | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | HA Load Balancer | If the UMS Server and the HA Load Balancer are running on the same host, the UMS Server will use port 30002 instead of 30001, and the HA Load Balancer will use port 30001. | Core (directly, without ICG) |
30005 (TCP/UDP) | Device (UMS agent) | UMS Server | To scan for devices, the UMS Server sends a broadcast. The UDP packets of this broadcast contain the port to which the device should send the response. The UMS sends new settings to the device. The UMS periodically checks if the device is online. | Core (scanning for devices, sending new settings, checking if the device is online etc.) |
30022 (TCP) | Device (UMS agent) | UMS Server | See UMS and Devices: Secure Terminal | Core (secure terminal) |
61616 (TCP/UDP) | HA Load Balancer UMS Server | HA Load Balancer UMS Server | Both HA Load Balancer and UMS Server listen on port 61616 and use it for communication. | High Availability (HA) |
Auto ("high port") | UMS Server (Windows: service IGELRMGUIServer; Linux: daemon igelRMServer) | Device | The device responds to a broadcast sent by the UMS during a scan. The port number to be used is contained in the UDP packet sent by the UMS. | Core (scanning for devices) |