Contents

Policy-based routing commands· 1

apply access-vpn vpn-instance· 1

apply default-next-hop· 1

apply default-srv6-be· 2

apply next-hop· 3

apply output-interface· 4

apply precedence· 5

apply srv6-be· 5

apply srv6-policy· 6

display ip policy-based-route· 7

display ip policy-based-route interface· 9

display ip policy-based-route local 12

display ip policy-based-route setup· 14

if-match acl 14

ip local policy-based-route· 15

ip policy-based-route· 16

ip policy-based-route-log enable· 17

policy-based-route· 17

reset ip policy-based-route statistics· 18

 

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

undo apply access-vpn vpn-instance [ vpn-instance-name ]

Default

No VPN instance is 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.

Usage guidelines

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 for node 10. (VPN 1 already exists.)

<Sysname> system-view

[Sysname] policy-based-route policy1 permit node 10

[Sysname-pbr-policy1-10] apply access-vpn vpn-instance vpn1

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 ] { ip-address [ direct ] [ track track-entry-number ] }&<1-2>

undo apply default-next-hop [ [ vpn-instance vpn-instance-name ] ip-address&<1-2> ]

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 to which the default next hop belongs. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the default next hop belongs to the public network, do not specify this option.

ip-address: Specifies the IP address of the default next hop.

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-2>: Indicates that you can specify up to two default next hops.

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

apply default-srv6-be

Use apply default-srv6-be to configure packet forwarding in default SRv6 BE mode.

Use undo apply default-srv6-be to remove the configuration.

Syntax

apply default-srv6-be remote-sid { remote-sid locator-prefix-len }&<1-2>

undo apply default-srv6-be remote-sid [ { remote-sid locator-prefix-len }&<1-2> ]

Default

Packet are not forwarded in default SRv6 BE mode.

Views

Policy node view

Predefined user roles

network-admin

Parameters

remote-sid remote-sid: Specifies the default SRv6 BE destination node SID.

locator-prefix-len: Specifies the locator length for the destination node SID, in the range of 32 to 120.

&<1-2>: Indicates that the argument before it can be entered up to two times.

Usage guidelines

You can use the remote-sid and locator-prefix-len arguments to uniquely identify a locator. The device performs SRv6 encapsulation for matching packets (encapsulates an IPv6 header with the default SRv6 BE destination node SID used as the destination address), and forwards them through the IGP route associated with the locator. You can specify up to two destination node SIDs for the default SRv6 BE mode for backup in one command line or by executing this command multiple times. When you specify up to two SIDs, you cannot specify new SIDs.

With a default SRv6 BE destination node SID specified, the undo form of the command removes the specified default SRv6 BE destination node SID. Without any default SRv6 BE destination node SIDs specified, the undo form of the command removes all configured default SRv6 BE destination node SIDs.

Examples

# Configure packet forwarding in default SRv6 BE mode. Specify the default SRv6 BE destination node SID as 1000::1 and the locator length as 32.

<Sysname> system-view

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

[Sysname-pbr-aa-1] apply default-srv6-be remote-sid 1000::1 32

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 ] { ip-address [ direct ] [ track track-entry-number ] }&<1-2>

undo apply next-hop [ [ vpn-instance vpn-instance-name ] ip-address&<1-2> ]

Default

No next hop is set.

Views

Policy node view

Predefined user roles

network-admin

Parameters

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance to which the next hop belongs. The vpn-instance-name argument is a case-sensitive string of 1 to 31 characters. If the next hop belongs to the public network, do not specify this option.

ip-address: Specifies the IP address of the next hop.

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.

&<1-2>: Indicates that you can specify up to two next hops.

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 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 ] }

undo apply output-interface [ { interface-type interface-number } ]

Default

No output interface is 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.

Usage guidelines

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 Ten-GigabitEthernet 3/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 ten-gigabitethernet 3/0/1

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 srv6-be

Use apply srv6-be to configure packet forwarding in SRv6 BE mode.

Use undo apply srv6-be to remove the configuration.

Syntax

apply srv6-be remote-sid { remote-sid locator-prefix-len }&<1-2>

undo apply srv6-be remote-sid [ { remote-sid locator-prefix-len }&<1-2> ]

Default

Packet are not forwarded in SRv6 BE mode.

Views

Policy node view

Predefined user roles

network-admin

Parameters

remote-sid remote-sid: Specifies the SRv6 BE destination node SID.

locator-prefix-len: Specifies the locator length for the destination node SID, in the range of 32 to 120.

&<1-2>: Indicates that the argument before it can be entered up to two times.

Usage guidelines

You can use the remote-sid and locator-prefix-len arguments to uniquely identify a locator. The device performs SRv6 encapsulation for matching packets (encapsulates an IPv6 header with the SRv6 BE destination node SID used as the destination address), and forwards them through the IGP route associated with the locator. You can specify up to two destination node SIDs for the SRv6 BE mode for backup in one command line or by executing this command multiple times. When you specify up to two SIDs, you cannot specify new SIDs.

With an SRv6 BE destination node SID specified, the undo form of the command removes the specified SRv6 BE destination node SID. Without any SRv6 BE destination node SIDs specified, the undo form of the command removes all configured SRv6 BE destination node SIDs.

Examples

# Configure packet forwarding in SRv6 BE mode. Specify the SRv6 BE destination node SID as 1000::1 and the locator length as 32.

<Sysname> system-view

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

[Sysname-pbr-aa-1] apply srv6-be remote-sid 1000::1 32

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

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 (active)

    apply next-hop 2.2.2.2 (active)

  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)

  node 11 permit:

    if-match acl 3001

    apply srv6-be remote-sid 2002::1 32 (NibID: 0x2a000001, VNID: 0x12a000001)

    apply default-srv6-be remote-sid 2001::2 32 (NibID: 0x2a000002, VNID: 0x22a000002)

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 (active)	Specifies a next hop for permitted packets. This field also displays the state of the next hop. ·     active—The next hop is reachable. ·     inactive—The next hop is unreachable.
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.
apply srv6-be remote-sid 2002::1 32 (NibID: 0x2a000001, VNID: 0x12a000001)	Forwards permitted packets in SRv6 BE mode. Associated information about the SRv6 BE mode include: ·     Destination node SID 2002::1. ·     Locator length 32. ·     NIB ID 0x2a000001. ·     VN entry ID 0x12a000001.
apply default-srv6-be remote-sid 2001::2 32 (NibID: 0x2a000002, VNID: 0x22a000002)	Forwards permitted packets in default SRv6 BE mode. Associated information about the default SRv6 BE mode include: ·     Destination node SID 2001::2. ·     Locator length 32. ·     NIB ID 0x2a000002. ·     VN entry ID 0x22a000002.

‌

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

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 interface PBR configuration and statistics on the active MPU.

Examples

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

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

Policy based routing information for interface Ten-GigabitEthernet3/0/1(failed):

Policy name: aaa

  node 0 deny:

  Matched: 0, bytes: 0

  node 1 permit:

    if-match acl 3999

  Matched: 0, bytes: 0

  node 2 permit:

    if-match acl 2000

    apply next-hop 2.2.2.2 (active)

  Matched: 0, bytes: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1.1.1.1 (active)

    apply output-interface Ten-GigabitEthernet3/0/2 track 1(down)

    apply output-interface Ten-GigabitEthernet3/0/3 track 2(down)

  Matched: 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

  node 9 permit:

   if-match acl 3300

    apply srv6-be remote-sid 2002::1 32 (NibID: 0x2a000001, VNID: 0x12a000001)

    apply default-srv6-be remote-sid 2001::2 32 (NibID: 0x2a000002, VNID: 0x22a000002)

Total matched: 0, total bytes: 0

Table 3 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. The failed status will persist after the policy is successfully issued. To clear the failed status, you must remove the policy from the interface and then apply it on the interface again. 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 (active)	Specifies a next hop for permitted packets. This field also displays the state of the next hop. ·     active—The next hop is reachable. ·     inactive—The next hop is unreachable.
apply output-interface track 1 (down)	Specifies an output interface for permitted packets. This field displays the interface status in brackets. ·     inactive—The card that hosts the interface is not in position. ·     down—The interface is down at network layer.
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.
apply srv6-be remote-sid 2002::1 32 (NibID: 0x2a000001, VNID: 0x12a000001)	Forwards permitted packets in SRv6 BE mode. Associated information about the SRv6 BE mode include: ·     Destination node SID 2002::1. ·     Locator length 32. ·     NIB ID 0x2a000001. ·     VN entry ID 0x12a000001.
apply default-srv6-be remote-sid 2001::2 32 (NibID: 0x2a000002, VNID: 0x22a000002)	Forwards permitted packets in default SRv6 BE mode. Associated information about the default SRv6 BE mode include: ·     Destination node SID 2001::2. ·     Locator length 32. ·     NIB ID 0x2a000002. ·     VN entry ID 0x22a000002.
Matched	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. 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 matched	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 policy-based-route

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 on 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:

  Matched: 0, bytes: 0

  node 1 permit:

    if-match acl 3999

  Matched: 0, bytes: 0

  node 2 permit:

    if-match acl 2000

    apply next-hop 2.2.2.2 (active)

  Matched: 0, bytes: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1.1.1.1 (active)

  Matched: 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

  node 9 permit:

   if-match acl 3300

    apply srv6-be remote-sid 2002::1 32 (NibID: 0x2a000001, VNID: 0x12a000001)

    apply default-srv6-be remote-sid 2001::2 32 (NibID: 0x2a000002, VNID: 0x22a000002)

  Matches: 0, bytes: 0

Total matched: 0, total bytes: 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 (active)	Specifies a next hop for permitted packets. This field also displays the state of the next hop. ·     active—The next hop is reachable. ·     inactive—The next hop is unreachable.
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.
apply srv6-be remote-sid 2002::1 32 (NibID: 0x2a000001, VNID: 0x12a000001)	Forwards permitted packets in SRv6 BE mode. Associated information about the SRv6 BE mode include: ·     Destination node SID 2002::1. ·     Locator length 32. ·     NIB ID 0x2a000001. ·     VN entry ID 0x12a000001.
apply default-srv6-be remote-sid 2001::2 32 (NibID: 0x2a000002, VNID: 0x22a000002)	Forwards permitted packets in default SRv6 BE mode. Associated information about the default SRv6 BE mode include: ·     Destination node SID 2001::2. ·     Locator length 32. ·     NIB ID 0x2a000002. ·     VN entry ID 0x22a000002.
Matched	Number of successful matches on the node. 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 the node.
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 matched	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 local policy-based-route

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.

Policy name              Type     Interface

aaa                      Forward  Ten-GigabitEthernet3/0/1

aaa                      Forward  Ten-GigabitEthernet3/0/2

aaa                      Local    N/A

Table 5 Command output

Field	Description
Type	Type of the PBR: ·     Forward—Interface PBR. ·     Egress—Outbound PBR. ·     Local—Local PBR.
Interface	Interface where the policy is applied.

‌

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 a letter. The ACL name cannot be all.

Usage guidelines

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

If the vpn-instance keyword is specified for an ACL rule, the rule applies to only VPN packets. If the vpn-instance keyword is not specified, the rule applies to only public network packets.

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

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 specified 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 local

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 apply only one policy to an interface. Before you apply a new policy, you must first remove the current policy from the interface.

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 Ten-GigabitEthernet 3/0/1.

<Sysname> system-view

[Sysname] interface ten-gigabitethernet 3/0/1

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

Related commands

display ip policy-based-route

ip policy-based-route-log enable

Use ip policy-based-route-log enable to enable the PBR logging feature.

Use undo ip policy-based-route-log enable to disable the PBR logging feature.

Syntax

ip policy-based-route-log enable

undo ip policy-based-route-log enable

Default

The PBR logging feature is disabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

The PBR logging feature helps the administrator locate and fix faults. The feature logs PBR events and sends the logs to the information center. The information center processes the logs according to output rules. For more information about the information center, see Network Management and Monitoring Configuration Guide.

Excessive PBR log messages degrade the performance of the device. To avoid this problem, disable the PBR logging feature.

Examples

# Enable the PBR logging feature.

<Sysname> system-view

[Sysname] ip policy-based-route-log enable

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 is 0 to 255.

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

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