- 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.
Adding a Prefix Rule to an IP Address Prefix List
Scenarios
This section describes how to add prefix rules to an IP prefix list. Each IP prefix list can have multiple prefix rules.
Notes and Constraints
- IP prefix rules change the path through which network traffic passes. If the route policy of a prefix rule has already been associated with an enterprise router, evaluate the impact on services before adding a prefix rule to the policy.
- Each prefix rule in an IP prefix list must have its unique sequence number and IP prefix.
Prerequisites
An IP prefix list is available. You can create one by referring to Creating an IP Prefix List.
Procedure
- Go to the Prefix Lists page.
- Click the name of the target IP prefix list.
The prefix rule list is displayed.
- Click Add Prefix Rule in the upper left corner of the list.
The Add Prefix Rule dialog box is displayed.
- Configure the parameters based on Table 1.
Table 1 Parameters for adding a prefix rule Parameter
Description
Example Value
Configuration
Mandatory
Choose Quick or Advanced.- Quick
Enter the IP prefix in the CIDR format. An IP prefix specifies the first bits of an IP address range that a route destination must match.
The following are parameters that you do not need to configure:- Sequence Number: Automatically generated. The sequence number increases by a multiple of 10, with that of the first rule set to 10. The subsequent numbers are 20, 30, and so on.
- Action: Allow by default
- Min. Netmask Length and Max. Netmask Length
- Advanced
- Sequence Number: An IP prefix list consists of one or more prefix rules that are applied to filter routes based on their sequence numbers, in ascending order. A sequence number can be from 0 to 65535. You are advised to set the sequence number of the first rule to 20.
- Action: Select Allow or Deny. If a route matches a prefix rule with Action set to Allow, the route is allowed. If the prefix rule has Action set to Deny, the route is denied.
- IP Prefix: Enter the IP prefix in the CIDR format. This parameter specifies the first bits of an IP address range that a route destination must match.
- Min. Netmask Length: It cannot be smaller than the netmask length of the IP prefix. For example, if the netmask length of the IP prefix is 16, the min. netmask length must be greater than or equal to 16 (for example, 18).
- Max. Netmask Length: It cannot be smaller than the min. netmask length. For example, if the min. netmask length is 18, the max. netmask length must be from 18 to 32 (for example, 20).
- Sequence Number: 10
- Action: Allow
- IP Prefix: 10.0.0.0/16
- Min. Netmask Length: 20
- Max. Netmask Length: 28
- Quick
- Click OK.
You can view the added prefix rule.
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