Login
- Table of Contents
-
- 05-Layer 3-IP Routing Command Reference
- 00-Preface
- 01-Basic IP routing commands
- 02-Static routing commands
- 03-RIP commands
- 04-OSPF commands
- 05-IS-IS commands
- 06-BGP commands
- 07-Policy-based routing commands
- 08-IPv6 static routing commands
- 09-RIPng commands
- 10-OSPFv3 commands
- 11-IPv6 IS-IS commands
- 12-IPv6 policy-based routing commands
- 13-Routing policy commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 13-Routing policy commands | 137.93 KB |
Routing policy commands
Common routing policy commands
apply as-path
Use apply as-path to set the AS_PATH attribute for BGP routes.
Use undo apply as-path to restore the default.
Syntax
apply as-path as-number&<1-32> [ replace ]
undo apply as-path
Default
No AS_PATH attribute is set.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
as-number&<1-32>: Specifies an AS by its number in the range of 1 to 4294967295. &<1-32> indicates that the argument before it can be entered up to 32 times.
replace: Replaces the original AS numbers. If you do not specify this keyword, the command adds the specified AS numbers before the original AS_PATH attribute.
Examples
# Configure node 10 in permit mode for routing policy policy1 to add AS number 200 before the original AS_PATH attribute of BGP routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply as-path 200
Related commands
· display ip as-path
· if-match as-path
· ip as-path
apply comm-list delete
Use apply comm-list delete to delete the COMMUNITY attributes from BGP routes.
Use undo apply comm-list to restore the default.
Syntax
apply comm-list { comm-list-number | comm-list-name } delete
undo apply comm-list
Default
No COMMUNITY attributes are deleted from BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
comm-list-number: Specifies a basic community list by its number in the range of 1 to 99 or an advanced community list by its number in the range of 100 to 199.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters that cannot contain only numbers.
Examples
# Configure node 10 in permit mode for routing policy policy1 to remove the COMMUNITY attributes specified in community list 1 from BGP routes.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] apply comm-list 1 delete
Related commands
ip community-list
apply community
Use apply community to set a specified COMMUNITY attribute for BGP routes.
Use undo apply community to remove the configuration.
Syntax
apply community { none | additive | { community-number&<1-32> | aa:nn&<1-32> | internet | no-advertise | no-export | no-export-subconfed } * [ additive ] }
undo apply community [ none | additive | { community-number&<1-32> | aa:nn&<1-32> | internet | no-advertise | no-export | no-export-subconfed } * [ additive ] ]
Default
No COMMUNITY attribute is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
none: Removes the COMMUNITY attributes of BGP routes.
community-number&<1-32>: Specifies a community sequence number in the range of 1 to 4294967295. &<1-32> indicates that the argument before it can be entered up to 32 times.
aa:nn&<1-32>: Specifies a community number. Both aa and nn are in the range of 0 to 65535. &<1-32> indicates that the argument before it can be entered up to 32 times.
internet: Sets the INTERNET community attribute for BGP routes. Routes with this attribute can be advertised to all BGP peers. By default, all routes have this attribute.
no-advertise: Sets the NO_ADVERTISE community attribute for BGP routes. Routes with this attribute cannot be advertised to any peers.
no-export: Sets the NO_EXPORT community attribute for BGP routes. Routes with this attribute cannot be advertised out of the AS or confederation, but can be advertised to other sub-ASs in the confederation.
no-export-subconfed: Sets the NO_EXPORT_SUBCONFED community attribute for BGP routes. Routes with this attribute cannot be advertised out of the local AS or to other sub-ASs in the confederation.
additive: Adds the specified COMMUNITY attribute to the original COMMUNITY attribute of BGP routes.
Examples
# Configure node 16 in permit mode for routing policy setcommunity to set the NO_EXPORT community attribute for BGP routes.
<Sysname> system-view
[Sysname] route-policy setcommunity permit node 16
[Sysname-route-policy-setcommunity-16] apply community no-export
Related commands
· if-match community
· ip community-list
apply cost
Use apply cost to set a cost for routes.
Use undo apply cost to restore the default.
Syntax
apply cost [ + | - ] value
undo apply cost
Default
No cost is set for routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
+: Increases a cost value.
-: Decreases a cost value.
value: Specifies a cost in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a cost of 120 for OSPF external routes.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match route-type external-type1or2
[Sysname-route-policy-policy1-10] apply cost 120
apply cost-type
Use apply cost-type to set a cost type for routes.
Use undo apply cost-type to restore the default.
Syntax
apply cost-type { external | internal | type-1 | type-2 }
undo apply cost-type
Default
No cost type is set for routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
external: Sets the cost type to IS-IS external route.
internal: Sets the cost type to IS-IS internal route, or sets the MED value for a matching BGP route to the IGP metric of the route's next hop.
type-1: Sets the cost type to OSPF Type-1 external route.
type-2: Sets the cost type to OSPF Type-2 external route.
Usage guidelines
For IS-IS, the apply cost-type internal command sets the cost type for a matching IS-IS route to IS-IS internal route.
For BGP, the apply cost-type internal command sets the MED for a matching BGP route learned from an IBGP peer to the IGP metric of the route's next hop. The MED is modified before BGP advertises the route to an EBGP peer.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set the cost type for routes that have a tag of 8 to IS-IS internal route.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match tag 8
[Sysname-route-policy-policy1-10] apply cost-type internal
apply isis
Use apply isis to redistribute routes into a specified IS-IS level.
Use undo apply isis to restore the default.
Syntax
apply isis { level-1 | level-1-2 | level-2 }
undo apply isis
Default
No IS-IS level is set.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
level-1: Redistributes routes into IS-IS Level-1.
level-1-2: Redistributes routes into both IS-IS Level-1 and Level-2.
level-2: Redistributes routes into IS-IS Level-2.
Examples
# Configure node 10 in permit mode for routing policy policy1 to redistribute routes that have a tag of 8 to IS-IS level-2.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match tag 8
[Sysname-route-policy-policy1-10] apply isis level-2
apply local-preference
Use apply local-preference to set a local preference for BGP routes.
Use undo apply local-preference to restore the default.
Syntax
apply local-preference preference
undo apply local-preference
Default
No local preference is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preference: Specifies a local preference in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a local preference of 130 for routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply local-preference 130
apply origin
Use apply origin to set an ORIGIN attribute for BGP routes.
Use undo apply origin to restore the default.
Syntax
apply origin { egp as-number | igp | incomplete }
undo apply origin
Default
No ORIGIN attribute is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
egp as-number: Sets the ORIGIN attribute to EGP. The as-number argument specifies an AS number in the range 1 to 4294967295 for EGP routes.
igp: Sets the ORIGIN attribute to IGP.
incomplete: Sets the ORIGIN attribute to UNKNOWN.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set the ORIGIN attribute for routes matching AS path list 1 to IGP.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply origin igp
apply preference
Use apply preference to set a preference for a routing protocol.
Use undo apply preference to restore the default.
Syntax
apply preference preference
undo apply preference
Default
No preference is set for a routing protocol.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preference: Specifies a preference in the range of 1 to 255.
Usage guidelines
If you have set preferences for routing protocols with the preference command, the apply preference command sets a new preference for the matching routing protocol. Non-matching routing protocols still use the preferences set by the preference command.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set the preference for OSPF external routes to 90.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match route-type external-type1or2
[Sysname-route-policy-policy1-10] apply preference 90
apply preferred-value
Use apply preferred-value to set a preferred value for BGP routes.
Use undo apply preferred-value to restore the default.
Syntax
apply preferred-value preferred-value
undo apply preferred-value
Default
No preferred value is set for BGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preferred-value: Specifies a preferred value in the range of 0 to 65535.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a preferred value of 66 for BGP routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply preferred-value 66
apply prefix-priority
Use apply prefix-priority to set a prefix priority for routes.
Use undo apply prefix-priority to restore the default.
Syntax
apply prefix-priority { critical | high | medium }
undo apply prefix-priority
Default
No prefix priority is set, which means the prefix priority is low.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
critical: Sets the critical prefix priority for routes.
high: Sets the high prefix priority for routes.
medium: Sets the medium prefix priority for routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set prefix priority critical for routes matching prefix list abc.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ip address prefix-list abc
[Sysname-route-policy-policy1-10] apply prefix-priority critical
apply tag
Use apply tag to set a specified tag for IGP routes.
Use undo apply tag to restore the default.
Syntax
apply tag value
undo apply tag
Default
No routing tag is set for IGP routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
value: Specifies the tag value in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set a tag of 100.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] apply tag 100
continue
Use continue to specify the next node to be matched.
Use undo continue to restore the default.
Syntax
continue [ node-number ]
undo continue
Default
No next node is specified.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
node-number: Specifies the routing policy node number in the range of 0 to 65535.
Usage guidelines
The specified next node must have a larger number than the current node.
Example
# Specify the next node 20 for node 10 of routing policy policy1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] continue 20
display ip as-path
Use display ip as-path to display BGP AS path list information.
Syntax
display ip as-path [ as-path-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
as-path-number: Specifies an AS path list by its number in the range of 1 to 256. If you do not specify this argument, the command displays information about all BGP AS path lists.
Examples
# Display information about BGP AS path list 1.
<Sysname> display ip as-path 1
ListID Mode Expression
1 permit 2
Table 1 Command output
|
Field |
Description |
|
ListID |
AS path list ID. |
|
Mode |
Match mode: · permit. · deny. |
|
Expression |
Regular expression used to match routes. |
display ip community-list
Use display ip community-list to display BGP community list information.
Syntax
display ip community-list [ basic-community-list-number | adv-community-list-number | name comm-list-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
name comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters that cannot contain only numbers.
Usage guidelines
If no community list is specified, this command displays information about all BGP community lists.
Examples
# Display information about all BGP community lists.
<Sysname> display ip community-list
Community List Basic aaa
permit
Community List Advanced bbb
permit 3333
Table 2 Command output
|
Field |
Description |
|
Community List Basic |
Basic community list. |
|
Community List Advanced |
Advanced community list. |
|
permit |
Match mode: · permit. · deny. |
display route-policy
Use display route-policy to display routing policy information.
Syntax
display route-policy [ name route-policy-name ]
Views
Predefined user roles
network-admin
network-operator
Parameters
name route-policy-name: Specifies a routing policy by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays information about all routing policies.
Examples
# Display information about routing policy 1.
<Sysname> display route-policy name policy1
Route-policy: policy1
permit : 1
if-match cost 10
continue: next node 11
apply comm-list a delete
Table 3 Command output
|
Field |
Description |
|
Route-policy |
Routing policy name. |
|
permit |
Match mode: · permit. · deny. |
|
if-match |
Match criterion. |
|
continue |
Specify the next node to be matched. |
|
apply |
Action. |
if-match as-path
Use if-match as-path to match BGP routes whose AS_PATH attribute matches a specified AS path list.
Use undo if-match as-path to remove the configuration.
Syntax
if-match as-path as-path-number&<1-32>
undo if-match as-path [ as-path-number&<1-32> ]
Default
No match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
as-path-number&<1-32>: Specifies an AS path list by its number in the range of 1 to 256. &<1-32> indicates that the argument before it can be entered up to 32 times.
Examples
# Define AS path list 2 to permit BGP routes containing AS number 200 or 300 to pass. Configure node 10 in permit mode for routing policy test to match AS path list 2.
<Sysname> system-view
[Sysname] ip as-path 2 permit _*200.*300
[Sysname] route-policy test permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 2
Related commands
· apply as-path
· ip as-path
if-match community
Use if-match community to match BGP routes whose COMMUNITY attribute matches a specified community list.
Use undo if-match community to remove the configuration.
Syntax
if-match community { { basic-community-list-number | name comm-list-name } [ whole-match ] | adv-community-list-number }&<1-32>
undo if-match community [ { basic-community-list-number | name comm-list-name } [ whole-match ] | adv-community-list-number ]&<1-32>
Default
No community list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
basic-community-list-number: Specifies a basic community list by its number in the range of 1 to 99.
adv-community-list-number: Specifies an advanced community list by its number in the range of 100 to 199.
comm-list-name: Specifies a community list by its name, a case-sensitive string of 1 to 63 characters that cannot contain only numbers.
whole-match: Exactly matches the specified community list.
&<1-32>: Indicates that the argument before it can be entered up to 32 times.
Examples
# Configure community list 1 to permit BGP routes with community number 100 or 200. Then configure node 10 in permit mode for routing policy test to use community list 1 to match BGP routes.
[Sysname] ip community-list 1 permit 100 200
[Sysname] route-policy test permit node 10
[Sysname-route-policy-test-10] if-match community 1
Related commands
· apply community
· ip community-list
if-match cost
Use if-match cost to match routes having the specified cost.
Use undo if-match cost to restore the default.
Syntax
if-match cost value
undo if-match cost
Default
No cost match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
value: Specifies a cost in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to permit routes with a cost of 8.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match cost 8
if-match interface
Use if-match interface to match routes having the specified output interface.
Use undo if-match interface to remove the configuration.
Syntax
if-match interface { interface-type interface-number }&<1-16>
undo if-match interface [ interface-type interface-number ]&<1-16>
Default
No match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
&<1-16>: Indicates that the argument before it can be entered up to 16 times.
Usage guidelines
BGP does not support criteria for matching the output interface of routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to permit routes with the output interface VLAN-interface 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match interface vlan-interface 1
if-match local-preference
Use if-match local-preference to match BGP routes having the specified local preference.
Use undo if-match local-preference to restore the default.
Syntax
if-match local-preference preference
undo if-match local-preference
Default
No local preference match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
preference: Specifies a local preference in the range of 0 to 4294967295.
Examples
# Create node 10 in permit mode for routing policy policy1 to match BGP routes having a local preference of 2.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match preference 2
if-match route-type
Use if-match route-type to configure a route-type match criterion.
Use undo if-match route-type to remove the configuration.
Syntax
if-match route-type { external-type1 | external-type1or2 | external-type2 | internal | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type1or2 | nssa-external-type2 } *
undo if-match route-type [ external-type1 | external-type1or2 | external-type2 | internal | is-is-level-1 | is-is-level-2 | nssa-external-type1 | nssa-external-type1or2 | nssa-external-type2 ] *
Default
No route-type match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
external-type1: Matches OSPF Type 1 external routes.
external-type1or2: Matches OSPF Type 1 and Type 2 external routes.
external-type2: Matches OSPF Type 2 external routes.
internal: Matches OSPF internal routes (including OSPF intra-area and inter-area routes).
is-is-level-1: Matches IS-IS Level-1 routes.
is-is-level-2: Matches IS-IS Level-2 routes.
nssa-external-type1: Matches OSPF NSSA Type 1 external routes.
nssa-external-type1or2: Matches OSPF NSSA Type 1 and 2 external routes.
nssa-external-type2: Matches OSPF NSSA Type 2 external routes.
Examples
# Configure node 10 in permit mode for routing policy policy1 to match OSPF internal routes.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match route-type internal
if-match tag
Use if-match tag to match IGP routes having the specified tag.
Use undo if-match tag to restore the default.
Syntax
if-match tag value
undo if-match tag
Default
No tag match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
value: Specifies a tag in the range of 0 to 4294967295.
Examples
# Configure node 10 in permit mode for routing policy policy1 to match IGP routes having a tag of 8.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match tag 8
ip as-path
Use ip as-path to configure an AS path list.
Use undo ip as-path to remove an AS path list.
Syntax
ip as-path as-path-number { deny | permit } regular-expression
undo ip as-path as-path-number [ regular-expression | deny | permit ]
Default
No AS path list is configured.
Views
System view
Predefined user roles
network-admin
Parameters
as-path-number: Specifies a number for the AS path list, in the range of 1 to 256.
deny: Specifies the match mode for the AS path list as deny.
permit: Specifies the match mode for the AS path list as permit.
regular-expression: Specifies an AS path regular expression, a string of 1 to 63 characters.
Usage guidelines
BGP routing updates contain an AS_PATH attribute field that identifies the ASs through which the routes have passed. An AS path regular expression, for example, ^200. *100$, matches the AS_PATH attribute that starts with AS 200 and ends with AS 100. For more information about regular expressions, see Fundamentals Configuration Guide.
Examples
# Configure AS path list 1 to permit routes whose AS_PATH attribute starts with 10.
<Sysname> system-view
[Sysname] ip as-path 1 permit ^10
Related commands
· apply as-path
· display ip as-path
· if-match as-path
ip community-list
Use ip community-list to configure a community list.
Use undo ip community-list to remove a community list.
Syntax
ip community-list { basic-comm-list-num | basic basic-comm-list-name } { deny | permit } [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] *
undo ip community-list { basic-comm-list-num | basic basic-comm-list-name } [ deny | permit ] [ community-number&<1-32> | aa:nn&<1-32> ] [ internet | no-advertise | no-export | no-export-subconfed ] *
ip community-list { adv-comm-list-num | advanced adv-comm-list-name } { deny | permit } regular-expression
undo ip community-list { adv-comm-list-num | advanced adv-comm-list-name } [ deny | permit ] [ regular-expression ]
Default
No community list is configured.
Views
System view
Predefined user roles
network-admin
Parameters
basic-comm-list-num: Specifies a number for the basic community list, in the range of 1 to 99.
basic: Specifies a name for the basic communist list.
advanced: Specifies a name for the advanced communist list.
basic-comm-list-name: Specifies the basic community list name, a case-sensitive string of 1 to 63 characters that cannot contain only letters.
adv-comm-list-name: Specifies the advanced community list name, a case-sensitive string of 1 to 63 characters that cannot contain only letters.
adv-comm-list-num: Specifies the advanced community list number in the range of 100 to 199.
regular-expression: Specifies a regular expression for the advanced community list, a string of 1 to 63 characters. For more information about regular expressions, see Fundamentals Configuration Guide.
deny: Specifies the match mode for the community list as deny.
permit: Specifies the match mode for the community list as permit.
community-number&<1-32>: Specifies a community sequence number in the range of 1 to 4294967295. &<1-32> indicates that the argument before it can be entered up to 32 times.
aa:nn&<1-32>: Specifies a community number. Both aa and nn are in the range of 0 to 65535. &<1-32> indicates that the argument before it can be entered up to 32 times.
internet: Specifies the INTERNET community attribute. Routes with this attribute can be advertised to all BGP peers. By default, all routes have this attribute.
no-advertise: Specifies the NO_ADVERTISE community attribute. Routes with this attribute cannot be advertised to other BGP peers.
no-export: Specifies the NO_EXPORT community attribute. Routes with this attribute cannot be advertised out of the local AS or the local confederation but can be advertised to other ASs in the confederation.
no-export-subconfed: Specifies the NO_EXPORT_SUBCONFED community attribute. Routes with this attribute cannot be advertised out of the local AS, or to other sub-ASs in the local confederation.
Examples
# Configure basic community list 1 to permit routes with the INTERNET community attribute.
<Sysname> system-view
[Sysname] ip community-list 1 permit internet
# Configure advanced community list 100 to permit routes with the COMMUNITY attribute starting with 10.
<Sysname> system-view
[Sysname] ip community-list 100 permit ^10
Related commands
· apply comm-list delete
· apply community
· display ip community-list
· if-match community
route-policy
Use route-policy to create a routing policy and a node, and enter routing policy node view.
Use undo route-policy to remove a routing policy or a node of it.
Syntax
route-policy route-policy-name { deny | permit } node node-number
undo route-policy route-policy-name [ deny | permit ] [ node node-number ]
Default
No routing policy is created.
Views
System view
Predefined user roles
network-admin
Parameters
route-policy-name: Specifies a name for the routing policy, a case-sensitive string of 1 to 63 characters.
deny: Specifies the deny match mode for the routing policy node. If a route matches all the if-match clauses of the node, it is denied without matching against the next node. If not, it matches against the next node.
permit: Specifies the permit match mode for the routing policy node. If a route matches all the if-match clauses of the node, it is handled by the apply clauses of the node. If not, it matches against the next node.
node node-number: Specifies a number for the node, in the range of 0 to 65535. A node with a smaller number is matched first.
Usage guidelines
Use a routing policy to filter routing information. A routing policy can contain several nodes and each node contains a set of if-match and apply clauses. The if-match clauses define the match criteria of the node and the apply clauses define the actions to be taken on packets matching the criteria. The relation between the if-match clauses of a node is logical AND. All the if-match clauses must be met. The relation between nodes is logical OR. A packet passing a node passes the routing policy.
Examples
# Create node 10 in permit mode for routing policy policy1 and enter routing policy node view.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10]
Related commands
display route-policy
IPv4 routing policy commands
apply fast-reroute
Use apply fast-reroute to set a backup link for fast route (FRR).
Use undo apply fast-reroute to remove the configuration.
Syntax
undo apply fast-reroute
Default
No backup link for FRR is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
backup-interface interface-type interface-number: Specifies a backup output interface. If the specified interface is a non-P2P interface, you must also specify a backup next hop. Non-P2P interfaces include NBMA and broadcast interfaces such as Ethernet interfaces or VLAN interfaces.
backup-nexthop ip-address: Specifies a backup next hop.
Usage guidelines
This command sets a backup link in the routing policy for FRR.
Using the routing policy, a routing protocol can designate a backup link for specific routes to implement FRR. When the primary link fails, FRR immediately directs packets to the backup link to minimize interruption time.
Examples
# Configure node 10 of routing policy policy1 to set the backup output interface VLAN-interface 1 and backup next hop 193.1.1.8 for the route destined to 100.1.1.0/24.
<Sysname> system-view
[Sysname] ip prefix-list abc index 10 permit 100.1.1.0 24
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ip address prefix-list abc
[Sysname-route-policy-policy1-10] apply fast-reroute backup-interface vlan-interface 1 backup-nexthop 193.1.1.8
apply ip-address next-hop
Use apply ip-address next-hop to set a next hop for IPv4 routes.
Use undo apply ip-address next-hop to restore the default.
Syntax
apply ip-address next-hop ip-address [ public ]
undo apply ip-address next-hop
Default
No next hop is set for IPv4 routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
ip-address: Specifies the next hop IP address.
public: Specifies the public network.
Usage guidelines
This command cannot set a next hop for redistributed routes.
If you do not specify the public keyword, the next hop belongs to the public network.
Examples
# Configure node 10 in permit mode for routing policy policy1 to set next hop 193.1.1.8 for routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply ip-address next-hop 193.1.1.8
display ip prefix-list
Use display ip prefix-list to display IPv4 prefix list statistics.
Syntax
display ip prefix-list [ name prefix-list-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays statistics for all IPv4 prefix lists.
Examples
# Display the statistics for IPv4 prefix list abc.
<Sysname> display ip prefix-list name abc
Prefix-list: abc
Permitted 0
Denied 0
index: 10 deny 6.6.6.0/24 ge 26 le 28
Table 4 Command output
|
Field |
Description |
|
Prefix-list |
Name of the IPv4 prefix list. |
|
Permitted |
Number of routes matching the criterion. |
|
Denied |
Number of routes not matching the criterion. |
|
index |
Index of an item. |
|
deny |
Match mode of the item: · permit. · deny. |
|
6.6.6.0/24 |
IP address and mask. |
|
ge |
Greater-equal, the lower mask length. |
|
le |
Less-equal, the upper mask length. |
Related commands
· ip prefix-list
· reset ip prefix-list
if-match ip
Use if-match ip to match IPv4 routes whose destination, next hop, or source address matches an ACL or IPv4 prefix list.
Use undo if-match ip to remove the configuration.
Syntax
if-match ip { address | next-hop | route-source } { acl acl-number | prefix-list prefix-list-name }
undo if-match ip { address | next-hop | route-source } [ acl | prefix-list ]
Default
No ACL or IPv4 prefix list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
address: Matches the destination address of IPv4 routes.
next-hop: Matches the next hop of IPv4 routes.
route-source: Matches the source address of IPv4 routes.
acl acl-number: Specifies an ACL by its number. The value range is 2000 to 3999 for the address keyword, and 2000 to 2999 for the next-hop and route-source keywords.
prefix-list prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters.
Examples
# Configure node 10 of routing policy policy1 to match IPv4 routes whose next hop matches IP prefix list p1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ip next-hop prefix-list p1
ip prefix-list
Use ip prefix-list to configure an IPv4 prefix list or an item for the list.
Use undo ip prefix-list to remove an IPv4 prefix list or an item of it.
Syntax
ip prefix-list prefix-list-name [ index index-number ] { deny | permit } ip-address mask-length [ greater-equal min-mask-length ] [ less-equal max-mask-length ]
undo ip prefix-list prefix-list-name [ index index-number ]
Default
No IPv4 prefix list is configured.
Views
System view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies a name for the IPv4 prefix list, a case-sensitive string of 1 to 63 characters.
index-number: Specifies an index number for an IPv4 prefix list item, in the range of 1 to 65535. An item with a smaller number is matched first.
deny: Specifies the deny mode. If a route matches the item, the route is denied without matching against the next item. If not, the route matches against the next item (suppose the IPv4 prefix list has multiple items).
permit: Specifies the permit mode. If a route matches the item, it passes the IPv4 prefix list. If not, it matches against the next item (suppose the IPv4 prefix list has multiple items).
ip-address mask-length: Specifies an IPv4 prefix and mask length. The value range for the mask-length argument is 0 to 32.
min-mask-length, max-mask-length: Specifies a prefix length range. The greater-equal keyword means "greater than or equal to" and the less-equal keyword means "less than or equal to." The range relation is mask-length <= min-mask-length <= max-mask-length <= 32.
· If only the min-mask-length argument is specified, the prefix length range is [ min-mask-length, 32 ].
· If only the max-mask-length argument is specified, the prefix length range is [ mask-length, max-mask-length ].
· If both the min-mask-length and max-mask-length arguments are specified, the prefix length range is [ min-mask-length, max-mask-length ].
Usage guidelines
An IPv4 prefix list is used to filter IPv4 addresses. It can contain multiple items, each of which specifies a range of IPv4 prefixes. The relation between the items is logical OR. If an item is passed, the IPv4 prefix list is passed. If no item is passed, the IP prefix list cannot be passed.
If both the ip-address and mask-length arguments are specified as 0.0.0.0 0, only the default route will be matched.
To match all routes, use 0.0.0.0 0 less-equal 32.
Examples
# Configure IP prefix list p1 to permit routes destined for network 10.0.0.0/8 and with mask length 17 or 18.
<Sysname> system-view
[Sysname] ip prefix-list p1 permit 10.0.0.0 8 greater-equal 17 less-equal 18
Related commands
· display ip prefix-list
· reset ip prefix-list
reset ip prefix-list
Use reset ip prefix-list to clear IPv4 prefix list statistics.
Syntax
reset ip prefix-list [ prefix-list-name ]
Views
User view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies an IP prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics for all IPv4 prefix lists.
Examples
# Clear the statistics for IPv4 prefix list abc.
<Sysname> reset ip prefix-list abc
Related commands
· display ip prefix-list
· ip prefix-list
IPv6 routing policy commands
apply ipv6 fast-reroute
Use apply ipv6 fast-reroute to set a backup link for FRR.
Use undo apply ipv6 fast-reroute to remove the configuration.
Syntax
apply ipv6 fast-reroute backup-nexthop ipv6-address
undo apply ipv6 fast-reroute
Default
No backup link for FRR is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
backup-nexthop ipv6-address: Specifies an IPv6 backup next hop.
Usage guidelines
This command sets a backup link in the routing policy for FRR.
Using the routing policy, a routing protocol can designate a backup link for specific routes to implement FRR. When the primary link fails, FRR immediately directs packets to the backup link to minimize interruption time.
Examples
# Configure node 10 of routing policy policy1 to set the backup next hop 1::1/64 for the route destined to 100::1/64.
[Sysname] ipv6 prefix-list abc index 10 permit 100::1 64
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ipv6 address prefix-list abc
[Sysname-route-policy-policy1-10] apply ipv6 fast-reroute backup-nexthop 1::1
apply ipv6 next-hop
Use apply ipv6 next-hop to set a next hop for IPv6 routes.
Use undo apply ipv6 next-hop to restore the default.
Syntax
apply ipv6 next-hop ipv6-address
undo apply ipv6 next-hop
Default
No next hop is set for IPv6 routes.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
ipv6-address: Specifies the next hop IPv6 address.
Usage guidelines
This command cannot set a next hop for redistributed routes.
Examples
# Configure node 10 for routing policy policy1 to set next hop 3ffe:506::1 for IPv6 routes matching AS path list 1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match as-path 1
[Sysname-route-policy-policy1-10] apply ipv6 next-hop 3ffe:506::1
display ipv6 prefix-list
Use display ipv6 prefix-list to display IPv6 prefix list statistics.
Syntax
display ipv6 prefix-list [ name prefix-list-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
name prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this option, the command displays statistics for all IPv6 prefix lists.
Examples
# Display the statistics for all IPv6 prefix lists.
<Sysname> display ipv6 prefix-list
Prefix-list6: 666
Permitted 0
Denied 0
index: 10 permit 6::/64 ge 66 le 88
Table 5 Command output
|
Field |
Description |
|
Prefix-list6 |
Name of the IPv6 prefix list. |
|
Permitted |
Number of routes matching the criterion. |
|
Denied |
Number of routes not matching the criterion. |
|
index |
Index number of an item. |
|
permit |
Match mode of the item: · permit. · deny. |
|
6::/64 |
IPv6 address and prefix length for matching. |
|
ge |
Greater-equal, the lower prefix length. |
|
le |
Less-equal, the upper prefix length. |
Related commands
· ipv6 prefix-list
· reset ipv6 prefix-list
if-match ipv6
Use if-match ipv6 to match IPv6 routes whose destination, next hop, or source address matches an ACL or IPv6 prefix list.
Use undo if-match ipv6 to remove the configuration.
Syntax
if-match ipv6 { address | next-hop | route-source } { acl acl6-number | prefix-list prefix-list-name
undo if-match ipv6 { address | next-hop | route-source } [ acl | prefix-list ]
Default
No ACL or IPv6 prefix list match criterion is configured.
Views
Routing policy node view
Predefined user roles
network-admin
Parameters
address: Matches the destination address of IPv6 routes.
next-hop: Matches the next hop of IPv6 routes.
route-source: Matches the source address of IPv6 routes.
acl acl6-number: Specifies an IPv6 ACL by its number. The value range is 2000 to 3999 for the address keyword, and 2000 to 2999 for the next-hop and route-source keywords.
prefix-list prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters.
Examples
# Configure node 10 of routing policy policy1 to permit routes whose next hop matches IPv6 prefix list p1.
<Sysname> system-view
[Sysname] route-policy policy1 permit node 10
[Sysname-route-policy-policy1-10] if-match ipv6 next-hop prefix-list p1
ipv6 prefix-list
Use ipv6 prefix-list to configure an IPv6 prefix list or an item for it.
Use undo ipv6 prefix-list to remove an IPv6 prefix list or an item.
Syntax
ipv6 prefix-list prefix-list-name [ index index-number ] { deny | permit } ipv6-address prefix-length [ greater-equal min-prefix-length ] [ less-equal max-prefix-length ]
undo ipv6 prefix-list prefix-list-name [ index index-number ]
Default
No IPv6 prefix list is configured.
Views
System view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies a name for the IPv6 prefix list, a case-sensitive string of 1 to 63 characters.
index-number: Specifies an index number for an IPv6 prefix list item, in the range of 1 to 65535. An item with a smaller number is matched first.
deny: Specifies the deny mode. If a route matches the item, the route is denied without matching against the next item; if not, the route matches against the next item (suppose the IPv6 prefix list has multiple items).
permit: Specifies the permit mode. If a route matches the item, it passes the IPv4 prefix list. If not, it matches against the next item (suppose the IPv6 prefix list has multiple items).
ipv6-address prefix-length: Specifies an IPv6 prefix and prefix length. The value range for the prefix-length argument is 0 to 128. When specified as :: 0, the argument matches the default route.
greater-equal min-prefix-length: Greater than or equal to the minimum prefix length.
less-equal max-prefix-length: Less than or equal to the maximum prefix length.
The length relation is mask-length <= min-mask-length <= max-mask-length <= 128.
· If only the min-prefix-length argument is specified, the prefix length range is [ min-prefix-length, 128 ].
· If only the max-prefix-length argument is specified, the prefix length range is [ prefix-length, max-prefix-length ].
· If both the min-prefix-length and max-prefix-length arguments are specified, the prefix length range is [ min-prefix-length, max-prefix-length ].
inverse prefix-length: Matches IPv6 addresses from the least significant bit to the specified length. The value range for the prefix-length argument is 1 to 128.
Usage guidelines
An IPv6 prefix list can have multiple items, and each of them specifies a range of IPv6 prefixes. The relation between the items is logical OR. If a route passes an item, it passes the IPv6 prefix list.
If the ipv6-address prefix-length argument is specified as :: 0, only the default route matches.
To match all routes, configure :: 0 less-equal 128.
Examples
# Permit IPv6 addresses with a mask length between 32 bits and 64 bits.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc permit :: 0 greater-equal 32 less-equal 64
# Deny IPv6 addresses with a prefix 3FFE:D00::/32 and a prefix length greater than or equal to 32 bits.
<Sysname> system-view
[Sysname] ipv6 prefix-list abc deny 3FFE:D00:: 32 less-equal 128
# Permit IPv6 addresses whose least significant bit is 0.
[Sysname] ipv6 prefix-list abc permit ::0 inverse 1
# Permit IPv6 addresses whose least significant bit is 1.
[Sysname] ipv6 prefix-list abc permit ::1 inverse 1
Related commands
· display ipv6 prefix-list
· reset ipv6 prefix-list
reset ipv6 prefix-list
Use reset ipv6 prefix-list to clear IPv6 prefix list statistics.
Syntax
reset ipv6 prefix-list [ prefix-list-name ]
Views
User view
Predefined user roles
network-admin
Parameters
prefix-list-name: Specifies an IPv6 prefix list by its name, a case-sensitive string of 1 to 63 characters. If you do not specify this argument, the command clears statistics for all IPv6 prefix lists.
Examples
# Clear the statistics for IPv6 prefix list abc.
<Sysname> reset ipv6 prefix-list abc
Related commands
· display ipv6 prefix-list
· ipv6 prefix-list
