Its purely a question for which the answer revolves around the control and the forwarding plane. This is what will happen in this scenario.
1) A will receive Label Bindings for all the IGP routes from two neighbors, B and D. (Different Labels for the same prefixes from two different neighbors)
2) D will receive Label Bindings for all the IGP routes from two neighbors C and A.(Different Labels for the same prefixes from two different neighbors)
3) These Label Bindings will create our LIB, which is nothing but the Label Information Base, which contains LDP ID to Label to Prefix Mapping per neighbor. (You can view this by "show mpls ldp bindings")
4) Now what happens with these LIB is not all the received bindings are used.Because when the PE learns a label for a prefix from an LDP peer, it must be able to determine whether that peer is currently a next hop for the prefix to determine whether it needs to start using the newly learned label when forwarding packets that match the prefix.
So what happens is the Label which was received from B at A will be used. Also in case of D the same would happen and it will use the label bindings received from C and not from A.
So for the traffic received from lets say VRF at A which needs to go to D will go Hop by Hop with normal label swapping.
This happens as the next hop for a prefix should be equal to the LDP ID from which the label binding was received. Other bindings are just preserved in the LIB.
Once this is clear the next question which may come to mind is how it happens for ATOM, which also uses directed LDP.
NHLFE is all about how you take your forwarding decisions based on elgible received Label bindings. What i tried to mention in my previous post was what is considered eligible.
(This refers to RFC 3036 - Section 2.7)
Now, coming to your scenarios, if you go by basics the answers would be very clear,
As they all are Label ditribution protocols. A Stack will only be created if one protocol is using the LSP created by another protocol to learn the label information from its peer.
Just running multiple label distribution protocols together wont give a Label Stack,
1) In this again you will not use your directed LDP labels as the LDP ID cannot be reached as the next hop. The traffic will go out with a Tunnel Label only. As your RSVP can generate labels
using the TE entension to create LSP Tunnel so you get a Tunnel Label. Refer to RFC 3209.
"""VPN LSP Path Break."""
2) Again there is no label stack. As the directed LDP wont be established in this case.
As the RSVP tunnel doesnt support LDP by default.
Having said that if you enable RSVP tunnels for LDP then you will get a stack if there is anything downstream your router C. Or else it would be a PoP label for C loopback. with the Tunnel Label. In this Case its VPN will go with a """VPN + TE label."""
3) In this scenario even though for LDP the neighbors are connected directly. Because of the RSVP tunnels the sessions between each neighbors would be a directed session.
Again there wont be any stack if your tunnels are not enabled for LDP or TDP.
If enabled then the stack would be your LDP/TDP label + Tunnel Label.
"""VPN LSP Path Break."""
End of the day, we need to understand the basic thing that all RSVP-TE, LDP, BGP are label distribution mechanisims. If one protocol provides an existing LSP for another protocol to
ride over and learn some more information with a certain peer, then only a stack comes into picture. Or else only Tunnel Label prevails as that is the only thing which figures up in your
forwarding table. And in these examples we havent considered your end VRF's. which is bound to suffer in these 3 scenarios
PS: If you plan to run a full network without LDP, then you should not run tunnels Hop by Hop basis. You sould run then across edges in a full mesh.
Refer to this link as well it has numerous such combinations.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...