API Doc
Search Docs...
⌘ K
OverviewDeploymentManagementOperationReferenceGlossary
    Observability 1.3.0
  • Deploying Observability>
  • Requirements

Planning the observability service network

Before deployment, it is necessary to plan the ports and IP addresses for the observability service.

Planning ports

To ensure the proper functioning of the observability service, the target end should have certain ports open when it is accessed by the source end. The open ports and their descriptions are as follows. By default, all the following ports are TCP ports unless specified otherwise, such as UDP ports.

Source Target Open TCP port on the target end 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 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 22 The AOC virtual machine imports images and provides startup services through this port.
User AOC virtual machine 80 The user accesses the AOC virtual machine through this port.
User Observability virtual machine 22 The user logs into the observability virtual machine through this port.
Physical hosts in associated clusters Observability virtual machine 80 The data collectors on the physical machines in the associated cluster report data to the observability service virtual machine through this port.
Physical hosts in associated clusters Observability virtual machine 22 During data migration, the migration data collector reports data to the observability service virtual machine through this port.
Observability virtual machine AOC virtual machine 80 The observability virtual machine obtains security policies and virtual machine information from the AOC virtual machine through this port.
Observability virtual machine Physical hosts in associated clusters 80 The observability virtual machine obtains configurations from clusters through this port.
AOC virtual machine Physical hosts in associated clusters 8686 AOC virtual machine performs health checks on physical machines in the associated cluster through this port.
AOC virtual machine Physical hosts in associated clusters 10000 AOC virtual machine deploys distributed network data collectors on physical hosts in the associated cluster through this port.
AOC virtual machine Physical hosts in associated clusters 3260, 3261 When deploying an observability service, the AOC virtual machine uploads images through this port.

Planning IP addresses

The observability virtual machine needs to connect to AOC and associated clusters through the VM network. Therefore, a VM network that can connect to the management network needs to be created in advance in the target cluster.

You need to plan an IP address, subnet mask, and gateway for each observability virtual machine, and ensure that the IP address is connected to AOC's IP address and the management IP addresses of the cluster to be associated. Remember to apply for the IP address in advance.

Note:

The IP address cannot overlap with any IP addresses 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
  • 0.0.0.0/8