Dears,
I am simulating the attached topology in eNSP. The strange behaviour is that I only see MPLS labels for the router's loopbacks addresses, and not for the ethernet interfaces.
Taking R1 as an example, the output confirms the above:
<R1>display mpls lsp
-------------------------------------------------------------------------------
LSP Information: LDP LSP
-------------------------------------------------------------------------------
FEC In/Out Label In/Out IF Vrf Name
1.1.1.1/32 3/NULL -/-
5.5.5.5/32 NULL/1025 -/GE0/0/0
5.5.5.5/32 1024/1025 -/GE0/0/0
3.3.3.3/32 NULL/1026 -/GE0/0/0
3.3.3.3/32 1025/1026 -/GE0/0/0
2.2.2.2/32 NULL/3 -/GE0/0/0
2.2.2.2/32 1026/3 -/GE0/0/0
4.4.4.4/32 NULL/1027 -/GE0/0/0
4.4.4.4/32 1027/1027 -/GE0/0/0
6.6.6.6/32 NULL/1028 -/GE0/0/0
6.6.6.6/32 1028/1028 -/GE0/0/0
<R1>display mpls lsp include 192.168.1.0 24 verbose
<R1>
I have captured packets while pinging some loopback addresses and I can see MPLS label on the packet header. But when I ping PC 192.168.1.1 or any router ethernet interface (for instance, 172.16.1.10) there is no MPLS label at all, it is not label forwarding but IP forwarding.
Then, where is the advantage of MPLS label related to forwarding efficiency if there is only label switching for loopbacks addresses? How can this be solved?
Thank you in advance,
Julián
