Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
during my studies about LDP as Signaling Protocol i found the below:
set routing-instances MPLS-VPLS-VLAN20 protocols vpls neighbor 192.168.10.32set protocols ldp session 192.168.10.32 authentication-key "abcdef"
The first one should be
"Specify each of the PE routers participating in the VPLS domain. Configuring this statement enables LDP for signaling VPLS."
The second one is for:
"Configure LDP session parameters by specifying the session destination address."
As far as I understood the first one is needed for enabling LDP, so is a must to have command
The second command is only in case we want to use authentication between the LDP peers.
Could you please someone confirm?
More, analising the network, I have only 2 PE devices and MPLS/LDP is active between them.
Is there any way to distinguish, in the configuration, which signaling protocol is used to establish the transport tunnel(outer label)
and which signaling protcol is instead used for the inner label? (In this case the "service" which use the mpls is vpls).
As far as i understood so far, from my studies, the typical situation is
PE1 <-> P <-> PE1
In this case are needed 2 LDP session between
P <-> PE2
for creating the transport protocol
and LDP session (targeted LDP session i guess) beetwen
for exchange the "inner" label.
In my case the topolgy is simple
PE1 <-> PE2 and is confusing me on how can i distinguish the 2 case above mentioned.
To enable LDP, here's very basic command:
set protocols ldp interface <>
set protocols ldp interface lo0.x
I think what you want to ask is for LDP signalled VPLS
#1 command: This will create targeted LDP session (with assumption that underlay ldp neighbors are all established)
#2 commadn: Your understanding is correct.
"show vpls connection" is the best way to check vpls related status. To find out whether it is using BGP or LDP as signaling protocol, I would say you need to check from configuration perspective. To check the inner label, you can also use "show route forwarding-table family vpls", you should see "push push(Top)" option
Few cli commands which may be interesting to you while troubleshooting,
Few Ldp cli commands,
show ldp session
show ldp path
show route <one of vpn route> table <vpn>.inet.0
show ldp database
show route table inet.3
show route <PE/RR loopback> | no-more
show route <PE/RR loopback> details| no-more
show route forwarding-table destination <PE/RR loopback> | no-more
show ldp neighbor | no-more
show ldp session | no-more
show ldp neighbor details | no-more
show ldp session details | no-more
set protocols ldp traceoptions flag route detail
set protocols ldp traceoptions file ldp-trace size 10m files 10
set protocols ldp traceoptions flag label detail
set protocols ldp traceoptions flag binding detail
set protocols ldp traceoptions flag error detail
show mpls lsp ingress
show configuration potocols mpls
show mpls lsp ingress extensive
show mpls lsp
show rsvp session detail ingress