Communication Ports Used By ControlUp: Hybrid Cloud (EU Customers)
  • Dark
    Light
  • PDF

Communication Ports Used By ControlUp: Hybrid Cloud (EU Customers)

  • Dark
    Light
  • PDF

image.png

Outbound Connections

Devices and servers used by ControlUp, providing configuration interface, data aggregration, upload and authorization validation for Solve access, and other services. This requires TCP 443 / SSL outbound connectivity to the following IPs / URLs:

DNS IP Purpose
fe1.controlup.com 52.31.169.19 Real-Time DX login services
fe3.controlup.com 52.31.158.49 Real-Time DX login services
rt-app.controlup.com 18.200.38.56
52.212.202.250
Real-Time DX configuration services
mp.controlup.com 54.145.10.60
50.19.173.115
3.229.60.149
Real-Time DX <> Solve query engine
s3.eu-central-1.amazonaws.com Real-Time DX / Insights historical data uploads
cu-ca-eu.controlup.com Real-Time DX Centralized Auditing services
uploader-eu-central-1.controlup.com 3.69.222.61
3.120.161.2
3.70.55.18
Real-Time DX / Insights historical data uploads
insights-hec.controlup.com HTTP Event Collector (HEC) Endpoint - telemetry data from ControlUp Monitors

Web Browser Access

Administrators and other ControlUp users need to have web browser access (TCP port 443, https) to the following addresses:

Destination Details
https://solve.controlup.com ControlUp Solve Portal
https://insights.controlup.com ControlUp Insights Portal
https://[tenant-name].sip.controlup.com
https://maps.google.com
Edge DX Portal
https://app.eu.scoutbees.io Scoutbees Portal

Connectivity to Devices and Services in Your Network

In most networks, the following will be required for proper functioning of the ControlUp Monitors and virtual machines being monitored:

Destination Type Port Protocol Details
ControlUp Agent TCP 40705 WCF Incoming TCP / WCF traffic from Console and Monitor cluster to ControlUp Agents
ControlUp Monitor TCP 40706 Used for Console ⇔ Monitor and internal Monitor cluster communication
ControlUp Monitor TCP 135 - 139, 445 RPC / WMI / SMB Used for monitor deployment via the console
Domain Controllers TCP 389 LDAP LDAP communication from the Real-Time Console and ControlUp Monitors with Domain Controllers

The following is a comprehensive list of services that you want to monitor with ControlUp. This table includes information on the default ports and protocols. According to the case, there can be a source such as ControlUp Monitors, Real-Time Console, or Scoutbees Hives.

There is no requirement to configure all and it depends on what you want to monitor:

Destination Type Port Protocol Details
Citrix XenDesktop Controllers TCP 80 HTTP Communication with XenDesktop Infrastructure
Citrix XenServer Pool Master/Hosts TCP 80 HTTP Communication with XenServer Infrastructure (and RRD communications)
ControlUp Agent TCP 135 - 139, 445, 49152-65535 RPC / WMI / SMB Agent deployment and upgrades via the console Certain OOB actions, such as restarting the agent
Data Collector TCP 40705 WCF ControlUp Console - Data collector port
Domain Controllers TCP 389 LDAP LDAP communication with Domain Controllers
NetScalers TCP 443 / 80 HTTP(S) Depending on what the administrator configured
Nutanix/AHV TCP 9440 Communication with Nutanix Infrastructure
VMware Horizon Connection Server TCP 443 HTTPS Communication with Horizon Infrastructure
VMware vCenter Server TCP 443 HTTPS Communication with vSphere Infrastructure
Linux Client TCP 22 SSH Communications with Linux machines

Connection Requirements for APIs

Depending on if you plan to use the respective API, enable the following API URIs:

Destination Type Port Protocol Details
*.cloud.com TCP 443 HTTPS Communication with Citrix Cloud
https://sts.amazonaws.com
https://ec2.amazonaws.com
TCP 443 HTTPS AWS API
https://management.azure.com TCP 443 HTTPS Azure API
edgedx-functions.azurewebsites.net TCP 443 HTTPS Creating tenant for Edge DX

Was this article helpful?