> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.13/install-cortex-xsoar/system-requirements/port-requirements-for-cluster-communication.md).

# Port requirements for cluster communication

Review port requirements for Cortex XSOAR 8.13 On-prem.

The following ports are required for standalone (one VM) and a three-node cluster (three VMs).

| Port | Protocol | Purpose                                 |
| ---- | -------- | --------------------------------------- |
| 22   | TCP      | SSH communication                       |
| 8880 | TCP      | Node communication                      |
| 2049 | TCP      | Backup and restore server communication |
| 111  | TCP      | Backup and restore server communication |

### **Required control plane ports**

A Kubernetes cluster consists of a control plane and one or more worker nodes. For Cortex XSOAR, in standalone (one VM), the VM acts as both the control plane and a worker node. In multi-node clusters, the first three nodes act as both control plane and worker nodes, and any additional node added acts as a worker node.

The following ports are required for a control plane. They are open only between the nodes in the cluster. For standalone, none of these ports are required.

| Name                    | Port  | Protocol |
| ----------------------- | ----- | -------- |
| etcd client port        | 2379  | TCP      |
| etcd peer port          | 2380  | TCP      |
| Kubernetes API          | 6443  | TCP      |
| Kubelet API             | 10250 | TCP      |
| kube-scheduler          | 10257 | TCP      |
| kube-controller-manager | 10259 | TCP      |

### **Required worker node port**

The following port is required for a worker node. It is open only between the nodes in the cluster.

| Name                | Port        | Protocol |
| ------------------- | ----------- | -------- |
| kube nodeport range | 30000:32767 | TCP      |

### **Intra-node communication**

The following port is required for a multi-node cluster (three VMs). It is open only between the nodes in the cluster. It is not required for standalone.

| Name                       | Port  | Protocol |
| -------------------------- | ----- | -------- |
| Calico with IPv4 Wireguard | 51820 | UDP      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.13/install-cortex-xsoar/system-requirements/port-requirements-for-cluster-communication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.