superb explanation. I needed to revise the basics of MPLS-TP which I worked on previously, and this is a great video. Hope Psuedowires, tunnels and MEP are described too. Kudos man.
at 7:05, whats the purpose of it swapping the label for a new number? why doesn't it just keep label 17 in this example? or is that new label effectively the identity of the next LSR in the LSP as predetermined by the LDP?
I think swapping of the labels helps to identify where a packet is coming from, probably within Routers belonging to a single ISP or from routers belonging to several ISPs since the internet cloud is a collection of several ISPs.
Thanks a lot for the great presentation. I agree with the comment from Peter concerning the label. What does it represent, how does it change. I need to talk to my new crew...
IT was very informativ, but i think that at 9min 21 seconds PHP happens, beacause LER send label 3. < Very close to last LER, remove label, so he will not do two look up, only IP look up and send normal IP packet> So R4 send label 3 to R3. In case of MPLS VPN, R4 should receive bottom label | vpn label| thx
Thanks for the comment, which is correct for IP/MPLS. But remember that PHP is not used in MPLS-TP. The video is intended to get across basic principles. PHP, ECMP and Label Merge are not covered here.
What you describe is PHP (penultimate hop popping) - and indeed this can be a feature of IP/MPLS to reduce the load on the final LER. However, it is not (and must not) be a feature of MPLS-TP to ensure end to end traceability is possible. See my second video on MPLS-TP.
There is no explanation on what the label is used for, just that it is mapped to the original IP address, exchanged, and popped as it goes through the MPLS network... My question, what does the label represent? What is it used for? I'd be guessing that the the label is that of the next hop LSR and that each LSR would need to strip the label, execute a table lookup on the destination IP and then add it's own label for the next hop LSR. How is this quicker with each LSR executing a table lookup? I must be missing something....
+Peter Nowak The point is that - after all the tunnel paths in the MPLS network are initially set up (by for example LDP in IP/MPLS or configuration in MPLS-TP) - the ongoing switching of traffic packets in any LSR from input port to output port will be very rapid, because the only thing the LSR has to do is look at the incoming label, do a simple table lookup to find out which port to send it out of, and swap the label. That should always be much quicker than the analysis of IP routing tables - which requires a match with the longest prefix before forwarding can take place. LSP labels themselves don't represent anything - they only have local significance. Let's take an example: - in an LSR any packet arriving with label 100 will always be swapped for label 101 and forwarded out of port 2; any packet arriving with label 200 will always be swapped for label 300 and forwarded out of port 5, and so on ... In more complex networks packets can have multiple 'stacked' labels - but even then the process is just as quick because only the topmost label is 'examined' and acted on.
Labels also help to identify the source of a packet and where next is to be forwarded (Destination) so quickly without having to start analyzing the header of the packet which can be time consuming. The path of the label is already predetermined.
Thanks for the comment. However Brits (like me) and Europeans pronounce it as "Rooter". The way Americans pronounce it we reserve for a woodworking tool.
Best video on MPLS I've seen so far. If only teachers were able to explain things in such an easy way.
Totally agree!
Lord, it's a pleasure to listen to this guy talk. Also, best and most concise explanation I've come across.
Look up "Peter Baker." He's a well-known voice actor.
Probably the best video I've seen on MPLS so far, explained really well. Thank you !
This video makes MPLS easy to understand.... 5 stars from me
THE BEST TUTORIAL I HAVE SEEN ON MPLS !!!! Great job, helped me a lot thanks you!!
Guys ... what a great explanation ... clear, simple and superb graphics. Thank you.
The best video about MPLS EVER!!!!
Well, we're certainly glad to hear it, Ronald Retana.
excellent video on MPLS. help understand MPLS in an easy and clear way ! thank you
Thank you! We are glad to hear that.
Best and simplest MPLS video I have seen.
The best tutorial video I have seen thank very much I’m appreciate your efforts
Thanks!!! the best MPLS explanation on youtube. Keep it up with more tutorials.
I am not a religious person, but THANK GOD for this God given tutorial!
this is a great explanation of the basic MPLS.
by far the best explanation I have come across.
WAO, so impressed about this explanation. This guy is very intelligent. MPLS simplified! Well explained!
The clearest intro video on MPLS that I have seen. Thanks!
The best video on MPLS
A very clear explanation. I was relieved to hear the correct English pronunciation of route, router and routing :)
bcz u uploaded 3 parts only...... and now only i referred first part video excellent presentation and explanation.
Fantastic intro to MPLS!!!!!! Thank you!
Best Video on MPLS.
WoW , what a video mate. Thanks
thanks for your all efforts and explaining things in such an easy way
Great video. The graphics really helped to illustrate the concepts
Simply Awesome.. very clean to understand the concept.
Excellent Video. Thanks for sharing.
Thanks for watching & your nice feedback!
This is awesome, thank you for the clear explanation
Great Job, thank you
Thank you! Excellent presentation. Ver well said and understood.
superb explanation. I needed to revise the basics of MPLS-TP which I worked on previously, and this is a great video. Hope Psuedowires, tunnels and MEP are described too. Kudos man.
Simply beautiful explanation!! Best for preparing for an interview :)
Basics very well explained, thanks
This is excellent basic presentation,keep it up & simple!!
Really very clean explanation
amazing tutorial im not really good in english but i understood everything thank you very much :)
Well explained for beginners, need to upload some more videos for deep dive. Thank you :)
thank you so much. That really helped me to understand the concept.
Only masters can make complex things easy instead of vice vesa.
Very nice explanation. thank you very much
Appreciate your effort, very good explanation!!!
Great tutorial!! Congratulations
Excellent - very well explained.
thanks for this video is very simple to understand
Amazing Tutorial! Many Thanks!!
good. Beginners can understand easily.
at 7:05, whats the purpose of it swapping the label for a new number? why doesn't it just keep label 17 in this example? or is that new label effectively the identity of the next LSR in the LSP as predetermined by the LDP?
Yes, its the identity of the next LSR in the LSP.
I think swapping of the labels helps to identify where a packet is coming from, probably within Routers belonging to a single ISP or from routers belonging to several ISPs since the internet cloud is a collection of several ISPs.
Thanks a lot for the great presentation. I agree with the comment from Peter concerning the label.
What does it represent, how does it change. I need to talk to my new crew...
Thanks , is it still relevant after 7 years ?
Excellent Explanation!!!
Many thanks
Very Interesting ... Thanks!
Very nice! Thanks.
Amazing! Thanks a million!
GREAT video
The best explanation!!!!
Very informative and easy to understand! And i like your voice very much too :)
Nice explanation but u didnt mentioned about DATA label as i know there are two label imposed the VPN label and the DATA label.
Nice one. Thanks!
label 17 ignored until arrive to destination LER, so what the point the packages get label 17 on incoming LER then?
IT was very informativ, but i think that at 9min 21 seconds PHP happens, beacause LER send label 3. < Very close to last LER, remove label, so he will not do two look up, only IP look up and send normal IP packet> So R4 send label 3 to R3. In case of MPLS VPN, R4 should receive bottom label | vpn label| thx
Thanks for the comment, which is correct for IP/MPLS. But remember that PHP is not used in MPLS-TP. The video is intended to get across basic principles. PHP, ECMP and Label Merge are not covered here.
Can you please make a video on cross connection of your device LCC XMP-1.
Good work
Good stuff!
amazing ...............
I didn't know James May knew networking!
Delivered with the same level of excitement also!
GregRS3 i
I thought the last LSR did the pop before going to the LER? Penultimate pop?
What you describe is PHP (penultimate hop popping) - and indeed this can be a feature of IP/MPLS to reduce the load on the final LER. However, it is not (and must not) be a feature of MPLS-TP to ensure end to end traceability is possible. See my second video on MPLS-TP.
There is no explanation on what the label is used for, just that it is mapped to the original IP address, exchanged, and popped as it goes through the MPLS network... My question, what does the label represent? What is it used for? I'd be guessing that the the label is that of the next hop LSR and that each LSR would need to strip the label, execute a table lookup on the destination IP and then add it's own label for the next hop LSR. How is this quicker with each LSR executing a table lookup? I must be missing something....
+Peter Nowak The point is that - after all the tunnel paths in the MPLS network are initially set up (by for example LDP in IP/MPLS or configuration in MPLS-TP) - the ongoing switching of traffic packets in any LSR from input port to output port will be very rapid, because the only thing the LSR has to do is look at the incoming label, do a simple table lookup to find out which port to send it out of, and swap the label. That should always be much quicker than the analysis of IP routing tables - which requires a match with the longest prefix before forwarding can take place. LSP labels themselves don't represent anything - they only have local significance. Let's take an example: - in an LSR any packet arriving with label 100 will always be swapped for label 101 and forwarded out of port 2; any packet arriving with label 200 will always be swapped for label 300 and forwarded out of port 5, and so on ... In more complex networks packets can have multiple 'stacked' labels - but even then the process is just as quick because only the topmost label is 'examined' and acted on.
+John Collinson thank you. this helped answer the same question.
Labels also help to identify the source of a packet and where next is to be forwarded (Destination) so quickly without having to start analyzing the header of the packet which can be time consuming. The path of the label is already predetermined.
great job thanks
lucid explanation
what if I add a switch (due to some reason) between LER n LSR would the switch create any congestion?
As long as the switch is capable of handling the larger frame size there usually shouldn't be a problem.
is there a better quality of this video somewhere?
i'm afraid that is the only video there is. maybe one day i will remake it.
excellent !
Thank you!
nice content
thank you so much.
Thanks for saving me :)
thanks teacher
thank you very mutch
how many parts in mpls?
Great!
This is what happened to TTSL Seshadhri vs Archana Patnaik. Or Sumanth..ellamthala yeluthu...
Can we say the MPLS is like an INTERNET cloud?
thanks
Thank u
Watch in 1.5x-2x. You're welcome
Tata group will follow the old traditional model ..then they will be fixed in all sectors by him admk
It's ROUTER... not ROOTER.
Thanks for the comment. However Brits (like me) and Europeans pronounce it as "Rooter". The way Americans pronounce it we reserve for a woodworking tool.
Hi
Sound quality is shit
Thumbs up!!
Very well explained the topic. Thank you
You're welcome!