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

Introduction

An elastic IP pool on SCP is a collection of public IP addresses purchased from an ISP. It enables access to cloud resources from the internet. Tenants or tenant members can connect devices such as VMs and routers to external networks through elastic IP addresses. IPv4 elastic IP addresses can be directly bound to and unbound from VMs, routers, and other devices in a VPC. IPv6 elastic IP addresses can be bound to and unbound from devices if IPv6 is enabled for these devices after IPv6 global unicast is enabled for a subnet. An elastic IP pool needs to be associated with an edge, so that resources in the VPC connected to that edge can use elastic IP addresses within that range. This enables flexible public network access control.

Application Scenarios

• Public access to VM: To provide external web services (such as official website services) using a VM, bind the VM to an elastic IP address, so that the VM will be assigned a public IP address and allow access from internet users.

• Multi-tenant public resource isolation: A cloud service provider can allocate independent elastic IP pools to different tenants, so that each tenant's cloud resources use dedicated elastic IP addresses. This ensures public resource isolation for tenants and facilitates independent management of bandwidth and traffic by IP pool.

• IPv6 network interconnection: To deploy a business system that supports IPv6 (such as an app catering to international users), create an IPv6 elastic IP pool with BGP configuration for interconnection and communication with external IPv6 networks.

Line Creation

1. Introduction

Line types are used to classify elastic IP pools. You can set different line types (such as direct line, internet, and office network) for elastic IP pools based on your business requirements or the pools' characteristics. This optimizes elastic IP pool management and business scenario adaptability.

2. Application Scenarios

• Business scenario differentiation: To accurately match elastic IP pools with business scenarios, such as internet business like e-commerce platforms and internal business like financial systems connecting to banks, set the line type of the elastic IP pool for internet business to "Internet" and that of the elastic IP pool for internal business to "Direct Line".

• Multi-ISP line management: To help tenants select elastic IP pools that contain IP addresses provided by different ISPs based on their needs, set the line type of the elastic IP pool with Telecom IP addresses to "Telecom" and that of the elastic IP pool with Unicom IP addresses to "Unicom".

3. Steps

Step 1.Step 1. Log in to SCP and go to Networking > IP and Bandwidth > Elastic IP Pools.

Step 2.Step 2. Click Lines and BGP Configuration. The Lines and BGP Configuration pop-up window appears.

Step 3.Step 3. Click the Line Type tab and then click New.

Step 4.Step 4. Configure the fields as instructed in the table below:

Step 5.Step 5. Click OK to complete the creation. The created line type will appear in the line type list.

BGP Configuration

1. Introduction

Border Gateway Protocol (BGP) configuration is created to establish a peering relationship between a BGP device in the virtual network and that in the external autonomous system (AS) for communication. If you use an IPv6 elastic IP pool, you need to configure a BGP on the physical core router and create the corresponding BGP configuration on SCP to establish the peering relationship. The BGP configuration takes effect after being associated with the IPv6 elastic IP pool. This enables cross-AS communication for the IPv6 network.

2. Application Scenarios

• Cross-AS communication for IPv6 network: An enterprise can create BGP configuration to enable communication between its IPv6 network and an external AS (such as the network of another enterprise or an ISP) through routing information exchange, ensuring that the IPv6 elastic IP pool can be accessed from the internet.

• Multi-AS network interconnection: A large enterprise can create BGP configuration to enable interconnection between the elastic IP pools across multiple ASes (such as the one at the headquarters and the one at a branch), ensuring that cross-region services can be accessed from the internet.

3. Prerequisites

• Basic BGP configuration (including the AS number and neighbor IP address) is complete on the physical core router.

• A line type has been created and matches the business scenario corresponding to the BGP configuration.

4. Constraints and Restrictions

• After the BGP configuration is created successfully, the associated line type cannot be modified.

• The AS number of the virtual BGP configuration cannot be the same as that of the core router.

• The loopback IP address of the virtual BGP configuration and the BGP IP address of the BGP configuration of the core router must be on the same 64-bit network segment and cannot be the same.

• For BGP configurations associated with the same line type, BGP IP addresses of core routers must be on the same 64-bit network segment and not identical. For BGP configurations associated with different line types, these BGP IP addresses must be on different 64-bit network segments.

5. Steps

Step 1.Log in to SCP and go to Networking > IP and Bandwidth > Elastic IP Pools.

Step 2.Click Lines and BGP Configuration. The Lines and BGP Configuration pop-up window appears.

Step 3.Click the BGP Configuration tab and then click Create. The Create BGP Configuration pop-up window appears.

Step 4. Configure the fields as instructed in the table below:

Step 5.Step 5. After the BGP configuration is complete, click OK to save it.