{{ $t('productDocDetail.updateTime') }}: 2025-12-26

Introduction

A connectivity domain is a core functional component on SCP, which is designed to enable network connectivity and logical partition isolation among different resource pools. It aims to construct communication channels among resource pools within the virtual network environment through IP address resource planning. Meanwhile, it enables granular control over network traffic within the domain. Connectivity domains enable communications for VPCs and classic networks across resource pools. This ensures efficient interconnectivity between business systems in different resource pools while restricting unauthorized cross-pool access, which establishes a secure and manageable network environment within multi-resource-pool architectures.

The feature fixed the issue of complex network interconnection and insufficient isolation in traditional multi-resource-pool architectures by centrally managing resources such as IP ranges, subnet masks, and gateways. It provides flexible network connectivity and isolation solutions for enterprise network architectures requiring multi-resource-pool collaboration.

Applicable Scenarios

• Cross-pool business interconnectivity in multi-resource-pool environments: An enterprise deploys resource pools with x86 and c86 architectures. The ERP system runs in the X86 resource pool, while the big data analysis platform runs in the resource c86 pool. To achieve VPC connectivity between these two resource pools, you can create a connectivity domain. This enables data interaction between the ERP system and the big data analysis platform across pools, while unauthorized access from other resource pools can be isolated (Example: Access from a test pool), ensuring the security of core business data.

• Cloud services in hybrid resource pools: A cloud service provider has multiple resource pools (Example: Intel and Hygon resource pools) to provide cloud services across resource pools for tenants. You can use a connectivity domain to achieve VPC connectivity across Intel and Hygon resource pools for a tenant. The tenant can flexibly allocate computing resources from different pools based on business requirements without network communication issues among resource pools.

• Cross-resource-pool isolation with multiple tenants: In a cloud platform with multiple tenants, each tenant's services may be distributed across multiple resource pools. You can create an independent connectivity domain for each tenant, which enables network connectivity for their services across resource pools (Example: Communication between a web server in an X86 resource pool and a database in a c86 resource pool of tenant A). Meanwhile, access across resource pools for different tenants can be strictly isolated. This prevents unauthorized network access between tenant A's resource pool and tenant B's resource pool.

Prerequisites

1. Network Planning and Preparation

• The overall enterprise network topology design must be complete. The following must be specified: The number of connectivity domains to be created, the business scope covered by each connectivity domain, and the communication requirements across connectivity domains.

• The network type (VPC or classic network) to be associated with the connectivity domain must be specified, and the corresponding networks must already be created. (For details on creating VPC, see section 1 of the VPC Network Management Manual. For details on creating classic network, see section 2 of the Tenant Network Management Manual.)

2. IP Resource Preparation

3. Equipment and Permission Preparation

• The administrator on SCP must have admin permissions for SCP and can access the Network Deployment module.

• To associate the connectivity domain with an edge, the edge must already be created and in normal status. (For details on creating edge, see section 1 of the Physical Egress Creation and Management Manual.)

Constraints and Restrictions

• A connectivity domain can be associated with up to 3 networks (VPC or classic network), and the associated networks must be in the same resource pool.

• The IP range of a connectivity domain cannot overlap with the IP ranges of other connectivity domains, VPC subnets, or classic networks on the platform. Otherwise, network conflicts may occur.

• After a connectivity domain is created, its IP range and netmask cannot be modified. To adjust them, the connectivity domain must be deleted and recreated.

• Up to 20 connectivity domains can be created within each resource pool (The specific allowed number is subject to the platform version).

Precautions

• Before a connectivity domain is created, it is recommended to scan the planned IP range by using an IP scanning tool (Example: Advanced IP Scanner) to make sure that the IP addresses are not in use, thereby preventing address conflicts.

• If cross-domain communication is required for a connectivity domain, cross-domain communication policies (Example: ACL rules, security group configurations) must be planned in advance, and you can configure it in the network security module after the connectivity domain is created.

• When the gateway IP address is configured, make sure that the gateway device is properly deployed and can connect to the network devices associated with the connectivity domain. Otherwise, nodes within the connectivity domain will be unable to access external networks.

• After creation, it is recommended to deploy a test node within the connectivity domain to verify the functionality of IP address assignment, gateway connectivity, and DNS resolution.

Steps

Step 1.Log in to SCP and go to the Network Deployment > Connectivity Domains page.

Step 2.Click the creation button in the upper-right corner of the page. The connectivity domain creation pop-up window appears.

Step 3.In the basics section, configure the following fields:

• Connectivity Domain Name: Specify a name. It must contain business attributes. The recommended format is Business Type - Connectivity Domain – Number. Example: R&D Dept - Connectivity Domain - 01.
• Resource Pool: Select the resource pool where the connectivity domain resides in the drop-down list (Example: Intel Xen Cluster (x86)).
• Description (Optional): Enter information such as the business purpose and scope of the connectivity domain to facilitate later management. Example: Network zone for the R&D department’s core business systems.

Step 4.In the IP configuration section, configure the following fields:

• IP Range: Enter the planned private IP address range in the format of xxx.xxx.xxx.0/xx. Example: 192.168.10.0/24
• Netmask: Automatically generated based on the IP range. It can be manually modified as needed, which must match the IP range. Example: 255.255.255.0
• Gateway IP Address: Enter the planned gateway IP address. Example: 192.168.10.1
• DNS Server: Enter 1 to 2 DNS server addresses. Separate multiple addresses with commas. Example: 10.0.0.10,114.114.114.114

Step 5.In the associated network section, click the addition button. Select the VPCs or classic networks to be associated. Up to 3 networks can be associated. Click the confirmation button to finish the association.

Step 6.To configure static IP reservation, click addition button in the static IP reservations section. Enter the IP address range to be reserved (Example: 192.168.10.10-192.168.10.20) and remarks (Example: Static IP addresses for key servers), and click the confirmation button.

Step 7.After all configurations are complete, click the confirmation button at the bottom of the pop-up window. The connectivity domain will start to create. Upon successful creation, you can view information of the connectivity domain such as its name, IP range, and associated networks in the connectivity domain list.