Contents

IPv6 policy-based routing commands· 1

apply continue· 1

apply default-next-hop· 1

apply default-output-interface· 3

apply loadshare· 4

apply next-hop· 5

apply output-interface· 6

apply precedence· 7

display ipv6 policy-based-route· 8

display ipv6 policy-based-route interface· 9

display ipv6 policy-based-route local 10

display ipv6 policy-based-route setup· 11

if-match acl 12

ipv6 local policy-based-route· 13

ipv6 policy-based-route (interface view) 13

ipv6 policy-based-route (system view) 14

reset ipv6 policy-based-route statistics· 15

snmp-agent trap enable ipv6 policy-based-route· 15

 

IPv6 policy-based routing commands

apply continue

Use apply continue to compare packets with the next policy node upon forwarding failure through the specified path on the current node.

Use undo apply continue to restore the default.

Syntax

apply continue

undo apply continue

Default

IPv6 PBR does not compare packets with the next policy node upon forwarding failure through the specified path on the current node.

Views

IPv6 policy node view

Predefined user roles

network-admin

Usage guidelines

This command takes effect only when either of the following conditions exist and the mode of the node is permit:

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

¡     apply next-hop

¡     apply output-interface

¡     apply default-next-hop

¡     apply default-output-interface

·     One or multiple clauses used to direct packet forwarding are configured on the node, but they have 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 or the specified output interface is down.

‌

Examples

# Compare with the next policy node upon failure on the current node.

<Sysname> system-view

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

[Sysname-pbr6-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 { ipv6-address [ direct ] [ track track-entry-number ] }&<1-4>

undo apply default-next-hop [ ipv6-address&<1-4> ]

Default

No default next hops are set.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies  the IPv6 address of a 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-4>: Indicates that you can specify up to four default next hops, each of which can be associated with a track entry.

Usage guidelines

Application scenarios

You can specify multiple default next hops for backup or load sharing in one command line or by executing this command multiple times.

·     If the apply loadshare default-next-hop command is not configured on the policy node, multiple default next hops operate in primary/backup mode. PBR selects the first available default next hop according to the configuration order as the primary next hop to guide packet forwarding.

·     If the apply loadshare default-next-hop command is configured on the policy node, multiple default next hops operate in load sharing mode. PBR load shares packets in round robin manner, starting from the first configured default next hop. PBR performs per-packet load sharing for packets that do not match any fast forwarding entry, and performs per-flow load sharing for packets that match a fast forwarding entry.

Restrictions and guidelines

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

[Sysname-pbr6-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-4>

undo apply default-output-interface [ { interface-type interface-number }&<1-4> ]

Default

No default output interfaces are set.

Views

IPv6 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-4>: Indicates that you can specify up to four interfaces, each of which can be associated with a track entry.

Usage guidelines

Application scenarios

You can specify multiple default output interfaces for backup or load sharing in one command line or by executing this command multiple times.

·     If the apply loadshare default-output-interface command is not configured on the policy node, multiple default output interfaces operate in primary/backup mode. PBR selects the first available default output interface according to the configuration order as the primary output interface to guide packet forwarding.

·     If the apply loadshare default-output-interface command is configured on the policy node, multiple default output interfaces operate in load sharing mode. PBR load shares packets in round robin manner, starting from the first configured default output interface. PBR performs per-packet load sharing for packets that do not match any fast forwarding entry, and performs per-flow load sharing for packets that match a fast forwarding entry.

Restrictions and guidelines

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 VLAN-interface 2 as the default output interface for IPv6 packets. ‌

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply default-output-interface vlan-interface 2

Related commands

apply loadshare

apply loadshare

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

Use undo apply loadshare to restore the default.

Syntax

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

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

Default

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

Views

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

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

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

Usage guidelines

Multiple next hop, output interface, default next hop, or default output interface 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] ipv6 policy-based-route aa permit node 11

[Sysname-pbr6-aa-11] apply next-hop 1::1 2::2

[Sysname-pbr6-aa-11] apply loadshare next-hop

# Enable load sharing among multiple output interfaces. ‌

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply output-interface vlan-interface 1 vlan-interface 2

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

# Enable load sharing among multiple default next hops. ‌

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply default-next-hop 1::1 2::2

[Sysname-pbr6-aa-11] apply loadshare default-next-hop

# Enable load sharing among multiple default output interfaces. ‌

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply default-output-interface vlan-interface 1 vlan-interface 2

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

Related commands

apply default-next-hop

apply default-output-interface

apply next-hop

apply output-interface

apply next-hop

Use apply next-hop to set next hops.

Use undo apply next-hop to remove next hops.

Syntax

apply next-hop  { ipv6-address [ direct ] [ track track-entry-number ] } &<1-4>

undo apply next-hop [ ipv6-address&<1-4> ]

Default

No next hops are set.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

ipv6-address: Specifies the IPv6 address of a 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-4>: Indicates that you can specify up to four next hops, each of which can be associated with a track entry.

Usage guidelines

Application scenarios

You can specify multiple next hops for backup or load sharing in one command line or by executing this command multiple times.

·     If the apply loadshare next-hop command is not configured on the policy node, multiple next hops operate in primary/backup mode. PBR selects the first available next hop according to the configuration order as the primary next hop to guide packet forwarding.

·     If the apply loadshare next-hop command is configured on the policy node, multiple next hops operate in load sharing mode. PBR load shares packets in round robin manner, starting from the first configured next hop. PBR performs per-packet load sharing for packets that do not match any fast forwarding entry, and performs per-flow load sharing for packets that match a fast forwarding entry.

Restrictions and guidelines

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.

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply next-hop 1::1

Related commands

apply loadshare

apply output-interface

Use apply output-interface to set output interfaces.

Use undo apply output-interface to remove output interfaces.

Syntax

apply output-interface { interface-type interface-number [ track track-entry-number ] }&<1-4>

undo apply output-interface [ { interface-type interface-number }&<1-4> ]

Default

No output interfaces are set.

Views

IPv6 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-4>: Indicates that you can specify up to four interfaces, each of which can be associated with a track entry.

Usage guidelines

Application scenarios

You can specify multiple output interfaces for backup or load sharing in one command line or by executing this command multiple times.

·     If the apply loadshare output-interface command is not configured on the policy node, multiple output interfaces operate in primary/backup mode. PBR selects the first available output interface according to the configuration order as the primary output interface to guide packet forwarding.

·     If the apply loadshare output-interface command is configured on the policy node, multiple output interfaces operate in load sharing mode. PBR load shares packets in round robin manner, starting from the first configured output interface. PBR performs per-packet load sharing for packets that do not match any fast forwarding entry, and performs per-flow load sharing for packets that match a fast forwarding entry.

Restrictions and 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 VLAN-interface 2 as the output interface for IPv6 packets. ‌

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply output-interface vlan-interface 2

Related commands

apply loadshare

apply precedence

Use apply precedence to set a precedence for IPv6 packets.

Use undo apply precedence to restore the default.

Syntax

apply precedence { type | value }

undo apply precedence

Default

No precedence is set for IPv6 packets.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

type: Specifies the precedence type for IPv6 packets.

value: Specifies the precedence for IPv6 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 IPv6 packets.

Table 1 IP precedences and the 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 IPv6 packets.

<Sysname> system-view

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

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

display ipv6 policy-based-route

Use display ipv6 policy-based-route to display IPv6 PBR policy information.

Syntax

display ipv6 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 IPv6 PBR policies.

Examples

# Display all IPv6 policy information.

<Sysname> display ipv6 policy-based-route

Policy name: aaa

  node 1 permit:

    if-match acl 2000

    apply next-hop 1000::1

Table 2 Command output

Field	Description
node 1 permit	The match mode of Node 1 is permit.
if-match acl	Compares IPv6 packets with IPv6 ACL.
apply next-hop	Specifies a next hop for permitted IPv6 packets.

‌

Related commands

ipv6 policy-based-route (system view)

display ipv6 policy-based-route interface

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

Syntax

display ipv6 policy-based-route interface interface-type interface-number

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies an interface by its type and number.

Examples

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

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

Policy based routing information for interface Vlan-inerface2(failed):

Policy name: aaa

  node 0 deny:

  Matches: 0

  node 1 permit:

    if-match acl 3999

  Matches: 0

  node 2 permit:

    if-match acl 2000

    apply next-hop 1000::1

    apply output-interface Vlan-inerface3 track 1 (down)

    apply output-interface Vlan-inerface4 track 2 (inactive)

  Matches: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 1000::1

  Matches: 0

Total matches: 0

Table 3 Command output

Field	Description
Policy based routing information for interface XXXX	IPv6 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. To issue the policy, you must remove the policy from the interface and then apply it on the interface 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 IPv6 packets with the IPv6 ACL.
apply next-hop	Specifies a next hop for permitted IPv6 packets.
apply output-interface	Specifies an output interface for permitted packets. The interface status includes the following: ·     down—The interface is down at network layer. ·     inactive—The interface is not in position.
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.
Total matches	Total number of successful matches on all nodes.

‌

Related commands

ipv6 policy-based-route (interface view)

display ipv6 policy-based-route local

Use display ipv6 policy-based-route local to display IPv6 local PBR configuration and statistics.

Syntax

display ipv6 policy-based-route local

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display IPv6 local PBR configuration and statistics.

<Sysname> display ipv6 policy-based-route local

Policy based routing information for local:

Policy name: aaa

  node 0 deny:

  Matches: 0

  node 1 permit:

    if-match acl 3999

  Matches: 0

  node 2 permit:

    if-match acl 2000

    apply next-hop 1::1

  Matches: 0

  node 5 permit:

    if-match acl 3101

    apply next-hop 2::2

  Matches: 0

Total matches: 0

Table 4 Command output

Field	Description
Policy based routing information for local	IPv6 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.
Total matches	Total number of successful matches on all nodes.

‌

Related commands

ipv6 local policy-based-route

display ipv6 policy-based-route setup

Use display ipv6 policy-based-route setup to display IPv6 PBR configuration.

Syntax

display ipv6 policy-based-route setup

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display IPv6 PBR configuration. ‌

<Sysname> display ipv6 policy-based-route setup

Policy name              Type               Interface

pr01                     Forward            Vlan-interface 2

pr02                     Local              N/A

Table 5 Command output

Field	Description
Policy name	IPv6 PBR policy name.
Type	Type of the IPv6 PBR: ·     Forward—IPv6 interface PBR. ·     Local—IPv6 local PBR.
Interface	Interface where the policy is applied. This field displays N/A for an IPv6 local PBR policy.

‌

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 { ipv6-acl-number | name ipv6-acl-name }

undo if-match acl

Default

No ACL match criterion is set.

Views

IPv6 policy node view

Predefined user roles

network-admin

Parameters

ipv6-acl-number: Specifies an IPv6 ACL by its number in the range of 2000 to 3999. The value range of a basic ACL is 2000 to 2999 and that of an advanced ACL is 3000 to 3999.

name ipv6-acl-name: Specifies an IPv6 ACL by its name, a case-insensitive string of 1 to 63 characters starting with a letter. The ACL name cannot be all. For the command to take effect, make sure the specified IPv6 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 10 of policy aa to permit the packets matching ACL 2000.

<Sysname> system-view

[Sysname] ipv6 policy-based-route aa permit node 10

[Sysname-pbr6-aa-10] if-match acl 2000

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

<Sysname> system-view

[Sysname] ipv6 policy-based-route aa permit node 10

[Sysname-pbr6-aa-10] if-match acl name aaa

ipv6 local policy-based-route

Use ipv6 local policy-based-route to configure IPv6 local PBR based on a specified policy.

Use undo ipv6 local policy-based-route to restore the default.

Syntax

ipv6 local policy-based-route policy-name

undo ipv6 local policy-based-route

Default

No policy is specified for IPv6 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 IPv6 policy must already exist.

Usage guidelines

Application scenarios

IPv6 local PBR is used to route locally generated packets except the packets destined for the sender. This feature might affect local services. Do not configure IPv6 local PBR unless doing so is required.

Restrictions and guidelines

Before you configure this command, make sure the specified PBR policy already exists. If the PBR policy does not exist, this command cannot take effect.

You can apply only one policy locally. Before you apply a new policy, you must first remove the current policy.

Examples

# Configure IPv6 local PBR based on policy aaa.

<Sysname> system-view

[Sysname] ipv6 local policy-based-route aaa

Related commands

display ipv6 policy-based-route local

ipv6 policy-based-route (interface view)

Use ipv6 policy-based-route to configure IPv6 interface PBR by applying an IPv6 policy to an interface.

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

Syntax

ipv6 policy-based-route policy-name

undo ipv6 policy-based-route

Default

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

Usage guidelines

Application scenarios

Use this command to guide forwarding of the packets on an interface.

Restrictions and guidelines

You can apply only one policy to an interface. Before you can apply a new interface PBR policy to an interface, 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] ipv6 policy-based-route aaa

Related commands

display ipv6 policy-based-route interface

ipv6 policy-based-route (system view)

Use ipv6 policy-based-route to create an IPv6 policy node and enter its view, or enter the view of an existing IPv6 policy node.

Use undo ipv6 policy-based-route to delete an IPv6 policy or IPv6 policy node.

Syntax

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

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

Default

No IPv6 policy nodes exist.

Views

System view

Predefined user roles

network-admin

Parameters

policy-name: Specifies a policy 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 the number of the IPv6 policy node. A smaller number has a higher priority. The value range for the node-number argument is 0 to 65535.

Usage guidelines

To delete an IPv6 policy that has already applied to an interface, you must delete the policy from the interface first.

If a policy node is specified, the undo ipv6 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 node is specified, the command deletes the whole policy.

Examples

# Create permit-mode Node 10 for IPv6 policy aaa and enter its view.

<Sysname> system-view

[Sysname] ipv6 policy-based-route aaa permit node 10

[Sysname-pbr6-aaa-10]

Related commands

display ipv6 policy-based-route

reset ipv6 policy-based-route statistics

Use reset ipv6 policy-based-route statistics to clear IPv6 PBR statistics.

Syntax

reset ipv6 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 IPv6 PBR statistics for all policies.

Examples

# Clear all IPv6 PBR statistics.

<Sysname> reset ipv6 policy-based-route statistics

snmp-agent trap enable ipv6 policy-based-route

Use snmp-agent trap enable ipv6 policy-based-route to enable SNMP notifications for IPv6 PBR.

Use undo snmp-agent trap enable ipv6 policy-based-route to disable SNMP notifications for IPv6 PBR.

Syntax

snmp-agent trap enable ipv6 policy-based-route

undo snmp-agent trap enable ipv6 policy-based-route

Default

SNMP notifications are enabled for IPv6 PBR.

Views

System view

Predefined user roles

network-admin

Usage guidelines

After you enable this feature, IPv6 PBR can generate notifications and send them to the SNMP module when the next hop becomes invalid. For the IPv6 PBR notifications to be sent correctly, you must also configure SNMP on the device. For more information about configuring SNMP, see the network management and monitoring configuration guide for the device.

Examples

# Enable SNMP notifications for IPv6 PBR.

<Sysname> system-view

[Sysname] snmp-agent trap enable ipv6 policy-based-route