IPv6 policy-based routing commands -- apply access-vpn vpn-instance

Use apply access-vpn vpn-instance to set VPN instances.

Use undo apply access-vpn vpn-instance to remove VPN instances.

Syntax

apply access-vpn vpn-instance vpn-instance-name&<1-n>

undo apply access-vpn vpn-instance [ vpn-instance-name&<1-n> ]

Default

No VPN instance is specified for a node.

Views

IPv6 policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. The specified VPN must already exist.

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

Usage guidelines

You can specify a maximum of n VPN instances for a node. The matching packets are forwarded according to the forwarding table of the first available VPN instance.

With a VPN instance specified, the undo apply access-vpn vpn-instance command removes the VPN instance.

Without any VPN instance specified, the undo apply access-vpn vpn-instance command removes all VPN instances.

Examples

# Set VPN 1 and VPN 2 for node 10. (VPN 1 and VPN 2 already exist.)

<Sysname> system-view

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

[Sysname-pbr6-policy1-10] apply access-vpn vpn-instance vpn1 vpn2

IPv6 policy-based routing commands -- apply continue

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

Use undo apply continue to restore the default.

Syntax

apply continue

undo apply continue

Default

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

Views

IPv6 policy node view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

This command applies when the following clauses are not configured or become invalid:

· apply access-vpn vpn-instance

· apply next-hop

· apply output-interface

· apply default-next-hop

· apply default-output-interface

For example, the command applies when the specified next hop is unreachable, the packets cannot be forwarded in the specified VPN instance, or the specified output interface is down.

Examples

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

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply continue

IPv6 policy-based routing commands -- apply default-next-hop

Use apply default-next-hop to set default next hops.

Use undo apply default-next-hop to remove default next hops.

Syntax

apply default-next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ipv6-address [ direct ] [ track track-entry-number ] }&<1-n>

undo apply default-next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ipv6-address&<1-n> ]

Default

No default next hop is set.

Views

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

inbound-vpn: Specifies the VPN instance where the inbound interface belongs.

ipv6-address: Specifies the IPv6 address of the default next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the default next hop belongs to the public network.

direct: Specifies a directly connected default next hop.

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

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

Usage guidelines

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

With a default next hop specified, the undo apply default-next-hop command removes the default next hop.

Without any default next hop specified, the undo apply default-next-hop command removes all default next hops.

Examples

# Set a directly-connected default next hop of 1:1::1:1.

<Sysname> system-view

[Sysname] 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

IPv6 policy-based routing commands -- apply default-output-interface

Use apply default-output-interface to set default output interfaces.

Use undo apply default-output-interface to remove default output interfaces.

Syntax

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

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

Default

No default output interface is set.

Views

IPv6 policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

Usage guidelines

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

The default output interface must be P2P type. Using a non-P2P default output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and non-broadcast multi-access (NBMA) interfaces such as Ethernet and virtual-template interfaces. In NBMA networks, packets are sent in unicast.

With a default output interface specified, the undo apply default-output-interface command removes the default output interface.

Without any default output interface specified, the undo apply default-output-interface command removes all default output interfaces.

Examples

# Specify GigabitEthernet 1/0/1 as the default output interface for IPv6 packets. (Applicable to routers.)

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply default-output-interface gigabitethernet 1/0/1

# Specify VLAN-interface 2 as the default output interface for IPv6 packets. (Applicable to switches.)

<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

IPv6 policy-based routing commands -- 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

mdc-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 hops, output interfaces, default next hops, or default output interfaces operate in either primary/backup or load sharing mode. For example:

· Primary/backup mode—The first configured output interface is used. When the primary output interface fails, the first configured backup output interface takes over.

· Load sharing mode—Multiple output interfaces load share traffic on a per-packet basis in turn, according to the configuration order.

| NOTE: Multiple next hops load share traffic according to their weights. By default, all next hops have the same weight and traffic is load balanced among them.

Examples

# Enable load sharing among multiple next hops. (Applicable to routers.)

<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. (Applicable to routers.)

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2

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

# Enable load sharing among multiple default next hops. (Applicable to routers.)

<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. (Applicable to routers.)

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply default-output-interface gigabitethernet 1/0/1 gigabitethernet 1/0/2

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

# Enable load sharing among multiple next hops. (Applicable to switches.)

<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. (Applicable to switches.)

<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. (Applicable to switches.)

<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. (Applicable to switches.)

<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

IPv6 policy-based routing commands -- apply next-hop

Use apply next-hop to set next hops.

Use undo apply next-hop to remove next hops.

Syntax

apply next-hop [ vpn-instance vpn-instance-name | inbound-vpn ] { ipv6-address [ direct ] [ track track-entry-number ] [ weight weight-value ] } &<1-n>

undo apply next-hop [ [ vpn-instance vpn-instance-name | inbound-vpn ] ipv6-address&<1-n> ]

Default

No next hop is set.

Views

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

inbound-vpn: Specifies the VPN instance where the inbound interface belongs.

ipv6-address: Specifies the IPv6 address of the next hop. If you do not specify the vpn-instance vpn-instance-name option or the inbound-vpn keyword, the next hop belongs to the public network.

direct: Specifies that the next hop must be directly connected to take effect.

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

weight weight-value: Specifies a load sharing weight for the next hop, in the range of 1 to 100. The default is 10. If you specify weights 1, 1, and 2 for three next hops, they share 1/4, 1/4, and 1/2 of the whole traffic, respectively.

&<1-n>: Indicates that the argument before it can be entered up to n times. The value of n varies by device model.

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.

<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

IPv6 policy-based routing commands -- apply output-interface

Use apply output-interface to set output interfaces.

Use undo apply output-interface to remove output interfaces.

Syntax

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

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

Default

No output interface is set.

Views

IPv6 policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

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

Usage guidelines

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

The output interface must be P2P type. Using a non-P2P output interface can result in forwarding failures when the interface has multiple next hops. Non-P2P interfaces include broadcast and NBMA interfaces such as Ethernet and virtual-template interfaces.

With an output interface specified, the undo apply output-interface command removes the output interface.

Without any output interface specified, the undo apply output-interface command removes all output interfaces.

Examples

# Specify GigabitEthernet 1/0/1 as the output interface for IPv6 packets. (Applicable to routers.)

<Sysname> system-view

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

[Sysname-pbr6-aa-11] apply output-interface gigabitethernet 1/0/1

# Specify VLAN-interface 2 as the output interface for IPv6 packets. (Applicable to switches.)

<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

IPv6 policy-based routing commands -- 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

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

IPv6 policy-based routing commands -- 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

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

IPv6 policy-based routing commands -- display ipv6 policy-based-route apply

Use display ipv6 policy-based-route apply to display the IPv6 PBR configuration and statistics for a VLAN interface.

Syntax

Centralized devices:

display ipv6 policy-based-route apply vlan-interface interface-number

Distributed devices in standalone mode:Centralized IRF devices:

display ipv6 policy-based-route apply vlan-interface interface-number [ slot slot-number [ cpu cpu-number ] ]

Distributed devices in IRF mode:

display ipv6 policy-based-route apply vlan-interface interface-number [ chassis chassis-number slot slot-number [ cpu cpu-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

vlan-interface interface-number: Specifies a VLAN interface by its number.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for the specified VLAN interface on the active MPU. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays information for the specified VLAN interface on the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command displays information for the specified VLAN interface on the master device. (Centralized IRF devices.) (IRF 3 capable.)

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 for the specified VLAN interface on the global active MPU. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command displays information for the specified VLAN interface on the global active MPU. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Parameters

This command displays configuration and statistics for IPv6 PBR that is configured with the ipv6 policy-based-route apply command. To display configuration and statistics for IPv6 PBR that is configured in VLAN interface view, use the display ipv6 policy-based-route interface command.

Examples

# Display the IPv6 PBR configuration and statistics for VLAN-interface 100.

<Sysname> display ipv6 policy-based-route apply vlan-interface 100

Policy-based routing information for Vlan-interface 100:

Policy name: aaa

node 2 permit:

if-match acl 3000

apply next-hop 2::2

Matched: 0

Total matched: 0

Table 3 Command output

Field | Description
Policy-based routing information for Vlan-interface xxx | IPv6 PBR configuration and statistics for the VLAN interface.
node 2 permit | Match mode of the node: permit.
if-match acl | Compares packets with the ACL.
apply next-hop | Specifies a next hop for permitted packets.
Matched: 0 | Number of successful matches on the node.
Total matched | Total number of successful matches on all nodes.

IPv6 policy-based routing commands -- display ipv6 policy-based-route interface

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

Syntax

Centralized devices:

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

Distributed devices in standalone mode:Centralized IRF devices:

display ipv6 policy-based-route interface interface-type interface-number [ slot slot-number [ cpu cpu-number ] ]

Distributed devices in IRF mode:

display ipv6 policy-based-route interface interface-type interface-number [ chassis chassis-number slot slot-number [ cpu cpu-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 IPv6 interface PBR configuration and statistics for the active MPU. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays IPv6 interface PBR configuration and statistics for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command displays IPv6 interface PBR configuration and statistics for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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 IPv6 interface PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command displays IPv6 interface PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

Examples

# Display IPv6 PBR configuration and statistics on GigabitEthernet 1/0/1. (Applicable to routers.)

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

Policy based routing information for interface GigabitEthernet1/0/1(failed):

Policy name: aaa

node 0 deny:

Matched: 0

node 1 permit:

if-match acl 3999

Matched: 0

node 2 permit:

if-match acl 2000

apply next-hop 1000::1

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

apply output-interface GigabitEthernet1/0/3 track 2 (inactive)

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1000::1

Matched: 0

Total matched: 0

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

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

Policy name: aaa

node 0 deny(not support):

Matched: 0

node 1 permit:

if-match acl 3999

Matched: 0

node 2 permit(no resource):

if-match acl 2000

apply next-hop 1000::1

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

apply output-interface GigabitEthernet1/0/3 track 2 (inactive)

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1000::1

Matched: 0 (no statistics resource)

Total matched: 0

# Display IPv6 PBR configuration and statistics on VLAN-interface 2. (Applicable to switches.)

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

Matched: 0

node 1 permit:

if-match acl 3999

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

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1000::1

Matched: 0

Total matched: 0

<Sysname> display ipv6 policy-based-route interface Vlan-inerface2

Policy based routing information for interface Vlan-inerface2:

Policy name: aaa

node 0 deny(not support):

Matched: 0

node 1 permit:

if-match acl 3999

Matched: 0

node 2 permit(no resource):

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)

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1000::1

Matched: 0 (no statistics resource)

Total matched: 0

Table 4 Command output

Field | Description
Policy based routing information for interface XXXX(failed) | IPv6 PBR configuration and statistics on the interface. failed indicates the policy (including all its nodes) failed to be assigned to the driver. For a global interface (with only one-dimensional interface number, for example, VLAN-interface 10), failed can be displayed only when you specify the slot information for the command.
node 0 deny(not support) node 2 permit(no resource) | Match mode of the node, permit or deny. not support means the device does not support the match criteria configured on the node. no resource means the device has insufficient ACL resources, and failed to assign ACL resources to the node. For a global interface (with only one-dimensional interface number, for example, VLAN-interface 10), not support and no resource can be displayed only when you specify the slot information for the command.
if-match acl | Compares IPv6 packets with the IPv6 ACL.
apply next-hop | Specifies a next hop for permitted IPv6 packets.
apply output-interface track 1 (down) | Specifies an output interface for permitted packets. The interface status includes the following: · up—The interface is up. · down—The interface is down at network layer. · inactive—The interface is not in position.
Matched: 0 (no statistics resource) | Number of successful matches on the node (no statistics resource indicates insufficient statistics resources). For a global interface (with only one-dimensional interface number, for example, VLAN-interface 10), no statistics resource can be displayed only when you specify the slot information for the command.
Total matched | Total number of successful matches on all nodes.

Related commands

reset ipv6 policy-based-route statistics

IPv6 policy-based routing commands -- display ipv6 policy-based-route local

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

Syntax

Centralized devices:

display ipv6 policy-based-route local

Distributed devices in standalone mode:Centralized IRF devices:

display ipv6 policy-based-route local [ slot slot-number [ cpu cpu-number ] ]

Distributed devices in IRF mode:

display ipv6 policy-based-route local [ chassis chassis-number slot slot-number [ cpu cpu-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 IPv6 local PBR configuration and statistics for the active MPU. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays IPv6 local PBR configuration and statistics for the master device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. If you do not specify a member device or PEX, this command displays IPv6 local PBR configuration and statistics for the master device. (Centralized IRF devices.) (IRF 3 capable.)

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 IPv6 local PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. If you do not specify a card or PEX, this command displays IPv6 local PBR configuration and statistics for the global active MPU. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

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:

Matched: 0

node 1 permit:

if-match acl 3999

Matched: 0

node 2 permit:

if-match acl 2000

apply next-hop 1::1

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 2::2

Matched: 0

Total matched: 0

Table 5 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.
Matched: 0 | Number of successful matches on the node.
Total matched | Total number of successful matches on all nodes.

Related commands

reset ipv6 policy-based-route statistics

IPv6 policy-based routing commands -- 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

mdc-admin

mdc-operator

Examples

# Display IPv6 PBR configuration. (Applicable to routers.)

<Sysname> display ipv6 policy-based-route setup

Policy name Type Interface

pr01 Forward GigabitEthernet1/0/1

pr02 Local N/A

# Display IPv6 PBR configuration. (Applicable to switches.)

<Sysname> display ipv6 policy-based-route setup

Policy name Type Interface

pr01 Forward Vlan-interface 2

pr02 Local N/A

Table 6 Command output

Field | Description
Policy name | Policy name.
Type | Type of the PBR: · Forward—Interface PBR. · Local—Local PBR.
Interface | Interface where the policy is applied.

Related commands

ipv6 policy-based-route (interface view)

IPv6 policy-based routing commands -- 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

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

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 policy-based routing commands -- if-match packet-length

Use if-match packet-length to set an IPv6 packet length match criterion.

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

Syntax

if-match packet-length min-len max-len

undo if-match packet-length

Default

No packet length match criterion is set.

Views

IPv6 policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

min-len: Specifies the minimum IPv6 packet length in the range of 1 to 65535 bytes.

max-len: Specifies the maximum IP packet length in the range of 1 to 65535 bytes. The maximum length must be no less than the minimum length.

Usage guidelines

The packet length range includes boundary values. For example, if you set the min-len and max-len arguments to 100 and 200, respectively, packets with lengths of 100 bytes and 200 bytes are also matched.

Examples

# Match packets with a length from 100 to 200 bytes.

<Sysname> system-view

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

[Sysname-pbr6-aa-11] if-match packet-length 100 200

IPv6 policy-based routing commands -- 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.

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.

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

IPv6 policy-based routing commands -- 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 referenced for IPv6 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 IPv6 policy must already exist.

Usage guidelines

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

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.

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 setup

ipv6 policy-based-route (system view)

ipv6 policy-based-route apply

IPv6 policy-based routing commands -- 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 [ share-mode ]

undo ipv6 policy-based-route

Default

No IPv6 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: Sets the resource sharing mode for the policy. An IPv6 policy in this mode uses the same hardware resources on different interfaces of a card. If you do not specify this keyword, the policy uses different hardware resources.

Usage guidelines

Typically, an IPv6 policy on different interfaces of a card uses different hardware resources. To avoid resource usage overhead, you can set the resource sharing mode when applying the policy to each interface. This mode allows the policy to use the same hardware resources on different interfaces of the card.

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

Examples

# Apply policy aaa to GigabitEthernet 1/0/1. (Applicable to routers.)

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] ipv6 policy-based-route aaa

# Apply policy aaa to VLAN-interface 2. (Applicable to switches.)

<Sysname> system-view

[Sysname] interface vlan-interface 2

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

Related commands

display ipv6 policy-based-route setup

ipv6 policy-based-route (system view)

ipv6 policy-based-route apply

IPv6 policy-based routing commands -- 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

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

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

IPv6 policy-based routing commands -- ipv6 policy-based-route apply

Use ipv6 policy-based-route apply to specify an IPv6 policy for a list of VLAN interfaces.

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

Syntax

ipv6 policy-based-route policy-name apply vlan-interface interface-list &<1-8>

undo ipv6 policy-based-route policy-name apply [ vlan-interface interface-list &<1-8> ]

Default

No IPv6 policy is specified for the VLAN interfaces.

Views

System view

Predefined user roles

network-admin

mdc-admin

Parameters

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

vlan-interface interface-list: Specifies a space-separated list of up to eight VLAN interface items. Each item specifies a VLAN interface or a range of VLAN interfaces in the form of interface-type interface-number1 to interface-type interface-number2. The value for interface-number2 must be greater than or equal to the value for interface-number1. The interface type is VLAN interface.

Usage guidelines

You cannot specify different policies for a VLAN interface. You can use either of the following commands to specify a policy for a VLAN interface:

· ipv6 policy-based-route apply

· ipv6 policy-based-route (interface view)

To specify an IPv6 policy for multiple VLAN interfaces, you can use either of the following methods:

· Method 1—Execute the ip policy-based-route apply command. The policy is issued to the driver for all interfaces at the same time. This method reduces hardware entries and saves system resources. You can use this method to specify an IPv6 policy for VLAN interfaces that do not exist.

· Method 2—Use the interface range command to create an interface range, and specify a policy for the interface range. The policy is issued to the driver for each interface. The system creates a hardware entry for each interface.

Examples

# Specify IPv6 policy aaa for VLAN-interface 100 through VLAN-interface 200.

<Sysname> system-view

[Sysname] ipv6 policy-based-route aaa apply vlan-interface 100 to 200

Related commands

ipv6 local policy-based-route

ipv6 policy-based-route (interface view)

IPv6 policy-based routing commands -- 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

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

Examples

# Clear all IPv6 PBR statistics.

<Sysname> reset ipv6 policy-based-route statistics

Related commands

display ipv6 policy-based-route interface

display ipv6 policy-based-route local

IPv6 policy-based routing commands -- 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

mdc-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 SNMP configuration, 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