- Table of Contents
-
- 07-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
- 14-MTR commands
- 15-DCN commands
- Related Documents
-
Title | Size | Download |
---|---|---|
07-Policy-based routing commands | 91.67 KB |
apply default-output-interface
display ip policy-based-route interface
display ip policy-based-route local
display ip policy-based-route setup
reset ip policy-based-route statistics
Policy-based routing commands
apply access-vpn vpn-instance
Use apply access-vpn vpn-instance to set VPN instances.
Use undo apply access-vpn vpn-instance to remove VPN instances.
Syntax
apply access-vpn vpn-instance vpn-instance-name&<1-n>
undo apply access-vpn vpn-instance [ vpn-instance-name&<1-n> ]
Default
No VPN instance is specified for a node.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify a maximum of four VPN instances for a node. The matching packets are forwarded according to the forwarding table of the first available VPN instance.
With a VPN instance specified, the undo apply access-vpn vpn-instance command removes the VPN instance.
Without any VPN instance specified, the undo apply access-vpn vpn-instance command removes all VPN instances.
Examples
# Set VPN 1 and VPN 2 for node 10. (VPN 1 and VPN 2 already exist.)
<Sysname> system-view
[Sysname] policy-based-route policy1 permit node 10
[Sysname-pbr-policy1-10] apply access-vpn vpn-instance vpn1 vpn2
Related commands
apply remark-vpn
apply continue
Use apply continue to compare packets with the next policy node upon failure on the current node.
Use undo apply continue to restore the default.
Syntax
apply continue
undo apply continue
Default
PBR does not compare packets with the next policy node upon failure on the current node.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
This command takes effect only when the match mode of the node is permit.
This command applies when the following clauses are not configured or become invalid:
· apply access-vpn vpn-instance
· apply next-hop
· apply output-interface
· apply default-next-hop
· apply default-output-interface
For example, the command applies when the specified next hop is unreachable, the specified output interface is down, or the packets cannot be forwarded in the specified VPN instance.
Examples
# Compare with the next policy node upon failure on the current node.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply continue
apply default-next-hop
Use apply default-next-hop to set default next hops.
Use undo apply default-next-hop to remove default next hops.
Syntax
apply default-next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ip-address [ direct ] [ track track-entry-number ] }&<1-n>
undo apply default-next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ip-address&<1-n> ]
Default
No default next hop is set.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ip-address: Specifies the IP address of the default next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the default next hop belongs to the public network.
direct: Specifies a directly connected default next hop.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple default next hops for backup or load sharing in one command line or by executing this command multiple times.
With a default next hop specified, the undo apply default-next-hop command removes the default next hop.
Without any default next hop specified, the undo apply default-next-hop command removes all default next hops.
Examples
# Set a directly-connected default next hop of 1.1.1.1.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-next-hop 1.1.1.1 direct
Related commands
apply loadshare
apply default-output-interface
Use apply default-output-interface to set default output interfaces.
Use undo apply default-output-interface to remove default output interfaces.
Syntax
apply default-output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply default-output-interface [ { interface-type interface-number }&<1-n> ]
Default
No default output interface is set.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple default output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The default output interface must be P2P type. Using a non-P2P default output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and non-broadcast multi-access (NBMA) interfaces such as Ethernet and virtual-template interfaces. In NBMA networks, packets are sent in unicast.
With a default output interface specified, the undo apply default-output-interface command removes the default output interface.
Without any default output interface specified, the undo apply default-output-interface command removes all default output interfaces.
Examples
# Specify GigabitEthernet 2/1/1 as the default output interface for IP packets.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-output-interface gigabitethernet 2/1/1
Related commands
apply loadshare
apply ip-df
Use apply ip-df to set the Don't Fragment (DF) bit in the IP header of matching packets.
Use undo apply ip-df to restore the default.
Syntax
apply ip-df df-value
undo apply ip-df
Default
The DF bit is not set.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
df-value: Sets the DF bit in the IP header of matching packets. The value can be 0 or 1.
Usage guidelines
Setting the DF bit to 0 allows packet fragmentation.
Setting the DF bit to 1 prohibits packet fragmentation.
Examples
# Set the DF bit in the IP header of matching packets to 0.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply ip-df 0
apply loadshare
Use apply loadshare to enable load sharing among multiple next hops, output interfaces, default next hops, or default output interfaces.
Use undo apply loadshare to restore the default.
Syntax
apply loadshare { default-next-hop | default-output-interface | next-hop | output-interface }
undo apply loadshare { default-next-hop | default-output-interface | next-hop | output-interface }
Default
Multiple next hops, output interfaces, default next hops, or default output interfaces operate in primary/backup mode.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
default-next-hop: Enables load sharing among multiple default next hops.
default-output-interface: Enables load sharing among multiple default output interfaces.
next-hop: Enables load sharing among multiple next hops.
output-interface: Enables load sharing among multiple output interfaces.
Usage guidelines
Multiple next hops, output interfaces, default next hops, or default output interfaces operate in either primary/backup or load sharing mode. For example:
· Primary/backup mode—The first configured output interface is used. When the primary output interface fails, the first configured backup output interface takes over.
· Load sharing mode—Multiple output interfaces load share traffic on a per-packet basis in turn, according to the configuration order.
|
NOTE: Multiple next hops load share traffic according to their weights. By default, all next hops have the same weight and traffic is load balanced among them. |
Examples
# Enable load sharing among multiple next hops.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply next-hop 1.1.1.1 2.2.2.2
[Sysname-pbr-aa-11] apply loadshare next-hop
# Enable load sharing among multiple output interfaces.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply output-interface gigabitethernet 2/1/1 gigabitethernet 2/1/2
[Sysname-pbr-aa-11] apply loadshare output-interface
# Enable load sharing among multiple default next hops.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-next-hop 1.1.1.1 2.2.2.2
[Sysname-pbr-aa-11] apply loadshare default-next-hop
# Enable load sharing among multiple default output interfaces.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply default-output-interface gigabitethernet 2/1/1 gigabitethernet 2/1/2
[Sysname-pbr-aa-11] apply loadshare default-output-interface
Related commands
apply default-next-hop
apply default-output-interface
apply next-hop
apply output-interface
apply next-hop
Use apply next-hop to set next hops.
Use undo apply next-hop to remove next hops.
Syntax
apply next-hop [ vpn-instance vpn-instance-name| inbound-vpn ] { ip-address [ direct ] [ track track-entry-number ] [ weight weight-value ] }&<1-n>
undo apply next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ip-address&<1-n> ]
Default
No next hop is set.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.
inbound-vpn: Specifies the VPN instance where the inbound interface belongs.
ip-address: Specifies the IP address of the next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the next hop belongs to the public network.
direct: Specifies that the next hop must be directly connected to take effect.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
weight weight-value: Specifies a load sharing weight for the next hop, in the range of 1 to 100. The default is 10. If you specify weights 1, 1, and 2 for three next hops, they share 1/4, 1/4, and 1/2 of the whole traffic, respectively.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple next hops for backup or load sharing in one command line or by executing this command multiple times.
With a next hop specified, the undo apply next-hop command removes the next hop.
Without any next hop specified, the undo apply next-hop command removes all next hops.
Examples
# Set a directly-connected next hop of 1.1.1.1.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply next-hop 1.1.1.1 direct
apply loadshare
apply output-interface
Use apply output-interface to set output interfaces.
Use undo apply output-interface to remove output interfaces.
Syntax
apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-n>
undo apply output-interface [ { interface-type interface-number }&<1-n> ]
Default
No output interface is set.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.
&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n is 4.
Usage guidelines
You can specify multiple output interfaces for backup or load sharing in one command line or by executing this command multiple times.
The output interface must be P2P type. Using a non-P2P output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and NBMA interfaces such as Ethernet and virtual-template interfaces.
With an output interface specified, the undo apply output-interface command removes the output interface.
Without any output interface specified, the undo apply output-interface command removes all output interfaces.
Examples
# Specify GigabitEthernet 2/1/1 as the output interface for IP packets.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply output-interface gigabitethernet 2/1/1
Related commands
apply loadshare
apply precedence
Use apply precedence to set a precedence for IP packets.
Use undo apply precedence to restore the default.
Syntax
apply precedence { type | value }
undo apply precedence
Default
No precedence is set for IP packets.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
type: Specifies the precedence type for IP packets.
value: Specifies the precedence for IP packets. Eight precedence values (0 to 7) are available. Each precedence value corresponds to a precedence type, as shown in Table 1. You can set either a precedence value or a precedence type for IP packets.
Table 1 IP precedences and corresponding types
Precedence value |
Precedence type |
0 |
routine |
1 |
priority |
2 |
immediate |
3 |
flash |
4 |
flash-override |
5 |
critical |
6 |
internet |
7 |
network |
Examples
# Set the precedence to 5 (critical) for IP packets.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] apply precedence critical
apply remark-vpn
Use apply remark-vpn to mark the VPN instance for matching packets.
Use undo apply remark-vpn to restore the default.
Syntax
apply remark-vpn
undo apply remark-vpn
Default
The VPN instance is not marked for matching packets.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
The apply access-vpn vpn-instance command is used to forward matching packets in a specified VPN instance. To make the VPN instance known to the service modules, use the apply remark-vpn command to mark the VPN instance in the packets.
This command must be used together with the apply access-vpn vpn-instance command.
This command marks a VPN instance in a packet only when the packet is forwarded in the VPN instance specified by the apply access-vpn vpn-instance command.
Examples
# Mark VPN instance vpn1 for packets that match ACL 3000.
<Sysname> system-view
[Sysname] policy-based-route aaa permit node 10
[Sysname-pbr-aaa-10] if-match acl 3000
[Sysname-pbr-aaa-10] apply access-vpn vpn-instance vpn1
[Sysname-pbr-aaa-10] apply remark-vpn
Related commands
apply access-vpn vpn-instance
display ip policy-based-route
Use display ip policy-based-route to display PBR policy information.
Syntax
display ip policy-based-route [ policy policy-name ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command displays information for all PBR policies.
Examples
# Display all policy information.
<Sysname> display ip policy-based-route
Policy name: aaa
node 1 permit:
if-match acl 2000
apply next-hop 1.1.1.1
Table 2 Command output
Field |
Description |
node 1 permit |
The match mode of Node 1 is permit. |
if-match acl |
Compares packets with the ACL. |
apply next-hop |
Specifies a next hop for permitted packets. |
Related commands
policy-based-route
display ip policy-based-route interface
Use display ip policy-based-route interface to display interface PBR configuration and statistics.
Syntax
In standalone mode:
display ip policy-based-route interface interface-type interface-number [ slot slot-number ]
In IRF mode:
display ip policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
interface-type interface-number: Specifies an interface by its type and number.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays interface PBR configuration and statistics on the active MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays interface PBR configuration and statistics on the global active MPU. (In IRF mode.)
Examples
# Display PBR configuration and statistics on GigabitEthernet 2/1/1.
<Sysname> display ip policy-based-route interface gigabitethernet 2/1/1
Policy based routing information for interface GigabitEthernet2/1/1(failed):
Policy name: aaa
node 0 deny:
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit:
if-match acl 2000
apply next-hop 2.2.2.2
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1.1.1.1
apply output-interface GigabitEthernet2/1/2 track 1 (down)
apply output-interface GigabitEthernet2/1/3 track 2 (inactive)
Matched: 0
Total matched: 0
<Sysname> display ip policy-based-route interface gigabitethernet 2/1/1
Policy based routing information for interface GigabitEthernet2/1/1:
Policy name: aaa
node 0 deny(not support):
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit(no resource):
if-match acl 2000
apply next-hop 2.2.2.2
apply output-interface GigabitEthernet2/1/2 track 1 (down)
apply output-interface GigabitEthernet2/1/3 track 2 (inactive)
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1.1.1.1
Matched: 0 (no statistics resource)
Total matched: 0
Table 3 Command output
Field |
Description |
Policy based routing information for interface GigabitEthernet2/1/1(failed) |
PBR configuration and statistics on GigabitEthernet 2/1/1. failed indicates that the policy (including all its nodes) failed to be assigned to the driver. For a global interface (with only a one-dimensional interface number, for example, VLAN-interface 10), failed can be displayed only when you specify the slot slot-number or chassis chassis-number slot slot-number option for the command. |
node 0 deny(not support) node 2 permit(no resource) |
Match mode of the node, permit or deny. not support means the device does not support match criteria configured on the node. no resource means the device has insufficient ACL resources, and failed to assign ACL resources to the node. For a global interface (with only a one-dimensional interface number, for example, VLAN-interface 10), not support and no resource can be displayed only when you specify the slot slot-number or chassis chassis-number slot slot-number option for the command. |
if-match acl |
Compares packets with the ACL. |
apply next-hop |
Specifies a next hop for permitted packets. |
apply output-interface GigabitEthernet2/1/2 track 1 (down) |
Specifies an output interface for permitted packets. The interface status includes the following: · up—The interface is up. · down—The interface is down at network layer. · inactive—The card that hosts the interface is not in position. |
Matched: 0 (no statistics resource) |
Number of successful matches on the node (no statistics resource indicates insufficient statistics resources). For a global interface (with only a one-dimensional interface number, for example, VLAN-interface 10), no statistics resource can be displayed only when you specify the slot slot-number or chassis chassis-number slot slot-number option for the command. |
Total matched |
Total number of successful matches on all nodes. |
Related commands
reset ip policy-based-route statistics
display ip policy-based-route local
Use display ip policy-based-route local to display local PBR configuration and statistics.
Syntax
In standalone mode:
display ip policy-based-route local [ slot slot-number ]
In IRF mode:
display ip policy-based-route local [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays local PBR configuration and statistics on the active MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays local PBR configuration and statistics on the global active MPU. (In IRF mode.)
Examples
# Display local PBR configuration and statistics.
<Sysname> display ip policy-based-route local
Policy based routing information for local:
Policy name: aaa
node 0 deny:
Matched: 0
node 1 permit:
if-match acl 3999
Matched: 0
node 2 permit:
if-match acl 2000
apply next-hop 2.2.2.2
Matched: 0
node 5 permit:
if-match acl 3101
apply next-hop 1.1.1.1
Matched: 0
Total matched: 0
Table 4 Command output
Field |
Description |
Policy based routing information for local |
Local PBR configuration and statistics. |
node 0 deny/node 2 permit |
Match mode of the node: permit or deny. |
if-match acl |
Compares packets with the ACL. |
apply next-hop |
Specifies a next hop for permitted packets. |
Matched: 0 |
Number of successful matches on the node. |
Total matched |
Total number of successful matches on all nodes. |
Related commands
reset ip policy-based-route statistics
display ip policy-based-route setup
Use display ip policy-based-route setup to display PBR configuration.
Syntax
display ip policy-based-route setup
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Examples
# Display PBR configuration.
<Sysname> display ip policy-based-route setup
Policy Name Interface Name
pr01 GigabitEthernet 2/1/1
Table 5 Command output
Field |
Description |
Interface Name |
Interface where the policy is applied. |
Related commands
ip policy-based-route
if-match acl
Use if-match acl to set an ACL match criterion.
Use undo if-match acl to restore the default.
Syntax
if-match acl { acl-number | name acl-name }
undo if-match acl
Default
No ACL match criterion is set.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
acl-number: Specifies an ACL by its number in the range of 2000 to 2999 for a basic ACL, and in the range of 3000 to 3999 for an advanced ACL.
name acl-name: Specifies an ACL by its name, a case-insensitive string of 1 to 63 characters starting with letter a to z or A to Z. The ACL name cannot be all.
Examples
# Configure Node 11 of policy aa to permit the packets matching ACL 2011.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match acl 2011
# Configure Node 11 of policy aa to permit the packets matching ACL aaa.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match acl name aaa
if-match packet-length
Use if-match packet-length to set a packet length match criterion.
Use undo if-match packet-length to delete the match criterion.
Syntax
if-match packet-length min-len max-len
undo if-match packet-length
Default
No packet length match criterion is set.
Views
Policy node view
Predefined user roles
network-admin
mdc-admin
Parameters
min-len: Specifies the minimum IP packet length in the range of 1 to 65535 bytes.
max-len: Specifies the maximum IP packet length in the range of 1 to 65535 bytes. The maximum length must be no less than the minimum length.
Usage guidelines
Use this command to set a criterion to match the total length of data packets.
The packet length range includes boundary values. For example, if you set the min-len and max-len arguments to 100 and 200, respectively, packets with lengths of 100 bytes and 200 bytes are also matched.
Examples
# Match packets with a length from 100 to 200 bytes.
<Sysname> system-view
[Sysname] policy-based-route aa permit node 11
[Sysname-pbr-aa-11] if-match packet-length 100 200
ip local policy-based-route
Use ip local policy-based-route to configure local PBR based on a policy.
Use undo ip local policy-based-route to restore the default.
Syntax
ip local policy-based-route policy-name
undo ip local policy-based-route
Default
No policy is referenced for local PBR.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified policy must already exist.
Usage guidelines
You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.
Local PBR is used to route locally generated packets except the packets destined for the sender. This feature might affect local services. Do not configure local PBR unless doing so is required.
Examples
# Configure local PBR based on policy aaa.
<Sysname> system-view
[Sysname] ip local policy-based-route aaa
Related commands
display ip policy-based-route setup
policy-based-route
ip policy-based-route
Use ip policy-based-route to configure interface PBR by applying a policy to an interface.
Use undo ip policy-based-route to restore the default.
Syntax
ip policy-based-route policy-name
undo ip policy-based-route
Default
No policy is applied to an interface.
Views
Interface view
Predefined user roles
network-admin
mdc-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. The specified policy must already exist.
Usage guidelines
You can apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface.
Examples
# Apply policy aaa to GigabitEthernet 2/1/1.
<Sysname> system-view
[Sysname] interface gigabitethernet 2/1/1
[Sysname-GigabitEthernet2/1/1] ip policy-based-route aaa
Related commands
display ip policy-based-route setup
policy-based-route
policy-based-route
Use policy-based-route to create a policy node and enter its view, or enter the view of an existing policy node.
Use undo policy-based-route to delete a policy or policy node.
Syntax
policy-based-route policy-name [ deny | permit ] node node-number
undo policy-based-route policy-name [ deny | node node-number | permit ]
Default
No policy nodes exist.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters.
deny: Specifies the match mode for the policy node as deny.
permit: Specifies the match mode for the policy node as permit (default mode).
node node-number: Specifies a policy node by its number. A smaller number has a higher priority. The value range for the node-number argument is 0 to 65535.
Usage guidelines
A policy that has been applied to an interface or locally cannot be deleted. To delete it, you must first cancel the application.
· If a policy node is specified, the undo policy-based-route command deletes the specified policy node.
· If a match mode is specified, the command deletes all nodes configured with the match mode.
· If no policy node or match mode is specified, the command deletes the whole policy.
Examples
# Create permit-mode of Node 10 for policy policy1 and enter its view.
<Sysname> system-view
[Sysname] policy-based-route policy1 permit node 10
[Sysname-pbr-policy1-10]
Related commands
display ip policy-based-route
reset ip policy-based-route statistics
Use reset ip policy-based-route statistics to clear PBR statistics.
Syntax
reset ip policy-based-route statistics [ policy policy-name ]
Views
User view
Predefined user roles
network-admin
mdc-admin
Parameters
policy policy-name: Specifies a policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a policy, this command clears PBR statistics for all policies.
Examples
# Clear all PBR statistics.
<Sysname> reset ip policy-based-route statistics
Related commands
display ip policy-based-route interface
display ip policy-based-route local