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

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] policy-based-route policy1 permit node 10

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

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

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

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This command takes effect only when the match 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] policy-based-route aa permit node 11

[Sysname-pbr-aa-11] apply continue

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

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

Default

No default next hop is 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.

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

ip-address: Specifies the IP 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] policy-based-route aa permit node 11

[Sysname-pbr-aa-11] apply default-next-hop 1.1.1.1 direct

Related commands

apply loadshare

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

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

<Sysname> system-view

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

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

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

<Sysname> system-view

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

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

Related commands

apply loadshare

Policy-based routing commands -- apply ip-df

Use apply ip-df to set the Don't Fragment (DF) bit in the IP header of matching packets.

Use undo apply ip-df to restore the default.

Syntax

apply ip-df df-value

undo apply ip-df

Default

The DF bit is not set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

df-value: Sets the DF bit in the IP header of matching packets. The value can be 0 or 1.

Usage guidelines

Setting the DF bit to 0 allows packet fragmentation.

Setting the DF bit to 1 prohibits packet fragmentation.

Examples

# Set the DF bit in the IP header of matching packets to 0.

<Sysname> system-view

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

[Sysname-pbr-aa-11] apply ip-df 0

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

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

<Sysname> system-view

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

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

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

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

<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

# Enable load sharing among multiple default output interfaces. (Applicable to routers.)

<Sysname> system-view

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

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

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

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

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

<Sysname> system-view

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

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

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

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

<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

# Enable load sharing among multiple default output interfaces. (Applicable to switches.)

<Sysname> system-view

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

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

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

Related commands

apply default-next-hop

apply default-output-interface

apply next-hop

apply output-interface

Policy-based routing commands -- apply mirror-to-next-hop

Use apply mirror-to-next-hop to set a mirroring action that mirrors packets to a next hop.

Use undo apply mirror-to-next-hop to restore the default.

Syntax

apply mirror-to-next-hop [ vpn-instance vpn-instance-name ] { ip-address [ track track-entry-number ] }&<1-2>

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

Default

The mirroring action is not 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.

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. In primary/backup mode, the next hop configured first is the primary next hop, and the next hop configured at last is the backup next hop.

Usage guidelines

Use this command to send mirrored packets to a specific interface. You can test the traffic and capture packets on the interface to collect traffic statistics or solve communication problems.

Examples

# Set a mirroring action that mirrors packets to the next hop 1.1.1.1, and associate the next hop with track entry 1.

<Sysname> system-view

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

[Sysname-pbr-aa-5] apply mirror-to-next-hop 1.1.1.1 track 1

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

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

Default

No next hop is 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.

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

ip-address: Specifies the IP 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.

Usage guidelines

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

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

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

Examples

# Set a directly-connected next hop of 1.1.1.1.

<Sysname> system-view

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

[Sysname-pbr-aa-11] apply next-hop 1.1.1.1 direct

Related commands

apply loadshare

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

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

<Sysname> system-view

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

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

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

<Sysname> system-view

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

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

Related commands

apply loadshare

Policy-based routing commands -- 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

Policy-based routing commands -- apply service-chain

Use apply service-chain to set the service chain information.

Use undo apply service-chain to restore the default.

Syntax

apply service-chain path-id service-path-id [ path-index service-patch-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 16777215. The path ID uniquely identifies a service chain.

path-index service-path-index: Specifies a node in a service chain by its index in the range of 1 to 255. This option is used to distinguish different nodes in a service chain. If all packets are sent from one node, you do not need to specify this option.

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

Policy-based routing commands -- 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

Policy-based routing commands -- display ip policy-based-route apply

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

Syntax

Centralized devices:

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

Distributed devices in standalone mode:Centralized IRF devices:

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

Distributed devices in IRF mode:

display ip 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 PBR that is configured with the ip policy-based-route apply command. To display configuration and statistics for PBR that is configured in VLAN interface view, use the display ip policy-based-route interface command.

Examples

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

<Sysname> display ip 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.2.2

Matched: 0

Total matched: 0

Table 3 Command output

Field | Description
Policy-based routing information for Vlan-interface xxx | 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.

Policy-based routing commands -- display ip policy-based-route egress interface

Use display ip policy-based-route egress interface to display the outbound PBR configuration and statistics for a VXLAN tunnel interface.

Syntax

Centralized devices:

display ip policy-based-route egress interface interface-type interface-number

Distributed devices in standalone mode:Centralized IRF devices:

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

Distributed devices in IRF mode:

display ip policy-based-route egress 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 a VXLAN tunnel 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 for the specified VXLAN tunnel 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 VXLAN tunnel 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 VXLAN tunnel 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 VXLAN tunnel 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 VXLAN tunnel 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.

Examples

# Display the outbound PBR configuration and statistics for Tunnel 1.

<Sysname> display ip policy-based-route egress interface tunnel 1

Policy based routing information for interface Tunnel1:

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 2.2.2.2

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1.1.1.1

apply output-interface GigabitEthernet1/0/2 track 1

apply output-interface GigabitEthernet1/0/3 track 2

Matched: 0

Total matched: 0

Table 4 Command output

Field | Description
Policy based routing information for interface xxxx(failed) | Outbound PBR configuration and statistics for the VXLAN tunnel interface. NOTE: If you specify a slot number, this field displays failed in brackets for a policy that failed to be issued to the driver. The failure means that all node configurations in the PBR policy failed to be issued.
node 0 deny(not support) node 2 permit(no resource) | Match mode of the node: permit or deny. NOTE: If you specify a slot number, this field displays the cause in brackets for a node that does not take effect: · not support—The device does not support the match criteria configured on the node. · no resource—The node does not have sufficient resources (for example, ACLs).
if-match acl | Compares packets with the ACL.
apply next-hop | Specifies a next hop for permitted packets.
apply output-interface xxxx track 1 (down) | Specifies an output interface and its associated track entry for permitted packets. This field displays the interface status in brackets. · up—The interface is up. · down—The interface is down at the network layer. · inactive—The card that hosts the interface is not in position.
Matched: 0 (no statistics resource) | Number of successful matches on the node. NOTE: If you specify a slot number but the device does not have sufficient resources to collect statistics on the slot, this field displays no statistics resource in brackets.
Total matched | Total number of successful matches on all nodes.

Related commands

reset ip policy-based-route statistics

Policy-based routing commands -- display ip policy-based-route interface

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

Syntax

Centralized devices:

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

Distributed devices in standalone mode:Centralized IRF devices:

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

Distributed devices in IRF mode:

display ip 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 information 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 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 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 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 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.

Examples

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

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

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

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 2.2.2.2

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1.1.1.1

apply output-interface GigabitEthernet1/0/2 track 1

apply output-interface GigabitEthernet1/0/3 track 2

Matched: 0

Total matched: 0

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

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

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 2.2.2.2

apply output-interface GigabitEthernet1/0/2 track 1

apply output-interface GigabitEthernet1/0/3 track 2

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1.1.1.1

Matched: 0

Total matched: 0

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

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

Policy based routing information for interface Vlan-interface2:

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 2.2.2.2

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1.1.1.1

apply output-interface Vlan-interface3 track 1

apply output-interface Vlan-interface4 track 2

Matched: 0

Total matched: 0

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

Policy based routing information for interface Vlan-interface2:

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 2.2.2.2

apply output-interface Vlan-interface3 track 1

apply output-interface Vlan-interface4 track 2

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1.1.1.1

Matched: 0

Total matched: 0

Table 5 Command output

Field | Description
Policy based routing information for interface XXXX(failed) | PBR configuration and statistics on the interface. NOTE: If you specify a slot number, this field displays failed in brackets for a policy that failed to be issued to the driver. The failure means that all node configurations in the PBR policy failed to be issued.
node 0 deny(not support) node 2 permit(no resource) | Match mode of the node, permit or deny. NOTE: If you specify a slot number, this field displays the cause in brackets for a node that does not take effect: · not support—The device does not support the match criteria configured on the node. · no resource—The node does not have sufficient resources (for example, ACLs).
if-match acl | Compares packets with the ACL.
apply next-hop | Specifies a next hop for permitted packets.
apply output-interface track 1 (down) | Specifies an output interface and its associated track entry for permitted packets. This field displays the interface status in brackets. · up—The interface is up. · down—The interface is down at network layer. · inactive—The card that hosts the interface is not in position.
Matched: 0 (no statistics resource) | Number of successful matches on the node. NOTE: If you specify a slot number but the device does not have sufficient resources to collect statistics on the slot, this field displays no statistics resource in brackets.
Total matched | Total number of successful matches on all nodes.

Related commands

reset ip policy-based-route statistics

Policy-based routing commands -- display ip policy-based-route local

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

Syntax

Centralized devices:

display ip policy-based-route local

Distributed devices in standalone mode:Centralized IRF devices:

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

Distributed devices in IRF mode:

display ip 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 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 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 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 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 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 local PBR configuration and statistics.

<Sysname> display ip policy-based-route local

Policy based routing information for local:

Policy name: aaa

node 0 deny:

Matched: 0

node 1 permit:

if-match acl 3999

Matched: 0

node 2 permit:

if-match acl 2000

apply next-hop 2.2.2.2

Matched: 0

node 5 permit:

if-match acl 3101

apply next-hop 1.1.1.1

Matched: 0

Total matched: 0

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

Related commands

reset ip policy-based-route statistics

Policy-based routing commands -- 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. (Applicable to routers.)

<Sysname> display ip policy-based-route setup

Policy name Type Interface

aaa Forward GigabitEthernet2/0/1

aaa Forward GigabitEthernet2/0/2

aaa Local N/A

# Display PBR configuration. (Applicable to switches.)

<Sysname> display ip policy-based-route setup

Policy name Type Interface

pr01 Forward Vlan-interface2

aaa Egress Tunnel1

aaa Local N/A

Table 7 Command output

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

Related commands

ip policy-based-route

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

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

Policy-based routing commands -- if-match app-group

Use if-match app-group to set application group match criteria.

Use undo if-match app-group to delete application group match criteria.

Syntax

if-match app-group app-group-name&<1-n>

undo if-match app-group [ app-group-name&<1-n> ]

Default

No application group match criteria are set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

app-group-name: Specifies an application group by its name, a case-insensitive string of 1 to 63 characters. The group name can include letters, digits, underscores (_), and hyphens (-). The application group name cannot be Invalid, other, or any application group name predefined by the system.

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

The application match criteria apply only to interface PBR.

If you specify an application group, the undo if-match app-group command deletes the application group match criterion.

If you do not specify an application group, the undo if-match app-group command deletes all application group match criteria.

Examples

# Specify the application group test as a match criterion.

<Sysname> system-view

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

[Sysname-pbr-aa-11] if-match app-group test

Policy-based routing commands -- if-match object-group

Use if-match object-group to set service object group match criteria.

Use undo if-match object-group to delete service object group match criteria.

Syntax

if-match object-group service object-group-name&<1-n>

undo if-match object-group service [ object-group-name&<1-n> ]

Default

No service object group match criteria are set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

service object-group-name: Specifies a service object group by its name, a case-insensitive string of 1 to 31 characters. The group name can include letters, digits, underscores (_), and hyphens (-).

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

If you specify a service object group, the undo if-match object-group command deletes the service object group match criterion.

If you do not specify a service object group, the undo if-match object-group command deletes all service object group match criteria.

Examples

# Specify the service object group test as a match criterion.

<Sysname> system-view

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

[Sysname-pbr-aa-11] if-match object-group service test

Policy-based routing commands -- if-match packet-length

Use if-match packet-length to set a 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

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

min-len: Specifies the minimum IP 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

Use this command to set a criterion to match the total length of data packets.

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

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

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

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

Syntax

if-match service-chain { path-id service-path-id [ path-index service-patch-index ] }&<1-n>

undo if-match service-chain [ path-id service-path-id ]&<1-n> ]

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 16777215. The path ID uniquely identifies a service chain.

path-index service-path-index: Specifies a node in a service chain by its index in the range of 1 to 255. This option is used to distinguish packets sent from different nodes in a service chain. If all packets are sent from one node, you do not need to specify this option.

&<1-n>: Indicates that you can repeat the path-id service-path-id option to specify a maximum of n path IDs when you execute the command or the undo form of the command. When you execute the command, you can alternatively specify a maximum of n path ID and node index pairs by repeating the path-id service-path-id path-index service-patch-index 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

Policy-based routing commands -- if-match vxlan-id

Use if-match vxlan-id to set a VXLAN match criterion

Use undo if-match vxlan-id to restore the default.

Syntax

if-match vxlan-id vxlan-id

undo if-match vxlan-id

Default

No VXLAN match criterion is set.

Views

Policy node view

Predefined user roles

network-admin

mdc-admin

Parameters

vxlan-id: Specifies a VXLAN ID in the range of 0 to 16777215.

Examples

# Configure Node 11 of policy aaa to permit packets with the VXLAN ID 1000.

<Sysname> system-view

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

[Sysname-pbr-aaa-11] if-match vxlan-id 1000

Policy-based routing commands -- 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 referenced 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 setup

ip policy-based-route apply

policy-based-route

Policy-based routing commands -- ip policy-based-route

Use ip policy-based-route to specify a policy for interface PBR on an interface.

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

Syntax

ip policy-based-route policy-name [ share-mode ]

undo ip policy-based-route

Default

No policy is applied to an interface.

Views

Interface view

Predefined user roles

network-admin

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. All interfaces applied with the policy on a card use the same hardware resources. If you do not specify this keyword, the interfaces use different hardware resources. On an interface, you can configure only one application in QoS and ACL resource sharing mode for traffic in one direction. The device supports only the packet filtering, QoS policy, and PBR applications. For information about packet filtering 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 GigabitEthernet 1/0/1. (Applicable to routers.)

<Sysname> system-view

[Sysname] interface gigabitethernet 1/0/1

[Sysname-GigabitEthernet1/0/1] ip 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] ip policy-based-route aaa

Related commands

display ip policy-based-route setup

ip policy-based-route apply

policy-based-route

Policy-based routing commands -- ip policy-based-route apply

Use ip policy-based-route apply to specify a policy for a list of VLAN interfaces.

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

Syntax

ip policy-based-route policy-name apply vlan-interface interface-list

undo ip policy-based-route policy-name apply [ vlan-interface interface-list ]

Default

No policy is specified for the VLAN interfaces.

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

· ip policy-based-route apply

· ip policy-based-route (interface view)

To specify a 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 a 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 policy aaa for VLAN-interface 100 through VLAN-interface 200.

<Sysname> system-view

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

Related commands

ip local policy-based-route

ip policy-based-route

Policy-based routing commands -- ip policy-based-route egress

Use ip policy-based-route egress to specify a policy for outbound PBR on a VXLAN tunnel interface.

Use undo ip policy-based-route egress to restore the default.

Syntax

ip policy-based-route policy-name egress

undo ip policy-based-route egress

Default

No policy is specified for outbound PBR on a VXLAN tunnel interface.

Views

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

Examples

# Apply policy aaa to Tunnel 1.

<Sysname> system-view

[Sysname] interface Tunnel 1 mode vxlan

[Sysname-Tunnel1] ip policy-based-route aaa egress

Policy-based routing commands -- ip policy-based-route vxlan-mode enable

Use ip policy-based-route vxlan-mode enable to enable VXLAN mode for PBR.

Use undo ip policy-based-route vxlan-mode enable to disable VXLAN mode for PBR.

Syntax

ip policy-based-route vxlan-mode enable

undo ip policy-based-route vxlan-mode enable

Default

VXLAN mode for PBR is disabled.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This feature causes forwarding entries to be updated on all interfaces of a device. Execute this command before you configure interface PBR to prevent the following consequences:

· The update is time-consuming because of too many forwarding entries.

· If the update is not performed on interfaces in interface configuration order, the device cannot provide enough resources for some interfaces.

Examples

# Enable VXLAN mode for PBR.

<Sysname> system-view

[Sysname] ip policy-based-route vxlan-mode enable

Policy-based routing commands -- 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 varies by device model.

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

Policy-based routing commands -- 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

Related commands

display ip policy-based-route egress interface

display ip policy-based-route interface

display ip policy-based-route local

Policy-based routing commands -- snmp-agent trap enable policy-based-route

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

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

Syntax

snmp-agent trap enable policy-based-route

undo snmp-agent trap enable policy-based-route

Default

SNMP notifications are enabled for PBR.

Views

System view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

After you enable this feature, PBR can generate notifications and send them to the SNMP module when the next hop becomes invalid. For the 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 PBR.

<Sysname> system-view

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