Before deployment, you need to plan the ports and IP addresses for observability services.
To ensure the proper functioning of an observability service, when the source accesses the target, the corresponding port on the target must be open. The ports to be opened and their descriptions are as follows. All ports mentioned below are TCP ports by default unless otherwise specified (e.g. UDP ports).
| Source | Target | Port | Description |
|---|---|---|---|
| AOC virtual machine | Observability virtual machine | 8686 | The AOC virtual machine performs health checks on the observability virtual machine through this port. |
| AOC virtual machine | Observability virtual machine | 80, 443 | The AOC virtual machine sends API requests to the observability virtual machine through this port, and all components in the observability virtual machine provide services through this port. |
| AOC virtual machine | Observability virtual machine | 10022 | The AOC virtual machine imports images and provides startup services through this port. Note: If the observability service is upgraded from an earlier version to this version, port 22 will be used. |
| Client | AOC virtual machine | 80 | The client accesses the AOC virtual machine through this port. |
| Client | Observability virtual machine | 10022 | The client logs in to the observability virtual machine through this port. Note: If the observability service is upgraded from an earlier version to this version, port 22 will be used. |
| Node in the associated cluster[1] | Observability virtual machine | 443 | The data collector on the node in the associated cluster reports data to the observability service virtual machine through this port. |
| Node in the associated cluster[1] | Observability virtual machine | 10022 | During data migration, the migration data collector reports data to the observability service virtual machine through this port. Note: If the observability service is upgraded from an earlier version to this version, port 22 will be used. |
| Observability virtual machine | AOC virtual machine | 443 | The observability virtual machine obtains security policies and virtual machine information from the AOC virtual machine through this port. |
| Observability virtual machine | Node in the associated cluster[1], management VIP of the associated cluster | 80, 443 | The observability virtual machine obtains configuration information from the cluster through this port. |
| AOC virtual machine | Node in the associated cluster[1] | 10000 | The AOC virtual machine deploys the distributed network data collector on the node in the associated cluster through this port. |
| AOC virtual machine | Node in the associated cluster[1] | 3260, 3261 | During deployment, the AOC virtual machine uploads images through this port. |
Information:
[1]: Nodes in the associated cluster include nodes running ACOS (AVE) or ACOS (VMware ESXi), depending on the type of the associated cluster.
An observability virtual machine needs to connect to AOC and the management networks of the associated clusters through the VM network. Therefore, before the deployment, you need to create a VM network that can connect to the cluster management network in the cluster where the service will be deployed.
Plan an IP address, a subnet mask, and a gateway for each observability virtual machine, and ensure that this IP address is connected to the AOC IP address and the management IP addresses of the clusters to be observed. Apply for the IP addresses from the network administrator in advance.
Note:
The IP addresses cannot overlap with any IP address within the following CIDR blocks:
- 169.254.0.0/16
- 240.0.0.0/4
- 224.0.0.0/4
- 198.18.0.0/15
- 127.0.0.0/8
- 10.4.0.0/24
- 0.0.0.0/8
