Contents

Policy-based routing commands· 1

apply default-next-hop· 1

apply loadshare· 2

apply next-hop· 3

apply output-interface· 5

apply precedence· 5

apply service-chain· 6

apply statistics· 7

description· 8

display ip policy-based-route· 8

display ip policy-based-route global 9

display ip policy-based-route interface· 11

display ip policy-based-route local 13

display ip policy-based-route setup· 14

if-match acl 15

if-match qos-local-id· 16

if-match service-chain· 17

ip global policy-based-route· 18

ip local policy-based-route· 18

ip policy-based-route· 19

policy-based-route· 20

reset ip policy-based-route statistics· 21

 

Policy-based routing commands

MDC is supported only when the device operates in standalone mode. For more information about MDC, see MDC configuration in Virtual Technologies Configuration Guide.

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.

‌

NOTE: This command takes effect only on the SF series interface modules.

‌

 

Syntax

apply default-next-hop [ vpn-instance vpn-instance-name ] { ip-address [ direct ] [ track track-entry-number ] [ service-chain path-id service-path-id [ path-index service-path-index ] ] }&<1-4>

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

Default

No default next hops are 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 instance must already exist.

ip-address: Specifies the IP address of the default next hop. If you do not specify the vpn-instance vpn-instance-name option, 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.

service-chain path-id service-path-id: Specifies a service chain by its path ID. A path ID uniquely identifies a service chain, and its value range is 1 to 65534 or 8388608 to 8454142.

path-index service-path-index: Specifies a node in the service chain as a default next hop by its index in the range of 1 to 255.

The service-chain path-id and path-index keywords take effect only when the device is operating in expert mode. For more information about device operating modes, see device management in Fundamentals Configuration Guide.

&<1-4>: Indicates that the argument before it can be entered up to four times in one command line. You can specify a maximum of eight default next hops for the policy node.

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.

To set multiple default next hops and specify their service chain parameters (service chain path ID and node index), follow these guidelines:

·     If the next hops are used in different service chains, use the apply default-next-hop command to specify the service chain parameters.

·     If the next hops are used in the same service chain, use the apply service-chain command to specify the service chain parameters as a best practice.

·     On a policy node, you cannot configure both the apply default-next-hop command with the service chain parameters and the apply service-chain command.

If you specify service chain parameters for this command, the apply loadshare { default-next-hop | next-hop } command does not take effect.

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 service-chain

apply loadshare

Use apply loadshare to enable load sharing among multiple next hops or default next hops.

Use undo apply loadshare to restore the default.

‌

NOTE: Only SF series interface modules support enabling load sharing among multiple default next hops.

‌

Syntax

apply loadshare { default-next-hop | next-hop }

undo apply loadshare { default-next-hop | next-hop }

Default

Multiple next hops or default next hops 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.

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

Usage guidelines

Multiple next hop or default next hop options operate in either primary/backup or load sharing mode.

·     Primary/backup mode—One option is selected from all options in configuration order for packet forwarding, with all remaining options as backups. For example, if multiple output interfaces are configured, the first configured output interface is selected. When the selected output interface fails, the next available output interface takes over.

·     Load sharing mode—Matching traffic is distributed across the available options in round robin manner, starting from the first configured option. They perform per-packet load sharing for traffic that does not match any fast forwarding entry, and perform per-flow load sharing for traffic that matches a fast forwarding entry.

If you configure both the apply service-chain and apply loadshare { default-next-hop | next-hop } commands, the apply loadshare does not take effect.

If you specify service chain parameters for the apply next-hop or apply default-next-hop command, the apply loadshare { default-next-hop | next-hop } command does not take effect.

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

Related commands

apply default-next-hop

apply next-hop

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 ] [ service-chain path-id service-path-id [ path-index service-path-index ] ] }&<1-8>

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

Default

No next hops are 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 instance must already exist.

ip-address: Specifies the IP address of the next hop. If you do not specify the vpn-instance vpn-instance-name option, 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.

service-chain path-id service-path-id: Specifies a service chain by its path ID. A path ID uniquely identifies a service chain, and its value range is 1 to 65534 or 8388608 to 8454142.

path-index service-path-index: Specifies a node in the service chain as a next hop by its index in the range of 1 to 255.

The service-chain path-id and path-index keywords take effect only on SF series interface modules.

The service-chain path-id and path-index keywords take effect only when the device is operating in expert mode. For more information about device operating modes, see device management in Fundamentals Configuration Guide.

&<1-8>: Indicates that the argument before it can be entered up to eight 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.

To set multiple next hops and specify their service chain parameters (service chain path ID and node index), follow these guidelines:

·     If the next hops are used in different service chains, use the apply next-hop command to specify the service chain parameters.

·     If the next hops are used in the same service chain, use the apply service-chain command to specify the service chain parameters as a best practice.

·     On a policy node, you cannot configure both the apply next-hop command with the service chain parameters and the apply service-chain command.

If you specify service chain parameters for this command, the apply loadshare { default-next-hop | next-hop } command does not take effect.

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

apply service-chain

apply output-interface

Use apply output-interface to set output interfaces.

Use undo apply output-interface to remove output interfaces.

Syntax

apply output-interface null 0

undo apply output-interface [ null 0 ]

Default

No output interfaces are set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

null 0: Specifies the Null 0 interface.

Usage guidelines

You can specify only Null 0 as the output interface.

Examples

# Specify Null 0 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 null 0

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 service-chain

Use apply service-chain to set service chain information.

Use undo apply service-chain to restore the default.

‌

NOTE: ·     This command takes effect only on SF series interface modules. ·     This command takes effect only when the device is operating in expert mode. For more information about device operating modes, see device management in Fundamentals Configuration Guide.

‌

Syntax

apply service-chain path-id service-path-id [ path-index service-path-index ]

undo apply service-chain

Default

No service chain information is set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

path-id service-path-id: Specifies a service chain by its path ID in the range of 1 to 65534 or 8388608 to 8454142. The path ID uniquely identifies a service chain.

path-index service-path-index: Specifies the path index of the node to which you are sending the matching packets. The value range for path indexes is 1 to 255. Specify this option if the destination node might receive packets from different nodes in the service chain. If the destination node receives packets only from the device, you do not need to specify this option.

Usage guidelines

When the device has SF series interface modules installed and is operating in expert mode, you cannot configure both the apply service-chain and apply statistics commands. For more information about device operating modes, see device management in Fundamentals Configuration Guide.

If you configure both the apply service-chain and apply loadshare { default-next-hop | next-hop } commands, the apply loadshare command does not take effect.

Examples

# Set service chain path ID 1 and node index 10.

<Sysname> system-view

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

[Sysname-pbr-aa-5] apply service-chain path-id 1 path-index 10

apply statistics

Use apply statistics to enable match counting on a policy node.

Use undo apply statistics to restore the default.

Syntax

apply statistics

undo apply statistics

Default

Counting successful policy node matches is disabled.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

To include the number of successful matches and matching bytes on a policy node in the statistics displayed by a display command, execute this command. As a best practice to conserve hardware resources, disable this counting function.

When the device has SF series interface modules installed and is operating in expert mode, you cannot configure both the apply service-chain and apply statistics commands. For more information about device operating modes, see device management in Fundamentals Configuration Guide.

Examples

# Enable match counting on policy node 11.

<Sysname> system-view

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

[Sysname-pbr-aa-11] apply statistics

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

mdc-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

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 global

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

Syntax

In standalone mode:

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

In IRF mode:

display ip policy-based-route global [ 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 information about global PBR 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 information about global PBR on the global active MPU. (In IRF mode.)

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.
Matches	Number of successful matches on the node. 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 is not displayed if match counting is disabled on the node.
Total matches	Total number of successful matches on all nodes. 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 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

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 information 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 information on the global active MPU. (In IRF mode.)

Examples

# Display PBR configuration and statistics on VLAN-interface 2.

<Sysname> display ip policy-based-route interface vlan-interface 2

Policy based routing information for interface Vlan-interface2:

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 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. The failed status will persist even 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	Specifies a next hop for permitted packets.
Matches	This field is not supported in the current software version. Number of successful matches on the node. 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	This field is not supported in the current software version. Number of matching bytes on the node. This field is not displayed if match counting is disabled on the node.
Total matches	This field is not supported in the current software version. Total number of successful matches on all nodes. This field is not displayed if match counting is disabled on all nodes.
total bytes	This field is not supported in the current software version. Total number of matching bytes on all nodes. 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

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

  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 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.
Matches	Number of successful matches on the node. This field is not displayed if match counting is disabled on the node.
bytes	Number of matching bytes on the 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 is not displayed if match counting is disabled on all nodes.
total bytes	Total number of matching bytes on all nodes. 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

mdc-admin

mdc-operator

Examples

# Display PBR configuration.

<Sysname> display ip policy-based-route setup

Policy name              Type     Interface

pr01                     Forward  Vlan-interface2

aaa                      Local    N/A

Table 6 Command output

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

‌

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

For SD interface modules, Layer 3 Ethernet interfaces, Layer 3 aggregate interfaces, Layer 3 Ethernet subinterfaces, and Layer 3 aggregate subinterfaces, if the vpn-instance or microsegment keyword is specified for an ACL rule, the rule does not take effect.

If the vpn-instance keyword is not specified for an ACL rule, the following situations will occur:

·     In an interface or global PBR policy, the rule applies to both public network and VPN packets.

·     In a local PBR policy, the rule applies to only public network packets.

You cannot specify the same local QoS ID for both the if-match qos-local-id and if-match acl commands on a policy node.

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 qos-local-id

Use if-match qos-local-id to set a local QoS ID match criterion.

Use undo if-match qos-local-id to restore the default.

‌

NOTE: This command takes effect only on SF series interface modules.

‌

Syntax

if-match qos-local-id local-id-value

undo if-match qos-local-id

Default

No local QoS ID match criterion is set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

local-id-value: Specifies a local QoS ID in the range of 1 to 4095.

Usage guidelines

You cannot specify the same local QoS ID for both the if-match qos-local-id and if-match acl commands on a policy node.

Examples

# Match packets with local QoS ID 200.

<Sysname> system-view

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

[Sysname-pbr-aa-11] if-match qos-local-id 200

if-match service-chain

Use if-match service-chain to set a service chain match criterion.

Use undo if-match service-chain to restore the default.

‌

NOTE: ·     This command takes effect only on SF series interface modules. ·     This command takes effect only when the device is operating in expert mode. For more information about device operating modes, see device management in Fundamentals Configuration Guide.

‌

Syntax

if-match service-chain path-id service-path-id [ path-index service-patch-index ]

undo if-match service-chain [ path-id service-path-id ]

Default

No service chain match criteria are set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

path-id service-path-id: Specifies a service chain by its path ID in the range of 1 to 65534 or 8388608 to 8454142. The path ID uniquely identifies a service chain.

path-index service-path-index: Specifies a node in the service chain by its index to match packets sent from that node. The value range for path indexes is 1 to 255. Specify this option if the device might receive packets from different nodes in the service chain. If only one node in the service chain sends packets to the device, you do not need to specify this option.

Examples

# Set a service chain match criterion to match packets with service chain path ID 1 and node index 10.

<Sysname> system-view

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

[Sysname-pbr-aa-5] if-match service-chain path-id 1 path-index 10

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

mdc-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

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

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

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.

‌

NOTE: The share-mode keyword takes effect only on SF series interface modules.

‌

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

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.

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 VLAN-interface 2.

<Sysname> system-view

[Sysname] interface vlan-interface 2

[Sysname-Vlan-interface2] ip policy-based-route aaa

Related commands

display ip policy-based-route interface

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