Port configuration

To support communication between Turbonomic and your intended targets, Turbonomic must be able to reach the targets through the following ports.

Note:

For Turbonomic SaaS deployments, if you are using the secure client to manage targets, the following ports need to be opened to the secure client instead of the SaaS server.

Applications and databases

Target

Port

Apache Tomcat

1009

AppDynamics

443

DataDog

443

Dynatrace

443

WebSphere

8879, 8880

Instana

443

JBoss

9990

JVM/Java

9875

SQL Server

1434, 1433

MySQL

3306

New Relic

443

Oracle

1521

Oracle WebLogic

7001

Container Platform

Target

Port

Kubernetes kubelet (with Kubeturbo)

10250 or 10255

Turbonomic (through Kubeturbo using WSS)

443

Fabric and network

Target

Port

HPE OneView

80, 443

Cisco UCS

80, 443

Guest OS process

Target

Port

SNMP (Linux/UNIX)

161

WMI (Windows)

135 + dynamic ports 49152 - 65535

Hyperconverged

Target

Port

Cisco HyperFlex

433

Nutanix

9440

Hypervisors

Target

Port

IBM PowerVM

80, 443

Microsoft Hyper-V

5985, 5986

Microsoft Hyper-V (Kerberos)

88

VMware vCenter (Monitoring)

443

VMware vCenter (Tags)

10443

VMware vCenter (Kerberos)

88

Orchestrator

Target

Port

Action Script

22

Flexera One

443

ServiceNow

443

Private cloud

Target

Port

Microsoft VMM

5985, 5986

Public cloud

Target

Port

All public cloud targets

443

Secure client

Target

Port

Turbonomic secure client to SaaS server

443

Storage

Target

Port

EMC Storage

5988, 5989, 443

HPE 3PAR

5988, 5989, 8080

IBM FlashSystem

7443, 443

NetApp

80, 443

Pure Storage

80, 443

Virtual desktop infrastructure

Target

Port

VMware Horizon

443