Contents

Policy-based routing commands· 1

apply access-vpn vpn-instance· 1

apply continue· 1

apply default-next-hop· 2

apply default-output-interface· 3

apply default-srv6-policy· 4

apply ip-df 5

apply loadshare· 6

apply next-hop· 7

apply output-interface· 8

apply precedence· 9

apply remark-vpn· 10

apply srv6-policy· 11

description· 12

display ip policy-based-route· 13

display ip policy-based-route global 14

display ip policy-based-route interface· 15

display ip policy-based-route local 18

display ip policy-based-route setup· 20

if-match acl 20

if-match app-group· 21

if-match packet-length· 22

if-match source-ip· 22

ip global policy-based-route· 23

ip local policy-based-route· 24

ip policy-based-route· 25

policy-based-route· 26

reset ip policy-based-route statistics· 27

 

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 instances are specified for a node.

Views

Policy node view

Predefined user roles

network-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.

Usage guidelines

You can specify a maximum of n 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

Usage guidelines

This command takes effect only when the match mode of the node is permit.

This command applies when either of the following conditions exist:

·     None of the following clauses is configured for packet forwarding:

¡     apply access-vpn vpn-instance

¡     apply next-hop

¡     apply output-interface

¡     apply default-next-hop

¡     apply default-output-interface

·     A clause listed above is configured, but it has become invalid. Then, a routing table lookup also fails for the matching packet.

‌

NOTE: A clause might become invalid because the specified next hop is unreachable, packets cannot be forwarded in the specified VPN instance, or the specified output interface is down.

‌

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 hops are set.

Views

Policy node view

Predefined user roles

network-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 instance 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.

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 interfaces are set.

Views

Policy node view

Predefined user roles

network-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.

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 0/0/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 0/0/1

Related commands

apply loadshare

apply default-srv6-policy

Use apply default-srv6-policy to set default SRv6 TE policies.

Use undo apply default-srv6-policy to remove default SRv6 TE policies.

Syntax

apply default-srv6-policy { endpoint color [ { sid | vpnsid } sid ] }&<1-n>

undo apply default-srv6-policy [ { endpoint color }&<1-n> ]

Default

No default SRv6 TE policies are set.

Views

Policy node view

Predefined user roles

network-admin

Parameters

endpoint: Specifies a default SRv6 TE policy by its endpoint IPv6 address.

color: Specifies a default SRv6 TE policy by its color attribute value in the range of 0 to 4294967295.

sid: Indicates that the SRv6 SID of the destination node is a public network SID.

vpnsid: Indicates that the SRv6 SID of the destination node is a VPN SID.

sid: Specifies the SRv6 SID of the destination node in IPv6 address format.

&<1-n>: Indicates that you can specify up to n default SRv6 TE policies.

Usage guidelines

You can specify multiple default SRv6 TE policies for backup in one command line or by executing this command multiple times. The first available default SRv6 TE policy selected according to configuration order will be used to forward matching packets.

Without any default SRv6 TE policy specified, the undo apply default-srv6-policy command removes all default SRv6 TE policies.

Use the { sid | vpnsid } sid option on the source node to specify the SRv6 SID of the destination node and its attribute information (public network SID or VPN SID). The attribute information is not encapsulated in packets and does not affect packet forwarding.

When encapsulating packets matching the default SRv6 TE policy, the source node adds the SRv6 SID of the destination node to the SRH header of the packets. The SRv6 SID is added after the SID list of the default SRv6 TE policy. Upon receiving the packets forwarded based on the default SRv6 TE policy, the destination node uses the specified SRv6 SID to perform an SRv6 local SID forwarding table lookup to forward the packets.

Examples

# Specify a default SRv6 TE policy with destination node IPv6 address 1000::1, color attribute value 10, and destination node SRv6 SID 2000::2.

<Sysname> system-view

[Sysname] policy-based-route aa permit node 1

[Sysname-pbr-aa-1] apply default-srv6-policy 1000::1 10 sid 2000::2

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

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, SRv6 TE policies, default SRv6 TE policies, or default output interfaces.

Use undo apply loadshare to restore the default.

Syntax

apply loadshare { default-next-hop | default-output-interface | default-srv6-policy | next-hop | output-interface | srv6-policy }

undo apply loadshare { default-next-hop | default-output-interface | default-srv6-policy | next-hop | output-interface | srv6-policy }

Default

Multiple next hops, output interfaces, default next hops, SRv6 TE policies, default SRv6 TE policies, or default output interfaces operate in primary/backup mode.

Views

Policy node view

Predefined user roles

network-admin

Parameters

default-next-hop: Enables load sharing among multiple default next hops.

default-output-interface: Enables load sharing among multiple default output interfaces.

default-srv6-policy: Enables load sharing among multiple default SRv6 TE policies.

next-hop: Enables load sharing among multiple next hops.

output-interface: Enables load sharing among multiple output interfaces.

srv6-policy: Enables load sharing among multiple SRv6 TE policies.

Usage guidelines

Multiple next hop, output interface, SRv6 TE policy, default next hop, default output interface, or default SRv6 TE policy options operate in either primary/backup or load sharing mode. The following description uses multiple next hops as an example:

·     Primary/backup mode—A next hop is selected from all next hops in configuration order for packet forwarding, with all remaining next hops as backups. When the selected next hop fails, the next available next hop takes over.

·     Load sharing mode—Matching traffic is distributed across the available next hops. If the traffic does not match any fast forwarding entries, per-packet load sharing is performed. If the traffic matches a fast forwarding entry, per-flow load sharing is performed.

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 0/0/1 gigabitethernet 0/0/2

[Sysname-pbr-aa-11] apply loadshare output-interface

# Enable load sharing among multiple SRv6 TE policies.

<Sysname> system-view

[Sysname] policy-based-route aa permit node 11

[Sysname-pbr-aa-11] apply srv6-policy 1000::1 10 sid 2000::2 3000::1 12 sid 4000::2

[Sysname-pbr-aa-11] apply loadshare srv6-policy

# 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 0/0/1 gigabitethernet 0/0/2

[Sysname-pbr-aa-11] apply loadshare default-output-interface

# Enable load sharing among multiple default SRv6 TE policies.

<Sysname> system-view

[Sysname] policy-based-route aa permit node 11

[Sysname-pbr-aa-11] apply default-srv6-policy 1000::1 10 sid 2000::2 3000::1 12 sid 4000::2

[Sysname-pbr-aa-11] apply loadshare default-srv6-policy

Related commands

apply default-next-hop

apply default-output-interface

apply default-srv6-policy

apply next-hop

apply output-interface

apply srv6-policy

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 hops are set.

Views

Policy node view

Predefined user roles

network-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 instance 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.

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

Related commands

apply loadshare

ip policy-based-route-log enable

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 interfaces are set.

Views

Policy node view

Predefined user roles

network-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.

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 0/0/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 0/0/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

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 enable VPN remark action.

Use undo apply remark-vpn to restore the default.

Syntax

apply remark-vpn

undo apply remark-vpn

Default

VPN remark action is not configured.

Views

Policy node view

Predefined user roles

network-admin

Usage guidelines

VPN remark action marks the matching packets as belonging to the VPN instance to which they are forwarded based on the apply access-vpn vpn-instance command. All subsequent service modules of PBR handle the packets as belonging to the re-marked VPN instance.

If the VPN remark action is not enabled, the forwarded matching packets are marked as belonging to the VPN instance or the public network from which they were received.

VPN remark action applies only to packets that have been successfully forwarded based on the apply access-vpn vpn-instance command.

Examples

# Forward packets that match ACL 3000 based on the forwarding table of VPN instance vpn1 and perform VPN remark action on the successfully forwarded packets.

<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

apply srv6-policy

Use apply srv6-policy to set SRv6 TE policies.

Use undo apply srv6-policy to remove SRv6 TE policies.

Syntax

apply srv6-policy { endpoint color [ { sid | vpnsid } sid ] }&<1-2>

undo apply srv6-policy [ { endpoint color }&<1-2> ]

Default

No SRv6 TE policies are set.

Views

Policy node view

Predefined user roles

network-admin

Parameters

endpoint: Specifies an SRv6 TE policy by its endpoint IPv6 address.

color: Specifies an SRv6 TE policy by its color attribute value in the range of 0 to 4294967295.

sid: Indicates that the SRv6 SID of the destination node is a public network SID.

vpnsid: Indicates that the SRv6 SID of the destination node is a VPN SID.

sid: Specifies the SRv6 SID of the destination node in IPv6 address format.

&<1-2>: Indicates that you can specify up to two SRv6 TE policies.

Usage guidelines

You can specify multiple SRv6 TE policies for backup in one command line or by executing this command multiple times. The first available SRv6 TE policy selected according to configuration order will be used to forward matching packets.

Without any SRv6 TE policy specified, the undo apply srv6-policy command removes all SRv6 TE policies.

Use the { sid | vpnsid } sid option on the source node to specify the SRv6 SID of the destination node and its attribute information (public network SID or VPN SID). The attribute information is not encapsulated in packets and does not affect packet forwarding.

When encapsulating packets matching the SRv6 TE policy, the source node adds the SRv6 SID of the destination node to the SRH header of the packets. The SRv6 SID is added after the SID list of the SRv6 TE policy. Upon receiving the packets forwarded based on the SRv6 TE policy, the destination node uses the specified SRv6 SID to perform an SRv6 local SID forwarding table lookup to forward the packets.

Examples

# Specify an SRv6 TE policy with destination node IPv6 address 1000::1, color attribute value 10, and destination node SRv6 SID 2000::2.

<Sysname> system-view

[Sysname] policy-based-route aa permit node 1

[Sysname-pbr-aa-1] apply srv6-policy 1000::1 10 sid 2000::2

description

Use description to configure a description for a policy node.

Use undo description to restore the default.

Syntax

description text

undo description

Default

No description is configured for a policy node.

Views

Policy node view

Predefined user roles

network-admin

Parameters

text: Specifies a description, a case-sensitive string of 1 to 127 characters.

Examples

# Configure the description as Officeuse for policy node 1.

<Sysname> system-view

[Sysname] policy-based-route 1 permit node 1

[Sysname-pbr-1-1] description Officeuse

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

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

  node 10 permit:

    if-match acl 3000

    apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)

    apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)

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.
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)	Specifies an SRv6 TE policy for permitted packets. Associated information about the SRv6 TE policy include: ·     Destination node IPv6 address 1000::1. ·     Color attribute value 10. ·     Destination node SRv6 SID 2000::2. ·     Next Hop Label Forwarding Entry (NHLFE) index 2150629377.
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)	Specifies a default SRv6 TE policy for permitted packets. Associated information about the SRv6 TE policy include: ·     Destination node IPv6 address 3000::3. ·     Color attribute value 20. ·     Destination node SRv6 SID 4000::4. ·     NHLFE index 2149580801.

 

Related commands

policy-based-route

display ip policy-based-route global

Use display ip policy-based-route global to display information about global PBR, including its configuration and statistics.

Syntax

display ip policy-based-route global [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information about global PBR on the active MPU.

Examples

# Display information about global PBR.

<Sysname> display ip policy-based-route global

Global policy-based routing information:

Policy name: aaa

  node 0 deny:

  Matches: 0, bytes: 0

  node 1 permit:

    if-match acl 3999

  Matches: 0, bytes: 0

  node 2 permit:

    if-match acl 2000

    apply next-hop 2.2.2.2

  Matches: 0, bytes: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1.1.1.1

  Matches: 0, bytes: 0

Total matches: 0, total bytes: 0

Table 3 Command output

Field	Description
Global policy-based routing information	Global PBR configuration and statistics. This field displays failed in brackets if none of the nodes in the policy has been successfully issued to the driver. The failed status will persist even after the policy is successfully issued. To clear the failed status, you must remove the policy and then apply it again.
node 0 deny node 2 permit	Match mode of the node, permit or deny. If a node fails to be issued to the driver, the command displays the cause in brackets, which include: ·     not support—The device does not support the match criteria configured on the node. ·     no resource—No sufficient resources (for example, ACLs) are available for the node.
if-match acl	Compares packets with the ACL.
apply next-hop	Specifies a next hop for permitted packets.
apply output-interface XXXX track 1	Specifies an output interface for permitted packets. This field displays the interface status in brackets. ·     down—The interface is down at the network layer. ·     inactive—The card that hosts the interface is not in position.
Matches	Number of successful matches on the node. If the device does not support counting successful matches on a node, this field displays N/A. If match counting is disabled on the node, this field is not displayed. If the device does not have sufficient resources to count matches, this field displays no statistics resource in brackets.
bytes	Number of matching bytes on the node. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled on the node.
Total matches	Total number of successful matches on all nodes. This field displays N/A if the device does not support counting successful matches on a node. This field is not displayed if match counting is disabled on all nodes.
total bytes	Total number of matching bytes on all nodes. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled on all nodes.

 

Related commands

ip global policy-based-route

display ip policy-based-route interface

Use display ip policy-based-route interface to display interface PBR configuration and statistics.

Syntax

display ip policy-based-route interface interface-type interface-number [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-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 information on the active MPU.

Examples

# Display PBR configuration and statistics on GigabitEthernet 0/0/1.

<Sysname> display ip policy-based-route interface gigabitethernet 0/0/1

Policy based routing information for interface GigabitEthernet0/0/1:

Policy name: aaa

  node 0 deny:

  Matches: 0, bytes: 0

  node 1 permit:

    if-match acl 3999

  Matches: 0, bytes: 0

  node 2 permit:

    if-match acl 2000

    apply next-hop 2.2.2.2

  Matches: 0, bytes: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1.1.1.1

    apply output-interface GigabitEthernet0/0/2 track 1

    apply output-interface GigabitEthernet0/0/3 track 2

  Matches: 0, bytes: 0

  node 8 permit:

   if-match acl 3200

    apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)

    apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)

  Matched: 0, bytes: 0

Total matches: 0, total bytes: 0

Table 4 Command output

Field	Description
Policy based routing information for interface XXXX	PBR configuration and statistics on the interface. This field displays failed in brackets if none of the nodes in the policy has been successfully issued to the driver. NOTE: The failed status is available on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. ·     For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. ·     For a physical interface, specify its slot number.
node 0 deny node 2 permit	Match mode of the node, permit or deny. If a node fails to be issued to the driver, the command displays the cause in brackets, which include: ·     not support—The device does not support the match criteria configured on the node. ·     no resource—No sufficient resources (for example, ACLs) are available for the node. NOTE: The cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. ·     For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. ·     For a physical interface, specify its slot number.
if-match acl	Compares packets with the ACL.
apply next-hop	Specifies a next hop for permitted packets.
apply output-interface track 1	Specifies an output interface and its associated track entry for permitted packets. This field displays the interface status in brackets. ·     up—The interface is up. ·     down—The interface is down at network layer. ·     inactive—The card that hosts the interface is not in position.
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)	Specifies an SRv6 TE policy for permitted packets. Associated information about the SRv6 TE policy include: ·     Destination node IPv6 address 1000::1. ·     Color attribute value 10. ·     Destination node SRv6 SID 2000::2. ·     NHLFE index 2150629377.
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)	Specifies a default SRv6 TE policy for permitted packets. Associated information about the SRv6 TE policy include: ·     Destination node IPv6 address 3000::3. ·     Color attribute value 20. ·     Destination node SRv6 SID 4000::4. ·     NHLFE index 2149580801.
Matches	Number of successful matches on the node. If the device does not have sufficient resources to count matches, this field displays no statistics resource in brackets. If the device does not support counting successful matches on a node, this field displays N/A. If match counting is disabled on the node, this field is not displayed. NOTE: The statistics collection failure cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command. ·     For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces. ·     For a physical interface, specify its slot number.
bytes	Number of matching bytes on the node. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled on the node.
Total matches	Total number of successful matches on all nodes. This field displays N/A if the device does not support counting successful matches on a node. This field is not displayed if match counting is disabled on all nodes.
total bytes	Total number of matching bytes on all nodes. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled 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

display ip policy-based-route local [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-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 for the active MPU.

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:

  Matches: 0, bytes: 0

  node 1 permit:

    if-match acl 3999

  Matches: 0, bytes: 0

  node 2 permit:

    if-match acl 2000

    apply next-hop 2.2.2.2

  Matches: 0, bytes: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1.1.1.1

  Matches: 0, bytes: 0

  node 8 permit:

   if-match acl 3200

    apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)

    apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)

  Matched: 0, bytes: 0

Total matches: 0, total bytes: 0

Table 5 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.
apply srv6-policy 1000::1 10 sid 2000::2(NID: 2150629377)	Specifies an SRv6 TE policy for permitted packets. Associated information about the SRv6 TE policy include: ·     Destination node IPv6 address 1000::1. ·     Color attribute value 10. ·     Destination node SRv6 SID 2000::2. ·     NHLFE index 2150629377.
apply default-srv6-policy 3000::3 20 vpnsid 4000::4(NID: 2149580801)	Specifies a default SRv6 TE policy for permitted packets. Associated information about the SRv6 TE policy include: ·     Destination node IPv6 address 3000::3. ·     Color attribute value 20. ·     Destination node SRv6 SID 4000::4. ·     NHLFE index 2149580801.
Matches	Number of successful matches on the node. If the device does not support counting successful matches on a node, this field displays N/A. If match counting is disabled on the node, this field is not displayed.
bytes	Number of matching bytes on the node. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled on the node.
Total matches	Total number of successful matches on all nodes. This field displays N/A if the device does not support counting successful matches on a node. This field is not displayed if match counting is disabled on all nodes.
total bytes	Total number of matching bytes on all nodes. This field displays N/A if the device does not support counting matching bytes on a node. This field is not displayed if match counting is disabled 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

Examples

# Display PBR configuration.

<Sysname> display ip policy-based-route setup

Policy name              Type     Interface

aaa                      Forward  GigabitEthernet0/0/1

aaa                      Forward  GigabitEthernet0/0/2

aaa                      Local    N/A

abc                      Global   N/A

Table 6 Command output

Field	Description
Type	Type of the PBR: ·     Forward—Interface PBR. ·     Egress—Outbound PBR. ·     Local—Local PBR. ·     Global—Global PBR.
Interface	Interface where the policy is applied. This field displays N/A for local and global PBR.

 

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

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. For the command to take effect, make sure the specified ACL is a basic or advanced ACL.

Usage guidelines

If the specified ACL does not exist or has no rules configured, no packets will match the ACL.

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 app-group

Use if-match app-group to set application group match criteria.

Use undo if-match app-group to delete application group match criteria.

Syntax

if-match app-group app-group-name&<1-n>

undo if-match app-group [ app-group-name&<1-n> ]

Default

No application group match criteria are set.

Views

Policy node view

Predefined user roles

network-admin

Parameters

app-group-name: Specifies an application group by its name, a case-insensitive string of 1 to 63 characters. The group name can include letters, digits, underscores (_), and hyphens (-). The application group name cannot be Invalid, other, or any application group name predefined by the system.

&<1-n>: Indicates that the argument before it can be entered up to n times. The value for n is six on the device.

Usage guidelines

The application match criteria apply only to interface PBR.

If you specify an application group, the undo if-match app-group command deletes the application group match criterion.

If you do not specify an application group, the undo if-match app-group command deletes all application group match criteria.

Examples

# Specify the application group test as a match criterion.

<Sysname> system-view

[Sysname] policy-based-route aa permit node 11

[Sysname-pbr-aa-11] if-match app-group test

if-match packet-length

Use if-match packet-length to set a packet length match criterion.

Use undo if-match packet-length to restore the default.

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

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

if-match source-ip

Use if-match source-ip to set a source IP address match criterion to match locally generated packets.

Use undo if-match source-ip to delete the source IP address match criterion to match locally generated packets.

Syntax

if-match source-ip { interface interface-type interface-number | [ vpn-instance vpn-instance-name ] ip-address }

undo if-match source-ip

Default

No source IP address match criterion is set.

Views

Policy node view

Predefined user roles

network-admin

Parameters

interface interface-type interface-number: Specifies an interface by its type and number. The primary IP address of the interface will be used to match packets.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the specified IP address belongs to the public network.

ip-address: Specifies an IP address in dotted decimal notation.

Usage guidelines

This command matches locally generated packets sent out with the specified IP address or the primary IP address of the specified interface.

Typically, you use this command to make sure local tunneled or VPN traffic (for example, IPsec packets) is sent towards the correct ISP when the device is dual- or multi-homed to different ISPs. This command helps you avoid packet drops that might occur when packets are sent to an incorrect ISP.

For the matching traffic, use the apply next-hop or apply output-interface command to specify the next hop or the output interface. As a best practice, specify the output interface in the apply clause if you specify the source interface in the if-match clause.

As a best practice, do not specify the interface of a VXLAN tunnel automatically created by EVPN for this command. If the tunnel interface number changes upon VXLAN tunnel reestablishment, the match criterion no longer takes effect. For more information about EVPN, see EVPN overview in EVPN Configuration Guide.

If you execute this command multiple times on a policy node, the most recent configuration takes effect.

Examples

# Match locally generated packets with source IP address 1.1.1.1.

<Sysname> system-view

[Sysname] policy-based-route aa permit node 11

[Sysname-pbr-aa-11] if-match source-ip 1.1.1.1

ip global policy-based-route

Use ip global policy-based-route to specify a PBR policy as the global PBR policy.

Use undo ip global policy-based-route to restore the default.

Syntax

ip global policy-based-route policy-name

undo ip global policy-based-route

Default

No policy is specified for global PBR.

Views

System view

Predefined user roles

network-admin

Parameters

policy-name: Specifies a PBR policy by its name, a case-sensitive string of 1 to 19 characters. The specified policy must already exist.

Usage guidelines

Global PBR guides the forwarding of packets on all interfaces of the device.

You can specify only one policy for global PBR on the device. Before you apply a new policy, you must first remove the current policy.

Interface PBR takes precedence over global PBR on an interface. When they are both configured and packets fail to match the interface PBR policy, global PBR applies.

Examples

# Specify PBR policy aaa for global PBR.

<Sysname> system-view

[Sysname] ip global policy-based-route aaa

Related commands

display ip policy-based-route global

policy-based-route

ip local policy-based-route

Use ip local policy-based-route to specify a policy for local PBR.

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

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

Local PBR guides the forwarding of locally generated packets, such as ICMP packets generated by using the ping command.

Local PBR might affect local services, such as ping and Telnet. When you use local PBR, make sure you fully understand its impact on local services of the device.

You can specify only one policy for local PBR and must make sure the specified policy already exists.

Before you apply a new policy, you must first remove the current policy.

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

ip policy-based-route apply

policy-based-route

ip policy-based-route

Use ip policy-based-route to specify a policy for interface PBR on an interface.

Use undo ip policy-based-route to restore the default.

Syntax

ip policy-based-route policy-name [ share-mode ]

undo ip policy-based-route

Default

No policy is applied to an interface.

Views

Interface view

Predefined user roles

network-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.

share-mode: Applies the policy in resource sharing mode. In this mode, all interfaces on an interface card with the same policy applied share one hardware resource. If you do not specify this keyword, each interface occupies one independent hardware resource. You can apply only one ACL, QoS policy, or PBR policy with the share-mode keyword specified to one direction of an interface. For information about ACL and QoS policies, see ACL commands and QoS policy commands in ACL and QoS Command Reference.

Usage guidelines

Typically, each interface on a card uses different hardware resources for a policy. To avoid resource usage overhead, you can specify the resource sharing mode when applying the policy to each interface. The interfaces will use the same hardware resources.

You can specify only one mode for the policy on an interface. Before you change the mode of the policy, you must first remove the current policy from the interface.

Examples

# Apply policy aaa to GigabitEthernet 0/0/1.

<Sysname> system-view

[Sysname] interface gigabitethernet 0/0/1

[Sysname-GigabitEthernet0/0/1] ip policy-based-route aaa

Related commands

display ip policy-based-route setup

ip policy-based-route apply

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

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 varies by device model.

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

ip policy-based-route-log enable

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

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 egress interface

display ip policy-based-route interface

display ip policy-based-route local