I'm glad you found it helpful!

Your feedback is a lot to me. Thanks for watching

Thanks for the feedback!

Glad you liked it

Thanks for your feedback.

@tannetpro when I find some time will watch all your videos. Your videos are much better than wasting time on vendor training! BigIP will be the next one to see if I can clear some doubts! Kudos to your hardworks Amigo 👏

Your feedback is a lot to me.

Your comments is a lot to me. Thanks for Your feedback, it's motivated me🙏

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.

@Rishi. Thanks for your feedback. It's motivated me

Always welcome

Thanks for your feedback 🙏

Thanks for watching. Pranam Mahendra🙏

Your feedback is a lot to me. Thanks for watching...

Please 🙏 provide it is very helpful for our career

Nope

I will try to do

You're welcome

Your feedback is a reward to me. I put a lot of effort into making things easier...

Yes it is there. In my playlist.

Yes

Thanks for watching. Yes you are right. But soft bgp reset may be needed. Router ID elected followed by criteria.

Most welcome

Thanks for watching.... But how can I share..☺️

@@tannetpro or place from where i can download... also can u name the router used in this lab... I ma using CSR and its very slow....

That's what. I don't have any personal repository to keep an image. You just email me on [email protected] I will try later

Thanks for watching and your feedback.. Yes you are absolutely right that I stopped uploading even though I don't know why I stopped. But YES I will start soon......

@@tannetpro Thank you for your response. Would love to learn more about MPLs and rsvp traffic engineering from you. If possible please upload tutorials on those topics. Than you again 🙏

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.

Thanks for watching. Here are 3 subnets created under each BD just for example. But in deployment you must follow best practices.

Thanks for watching .....and your feedback.

How can I help you?

Glad it was helpful!

It's a cedge image only. do you want?

@@tannetpro yes please if you can and many thanks for simplify the technology

Share your email id

Not yet however in the near future I will do it.

You're welcome

Thanks for watching and your feedback. For lab I have used EVeNg

Glad you enjoyed it. Thanks for your feedback..

You are most welcome

Glad 😊

Thanks for watching and your feedback.

Glad it helped. Thanks for your feedback

Thanks a lot 🙏 for your feedback

Thanks for your feedback. I understood your perception that the 37 min tutorial covers the entire VPLS L2 part. VPLS itself is vast, to cover everything in such a small video is not possible. Intent of this video makes things easy not complex what people think. Hope that covers. And yes you are right for one of the aspects of VPLS not all deployment or all requirements.

Thanks for watching and your feedback

You're welcome 😊

Thanks for your feedback

Thanks for watching. Thanks for your feedback. Not started yet

VLAN tagging mostly however it depends on demand and solutions

You are most welcome

Thanks

Thanks for your feedback

Glad you enjoyed it!

You are welcome!

Very soon