- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
-
Routing Control
-
Route Policies
- Route Policy Overview
- Creating a Route Policy
- Associating a Route Policy with an Enterprise Router
- Changing the Route Policy Associated with an Enterprise Router
- Disassociating a Route Policy from an Enterprise Router
- Modifying a Route Policy
- Viewing a Route Policy
- Deleting a Route Policy
- Adding a Policy Node to a Route Policy
- Modifying a Policy Node in a Route Policy
- Exporting Policy Nodes in a Route Policy
- Viewing a Policy Node in a Route Policy
- Deleting a Policy Node from a Route Policy
-
IP Prefix Lists
- IP Prefix List Overview
- Creating an IP Prefix List
- Modifying the Name of an IP Prefix List
- Viewing an IP Prefix List
- Deleting an IP Prefix List
- Adding a Prefix Rule to an IP Address Prefix List
- Modifying an IP Prefix Rule in an IP Prefix List
- Exporting Prefix Rules in an IP Prefix List
- Viewing a Prefix Rule in an IP Prefix List
- Deleting a Prefix Rule from an IP Prefix List
-
AS_Path Lists
- AS_Path List Overview
- Creating an AS_Path List
- Modifying the Name of an AS_Path List
- Viewing an AS_Path List
- Deleting an AS_Path List
- Adding an AS_Path Filter to an AS_Path List
- Exporting AS_Path Filters in an AS_Path List
- Viewing an AS_Path Filter in an AS_Path List
- Deleting an AS_Path Filter from an AS_Path List
-
Route Policies
- Sharing
- Flow Logs
- Monitoring and Auditing
- Tags
- Quotas
-
Best Practices
- Summary on Enterprise Router Best Practices
- Connecting VPCs Across Regions Using Enterprise Router and Central Network
- Using Enterprise Router to Isolate VPCs in the Same Region
- Using a Third-Party Firewall to Protect VPCs Connected by Enterprise Routers
- Enabling an On-Premises Data Center to Access Service VPCs Using an Enterprise Router and Transit VPC
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect Global DC Gateway
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Global DC Gateway)
-
Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Overview
- Network and Resource Planning
- Process of Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Procedure for Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Active/Standby Direct Connect Connections (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Global DC Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and Direct Connect (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router and a Pair of Direct Connect Connections (Virtual Gateway)
- Setting Up a Hybrid Cloud Network Using Enterprise Router, VPN, and Direct Connect (Virtual Gateway)
- Allowing VPCs to Share an EIP to Access the Internet Using Enterprise Router and NAT Gateway
- Using Enterprise Router to Migrate the Network Set Up Through VPC Peering
- Using Enterprise Router to Migrate the Network Set Up Through Direct Connect (Global DC Gateway)
- Using Enterprise Router and Central Network to Migrate the Network Set Up Through a Cloud Connection
- API Reference
- FAQs
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Interconnecting with CTS
- Permissions Management
- Tags
- Quotas
- FAQ
- Change History
-
User Guide (Ankara Region)
- Service Overview
- Getting Started
- Permissions Management
- Enterprise Routers
- Attachments
- Route Tables
- Associations
- Propagations
- Routes
- Sharing
- Flow Logs
- Monitoring
- Quotas
- FAQ
- Change History
- API Reference (Ankara Region)
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Creating a Route Policy
Scenarios
This section describes how to create a route policy.
Notes and Constraints
- Each node in a route policy must have a unique number.
- Each match condition of a node must be unique. For example, a node cannot have two IP prefix lists selected as the match condition at the same time.
Procedure
- Go to the Route Policies page.
- Click Create Route Policy in the upper right corner.
The Create Route Policy page is displayed.
- Configure the parameters based on Table 1.
Table 1 Parameters for creating a route policy Parameter
Description
Example Value
Name
Mandatory
Enter the name of the route policy. The name:- Can contain 1 to 64 characters.
- Can contain letters, digits, underscores (_), hyphens (-), and periods (.).
routePolicy-ab
Description
Optional
Enter the description of the route policy in the text box as required.
-
Node Number
Mandatory
A route policy consists of one or more nodes. When a route policy is used to filter routes, a node with a smaller number is matched first.
Enter a value from 0 to 65535.
20
Action
Mandatory
Set it to Allow or Deny.- If Action of a node is set to Allow and a route matches all the filtering conditions of the node, the route is allowed.
- If Action of a node is set to Deny and a route matches all the filtering conditions of the node, the route is denied.
NOTICE:By default, routes that do not match any node in a route policy are denied. If a route policy has one or more deny nodes, you need to create a node to allow all other routes.
Allow
Match Condition
Mandatory
Select match conditions. You can select a route type, prefix list, or AS_Path list.- Route type
- Static: Manually configured routes
Custom routes and propagated routes of VPC attachments in enterprise router route tables are static routes.
- BGP: Routes learned through BGP
Direct Connect virtual gateways communicate with enterprise routers using BGP so the routes of virtual gateway attachments propagated to enterprise router route tables are BGP routes.
Also, the routes of peering connection attachments, VPN gateway attachments, and global DC gateway attachments propagated to enterprise router route tables are BGP routes.
- Static: Manually configured routes
- An IP prefix list contains prefix rules for route filtering. You can define IP prefixes and netmasks in prefix rules to match the destination addresses or next hops of routes. For more information, see IP Prefix List Overview.
- An AS_Path list is a collection of filters that are used to filter BGP routes based on AS_Path attributes contained in BGP routes. AS_Path attributes record the number of each AS that BGP routes pass through from the source to the destination in distance-vector order. For more information, see AS_Path List Overview.
- Route type: BGP
- IP prefix list: prefixFilter-ab
- AS_Path list: asPathFilter-ab
Policy Value
Optional
You can configure policy values for a route as required if you set Action to Allow. Each node can have up to two policy values. You can click Add Policy Value to add policy values.- PrefVal:
PrefVal is a Huawei-specific route attribute. A larger PrefVal value indicates a higher route priority.
You can change the PrefVal value of a route by changing the PrefVal value in the route policy.
A PrefVal value must be an integer.
The default PrefVal values of routes for different types of enterprise router attachments are as follows:- Virtual gateway attachments: 100
- Peering connection attachments: 60
- VPN gateway attachments: 80
- Global DC gateway attachments: 100
NOTICE:Changing the PrefVal value of a route may adversely affect route selection of attachments. Submit a service ticket to evaluate the change.
- AS_Path attributes record the number of each AS that BGP routes pass through from the source to the destination in distance-vector order.
You can add, replace, or delete AS_Path policy values.
- Add a policy value to the left of AS_Path.
- Replace the original policy value of AS_Path.
- Delete the specified policy value of AS_Path.
AS_Path policy values must meet the following requirements:- Each value is an integer in the format of x or x.y. (x: 1 to 65535; y: 0 to 65535).
- A maximum of 10 values can be entered at a time.
- Each value must be unique.
- PrefVal: 20
- AS_Path: 2000 10.2 3.7 500
- Click Add Node to add more nodes if needed.
- Click Create Now.
The route policy list is displayed.
- View the route policy status.
If the status is Normal, the route policy has been created.
Follow-Up Operations
A route policy takes effect only after you associate it with an enterprise router. For details, see Associating a Route Policy with an Enterprise Router.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot