Communication Ports Used By ControlUp: Hybrid Cloud
-
Print
-
DarkLight
-
PDF
Communication Ports Used By ControlUp: Hybrid Cloud
-
Print
-
DarkLight
-
PDF
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 URLs:
| ControlUp component in your environment | Purpose | URLs |
|---|---|---|
| ControlUp Monitors ControlUp Real-Time Console |
Real-time cloud configuration (VDIs & data center) |
fe1.controlup.com fe2.controlup.com fe3.controlup.com fe4.controlup.com rt-app.controlup.com cu-ca-us.controlup.com cu-ca-eu.controlup.com |
| ControlUp Monitors | Provide real-time data to Solve | mp.controlup.com |
| ControlUp Monitors | Upload historical data for Insights and Solve | s3.amazonaws.com s3.eu-central-1.amazonaws.com insights-hec.controlup.com |
| Scoutbees Custom Hive | Receive configuration, task lists (API) and return scout results (Websockets) | https://api.scoutbees.io https://api.eu.scoutbees.io (EU Region) Websockets: https://ws.scoutbees.io https://ws.eu.scoutbees.io (EU Region) WebSocket - Default Port: 8008 Encapsulated WebSocket connection (via HDX protocol) from Custom Hive to VDAs. Relevant for StoreFront type scouts. HTTP/S - TCP Port 80 / 443:
|
| PCs, macOS or thin clients monitored with Edge DX | Per tenant / customer URL: [tenant name].sip.controlup.com downloads.sip.controlup.com |
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.scoutbees.io https://app.eu.scoutbees.io (EU Region) |
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:
| Source Component | Destination Component | Type / Protocol | Remote Port | Details |
|---|---|---|---|---|
| Console | Agent/Data Collector | TCP / WCF | 40705 | Communication between Console and Agent |
| Console | Agent/Data Collector | TCP / RPC, WMI, SMB | 135-139, 445 | Agent deployment and upgrades via Agent upgrades via Console |
| Console | Monitor | TCP | 40706 | |
| Console | Monitor | TCP / RPC, WMI, SMB | 135-139, 445 | Monitor deployment via Console |
| Console | Domain Controller | LDAP | ||
| Console | Data Collector | TCP / WCF | 40705 | Communication between Console and Data Collector |
| Data Collector | External resource | HTTPS | ||
| Monitor | Monitor | TCP | 40706 | Inter-Monitor communication |
| Monitor | Data Collector | TCP | 40705 | |
| Monitor | Domain Controller | LDAP | 389 |
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?