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.

ipv4-address: Specifies the IPv4 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.

ipv6-address: Specifies the IPv6 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.

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

Usage guidelines

You can specify multiple next hops for backup in one command line or by executing this command multiple times. The device selects the first configured next hop as the primary next hop. When the primary next hop becomes invalid, the device selects the next available next hop for forwarding packets based on configuration order.

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] dual-stack policy-based-route aa permit node 11

[Sysname-pbrdual-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 null 0 [ track track-entry-number ]

undo apply output-interface [ null 0 ]

Default

No output interfaces are set.

Views

Dual-stack policy node view

Predefined user roles

network-admin

Parameters

null 0: Specifies inteface Null 0.

track track-entry-number: Specifies a track entry by its number in the range of 1 to 1024.

Examples

# Specify Null 0 as the output interface for IPv4 or IPv6 packets.

<Sysname> system-view

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

[Sysname-pbrdual-aa-11] apply output-interface null 0

apply precedence

Use apply precedence to set an IP precedence for packets.

Use undo apply precedence to restore the default.

Syntax

apply precedence { type | value }

undo apply precedence

Default

No precedence is set for packets.

Views

Dual-stack policy node view

Predefined user roles

network-admin

Parameters

type: Specifies the precedence type for packets.

value: Specifies the IP precedence for 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 IP precedence to 5 (critical) for packets.

<Sysname> system-view

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

[Sysname-pbrdual-aa-11] apply precedence critical

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

Match counting is disabled on a policy node.

Views

Dual-stack policy node view

Predefined user roles

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

This apply clause is always executed for the policy node.

Examples

# Enable match counting on policy node 11.

<Sysname> system-view

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

[Sysname-pbrdual-aa-11] apply statistics

description

Use description to configure a description for a dual-stack policy node.

Use undo description to restore the default.

Syntax

description text

undo description

Default

No description is configured for a dual-stack policy node.

Views

Dual-stack 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] dual-stack policy-based-route 1 permit node 1

[Sysname-pbrdual-1-1] description Officeuse

display dual-stack policy-based-route

Use display dual-stack policy-based-route to display dual-stack PBR policy information.

Syntax

display dual-stack policy-based-route [ policy policy-name ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

policy policy-name: Specifies a dual-stack PBR policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a dual-stack PBR policy, this command displays information for all dual-stack PBR policies.

Examples

# Display all dual-stack PBR policy information.

<Sysname> display dual-stack policy-based-route

Policy name: aaa

node 1 permit:

if-match acl ipv4 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

dual-stack policy-based-route (system view)

display dual-stack policy-based-route global

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

Syntax

display dual-stack policy-based-route global [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, the master device is specified by default.

Examples

# Display information about global dual-stack PBR.

<Sysname> display dual-stack 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 ipv6 3999

Matches: 0, bytes: 0

node 2 permit:

if-match acl ipv4 2000

apply next-hop 2.2.2.2

Matches: 0, bytes: 0

node 5 permit:

if-match acl ipv4 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 dual-stack 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 global dual-stack PBR 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	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

dual-stack global policy-based-route

display dual-stack policy-based-route interface

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

Syntax

display dual-stack 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 an IRF member device by its member ID. If you do not specify a member device, the master device is specified by default.

Examples

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

<Sysname> display dual-stack 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 ipv6 3999

Matches: 0, bytes: 0

node 2 permit:

if-match acl ipv4 2000

apply next-hop 2.2.2.2

Matches: 0, bytes: 0

node 5 permit:

if-match acl ipv4 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	Dual-stack 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 dual-stack 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	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 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

dual-stack policy-based-route (interface view)

display dual-stack policy-based-route setup

Use display dual-stack policy-based-route setup to display dual-stack PBR configuration.

Syntax

display dual-stack policy-based-route setup

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display dual-stack PBR configuration.

<Sysname> display dual-stack policy-based-route setup

Policy name Type Interface

pr01 Forward Vlan-interface2

pr01 Global N/A

Table 5 Command output

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

Field

Description

Type

Type of the PBR:

· Forward—Interface PBR.

· Global—Global PBR.

Interface

Interface where the policy is applied.

This field displays N/A for local dual-stack PBR and global dual-stack 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 { ipv4 | ipv6 } { acl-number | name acl-name }

undo if-match acl

Default

No ACL match criterion is set.

Views

Dual-stack policy node view

Predefined user roles

network-admin

Parameters

ipv4: Specifies IPv4 ACL.

ipv6: Specifies IPv6 ACL.

acl-number: Specifies an ACL by its number in the range of 2000 to 2999 for a basic ACL and 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, user-defined, or advanced ACL.

Usage guidelines

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

For Layer 3 Ethernet interfaces, Layer 3 aggregate interfaces, Layer 3 Ethernet subinterfaces, and Layer 3 aggregate subinterfaces, if the vpn-instance keyword is specified for an ACL rule on the dual-stack policy node, the rule does not take effect.

For VLAN interfaces, if the vpn-instance keyword is specified for an ACL rule on the dual-stack policy node, the rule does not take effect.

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

Examples

# Configure Node 11 of policy aa to permit the packets matching IPv4 ACL 2011.

<Sysname> system-view

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

[Sysname-pbrdual-aa-11] if-match acl ipv4 2011

# Configure Node 11 of policy aa to permit the packets matching IPv6 ACL aaa.

<Sysname> system-view

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

[Sysname-pbrdual-aa-11] if-match acl ipv6 name aaa

dual-stack global policy-based-route

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

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

Syntax

dual-stack global policy-based-route policy-name

undo dual-stack global policy-based-route

Default

No policy is specified for global dual-stack 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 dual-stack PBR guides the forwarding of packets on all interfaces of the device.

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

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

Examples

# Specify policy aaa for global dual-stack PBR.

<Sysname> system-view

[Sysname] dual-stack global policy-based-route aaa

Related commands

display ip policy-based-route global

dual-stack policy-based-route (interface view)

Use dual-stack policy-based-route to apply a dual-stack PBR policy to an interface.

Use undo dual-stack policy-based-route to restore the default.

Syntax

dual-stack policy-based-route policy-name

undo dual-stack policy-based-route

Default

No dual-stack PBR 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.

Examples

# Apply dual-stack PBR policy aaa to VLAN-interface 2.

<Sysname> system-view

[Sysname] interface vlan-interface 2

[Sysname-Vlan-interface2] dual-stack policy-based-route aaa

Related commands

display dual-stack policy-based-route interface

dual-stack policy-based-route (system view)

Use dual-stack policy-based-route to create a dual-stack policy node and enter its view, or enter the view of an existing dual-stack policy node.

Use undo dual-stack policy-based-route to delete a dual-stack policy or dual-stack policy node.

Syntax

dual-stack policy-based-route policy-name [ deny | permit ] node node-number

undo dual-stack policy-based-route policy-name [ deny | node node-number | permit ]

Default

No dual-stack policy nodes exist.

Views

System view

Predefined user roles

network-admin

Parameters

policy-name: Specifies a dual-stack 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 dual-stack policy that has been applied to an interface or globally 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 dual-stack policy policy1 and enter its view.

<Sysname> system-view

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

[Sysname-pbrdual-policy1-10]

Related commands

display dual-stack policy-based-route

reset dual-stack policy-based-route statistics

Use reset dual-stack policy-based-route statistics to clear dual-stack PBR statistics.

Syntax

reset dual-stack policy-based-route statistics [ policy policy-name ]

Views

User view

Predefined user roles

network-admin

Parameters

policy policy-name: Specifies a dual-stack PBR policy by its name, a case-sensitive string of 1 to 19 characters. If you do not specify a dual-stack PBR policy, this command clears statistics for all dual-stack PBR policies.

Examples

# Clear all dual-stack PBR statistics.

<Sysname> reset dual-stack policy-based-route statistics

05-Layer 3—IP Routing Command Reference

display dual-stack policy-based-route

display dual-stack policy-based-route interface

dual-stack policy-based-route (interface view)

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us