---
schema_version: "1"
id: a29225cc72095f8f36e935a15d5e0fee2ef3026490eb674b5d6f9e72f6b72980
title: Network Prerequisites
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/private-cloud/3.2/prereq-network.md
canonical_url: https://docs.mulesoft.com/private-cloud/3.2/prereq-network
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 28c3a7c79e10f3c321ce50994b6a3cbbc89cc3be33be80edb23496a5c373c180
description: MuleSoft Documentation Site
release: "3.2"
latest: false
---
---
product: Anypoint Platform Private Cloud Edition
version: 3.2
---

# Network Prerequisites

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

To ensure the performance and stability of Anypoint Platform Private Cloud Edition (Anypoint
Platform PCE), every node in your Anypoint Platform PCE environment must meet the network
requirements described in this topic.

> [!IMPORTANT] Before you install Anypoint Platform PCE, your infrastructure team must review each
> of the following sections and verify that your environment meets the stated network requirements.
> If needed, contact your MuleSoft representative for assistance.

## Verify Static IPs

All nodes in the cluster must have static private IPv4 assigned to them, and these must persist
after restarts. If IP addresses are not persistent between reboots, the cluster can fail.

## Verify VXLAN

The version of Kubernetes supported by Anypoint Platform PCE uses an overlay VXLAN and UDP transport
to encapsulate traffic. There is direct communication between cluster components.

The following table lists the ports used for inter-host communication. The table uses the following
source and destination descriptions:

- Anypoint Platform PCE nodes: Nodes that are members of the cluster.

- Installer node: The node on which you started the installation.

- Load Balancer: Any source that is outside the cluster.

- localhost: The port that is used only within the host where the request started.

You must ensure that all of the following ports are configured correctly on all nodes.

<table><caption>Table 1. Port Configuration Requirements</caption> <colgroup><col> <col> <col> <col> <col></colgroup><thead><tr><th>Protocol</th><th>Port/Range</th><th>Purpose</th><th>Source</th><th>Destination</th></tr></thead><tbody><tr><td><p>TCP/UDP</p></td><td><p>53</p></td><td><p>Internal cluster DNS</p></td><td><p>localhost</p></td><td><p>localhost</p></td></tr><tr><td><p>TCP</p></td><td><p>2379, 2380, 4001, 7001</p></td><td><p>etcd distributed database</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>4242</p></td><td><p>Installer</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>6443</p></td><td><p>Kubernetes API server</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>9443</p></td><td><p>HAProxy to load balance Kubernetes API Server</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>9100</p></td><td><p>Prometheus node-exporter</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>10248, 10250</p></td><td><p>Kubernetes Kubelet</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>10249, 10256</p></td><td><p>Kubernetes kube-proxy</p></td><td><p>Anypoint Platform PCE</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>10251-10252</p></td><td><p>Kubernetes controller-manager and scheduler</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>10257-10259</p></td><td><p>Kubernetes controller-manager and scheduler (secure)</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>5000</p></td><td><p>Docker registry</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>3009-3012</p></td><td><p>Cluster control plane</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>3022</p></td><td><p>Cluster control plane</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>3023-3025</p></td><td><p>Cluster control plane</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>7575</p></td><td><p>Cluster control plane</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>7580</p></td><td><p>Cluster control plane monitoring endpoint</p></td><td><p>localhost</p></td><td><p>localhost</p></td></tr><tr><td><p>TCP</p></td><td><p>6060</p></td><td><p>Cluster control plane profiling endpoint</p></td><td><p>localhost</p></td><td><p>localhost</p></td></tr><tr><td><p>TCP</p></td><td><p>30000-32767</p></td><td><p>Internal services port range</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>61009-61010</p></td><td><p>Installer port ranges (only used during install)</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>installer node</p></td></tr><tr><td><p>TCP</p></td><td><p>61022-61024</p></td><td><p>Installer port ranges (only used during install)</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>installer node</p></td></tr><tr><td><p>TCP</p></td><td><p>61025</p></td><td><p>Installer port ranges (only used during install)</p></td><td><p>localhost</p></td><td><p>installer node</p></td></tr><tr><td><p>UDP</p></td><td><p>8472</p></td><td><p>Overlay VXLAN network</p></td><td><p>Anypoint Platform PCE nodes</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>32009</p></td><td><p>Ops Center Admin UI</p></td><td><p>Load Balancer</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>30080</p></td><td><p>HTTP public access</p></td><td><p>Load Balancer</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>30443</p></td><td><p>HTTPS public access</p></td><td><p>Load Balancer</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>30889</p></td><td><p>Mule Runtime Websocket</p></td><td><p>Load Balancer</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr><tr><td><p>TCP</p></td><td><p>30883</p></td><td><p>Mule Runtime Authentication Service (for certificate renewals)</p></td><td><p>Load Balancer</p></td><td><p>Anypoint Platform PCE nodes</p></td></tr></tbody></table>

You can use netcat or a similar utility to verify port configuration.  
Anypoint Platform PCE nodes need to hit the platform API address on the load balancer via HTTPS.

## Enable Required Ports

- You must enable TCP ports 53, 3011, and 3012 on all nodes to allow communication with the database
  cluster.

- If you plan to use the GUI installer to install Anypoint Platform PCE, you must enable port 61009.

## Verify NAT Traffic Requirements

In some situations, the Kubernetes overlay network uses NAT. NAT requires that nodes be able to send
and receive packages with a source and destination different from the node’s internal IP.

Any software that monitors the network traffic must be tuned to allow this type of network
interaction.

## Disable OS NetworkManager Services

In some operating systems, like RHEL/CentOS 8.4, NetworkManager includes two extra services:
`nm-cloud-setup.service` and `nm-cloud-setup.timer`. These services add routing tables that
interfere with the configuration of the Kubernetes Container Network Interface (CNI) plugin. If
those services exist, disable them and restart the node before proceeding with the installation.

## Verify SMTP Server Requirements

Your network must include an SMTP server to manage email alerts that are triggered by the platform.
Anypoint Platform PCE must be connected to this SMTP server.

For additional information, refer to the instructions in
[Configure SMTP in Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/3.2/access-management-SMTP).

## Verify External Identity Provider Configuration and Client Management

Your network must include an external identity provider that is compatible with LDAP, OpenIDConnect,
or SAML. To configure an External Identity Provider for user SSO (LDAP, OpenIDConnect, and SAML) or
for external client management as OpenID Connect, the cluster must be able to access the external
identity provider endpoint.

For additional information, refer to the instructions in
[Configure an External Identity Provider in Anypoint Platform PCE](https://docs.mulesoft.com/private-cloud/3.2/install-config-ldap-pce).

## Synchronize Clocks

Ensure that the clocks on all servers are synchronized. Unsynchronized clocks can cause problems
with platform communications.

## See Also

- [Environment Prerequisites](https://docs.mulesoft.com/private-cloud/3.2/prereq-platform)

- [Hardware Prerequisites](https://docs.mulesoft.com/private-cloud/3.2/prereq-hardware)

- [Software Prerequisites](https://docs.mulesoft.com/private-cloud/3.2/prereq-software)

- [NFS Server Prerequisites](https://docs.mulesoft.com/private-cloud/3.2/verify-nfs)

- [Preinstallation Verification](https://docs.mulesoft.com/private-cloud/3.2/prereq-gravity-check)