283
# Configure the P device.
[P] mpls lsr-id 2.2.2.9
[P] mpls
[P-mpls] lsp-trigger all
[P-mpls] quit
[P] mpls ldp
[P-mpls-ldp] quit
[P] interface pos 2/1/1
[P-POS2/1/1] mpls
[P-POS2/1/1] mpls ldp
[P-POS2/1/1] quit
[P] interface pos 2/1/2
[P-POS2/1/2] mpls
[P-POS2/1/2] mpls ldp
[P-POS2/1/2] quit
# Configure PE 2.
[PE2] mpls lsr-id 3.3.3.9
[PE2] mpls
[PE2-mpls] lsp-trigger all
[PE2-mpls] quit
[PE2] mpls ldp
[PE2-mpls-ldp] quit
[PE2] interface pos 2/1/1
[PE2-POS2/1/1] mpls
[PE2-POS2/1/1] mpls ldp
[PE2-POS2/1/1] quit
After you complete the configurations, LDP sessions are established between PE 1, P, and PE 2.
Issue the
display mpls ldp session
command. The output shows that the session status is
Operational. Issue the
display mpls ldp lsp
command. The output shows that the LSPs established
by LDP. The following takes PE 1 as an example:
[PE1] display mpls ldp session
LDP Session(s) in Public Network
----------------------------------------------------------------
Peer-ID Status LAM SsnRole FT MD5 KA-Sent/Rcv
---------------------------------------------------------------
2.2.2.9:0 Operational DU Passive Off Off 5/5
---------------------------------------------------------------
LAM : Label Advertisement Mode FT : Fault Tolerance
[PE1] display mpls ldp lsp
LDP LSP Information
------------------------------------------------------------------
SN DestAddress/Mask In/OutLabel Next-Hop In/Out-Interface
------------------------------------------------------------------
1 1.1.1.9/32 3/NULL 127.0.0.1 -------/InLoop0
2 2.2.2.9/32 NULL/3 172.1.1.2 -------/POS2/1/1
3 3.3.3.9/32 NULL/1024 172.1.1.2 -------/POS2/1/1
------------------------------------------------------------------
A '*' before an LSP means the LSP is not established