@@tannetpro actually in 1st question = 2nd rtr should also share label to edge router lable 0 (which mean auto pop out label by penhultmt one) 2nd qtn = what is default ldp protocol DU = dwnstrem unsolctd or Dod = dwnstrem on demand this qtn ans I dint found anywhere on RfC DOC
Platform based labels are shared across all interfaces of the device. This means that the labels assigned by the router are unique across the entire device. All interfaces use the same label table for forwarding decisions. In MPLS (Multiprotocol Label Switching), there are two main types of label spaces: 1. Platform-Wide Label Space (or Global Label Space): Description: In a platform-wide (or global) label space, labels are shared across all interfaces of the device. This means that the labels assigned by the router are unique across the entire device. All interfaces use the same label table for forwarding decisions. Characteristics: Labels are unique across the entire router. The label is recognized globally within the device, meaning that the same label has the same meaning on all interfaces. Commonly used for MPLS **core routers** and **transit routers** in an MPLS network. Typical Use Cases: MPLS transit routers in the core of the network, where labels are used to forward traffic without needing different labels per interface. It’s simpler and more efficient when traffic forwarding decisions are not interface-specific. Example: If a router receives a packet with label 100 on one interface and the same label 100 on another interface, it treats them the same way and forwards the packet based on the same forwarding entry. 2. Per-Interface Label Space (or Per-VRF Label Space) Description: In a per-interface label space, each interface has its own label table. The same label value can be used with different meanings on different interfaces. This type of label space is commonly used in MPLS VPN environments, where each interface (or VRF - Virtual Routing and Forwarding instance) needs its own separate label space. Characteristics: - Labels are only unique within the scope of a single interface or VRF. - The same label value can have different meanings on different interfaces. - Typically used in MPLS **edge routers** or **PE (Provider Edge) routers**, where the router is serving multiple customers or tenants using separate virtual routing instances (VRFs). Typical Use Cases: MPLS VPN: (Virtual Private Network) services, where different customers or services are assigned labels that may overlap but must remain distinct across interfaces. Provider Edge (PE) Routers: These routers use VRF instances to manage customer traffic, where a per-interface label space helps manage label allocation on a per-customer or per-service basis. Example: Label 200 on interface `GigabitEthernet0/1` might correspond to one VPN, while label 200 on interface `GigabitEthernet0/2` might correspond to a different VPN, even though the label number is the same.
😊. ..You are mixing TCP and LDP. initialisation for TCP only do follow active passive. Top of that LDP both way. But you are watching very minutely that's good. And Thanks for asking questions... I would request you to watch my bgp message video where TCP act same way. Again please tell me if you have any questions. Thanks
@@tannetpro Thanks for your reply. I will definitely watch your BGP message video. At 37:36 I see the first LDP initialization message sent from 3.3.3.3 to 2.2.2.2......2.2.2.2 replies with keepalives and 3.3.3.3 replies back only keepalives. I don't see any LDP initialization sent from 2.2.2.2 in the video, but you are saying the same process will be followed from 2.2.2.2 to 3.3.3.3 as well. Please correct me if I am wrong.
Good question... Right Observation. Just listen from 18:30 there I have mentioned the reply initialisation message sent along with keep alive message that's what. Check wireshark line no 29. 36:27. Trust me these tutorials are followed by RFC. Hope you enjoyed the tutorial. I appreciate your clear careful learning.
It is a Nice session, and thanks for dedicating us.
Your feedback is a reward to me.
I put a lot of effort into making things easier...
Thank you for the effort you have put in making this tutorial. This tutorial helps me to understand the RFC better.
Glad it helped.
Thanks for your feedback
Nice explanation
Thanks for Watching..
Very Good explanation
Thanks for watching.
Thanks for watching.
hey bro
thanks for sharing the knowldge
pls continue the ACI Series by making ACI end to end Lab Config
Give promise man
Thanks....Sure I will make that. But what I feel before drive in deep in ACI L3 out or more the basic reside on MPLS L2 VPN for EVPN and MPLS L3 VPN.
Have a doubt : 23:38 here lsr2 will share its label not only to lsr1 but also to lsr3 or not the penhultimate one ? And also what is default du or dod
1st and is Not penultimate.
2nd did not get your question
@@tannetpro actually in 1st question = 2nd rtr should also share label to edge router lable 0 (which mean auto pop out label by penhultmt one)
2nd qtn = what is default ldp protocol DU = dwnstrem unsolctd or Dod = dwnstrem on demand this qtn ans I dint found anywhere on RfC DOC
@@sankets392 The default protocol is the DU for Cisco. Without demand
What is Platform based in Label space ?
Platform based labels are shared across all interfaces of the device. This means that the labels assigned by the router are unique across the entire device. All interfaces use the same label table for forwarding decisions.
In MPLS (Multiprotocol Label Switching), there are two main types of label spaces:
1. Platform-Wide Label Space (or Global Label Space):
Description: In a platform-wide (or global) label space, labels are shared across all interfaces of the device. This means that the labels assigned by the router are unique across the entire device. All interfaces use the same label table for forwarding decisions.
Characteristics:
Labels are unique across the entire router.
The label is recognized globally within the device, meaning that the same label has the same meaning on all interfaces.
Commonly used for MPLS **core routers** and **transit routers** in an MPLS network.
Typical Use Cases:
MPLS transit routers in the core of the network, where labels are used to forward traffic without needing different labels per interface.
It’s simpler and more efficient when traffic forwarding decisions are not interface-specific.
Example:
If a router receives a packet with label 100 on one interface and the same label 100 on another interface, it treats them the same way and forwards the packet based on the same forwarding entry.
2. Per-Interface Label Space (or Per-VRF Label Space)
Description: In a per-interface label space, each interface has its own label table. The same label value can be used with different meanings on different interfaces. This type of label space is commonly used in MPLS VPN environments, where each interface (or VRF - Virtual Routing and Forwarding instance) needs its own separate label space.
Characteristics:
- Labels are only unique within the scope of a single interface or VRF.
- The same label value can have different meanings on different interfaces.
- Typically used in MPLS **edge routers** or **PE (Provider Edge) routers**, where the router is serving multiple customers or tenants using separate virtual routing instances (VRFs).
Typical Use Cases:
MPLS VPN: (Virtual Private Network) services, where different customers or services are assigned labels that may overlap but must remain distinct across interfaces.
Provider Edge (PE) Routers: These routers use VRF instances to manage customer traffic, where a per-interface label space helps manage label allocation on a per-customer or per-service basis.
Example:
Label 200 on interface `GigabitEthernet0/1` might correspond to one VPN, while label 200 on interface `GigabitEthernet0/2` might correspond to a different VPN, even though the label number is the same.
That too that grow uppen
Thanks for watching. But I didn't get what you wanted to say
Here is the query. Initially, you said that the initialization message is sent from passive to active but the capture shows the other way around.
I said active to passive. Chk 15.20 min and in capture the 3.3.3.3 is the active and started sync.
Please confirm me
@@tannetpro Please check at 17:18 passive initiates the LDP initialization message
😊. ..You are mixing TCP and LDP. initialisation for TCP only do follow active passive. Top of that LDP both way.
But you are watching very minutely that's good. And Thanks for asking questions... I would request you to watch my bgp message video where TCP act same way.
Again please tell me if you have any questions. Thanks
@@tannetpro Thanks for your reply. I will definitely watch your BGP message video. At 37:36 I see the first LDP initialization message sent from 3.3.3.3 to 2.2.2.2......2.2.2.2 replies with keepalives and 3.3.3.3 replies back only keepalives. I don't see any LDP initialization sent from 2.2.2.2 in the video, but you are saying the same process will be followed from 2.2.2.2 to 3.3.3.3 as well. Please correct me if I am wrong.
Good question... Right Observation.
Just listen from 18:30 there I have mentioned the reply initialisation message sent along with keep alive message that's what. Check wireshark line no 29. 36:27.
Trust me these tutorials are followed by RFC. Hope you enjoyed the tutorial. I appreciate your clear careful learning.
Thanks
sir Your way of teaching superb.Please let me know how to reach you for coaching classes.
Hi Khalid,
Thanks for watching. Thanks for your compliment 🙏.
But still I have not started any such course. Once it's started i will let you know.