Firewall enabled ports for clustered OVA deployments
In a clustered OVA deployment of API Connect, specific ports must be configured for communication between members of each API Connect subsystem.
OVA deployments require the common ports that are listed in Firewall requirements on Kubernetes. When the VMs are clustered, additional ports are used for communication between the members of the subsystems in the cluster.
All ports must be enabled inbound and outbound.
| Subsystem | Ports |
|---|---|
| Ports that must be open between all subsystem VMs | 442, 2379, 2380, 6443, 6444, 9099, 10248, 10249, 10250,10251, 10252, 10254, 10256,10257,
10259 These ports must be open between all servers within a given subsystem. For example, from management server to management server, or from portal server to portal server, or from analytics server to analytics server. These ports are not used for communication between subsystems. You
might need additional ports for Kubernetes-proxied services. The default range is |
| Additional ports that must be open between Management Service VMs | Port 8088 is required if the Automated testing behavior application is deployed for the Management Service VMs. |
| Additional ports that must be open between Developer Portal VMs | 3009, 3010, 3306, 3307, 4443, 4444, 4567, 4568, 30865 |
| Additional ports that must be open between Gateway Service VMs | 16380, 16381, 26380, 26381 |
| Additional ports that must be open between Analytics VMs | No additional ports are needed. |
These internal ports are not used for communication between VMs. Ensure that they are open on the VM server locally.
| Subsystem | Ports |
|---|---|
| Reserved local ports on all subsystem VMs | 8383, 8686, 8080, 8443, 30000:59999 |
| Management Service VMs | 2000, 2001, 2002, 2005, 2006, 2007, 2008, 2022, 3003, 3004, 3006, 3007, 3011, 3023, 4150, 4151, 4171, 4222, 5432, 6222, 7777, 8084, 8222, 8404 |
| Portal Service VMs | 3058, 3059, 3060, 3061 |
| Analytics VMs | 4443, 5000, 5601, 9200, 9300 |