Open Ports and Services
The cnSGW-C uses different ports for communication. The following table describes the default open ports and the associated services.
Port |
Type |
Service |
Usage |
---|---|---|---|
22 |
tcp |
SSH |
SMI uses TCP port to communicate with the virtual machines. |
53 |
tcp |
domain |
DNS port. |
80 |
tcp |
HTTP |
SMI uses TCP port for providing Web access to CLI, Documentation, and TAC. |
111 |
tcp |
rpcbind |
Open Network Computing Remote Procedure Call. |
179 |
tcp |
bgp |
Border Gateway Protocol (BGP) |
443 |
tcp |
SSL/HTTP |
SMI uses TCP port for providing Web access to CLI, Documentation, and TAC. |
2379 |
tcp |
etcd-client |
CoreOS etcd client communication. |
6443 |
tcp |
http |
SMI uses port to communicate with the Kubernetes API server. |
7472 |
tcp |
unknown |
speaker, used by Grafana. |
8083 |
tcp |
us-srv |
Kafka connects REST interface. |
8850 |
tcp |
unknown |
udp-proxy |
8879 |
tcp |
unknown |
udp-proxy |
9100 |
tcp |
jetdirect |
SMI uses TCP port to communicate with the Node Exporter. Node Exporter is a Prometheus exporter for hardware and OS metrics with pluggable metric collectors. It allows you to measure various machine resources, such as memory, disk, and CPU utilization. |
10250 |
tcp |
SSL/HTTP |
SMI uses TCP port to communicate with Kubelet. Kubelet is the lowest level component in Kubernetes. It is responsible for what is running on an individual machine. It is a process watcher or supervisor focused on active container. It ensures the specified containers are up and running. |
10251 |
tcp |
- |
SMI uses TCP port to interact with the Kube scheduler. Kube scheduler is the default scheduler for Kubernetes and runs as part of the control plane. A scheduler watches for newly created pods that have no node assigned. For every pod that the scheduler discovers, the scheduler becomes responsible for finding the best node for that pod to run on. |
10252 |
tcp |
apollo-relay |
SMI uses this TCP port to interact with the Kube controller. The Kubernetes controller manager is a daemon that embeds the core control loops shipped with Kubernetes. The controller is a control loop that watches the shared state of the cluster through the API server and makes changes to move the current state to the desired state. |
10256 |
- |
HTTP |
SMI uses TCP port to interact with the Kube proxy. Kube proxy is a network proxy that runs on each node in your cluster. Kube proxy maintains network rules on nodes. These network rules allow network communication to your pods from network sessions inside or outside of your cluster. |
50051 |
tcp |
unknown |
gRPC service listen port. |
53 |
udp |
domain ISC BIND (Fake version: 9.11.3- 1ubuntu1.9- Ubuntu) |
DNS port |
111 |
udp |
rpcbin |
Open Network Computing Remote Procedure Call |
2123 |
udp |
gtpc |
GTP control |
8805 |
udp |
pfcp |
Packet Forwarding Control Protocol (PFCP) |