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

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

interface-type interface-number: Specifies a VXLAN tunnel interface by its type and number.

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays information for the specified VXLAN tunnel interface on the master device.

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 Ten-GigabitEthernet1/0/2 track 1
    apply output-interface Ten-GigabitEthernet1/0/3 track 2
  Matched: 0
Total matched: 0

Table 121: Command output

Field

Description

Policy based routing information for interface xxxx(failed)

Outbound PBR configuration and statistics for the VXLAN tunnel interface.

This field displays failed in brackets if none of the nodes in the policy has been successfully issued to the driver.

NOTE:

The failed status is available on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command.

  • For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces.

  • For a physical interface, specify its slot number.

node 0 deny(not support)

node 2 permit(no resource)

Match mode of the node, permit or deny.

If a node fails to be issued to the driver, the command displays the cause in brackets, which include:

  • not support—The device does not support the match criteria configured on the node.

  • no resource—No sufficient resources (for example, ACLs) are available for the node.

NOTE:

The cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command.

  • For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces.

  • For a physical interface, specify its slot number.

if-match acl

Compares packets with the ACL.

apply next-hop

Specifies a next hop for permitted packets.

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. If the device does not have sufficient resources to count matches, this field displays no statistics resource in brackets.

NOTE:

The statistics collection failure cause is available only on a per-slot basis. To obtain this information, you must specify a slot number when you execute the command.

  • For a global interface (for example, a VLAN interface), which might have member physical interfaces on multiple slots, specify a slot that contains its member interfaces.

  • For a physical interface, specify its slot number.

Total matched

Total number of successful matches on all nodes.

Related commands

reset ip policy-based-route statistics