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.

Sorted by UMS Feature

Required by UMS FeaturePort (Protocol)

Who is Listening?

Applications/Service Binding to Port

Who is Talking?

Applications/Services Initiating Communications

Description
Automatic License Deployment (ALD)

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)

443 (TCP)

IGEL download server (HTTP server at fwus.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 Licensing Server.

Core

8443 (TCP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

UMS Console / UMS Web App

See UMS with Internal Database or UMS with External Database.

Core (directly, without 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 (direct device communication, not used with communication via ICG)

30001 (TCP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

Device

See Devices Contacting UMS.

Core (file transfer)

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 (firmware customization)8443 (TCP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

DeviceThe UMS provides files for customizing the look and feel of the device's GUI; see UMS and Devices: File Transfer.

Core (if Active Directory is used), Shared Workplace

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 Apache Derby is used)

1527 (TCP)

Apache Derby database (Derby Network Server)

UMS Server

See UMS with External Database.

Core (if LDAPS server is used)

636 (TCP)

LDAPS server (other than MS Active Directory)

UMS Server

The UMS Server sends an LDAP request over SSL.

Core (if MS SQL Server is used)

1433 (TCP)

Microsoft SQL Server database

UMS Server

See UMS with External Database.

Core (if Oracle is used)

1521 (TCP)

Oracle database

UMS Server

See UMS with External Database.

Core (if PostgreSQL is used)

5432 (TCP)

PostgreSQL database

UMS Server

See UMS with External Database.

Core (licenses)8443 (TCP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

DeviceThe UMS provides license files for the devices; see UMS and Devices: File Transfer.
Core (online check)

Auto ("high port")

(UDP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

Device

The device responds to a message sent by the UMS to check if the device is online.

The port number to be used is contained in the UDP packet sent by the UMS.

Core (scanning for device)30005 (TCP/UDP)

Device

(UMS agent)

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.

See UMS Server.

Core (scanning for device)

Auto ("high port")

(UDP)

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 (secure terminal)

30022

(TCP)

Device

(UMS agent)

UMS ServerSee UMS and Devices: Secure Terminal.

Core (shadowing)

5900 (TCP)

Device

(UMS agent)

UMS Console

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

Core (shadowing) via UMS Web App5900 (TCP)

Device

(UMS agent)

UMS ServerThe UMS Web App triggers the UMS Server to initiate a VNC session for shadowing. The VNC session is routed through the UMS Server; see UMS and Devices: Shadowing.

Core (unencrypted, no SSL)

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 (Universal Firmware Update)

443 (TCP)

IGEL download server (HTTP server at fwus.igel.com)

UMS Server


See UMS Contacting the Download Server to Check for New Updates.

Core (Universal Firmware Update)

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 (Wake on LAN)

9 (UDP)

Device

UMS Server

The UMS Server sends magic packets to the devices.

Core (with ICG)

8443 (TCP)

ICG (IGEL Cloud Gateway)

UMS Server

See Devices and UMS Server Contacting Each Other via ICG or UMS Server.

Core (with ICG)

8443 (TCP)

ICG (IGEL Cloud Gateway)

Device

See Devices and UMS Server Contacting Each Other via ICG.

High Availability (HA)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 Server
(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)
File synchronization between UMS Servers
High Availability (HA)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.

IMI

8443 (TCP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

3rd party component using IMI (IGEL Management Interface)

See IGEL Management Interface (IMI).

Sorted by Port Number

Port (Protocol)

Who is Listening?

Applications/Service Binding to Port

Who is Talking?

Applications/Services Initiating Communications

DescriptionRequired by UMS Feature

9 (UDP)

Device

UMS Server

The UMS Server sends magic packets to the devices.

Core (Wake on LAN)

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)

443 (TCP)

IGEL download server (HTTP server at fwus.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 Licensing Server.

Automatic License Deployment (ALD)

443 (TCP)

IGEL download server (HTTP server at fwus.igel.com)

UMS Server


See UMS Contacting the Download Server to Check for New Updates.Core (Universal Firmware Update)

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)

Device

(UMS agent)

UMS Console

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

Core (shadowing)

5900 (TCP)

Device

(UMS agent)

UMS ServerThe UMS Web App triggers the UMS Server to initiate a VNC session for shadowing. The VNC session is routed through the UMS Server; see UMS and Devices: Shadowing.Core (shadowing) via UMS Web App
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 / UMS Web App

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)

3rd party component using IMI (IGEL Management Interface)

See IGEL Management Interface (IMI).

IMI

8443 (TCP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

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

DeviceThe UMS provides license files for the devices; see UMS and Devices: File Transfer.Core (licenses)

8443 (TCP)

ICG (IGEL Cloud Gateway)

UMS Server

See Devices and UMS Server Contacting Each Other via ICG or UMS Server.

Core (with ICG)

8443 (TCP)

ICG (IGEL Cloud Gateway)

Device

See Devices and UMS Server Contacting Each Other via ICG.

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

See Devices Contacting UMS.

Core (direct device 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)

Device

(UMS agent)

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.

See UMS Server.

Core (scanning for device)

30022

(TCP)

Device

(UMS agent)

UMS ServerSee 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")

(UDP)

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

Auto ("high port")

(UDP)

UMS Server

(Windows: service IGELRMGUIServer; Linux: daemon igelRMServer)

Device

The device responds to a message sent by the UMS to check if the device is online.

The port number to be used is contained in the UDP packet sent by the UMS.

Core (online check)