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/service initiating communications

DescriptionRequired by UMS Feature

9 (UDP)

Thin client

UMS server

The UMS server sends magic packets to the thin clients.

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).

See UMS Contacting the Download Server

Automatic License Deployment (ALD)

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 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)

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

See UMS with External Database.

Core (if MS SQL Server is used)

1521 (TCP)

Oracle database

UMS server

See UMS with External Database.

Core (if Oracle is used)

1527 (TCP)

Apache Derby database (Derby Network Server)

UMS server

See UMS with External Database.

Core (if Apache Derby is used)

5432 (TCP)

PostgreSQL database

UMS server

See UMS with External Database.

Core (if PostgreSQL is used)

5900 (TCP)

Thin client

(UMS agent)

UMS Console

The UMS Console initiates a VNC session for shadowing; see UMS and Thin Clients: Shadowing.

Core (shadowing)

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)

Thin client

The thin client requests a file from the UMS; see UMS and Thin Clients: File Transfer .

Core (file transfer)

8443 (TCP)

UMS server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

Thin client

In the course of a Universal Firmware Update, the thin client requests a file from the UMS; see UMS and Thin Clients: File Transfer.

Core (Universal Firmware Update)

8443 (TCP)

UMS server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

3rd party component using IMI (IGEL Management Interface)

See IGEL Management Interface (IMI).

IMI

8443 (TCP)

ICG (IGEL Cloud Gateway)

UMS server

See Thin Clients and UMS Server Contacting Each Other via ICG.

Core (with ICG)

8443 (TCP)

ICG (IGEL Cloud Gateway)

Thin client

See Thin Clients and UMS Server Contacting Each Other via ICG.

Core (with ICG)

9080 (TCP)

UMS server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

Thin client

The thin client 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.
By default, Allow SSL Connections only is activated, and 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.
By default, Allow SSL Connections only is activated, and port 8443 is used by the UMS Console.

Core (unencrypted, no SSL)

30001 (TCP)

UMS server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

Thin clients

See Thin Clients Contacting UMS server.

Core (direct thin client communication, not used with communication via ICG)

30002 (TCP)

UMS server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

HA Load BalancerIf 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)

Thin client

(UMS agent)

Thin client

The thin client 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 thin clients)
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)

Thin client

The thin client 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 thin clients)



Last update: July 2, 2019