Creating a Static Route
Scenarios
You can create static routes in a route table of an enterprise router.
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- Click Service List and choose Networking > Enterprise Router.
The Enterprise Router homepage is displayed.
- Search for the target enterprise router by name.
Figure 2 Searching for an enterprise router
- Go to the Route Tables tab using either of the following methods:
- In the upper right corner of the enterprise router, click Manage Route Table.
- Click the enterprise router name and click Route Tables.
Figure 3 Creating a static route
- Click the route table where you want to create a static route. On the Routes tab, click Create Route.
The Create Route dialog box is displayed.
- Configure the parameters based on Table 1.
Table 1 Parameter description Parameter
Setting
Example Value
Destination
Mandatory
Enter the IP address or CIDR block of the attachment. For example, if it is a VPC attachment, enter the CIDR block of the VPC or a subnet of the VPC.
192.168.2.0/24
Blackhole Route
Optional
If Blackhole Route is enabled, you do not need to configure Attachment Type and Next Hop for the route. If the destination of a route is the same as, or is contained in, that of this blackhole route, all packets destined for the destination will be dropped.
-
Attachment Type
- If Blackhole Route is not enabled, you need to configure this parameter.
- If Blackhole Route is enabled, you do not need to configure this parameter.
VPC: Create a static route for a VPC attachment.
For more information, see Attachment Overview.
VPC
Next Hop
- If Blackhole Route is not enabled, you need to configure this parameter.
- If Blackhole Route is enabled, you do not need to configure this parameter.
In the drop-down list, select the target attachment.
er-attach-01
- Click OK.
Wait for 2 to 3 seconds, and click to refresh the route list. The created static route is displayed.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.