Contact Free trial Login

Network Prerequisites

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.

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 and uses the following source and destination descriptions:

Anypoint Platform PCE nodes

Nodes that are members of the cluster.

installer node

Node on which the installation was started.

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 1. Port Configuration Requirements
Protocol Port/Range Purpose Source Destination

TCP/UDP

53

Internal cluster DNS

localhost

localhost

TCP

2379, 2380, 4001, 7001

etcd distributed database

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

4242

Installer

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

6443

Kubernetes API server

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP/UDP

7496

Serf RPC agent

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

7373

Serf RPC agent

localhost

localhost

TCP

10248, 10250

Kubernetes Kubelet

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

10249

Kubernetes kube-proxy

localhost

localhost

TCP

10251, 10252

Kubernetes controller-manager and scheduler

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

5000

Docker registry

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

3009-3012

Cluster control plane

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

3022

Cluster control plane

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

3023-3026

Cluster control plane

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

7575

Cluster control plane

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

7580

Cluster control plane monitoring endpoint

localhost

localhost

TCP

6060

Cluster control plane profiling endpoint

localhost

localhost

TCP

30000-32767

Internal services port range

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

61009-61010

Installer port ranges (only used during install)

Anypoint Platform PCE nodes

installer node

TCP

61022-61024

Installer port ranges (only used during install)

Anypoint Platform PCE nodes

installer node

TCP

61025

Installer port ranges (only used during install)

localhost

installer node

UDP

8472

Overlay VXLAN network

Anypoint Platform PCE nodes

Anypoint Platform PCE nodes

TCP

32009

Ops Center Admin UI

Load Balancer

Anypoint Platform PCE nodes

TCP

30080

HTTP public access

Load Balancer

Anypoint Platform PCE nodes

TCP

30443

HTTPS public access

Load Balancer

Anypoint Platform PCE nodes

TCP

30889

Mule Runtime Websocket

Load Balancer

Anypoint Platform PCE nodes

TCP

30883

Mule Runtime Authentication Service (for certificate renewals)

Load Balancer

Anypoint Platform PCE nodes

You can use netcat or a similar utility to verify port configuration.

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.

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 Private Cloud.

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 Private Cloud.

Synchronize Clocks

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

Was this article helpful?

πŸ’™ Thanks for your feedback!

Edit on GitHub