API Doc
Search Docs...
⌘ K
OverviewDeploymentManagementOperationReferenceGlossary

Ports occupied by file storage internal services

To ensure the normal use of AFS services or functions, make sure that the following ports of the file controller are available or open, and ensure that the ports used by the service are not occupied by other services.

Service name Network used Ports used
sfs-agent File storage network 20045
sfs-meta File storage network 20010, 20015
sfs-data File storage network 20020, 20025
sfs-ganesha File access network 2049, 2050, 2051
File storage network 20030, 20031, 20035
File management network 9587
sfs-manager File storage network 20002
sfs-cloud-provider File storage network 20005, 20006
ntpm File management network 20003
obs-agent File management network 8681, 8682, 8685, 8429
traefik File storage network 20001
kube-etcd

File management network

File storage network

2379, 2380
kube-apiserver

File management network

File storage network

6443
kube-vip File management network 2112
node-exporter File management network 9100
cadvisor File management network 8080
sshd

File management network

File storage network

22
rpcbind File access network 111

Note:

The sfs-cloud-provider service of AFS relies on the meta proxy service provided by zbs-chunkd of ACOS. To ensure the normal operation of AFS services or functions, make sure that port 10206 is open on the hosts of the ACOS (AVE) cluster to which the file controllers are deployed.