- Table of Contents
-
- 09-MPLS Command Reference
- 00-Preface
- 01-Basic MPLS commands
- 02-Static LSP commands
- 03-LDP commands
- 04-MPLS TE commands
- 05-Static CRLSP commands
- 06-RSVP commands
- 07-Tunnel policy commands
- 08-MPLS L3VPN commands
- 09-MPLS L2VPN commands
- 10-VPLS commands
- 11-L2VPN access to L3VPN or IP backbone commands
- 12-MPLS OAM commands
- 13-MCE commands
- Related Documents
-
Title | Size | Download |
---|---|---|
01-Basic MPLS commands | 112.85 KB |
Basic MPLS commands
display mpls forwarding ilm
Use display mpls forwarding ilm to display Incoming Label Map (ILM) entries.
In standalone mode:
display mpls forwarding ilm [ label ] [ slot slot-number ]
In IRF mode:
display mpls forwarding ilm [ label ] [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
label: Displays the ILM entry with the specified incoming label. The value range for this argument is 16 to 1048575. If you do not specify an incoming label, this command displays ILM entry information for all incoming labels.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays ILM entries on the active MPU. (In standalone mode.)
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 ILM entries for the global active MPU. (In IRF mode.)
Usage guidelines
An ILM entry records the label operation type, outgoing label, and other forwarding information.
After an LSR receives a labeled packet, it performs the following operations:
1. Identifies the ILM entry that matches the top label of the packet.
2. Performs the specified label operation.
3. Forwards the packet.
Examples
# Display all ILM entries.
<Sysname> display mpls forwarding ilm
Total ILM entries: 3
Flags: T - Forwarded through a tunnel
N - Forwarded through the outgoing interface to the nexthop IP address
B - Backup forwarding information
A - Active forwarding information
M – P2MP forwarding information
InLabel Oper VRF Flag SwapLabel Forwarding Info
--------------------------------------------------------------------------------
30 SWAP 0 T 1000 1024
1279 POP 0 - - -
1407 SWAP 0 NA 1271 GE3/1/3 50.2.0.2
NB 1270 Tun0 0.0.0.0
Table 1 Command output
Field |
Description |
Total ILM entries |
Total number of ILM entries. |
InLabel |
Incoming label. |
Oper |
Operation type: · POP—Pops the label. · POPGO—Pops the label and forwards the packet to another tunnel. · SWAP—Swaps the label. |
VRF |
Index of a VPN instance. |
Flag |
Forwarding flag: · T—Forwarded through a tunnel. · N—Forwarded through the outgoing interface to the next hop IP address. · B—Backup forwarding information. · A—Active forwarding information. · M—P2MP forwarding information. |
SwapLabel |
Outgoing label value. |
Forwarding Info |
Forwarding information: · When the forwarding flag is N, the forwarding information records the outgoing interface and the next hop. · When the forwarding flag is T, the forwarding information records the NID. |
display mpls forwarding nhlfe
Use display mpls forwarding nhlfe to display Next Hop Label Forwarding Entry (NHLFE) entries.
Syntax
In standalone mode:
display mpls forwarding nhlfe [ nid ] [ slot slot-number ]
In IRF mode:
display mpls forwarding nhlfe [ nid ] [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
nid: Displays the NHLFE entry with the specified NID. The NID value range is 0 to 4294967294. If you do not specify an NID, this command displays NHLFE entry information for all NIDs.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays NHLFE entries on the active MPU. (In standalone mode.)
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 NHLFE entries for the global active MPU. (In IRF mode.)
Usage guidelines
An NHLFE entry records label forwarding information, such as the outgoing label and outgoing interface. NHLFE entries are mainly used to add multiple labels to packets.
To add multiple labels to a packet, an LSR performs the following operations:
1. Obtains the bottom label and NID in the matching FIB or ILM entry.
2. Obtains the outer label in the NHLFE entry identified by the NID.
Examples
# Display the NHLFE entry with NID 2048.
<Sysname> display mpls forwarding nhlfe 2048
Flags: T - Forwarded through a tunnel
N - Forwarded through the outgoing interface to the nexthop IP address
B - Backup forwarding information
A - Active forwarding information
M – P2MP forwarding information
NID Tnl-Type Flag OutLabel Forwarding Info
--------------------------------------------------------------------------------
2048 LSP NA 2025 GE3/1/2 10.11.112.26
# Display all NHLFE entries.
<Sysname> display mpls forwarding nhlfe
Total NHLFE entries: 5
Flags: T - Forwarded through a tunnel
N - Forwarded through the outgoing interface to the nexthop IP address
B - Backup forwarding information
A - Active forwarding information
M – P2MP forwarding information
NID Tnl-Type Flag OutLabel Forwarding Info
--------------------------------------------------------------------------------
10 - TA - 2049
20 - TA - 2050
2048 LSP NA 2025 GE3/1/2 10.11.112.26
2049 LSP NA 3024 GE3/1/2 10.11.112.26
TB 3026 20
2050 LSP NA 3025 GE3/1/1 10.11.113.26
Table 2 Command output
Field |
Description |
Total NHLFE entries |
Total number of NHLFE entries. |
NID |
NHLFE entry index. |
Tnl-Type |
Tunnel type: · LOCAL—Direct LSP tunnel. · LSP—Static LSP tunnel, or LSP tunnel signaled using LDP or BGP. · TE—TE tunnel. · GRE—GRE tunnel. · CRLSP—Static CRLSP tunnel or CRLSP tunnel signaled using RSVP. · SRLSP—Static SRLSP tunnel or SRLSP tunnel signaled using IS-IS or OSPF. If the tunnel type is invalid, this field display a hyphen (-). |
Flag |
Forwarding flag: · T—Forwarded through a tunnel. · N—Forwarded through the outgoing interface to the next hop IP address. · B—Backup forwarding information. · A—Active forwarding information. · M—P2MP forwarding information. |
OutLabel |
Outgoing label. |
Forwarding Info |
Forwarding information: · When the forwarding flag is N, the forwarding information records the outgoing interface and the next hop. · When the forwarding flag is T, the forwarding information records the NID. |
display mpls interface
Use display mpls interface to display MPLS interface information, including the interface name, interface status, and interface MPLS MTU.
Syntax
display mpls interface [ interface-type interface-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
interface-type interface-number: Specifies an interface by the interface type and number. If you do not specify an interface, this command displays MPLS information for all MPLS-enabled interfaces.
Examples
# Display all MPLS interfaces.
<Sysname> display mpls interface
Interface Status MPLS MTU
GE3/1/1 Up -
GE3/1/2 Up -
Table 3 Command output
Field |
Description |
Interface |
Interface name. |
Status |
Interface state. |
MPLS MTU |
This field is not supported and displays a hyphen (-) in the current software version. |
Related commands
mpls enable
display mpls label
Use display mpls label to display MPLS label usage information.
Syntax
display mpls label { label-value1 [ to label-value2 ] | all }
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
label-value1: Specifies a label value in the range of 16 to 1048575. If used with the label-value2 argument, the label-value1 argument represents the start label of a label range.
to label-value2: Specifies the end label of the label range, in the range of 16 to 1048575. If you specify a label range by using the label-value1 argument and the to label-value2 option, this command displays usage information for the specified range of labels.
all: Specifies all labels.
Examples
# Display usage information for labels 1025 through 1027.
<Sysname> display mpls label 1025 to 1027
Label Owner State
1025 LDP Alloc
1026 LDP Alloc
1027 LDP Inuse
Table 4 Command output
Field |
Description |
Label |
Label value. |
Owner |
Protocol that is using the label: · Static—Static LSP. · LDP. · BGP. · StaticCR—Static CRLSP or static SRLSP. · RSVP. · L2VPN. · ISIS. · OSPF. This field displays a hyphen (-) when the label state is Idle. |
State |
Usage state of the label: · Idle—The label is idle. · Alloc—The label has been allocated. · Pending—The label has been released but is still used by an LSP entry. · Inuse—The label has been allocated and used by an LSP entry. |
display mpls lsp
Use display mpls lsp to display LSP information.
Syntax
display mpls lsp [ egress | in-label label-value | ingress | outgoing-interface interface-type interface-number | protocol { bgp | isis | ldp | local | ospf | pce-sr | rsvp-te [ p2mp ] | static | static-cr } | transit ] [ vpn-instance vpn-instance-name ] [ ipv4-address mask-length | ipv6 [ ipv6-address prefix-length ] ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
egress: Displays the LSPs taking the current LSR as egress.
in-label label-value: Displays the LSPs using the specified label as the incoming label. The value range for the label-value argument is 0 to 1048575.
ingress: Displays the LSPs taking the current LSR as ingress.
outgoing-interface interface-type interface-number: Displays the LSPs using the specified interface as the outgoing interface. The interface-type interface-number argument specifies an interface by its type and number.
protocol: Displays the LSPs established by a protocol.
bgp: Displays BGP LSPs.
isis: Displays IS-IS SRLSPs.
ldp: Displays LDP LSPs.
local: Displays LSPs destined for the direct next hops, or displays LSPs that use the local MPLS TE tunnel interfaces or tunnel bundle interfaces as the LSP heads.
ospf: Displays OSPF SRLSPs.
pce-sr: Displays dynamic SRLSPs established by SR and stateful PCE. For more information about stateful PCE, see MPLS TE configuration in MPLS Configuration Guide.
rsvp-te: Displays CRLSPs established by RSVP-TE.
p2mp: Displays P2MP CRLSPs established by RSVP-TE. If you do not specify this keyword, the command displays information about P2P CRLSPs and P2MP CRLSPs established by RSVP-TE.
static: Displays static LSPs.
static-cr: Displays static CRLSPs and static SRLSPs.
transit: Displays the LSPs taking the current LSR as a transit LSR.
vpn-instance vpn-instance-name: Displays LSPs for the specified MPLS L3VPN instance. The vpn-instance-name is a case-sensitive string of 1 to 31 characters. If you do not specify this option, the command displays LSPs for the public network.
ipv4-address mask-length: Displays the IPv4 LSP for an FEC specified by an IPv4 address and a mask length. The value range for the mask length is 0 to 32.
ipv6: Displays IPv6 LSP information. If you do not specify this keyword, the command displays IPv4 LSP information.
ipv6-address prefix-length: Displays the IPv6 LSP for an FEC specified by an IPv6 address and a prefix length. The value range for the prefix length is 0 to 128.
verbose: Displays detailed LSP information. If you do not specify this keyword, the command displays brief LSP information.
Usage guidelines
If you do not specify any parameters, this command displays brief information about all LSPs. If you specify only the verbose keyword, this command displays detailed information about all LSPs.
Examples
# Display brief information about all IPv4 LSPs.
<Sysname> display mpls lsp
FEC Proto In/Out Label Out Inter/NHLFE/LSINDEX
100.100.100.100/24 LDP -/1049 GE3/1/1
Backup -/1050 GE3/1/2
100.100.100.10/24 LDP -/1051 GE3/1/3
Backup -/1050 GE3/1/2
100.100.100.10/24 LDP -/1049 GE3/1/4
101.100.100.10/24 LDP 1026/1049 GE3/1/1
102.100.100.10/24 LDP 1027/- -
103.100.100.10/24 LDP 1028/1049 Tun10
110.100.100.20/24 BGP -/1049 GE3/1/1
111.100.100.10/24 BGP 2028/1049 GE3/1/1
112.100.100.10/24 BGP 2029/- GE3/1/1
113.100.100.10/24 BGP 2030/1049 NHLFE1500
114.100.100.10/24 BGP 2031/1050 Tun100
100.100.100.100 Local -/- GE3/1/1
101.101.101.101/32 Static -/100 GE3/1/1
- Static 100/200 GE3/1/1
- Static 101/- GE3/1/1
200.200.200.200/64000/64000 RSVP -/1030 GE3/1/5
201.200.200.200/64000/64000 RSVP 1024/1031 GE3/1/5
202.200.200.200/64000/64000 RSVP 1025/- -
150.140.150.100/64001/0 StaticCR -/1000 GE3/1/5
- StaticCR 50/1001 GE3/1/5
- StaticCR 51/- -
110.100.100.20/32 ISIS -/16000 GE3/1/5
Backup -/17000 LSINDEX100
20.0.0.20/32/100 ISIS -/17000 GE3/1/1
100.100.100.100/16000 BGP 16000/- GE3/1/1
Table 5 Command output
Field |
Description |
FEC |
Forwarding equivalence class: · IP address/mask—Classifies FECs by destination address. · IP address/mask/LSINDEX—Classifies FECs by label stack index. · IP address/In Label—The LSP is created through BGP Peer-Set-SID. · IP address—Classifies FECs by next hop. · IP address/Out Label—Classifies FECs by next hop and outgoing label. · Ingress LSR ID/Tunnel ID/LSP ID—RSVP TE FEC. · - (a hyphen)—The LSP is a static transit LSP, static egress LSP, static transit CRLSP, static egress CRLSP, or adjacency path for static SRLSPs. · Backup—The LSP is a backup LSP of the previous LSP. |
Proto |
Label distribution protocol: · LDP. · BGP. · IS-IS. · RSVP. · Static. · StaticCR—Static CRLSP or static SRLSP. · OSPF. · PCE-SR—Dynamic SRLSP established by SR and stateful PCE. · Local—LSP to a direct next hop, or LSP that uses a local MPLS TE tunnel interface or tunnel bundle interface as the LSP head. |
In/Out Label |
Incoming label/outgoing label. |
Out Inter/NHLFE/LSINDEX |
Outgoing interface name, NHLFE entry index, or label stack index of the LSP. NHLFEnumber specifies the ingress LSP selected for the current LSP after route recursion. The ingress LSP is the one that matches the NHLFE entry with an NID of number. LSINDEXnumber specifies the ingress LSP selected for the current LSP after route recursion. The ingress LSP is the one that matches the LSINDEX entry with a label stack index of number. |
# Display IPv6 LSP information.
<Sysname> display mpls lsp ipv6
FEC : 100:100:100:100:100:100:100:100/128
Protocol : BGP In-Label : 1200
Out-Label: 1300 Out-Interface: GE3/1/1
BkLabel : 1400 BkInterface : GE3/1/2
Table 6 Command output
Field |
Description |
FEC |
Forwarding equivalence class: · IP address/mask—Classifies FECs by destination address. · IP address—Classifies FECs by next hop. · IP address/Out Label—Classifies FECs by next hop and outgoing label. · Ingress LSR ID/Tunnel ID/LSP ID—RSVP TE FEC. · - (a hyphen)—The LSP is a static transit LSP, static egress LSP, static transit CRLSP, or static egress CRLSP. |
Protocol |
Label distribution protocol: · LDP. · BGP. · RSVP. · Static. · StaticCR—Static CRLSP or static SRLSP. · Local—LSP to a direct next hop, or LSP that uses a local MPLS TE tunnel interface or tunnel bundle interface as the LSP head. |
BkLabel |
Outgoing label of the backup LSP. |
BkInterface |
Outgoing interface of the backup LSP. |
# Display detailed information about all LSPs.
<Sysname> display mpls lsp verbose
Destination : 56.10.10.2
FEC : 56.10.10.2/32
Protocol : LDP
LSR Type : Egress
Service : Statistics
In-Label : 1024
State : Active
Destination : 56.10.10.4
FEC : 56.10.10.2/32
Protocol : LDP
LSR Type : Transit
Service : Statistics
In-Label : 1026
Path ID : 0x40000000.1
State : Active
Out-Label : 1800
Nexthop : 10.1.1.2
Out-Interface: GE3/1/1
BkLabel : 1900
BkNexthop : 20.1.1.2
BkInterface : GE3/1/2
Destination : 56.10.10.4
FEC : 56.10.10.2/32
Protocol : LDP
LSR Type : Ingress
Service : -
NHLFE ID : 2000
State : Active
Out-Label : 1800
Nexthop : 10.1.1.2
Out-Interface: GE3/1/1
Destination : 110.100.100.20
FEC : 110.100.100.20/32
Protocol : ISIS
LSR Type : Ingress
Service :
State : Active
Out-Label : 16000
Nexthop : 10.1.1.2
Out-Interface: GE3/1/5
BkLabel : 17000
BkLsIndex : 100
Destination : 20.0.0.20
FEC : 20.0.0.20/32/100
Protocol : ISIS
LSR Type : Ingress
Service :
Out-Label : 17000,2175,16001
Nexthop : 10.1.1.2
Out-Interface: GE3/1/1
LsIndex : 100
Destination : -
FEC : -
Protocol : BGP
LSR Type : Transit
Service : -
In-Label : 16000
Path ID : 0x40000000.1
State : Active
Out-Label : -
OriginNexthop: 100.100.100.100
Nexthop : 10.1.1.2
Out-Interface: GE3/1/1
Path ID : 0x40000000.2
State : Active
Out-Label : -
OriginNexthop: 101.101.101.101
Nexthop : 11.1.1.2
Out-Interface: GE3/1/2
Path ID : 0x40000000.3
State : Active
Out-Label : -
OriginNexthop: 102.102.102.102
Nexthop : 12.1.1.2
Out-Interface: GE3/1/3
Table 7 Command output
Field |
Description |
Destination |
LSP destination address. |
FEC |
Forwarding equivalence class: · IP address/mask—Classifies FECs by destination address. · IP address—Classifies FECs by next hop. · IP address/Out Label—Classifies FECs by next hop and outgoing label. · Ingress LSR ID/Tunnel ID/LSP ID—RSVP TE or static SRLSP FEC. · - (a hyphen)—The LSP is a static transit LSP, static egress LSP, static transit CRLSP, static egress CRLSP, or adjacency path for static SRLSPs. |
Protocol |
Label distribution protocol: · LDP. · BGP (instance-name)—The instance-name specifies a BGP instance name. The value of default represents the default BGP instance. · IS-IS. · RSVP. · Static. · StaticCR—Static CRLSP or static SRLSP. · Local—LSP to a direct next hop, or LSP that uses a local MPLS TE tunnel interface or tunnel bundle interface as the LSP head. · OSPF. · PCE-SR—Dynamic SRLSP established by SR and stateful PCE. |
LSR Type |
LSR type: · Ingress—The current LSR is the ingress node of the LSP. · Transit—The current LSR is a transit node of the LSP. · Egress—The current LSR is the egress node of the LSP. |
Service |
Service deployed on the LSP. The service can only be Statistics, which indicates the MPLS forwarding statistics feature. |
Path ID |
Forwarding path. The value is in the format of 0xnn.m. The nn represents the NHLFE group ID of the outer LSPs that carry the current LSP, and m represents the sequence number of the equivalence path. |
NHLFE ID |
NHLFE entry index. |
State |
LSP state: · Active—The LSP is in use. · Inactive—The LSP is idle. |
LsIndex |
Label stack index of the LSP. |
BkLabel |
Outgoing label of the backup LSP. |
BkNexthop |
Next hop address of the backup LSP. |
BkInterface |
Outgoing interface of the backup LSP. |
BkLsIndex |
Label stack index of the backup LSP. |
Related commands
display mpls lsp statistics
display mpls lsp statistics
Use display mpls lsp statistics to display LSP statistics.
Syntax
display mpls lsp statistics [ ipv6 ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipv6: Displays IPv6 LSP statistics. If you do not specify this keyword, the command displays IPv4 LSP statistics.
Examples
# Display IPv4 LSP statistics.
<Sysname> display mpls lsp statistics
LSP Type Ingress/Transit/Egress Active
Static LSP 0/0/0 0/0/0
Static CRLSP 0/0/0 0/0/0
LDP LSP 2/2/1 2/2/1
RSVP CRLSP 0/0/0 0/0/0
BGP LSP 0/0/0 0/0/0
Local LSP 2/0/0 2/0/0
ISIS LSP 0/0/0 0/0/0
OSPF LSP 3/3/1 3/3/1
SR LSP 1/0/0 1/0/0
-----------------------------------------------------
Total 4/2/1 4/2/1
# Display IPv6 LSP statistics.
<Sysname> display mpls lsp statistics ipv6
LSP Type Ingress/Transit/Egress Active
Static LSP 0/0/0 0/0/0
Static CRLSP 0/0/0 0/0/0
LDP LSP 6/6/2 6/6/2
RSVP CRLSP 0/0/0 0/0/0
BGP LSP 0/0/0 0/0/0
Local LSP 2/0/0 2/0/0
ISIS LSP 0/0/0 0/0/0
-----------------------------------------------------
Total 8/6/2 8/6/2
Table 8 Command output
Field |
Description |
LSP Type |
LSP types: · Static LSP. · Static CRLSP—Static CRLSP or static SRLSP. · LDP LSP. · Local LSP—LSP to a direct next hop, or LSP that uses a local MPLS TE tunnel interface or tunnel bundle interface as the LSP head. · RSVP CRLSP. · BGP LSP. · IS-IS. · OSPF. · SR LSP—Dynamic SRLSP established by SR and stateful PCE. |
Total |
Total number of LSPs. |
Ingress |
Number of LSPs that take the local device as the ingress node. |
Transit |
Number of LSPs that take the local device as a transit node. |
Egress |
Number of LSPs that take the local device as the egress node. |
Active |
Number of active LSPs of a type. |
display mpls nib
Use display mpls nib to display MPLS Nexthop Information Base (NIB) information.
Syntax
display mpls nib [ nib-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
nib-id: Specifies a next hop ID in the range of 1 to FFFFFFFFFFFFFFFE. If you do not specify a next hop, this command displays information about all MPLS next hops.
Examples
# Display information about all MPLS next hops.
<Sysname> display mpls nib
NIB ID: 0x40000000
Users: 1
Status: Active
ECMP number: 1
Outgoing NHLFE ID: 1024
Backup outgoing NHLFE ID: 1027
Table 9 Command output
Field |
Description |
NIB ID |
ID of the next hop. |
Users |
Number of ILM entries that use this next hop. |
Status |
Next hop status: · Active—The next hop is active. · Dummy—The next hop is inactive. |
ECMP number |
Number of equal-cost NHLFE entries. |
Outgoing NHLFE ID |
ID of the NHLFE entry to which the next hop corresponds. |
Backup outgoing NHLFE ID |
ID of the backup NHLFE entry. |
display mpls nid
Use display mpls nid to display usage information for NIDs.
Syntax
display mpls nid [ nid-value1 [ to nid-value2 ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
nid-value1: Specifies an NID in the range of 0 to 65536. If used with the nid-value2 argument, the nid-value1 argument represents the start NID of an NID range.
to nid-value2: Specifies the end NID of the NID range, in the range of 0 to 65536. If you specify an NID range by using the nid-value1 argument and the to nid-value2 option, this command displays usage information for the specified range of NIDs.
Usage guidelines
NIDs are 32-bit binary numbers. They include fixed NIDs and dynamic NIDs.
· Fixed NIDs—Generated for tunnel interfaces or tunnel bundle interfaces. The highest four bits are a value other than 0000.
· Dynamic NIDs—NIDs except fixed NIDs. The highest four bits are 0s.
This command displays usage information only for dynamic NIDs.
If you do not specify any parameters, this command displays usage information for all dynamic NIDs.
Examples
# Display usage information for dynamic NIDs 1028 through 1500.
<Sysname> display mpls nid 1028 to 1500
NID alloc state: '.' means not used, '$' means used
1028 :...$.... ........ ........ ........ ........ ........ ........ ........
1092 :........ ........ ........ ........ ........ ........ ........ ........
1156 :........ ........ ........ ........ ........ ........ ........ ........
1220 :........ ........ ........ ........ ........ ........ ........ ........
1284 :........ ........ ........ ........ ........ ........ ........ ........
1348 :........ ........ ........ ........ ........ ........ ........ ........
1412 :........ ........ ........ ........ ........ ........ ........ ........
1476 :........ ........ ........ .
display mpls summary
Use display mpls summary to display MPLS summary information.
Syntax
display mpls summary
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display MPLS summary information.
<Sysname> display mpls summary
MPLS LSR ID : 1.1.1.1
Egress Label Type: Implicit-null
Labels:
Range Idle
16-1023 1004
1024-1009152 957986
16000-24000(reusable) 8001
Protocols:
Type State
LDP Normal
RSVP Normal
BGP(default) Normal
Static Normal
StaticCR Normal
Local Normal
BGP(xy) Normal
BGP(abc) Normal
Table 10 Command output
Field |
Description |
Egress Label Type |
Label type that the egress node assigns to the penultimate hop: · Implicit-null. · Explicit-null. · Non-null. |
Labels |
Label information. |
Range |
Label range. If labels within the label range can be reused, this field displays (reusable) behind the label range. |
Idle |
Number of idle labels in the label range. |
Protocols |
Label distribution protocols that generated LSPs and their running states. |
Type |
Protocol type: · LDP. · BGP (instance-name). The instance-name specifies a BGP instance name. The value of default represents the default BGP instance. · RSVP. · Static—Static LSP. · StaticCR—Static CRLSP. · TE. · ISIS. · OSPF. |
State |
Label distribution protocol running state: · Normal—The protocol is in normal state. · Recover—The protocol is in the GR process. |
mpls bandwidth-based-sharing
Use mpls bandwidth-based-sharing to enable bandwidth-based load sharing on an MPLS transit node.
Use undo mpls bandwidth-based-sharing to disable bandwidth-based load sharing on an MPLS transit node.
Syntax
mpls bandwidth-based-sharing
undo mpls bandwidth-based-sharing
Default
Bandwidth-based load sharing is disabled on an MPLS transit node.
Views
System view
Predefined user roles
network-admin
Usage guidelines
If equal-cost LDP LSPs exist on a transit node, the node evenly transmits MPLS packets through the LSPs. After you enable this feature, MPLS packets are transmitted through the LSPs in the proportion calculated based on the bandwidth of the egress interfaces.
Examples
# Enable bandwidth-based load sharing on an MPLS transit node.
<Sysname> system-view
[Sysname] mpls bandwidth-based-sharing
mpls enable
Use mpls enable to enable MPLS on an interface.
Use undo mpls enable to disable MPLS on an interface.
Syntax
mpls enable
undo mpls enable
Default
MPLS is disabled on an interface.
Views
Interface view
Predefined user roles
network-admin
Examples
# Enable MPLS on GigabitEthernet 3/1/1.
<Sysname> System-view
[Sysname] interface gigabitethernet 3/1/1
[Sysname-GigabitEthernet3/1/1] mpls enable
Related commands
display mpls interface
mpls label advertise
Use mpls label advertise to specify the type of label the egress node will advertise to the penultimate hop.
Use undo mpls label advertise to restore the default.
Syntax
mpls label advertise { explicit-null | implicit-null | non-null }
undo mpls label advertise
Default
As egress, the device advertises an implicit null label to the penultimate hop.
Views
System view
Predefined user roles
network-admin
Parameters
explicit-null: Specifies the egress node to advertise an explicit null label of 0 to the penultimate hop.
implicit-null: Specifies the egress node to advertise an implicit null label of 3 to the penultimate hop.
non-null: Specifies the egress node to advertise a non-null label to the penultimate hop.
Usage guidelines
As a best practice, configure the egress node to advertise an implicit null label to the penultimate hop if the penultimate hop supports PHP.
If you want to simplify packet forwarding on egress but keep labels to determine QoS policies, configure the egress node to advertise an explicit null label to the penultimate hop.
Use non-null labels only in particular scenarios. For example, when OAM is configured on the egress node, the egress node can get the OAM function entity status only through non-null labels.
As a penultimate hop, the device accepts the implicit null label, explicit null label, or non-null label advertised by the egress node.
For LDP LSPs, the mpls label advertise command triggers LDP to delete the LSPs established before the command is executed and re-establishes new LSPs.
For BGP LSPs, the mpls label advertise command takes effect only on the BGP LSPs established after the command is executed. To apply the new setting to BGP LSPs established before the command is executed, delete the routes corresponding to the BGP LSPs, and then redistribute the routes.
Examples
# Configure the egress node to advertise an implicit null label to the penultimate hop.
<Sysname> system-view
[Sysname] mpls label advertise implicit-null
Related commands
reset mpls ldp
mpls label range
Use mpls label range to set the value range for dynamic labels that the device can allocate.
Use undo mpls label range to restore the default.
Syntax
mpls label range minimum maximum
undo mpls label range
Default
The value range for dynamic labels that the device can allocate is not set.
Views
System view
Predefined user roles
network-admin
Parameters
minimum: Specifies the minimum label value that the device can allocate, in the range of 1024 to 1048575.
maximum: Specifies the maximum label value that the device can allocate, in the range of 1024 to 1048575.
Usage guidelines
This command sets the value range in which label distribution protocols can dynamically allocate labels.
This command does not take effect on static LSP labels, static CRLSP labels, static SRLSP labels, static PW labels, or SRGBs. For more information about static LSP labels, see "Configuring a static LSP." For more information about static CRLSP labels, see "Configuring a static CRLSP." For more information about static PW labels, see "Configuring VPLS" and "Configuring MPLS L2VPN." For more information about static SRLSPs and SRGBs, see MPLS SR configuration in Segment Routing Configuration Guide.
If you configure this command multiple times, the most recent configuration takes effect.
The following restrictions and guidelines apply if you configure both the mpls label range and mpls max-label commands:
· The minimum label value set by the mpls label range command must be smaller than the maximum label value set by the mpls max-label command.
· The maximum label value that can be allocated by the device is the smaller one of the maximum label values set by the two commands.
Examples
# Set the value range to 10000 to 15000 for dynamic labels that the device can allocate.
<Sysname> system-view
[Sysname] mpls label range 10000 15000
Related commands
mpls max-label
mpls load-sharing mode
Use mpls load-sharing mode to enable per-flow load sharing based on flow labels.
Use undo mpls load-sharing mode to restore the default.
Syntax
mpls load-sharing mode per-flow flow-label
undo mpls load-sharing mode
Default
MPLS performs per-flow load sharing based on the outmost two MPLS labels. If only one label exists, MPLS performs per-flow load sharing based on one MPLS label.
Views
System view
Predefined user roles
network-admin
Parameters
per-flow: Performs per-flow load sharing.
flow-label: Performs per-flow load sharing based on flow labels. MPLS performs per-flow load sharing based on the outmost two MPLS labels and the flow label. If only one MPLS label exists, MPLS performs per-flow load sharing based on the MPLS label and the flow label.
Usage guidelines
For MPLS to perform per-flow load sharing based on flow labels, you also need to configure the flow-label command on the PE to enable the PE to add different flow labels for packets of different traffic types.
Examples
# Enable per-flow load sharing based on flow labels.
<Sysname> system-view
[Sysname] mpls load-sharing mode per-flow flow-label
Related commands
flow-label (MPLS L2VPN commands)
flow-label (VPLS commands)
mpls lsr-id
Use mpls lsr-id to configure an LSR ID for the local LSR.
Use undo mpls lsr-id to restore the default.
Syntax
mpls lsr-id lsr-id
undo mpls lsr-id
Default
An LSR has no LSR ID.
Views
System view
Predefined user roles
network-admin
Parameters
lsr-id: Specifies an ID for identifying the LSR, in dotted decimal notation.
Usage guidelines
As a best practice, use the address of a loopback interface on the LSR as the LSR ID.
If no LDP LSR ID is configured for the public network or a VPN instance, LDP uses the MPLS LSR ID configured by the mpls lsr-id command. If you modify the MPLS LSR ID, the LDP sessions in the public network or VPN instance will be re-established. To configure an LDP LSR ID for the public network or a VPN instance, use the lsr-id command in LDP view or LDP-VPN instance view.
Examples
# Configure the LSR ID as 3.3.3.3 for the local node.
<Sysname> system-view
[Sysname] mpls lsr-id 3.3.3.3
# Change the LSR ID to 4.4.4.4.
[Sysname] mpls lsr-id 4.4.4.4
All LDP sessions using the MPLS LSR ID will be reset. Continue? [Y/N]:Y
Related commands
lsr-id
mpls max-label
Use mpls max-label to set the maximum label value that the device can allocate.
Use undo mpls max-label to restore the default.
Syntax
mpls max-label label-value
undo mpls max-label
Default
The maximum label value allocatable by the device is not set.
Views
System view
Predefined user roles
network-admin
Parameters
label-value: Specifies the maximum label value that the device can allocate, in the range of 16 to 1048575.
Usage guidelines
Configure this command when the interface modules on the device support different label value ranges.
This command sets the maximum label value that label distribution protocols can allocate dynamically. It does not take effect on static LSP labels, static CRLSP labels, static SRLSP labels, static PW labels, or SRGBs. For more information about static LSP labels, see "Configuring a static LSP." For more information about static CRLSP labels, see "Configuring a static CRLSP." For more information about static PW labels, see "Configuring VPLS" and "Configuring MPLS L2VPN." For more information about static SRLSPs and SRGBs, see MPLS SR configuration in Segment Routing Configuration Guide.
The configured maximum label value cannot be larger than any maximum label value supported by the interface modules on the device.
The following restrictions and guidelines apply if you configure both the mpls label range and mpls max-label commands:
· The maximum label value set by the mpls max-label command must be larger than the minimum label value set by the mpls label range command.
· The maximum label value that can be allocated by the device is the smaller one of the maximum label values set by the two commands.
The maximum label value set by this command takes effect on the next device startup. Save the current configuration before you reboot the device.
Examples
# Set the maximum label value that the device can allocate to 6000.
<Sysname> system-view
[Sysname] mpls max-label 6000
This setting takes effect after reboot. Please save the current configuration and reboot the device.
Related commands
display mpls summary
mpls label range
mpls mtu
Use mpls mtu to set the MPLS MTU for an interface.
Use undo mpls mtu to restore the default.
Syntax
mpls mtu size
undo mpls mtu
Default
The MPLS MTU of an interface is not configured. Fragmentation for MPLS packets is based on the MTU set on the interface by the ip mtu command. If no MTU is set by the ip mtu command, the fragmentation is based on the MTU of the interface. The length of a fragment does not include that of the MPLS label. Thus, after an MPLS label is added into a fragment, the length of the MPLS fragment might exceed the interface MTU.
Views
Interface view
Predefined user roles
network-admin
Parameters
size: Specifies the MPLS MTU of the interface, in the range of 1280 to 9600 bytes.
Usage guidelines
This command is effective only when MPLS is enabled on the interface.
If the MPLS MTU is larger than the interface MTU, data forwarding might fail.
MPLS TE tunnel interfaces do not support this command.
If an MPLS packet is received and has its label swapped for forwarding, the packet will not be fragmented unless you execute the mpls l3vpn fragment enable command.
This command is supported only on CSPEX cards (except CSPEX-1204 and CSPEX-1104-E).
Examples
# Set the MPLS MTU of GigabitEthernet3/1/1 to 1280 bytes.
<Sysname> system-view
[Sysname] interface gigabitethernet 3/1/1
[Sysname-GigabitEthernet3/1/1] mpls enable
[Sysname-GigabitEthernet3/1/1] mpls mtu 1280
Related commands
mpls l3vpn fragment enable
mpls statistics interval
Use mpls statistics interval to set the MPLS label forwarding statistics collection interval.
Use undo mpls statistics interval to remove the MPLS label forwarding statistics collection interval configuration.
Syntax
mpls statistics interval interval
undo mpls statistics interval
Default
The MPLS forwarding statistics collection interval is not set.
Views
System view
Predefined user roles
network-admin
Parameters
interval: Specifies the MPLS label forwarding statistics collection interval, in the range of 30 to 65535 seconds.
Usage guidelines
After you enable traffic statistics for an MPLS TE tunnel by using the mpls te statistics command, the MPLS label forwarding statistics feature is automatically enabled for the tunnel. The statistics collection interval is automatically set to 30 seconds. You can modify the interval by using the mpls statistics interval command.
Examples
# Set the MPLS label forwarding statistics collection interval to 30 seconds.
<Sysname> system-view
[Sysname] mpls statistics interval 30
Related commands
mpls te statistics
mpls ttl expiration enable
Use mpls ttl expiration enable to enable sending MPLS TTL-expired messages.
Use undo mpls ttl expiration enable to disable sending MPLS TTL-expired messages.
Syntax
mpls ttl expiration enable
undo mpls ttl expiration enable
Default
The MPLS TTL-expired messages sending feature is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command enables an LSR to generate an ICMP TTL-expired message upon receiving an MPLS packet with TTL being 1.
· If the MPLS packet has only one label, the LSR sends the ICMP TTL-expired message back to the source through IP routing.
· If the MPLS packet has multiple labels, the LSR forwards the ICMP TTL-expired message along the LSP of the MPLS packet to the egress node. Then, the egress node sends the message back to the source.
After you disable sending MPLS TTL-expired messages, an LSR discards MPLS packets with TTL being 1 without generating ICMP TTL-expired messages.
Examples
# Disable sending MPLS TTL-expired messages.
<Sysname> system-view
[Sysname] undo mpls ttl expiration enable
mpls ttl propagate
Use mpls ttl propagate to enable TTL propagation.
Use undo mpls ttl propagate to disable TTL propagation.
Syntax
mpls ttl propagate { public | vpn }
undo mpls ttl propagate { public | vpn }
Default
TTL propagation is enabled for public network packets and is disabled for VPN packets.
Views
System view
Predefined user roles
network-admin
Parameters
public: Specifies public network packets.
vpn: Specifies VPN packets.
Usage guidelines
Refresh routes after you enable or disable TTL propagation.
When TTL propagation is enabled, MPLS performs the following operations:
· Copies the IP TTL to the label TTL for packets entering the MPLS network.
· Copies the label TTL to the IP TTL for packets leaving the MPLS network.
If you enable TTL propagation on both ingress and egress, the IP tracert facility can show the real path in the MPLS network.
When TTL propagation is disabled, MPLS performs the following operations:
· Sets the label TTL to 255 for packets entering the MPLS network.
· Pops the label for packets leaving the MPLS network, without copying the label TTL value to the IP TTL.
The IP tracert facility cannot show the real path in the MPLS network.
Within an MPLS network, TTL is always copied between the labels of an MPLS packet. The mpls ttl propagate command affects only the propagation between IP TTL and label TTL.
As a best practice, set the same TTL processing mode on all LSRs of an LSP.
To enable TTL propagation for a VPN, you must enable it on all PE devices in the VPN. This allows you to obtain the same traceroute result (hop count) from those PEs.
Examples
# Enable TTL propagation for VPN packets.
<Sysname> system-view
[Sysname] mpls ttl propagate vpn
snmp-agent trap enable mpls
Use snmp-agent trap enable mpls to enable SNMP notifications for MPLS.
Use undo snmp-agent trap enable mpls to disable SNMP notifications for MPLS.
Syntax
snmp-agent trap enable mpls
undo snmp-agent trap enable mpls
Default
SNMP notifications for MPLS are disabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
To report critical MPLS events to an NMS, enable SNMP notifications for MPLS. For MPLS event 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 MPLS.
<Sysname> system-view
[Sysname] snmp-agent trap enable mpls