This practice describes how to use two dedicated lines to access the VPC on the cloud from the client site in the load mode.

Scenario Description

Most enterprises have high requirements for business system stability. For example, when xx enterprise performs business planning, it sees the high availability of business as the top priority of the business system. Ensuring stable business operation and safe data transmission is the key to building a business system. When deploying such businesses, there are higher requirements on the communication stability between the local data center and the resource pool on the cloud.

Solution

You can establish a stable and reliable communication channel between the local data center and eSurfing Cloud VPC through two dedicated lines in the load mode. In the load access mode, the two dedicated physical lines can forward the traffic between the local data center and the VPC on the cloud under normal circumstances. When one line fails, the traffic will be switched to another line for transmission to avoid affecting the business.

Prerequisites

Before this practice, contact your exclusive account manager or eSurfing Cloud customer service to apply for a dedicated physical line. If you do not have an exclusive account manager, please call the eSurfing Cloud customer service number for consultation.
You have made preliminary network planning for the use of CDA according to your business needs, such as how many dedicated lines are required, the bandwidth rate of CDA, etc. For details about the planning elements, please see FAQ > Management > What factors should I consider in the early stage of CDA access?
You have created a VPC on the cloud.

Procedure

This practice is divided into five steps:

Step I: Enabling the Dedicated Physical Line
Step II: Creating a CDA Gateway
Step III: Adding a Client-Side Route
Step IV: Adding a VPC
Step V: Conducting a Verification Test

Enabling the Dedicated Physical Line

After you communicate with our account manager to confirm the business model and sign the contract, our account manager will collect CDA-enabling information according to your network planning, including the client-side network segment and cloud-side network segment that need communication, the number of dedicated lines required, the bandwidth rate of CDA, and help you enable the dedicated physical line in the background of eSurfing Cloud.

Note: In this practice, the number of dedicated physical lines should be at least 2 to ensure the high availability of the service.

After the dedicated physical line is successfully enabled, you can go to the Network Console>Cloud Dedicated Access page of the eSurfing Cloud Network Console to view the enabled

dedicated physical line.

Creating a CDA Gateway

After a dedicated physical line is created, our account manager will continue to assist you in creating a CDA gateway and binding the dedicated physical line in the background. Note that one CDA gateway can be bound to two dedicated physical lines at the same time. If you have not created a CDA gateway, you can create one in the Console by following the steps below:

Log in to the Console .
Click in the upper left corner of the Console and select the region. Note that the dedicated physical line and the VPC must be in the same region.
Click Network Console>Cloud Dedicated Access to go to the Quick Start page. In the left navigation bar, click Cloud Dedicated Access>Dedicated Line Gateway to go to the Dedicated Line Gateway List page.
Click the Creat Dedicated Line Gateway button at the top left of the Dedicated Line Gateway List . The Creat Dedicated Line Gateway pop-up window appears.
In the Creat Dedicated Line Gateway pop-up window, you can customize the name of the CDA gateway. The name length is limited to 1-64 characters. The name can consist of Chinese characters, English letters, numbers, and special characters such as the at sign (@), underline (_), hyphen (-), dollar sign ($), and period (.). In the dedicated physical line configuration item, you can pull down and select the dedicated physical line that has been created. You can select enterprise projects for the CDA gateway or keep the parameter as default .
After the configuration is complete, click OK to successfully create the CDA gateway.
After the CDA gateway is successfully created, you can go to the Cloud Dedicated Access>Dedicated Line Gateway page of the eSurfing Cloud Network Console to view the created CDA gateway.

Adding a Client-Side Route

When you have created a dedicated physical line and a CDA gateway, it is necessary to add a client-side route to the CDA gateway, that is, the route entry from the CDA gateway to the local data center to realize the interconnectivity between your local data center and the CDA gateway.

Click Details in the Operation column of the target CDA gateway to go to the Dedicated Line Gateway Details page. Click Client Side Routing on the Dedicated Line Gateway Details page, and go to the Client Side Routing tab.
In the Client Side Routing tab, click the Add Route button.
Fill in the routing rule configuration parameters as promoted on the page. Click OK to complete the addition of the client-side routing rule. In this example, you need to bind two dedicated physical lines and set the same priority for the two lines to achieve the load mode. At the same time, please enable the Track mode.
When adding a client-side routing rule, you can configure more parameters as follows:

•Both static and BGP dynamic routes are supported. You can configure static routing rules in the console. If you need to configure the BGP dynamic route, please submit a work order to apply for configuration In this example, the static route is selected.

•Supported routing rules include IPv4 type, IPv6 type, and dual-stack type.

•In the static route, you can configure the primary/standby/load mode of multiple dedicated physical lines: When binding multiple dedicated physical lines, please set the priority of the dedicated physical line. The input range is 10-100.

• If you need to configure the primary/standby route, please set different priorities for the multiple dedicated physical lines bound. A smaller parameter value indicates a higher priority. At the same time, you need to enable Track or BFD.

• If you need to configure the load route, please set the same priority for the multiple dedicated physical lines bound. At the same time, you need to enable Track or BFD.

•In the static route, you can configure the load mode of multiple dedicated physical lines: When binding multiple dedicated physical lines, enable BFD for the lines that need load. Enable multi-path configuration and set the number of dedicated physical lines that need load.

•After Track or BFD is enabled, the system can automatically detect the link connectivity on the client side, and switch routes when the link fails.

Adding a VPC

You can add a route entry from the CDA gateway to the VPC to realize the interconnectivity between the CDA gateway and the VPC.

Click Details in the Operation column of the target CDA gateway to go to the Dedicated Line Gateway Details page. Click VPC on the Dedicated Line Gateway Details page, and go to the VPC tab.
In the VPC tab, click the Add VPC button to go to the Add VPC window. You can configure the VPC and subnet that communicate with the local data center as promoted on the page. The configuration is as follows:

•VPC Instance Type: Same account.

•VPC: Select the created VPC in the dropdown box.

•VPC ID: Automatically generated based on the VPC name.

•VPC network segment: Select the specified VPC network segment.

•Type: You can select IPv4, IPv6, or the dual-stack type.

•Subnet: Select the subnet in the VPC.

•Weight: Represents the weight of the current route from the CDA gateway to the VPC side. When the weights of multiple routes are the same, use the load balancing mode for traffic transmission. A higher weight value of a route indicates a higher priority. The weight options include 0 and 100.
After the parameter configuration is completed, click OK to complete the VPC addition.

Verifying Connectivity

You can verify the end-to-end connectivity between the data center and the server on the cloud. When conducting a connectivity test, you can open a command line window on a server in the local data center and execute the ping command to test whether the communication among the local data center, CDA gateway, and the VPC on the cloud is normal. If the reply packet can be received, it means that the connection has been successful.