display mpls te p2mp tunnel path

Function

The display mpls te p2mp tunnel path command displays path attributes of the P2MP TE tunnel.

Format

display mpls te p2mp tunnel path [ [ tunnel-name ] tunnel-name ] [ lsp-id ingress-id session-id p2mp-id lsp-id [ s2l-destination leaf ] ]

display mpls te p2mp tunnel path fast-reroute { local-protection-available | local-protection-inuse }

Parameters

Parameter Description Value
tunnel-name tunnel-name

Specifies the tunnel name.

The value is a string of 1 to 255 case-sensitive characters, spaces not supported. The tunnel name must be the same as that in the configuration file, case-sensitive and spaces not supported. For example, if a configuration file specifies the tunnel interface "interface Tunnel10", the tunnel-name parameter must specify the P2MP TE tunnel as "Tunnel10". Both "Tunnel10" and "Tunnel 10" are incorrect.

lsp-id

Specifies the LSP ID.

-

lsp-id

Specifies the LSP ID.

The value is an integer that ranges from 0 to 65535.

ingress-id

Specifies the ingress LSR ID.

The value is an integer ranging from 0 to 4294967295.

session-id

Specifies the ID of a session.

The value is an integer that ranges from 0 to 65535.

p2mp-id

Specifies the P2MP ID.

The value is in hexadecimal notation rangeing from 0 to FFFFFFFF.

s2l-destination leaf

Specifies the IP address of a leaf node.

The value is in dotted decimal notation.

fast-reroute

Indicates the FRR function.

-

local-protection-available

Indicates that the local protection function of FRR is available.

-

local-protection-inuse

Indicates that FRR local protection is in use.

-

Views

All views

Default Level

1: Monitoring level

Task Name and Operations

Task Name Operations
mpls-te read

Usage Guidelines

Usage Scenario

After a P2MP RSVP-TE tunnel is established, the display mpls te p2mp tunnel path can be run to display path attributes of a specific or all P2MP TE LSPs.

  • If a P2MP TE tunnel is established over an explicit path, information about the path of the established P2MP RSVP-TE tunnel is displayed.
  • If a P2MP TE tunnel is established by calculating the shortest path, information about the actual path of the P2MP RSVP-TE tunnel is displayed. Constraint shortest path first (CSPF) is used to calculate the shortest path that originates from the ingress and is destined for a leaf node.

Prerequisites

The mpls te record-route command must be configured before the path attributes are recorded and displayed.

Example

The actual command output varies according to the device. The command output here is only an example.

# Display information about all P2MP paths.
<HUAWEI> display mpls te p2mp tunnel path
Tunnel Interface Name : Tunnel1
 Lsp ID : 1.1.1.1 :100 : 0x1010101 :5
 S2L Dest Addr: 10.4.4.4
 Sub-Group Originator ID:1.1.1.1    Sub-Group ID:1
 Hop Information
  Hop 0   10.1.1.1
  Hop 1   10.1.1.2 Label 32768
  Hop 2   2.2.2.2 Label 32768
  Hop 3   10.2.1.1 Local-Protection available
  Hop 4   10.2.1.2 Label 32768
  Hop 5   10.4.4.4 Label 32768
  
 Tunnel Interface Name : Tunnel1
 Lsp ID : 1.1.1.1 :100 : 0x1010101 :5
 S2L Dest Addr: 10.5.5.5
 Sub-Group Originator ID:1.1.1.1    Sub-Group ID:2
 Hop Information
  Hop 0   10.1.1.1
  Hop 1   10.1.1.2 Label 32768
  Hop 2   2.2.2.2 Label 32768
  Hop 3   10.4.1.1
  Hop 4   10.4.1.2 Label 32768
  Hop 5   10.5.5.5 Label 32768
Table 1 Description of the display mpls te p2mp tunnel path command output
Item Description
Tunnel Interface Name

Name of a tunnel interface.

Lsp ID

LSP ID configured on the ingress of a tunnel.

S2L Dest Addr

Destination address of a leaf node.

Sub-Group Originator ID

Original ID of a sub-group.

Sub-Group ID

ID of a group.

Hop Information

Hop information, including the sequence number and destination address of each hop:

Hop 2 10.1.1.2 Label 35: detailed information about each hop and the corresponding label value.

  • Information about each hop is displayed only after the mpls te record-route command is run.
  • If the mpls te record-route command is not configured, "Path Information not available" is displayed.
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >