Overview
This article explains the ports to be used by components and the ports to be opened on the server related to FineOps FineBI projects.
Component-Occupied Port
There are many components in the O&M projects, and their operation will occupy some server ports.
Before deployment, ensure that the default mapping port is not in use. If it is already in use, arrange other free ports.
Note:Ensure that the ports of all servers are consistent and the port configuration meets the requirements since the components are randomly assigned during installation.
Component | Default Port Number | Description |
|---|---|---|
| bi-web | 8080 | Project-occupied port |
| 12100 | Port for the crash handling tool | |
7800 7830 7840 7850 7870 | Port for TCP communication in the cluster | |
| 50050 50051 50100 50101 50200 | Port for data synchronization in the cluster | |
bi-engine-worker (If multiple worker components need to be installed on one server, the default port numbers increase sequentially.) | 9001 | Port for calling the bi-engine-worker component |
| 9004 | Port for the monitor | |
| 13777 | Port for obtaining the monitoring information | |
| bi-engine-master | 8000 | Component-occupied port |
| 13787 | Port for obtaining the monitoring information | |
bi-minio | 9008 9009 | Port occupied by the client and the server |
| Ops_agent | 9070 | Component-occupied port |
filebeat | / | No ports occupied |
| nginx | 80 | Component-occupied port Note: |
redis | 6379 | Component-occupied port |
mysql | 3306 | Component-occupied port |
| minio | 9000 9001 | Port occupied by the client and the server |
elasticsearch | 9200 | Component-occupied port |
Networking
To ensure normal access to O&M projects and smooth O&M project deployment and monitoring via FineOps, certain server ports must be opened for use in different scenarios.
Extranet and O&M Project
| Description | Extranet | Relation | O&M Project |
|---|---|---|---|
| For the admin to access O&M projects | O&M personnel (unlimited IP address) | Access -> | Project nginx
|
| For reading/writing data | Business database | <-Access-> | Project nginx
|
| For FineOps to pull images from the cloud repository | FanRuan Cloud Image Repository (fineops-registry.cn-hangzhou.cr.aliyuncs.com:443) | <- Access | registry: 5000 |
O&M Project
Ensure that all the mentioned component-occupied ports can intercommunicate with each other.
FineOps and O&M Project
| Description | FineOps | Relation | O&M Project |
|---|---|---|---|
| Basic O&M | FineOps nginx
| <- Access | Each bi-web node of the project: 8080 |
| Each worker node of the project: 8080 | |||
| The master node of the project | |||
| Transmitting the server and component indicator information of the project to FineOps | FineOps nginx
| <- Access | The ops-agent component on every server of this project (on project nodes and cluster component nodes): 9070 |
Tracing | FineOps skywalking_oap: 11800 and 12800 | <- Access | Each bi-web node of the project: 8080 |
| Each worker node of the project: 8080 | |||
The master node of the project | |||
| Tracing | FineOps skywalking_oap: 11800 and 12800 | <- Access | Project nginx
|
| Pulling components from the image repository of FineOps for project deployment | registry: 5000 | <- Access | Project nodes and cluster component nodes of unlimited servers |
Previous：Confirming Server Configuration of the FineBI Project