Adding a Route for an Enhanced Datasource Connection

Updated on 2024-11-08 GMT+08:00

View PDF

Scenario

A route is configured with the destination, next hop type, and next hop to determine where the network traffic is directed. Routes are classified into system routes and custom routes.

After an enhanced connection is created, the subnet is automatically associated with the default route. You can add custom routes as needed to forward traffic destined for the destination to the specified next hop.

NOTE:

When an enhanced connection is created, the associated route table is the one associated with the subnet of the data source.
The route to be added in the Add Route dialog box must be one in the route table associated with the subnet of the resource pool.
The subnet of the data source must be different from that used by the resource pool. Otherwise, a network segment conflict occurs.

Procedure

Log in to the DLI management console.
In the left navigation pane, choose Datasource Connections.

On the Enhanced tab page displayed, locate the row containing the enhanced connection to which a route needs to be added, and add the route.

Method 1:
1. On the Enhanced tab page displayed, locate the enhanced datasource connection to which a route needs to be added and click Manage Route in the Operation column.
2. Click Add Route.
3. In the Add Route dialog box, enter the route information. For details about the parameters, see Table 1.
4. Click OK.
Method 2:
1. On the Enhanced tab page displayed, locate the enhanced datasource connection to which a route needs to be added, click More in the Operation column, and select Add Route.
2. In the Add Route dialog box, enter the route information. For details about the parameters, see Table 1.
3. Click OK.

**Table 1** Parameters for adding a custom route
Parameter	Description
Route Name	Name of a custom route, which is unique in the same enhanced datasource scenario. The name can contain 1 to 64 characters. Only digits, letters, underscores (_), and hyphens (-) are allowed.
IP Address	Custom route CIDR block. The CIDR block of different routes can overlap but cannot be the same. Do not add the CIDR blocks 100.125.xx.xx and 100.64.xx.xx to prevent conflicts with the internal CIDR blocks of services such as SWR. This can lead to failure of the enhanced datasource connection.

After adding a route, you can view the route information on the route details page.

Parent topic: Managing Enhanced Datasource Connections

Previous topic: Unbinding an Enhanced Datasource Connection from an Elastic Resource Pool

Next topic: Deleting the Route for an Enhanced Datasource Connection

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot