MPLS Evolution - IP Routing, LDP, RSVP-TE, MPLS-TP, to Segment Routing

[@哈哈投美股]

This is a really good one, not just tells you stuff, but also strings all together. It is really good for people to go over the mpls related knowledge. I watched three times.

[@BarbaraAnne]

Thanks! I’m glad you found it helpful!

[@haventfoundme]

Excellent overview of the topics. Really appreciate you putting the time into this video.

[@BarbaraAnne]

Thanks! Appreciate the feedback!

[@jaideepchoudhary4826]

A beautiful video to briefly present the Network Evolution/transformation. Very very useful for the Network Engineers trying to understand the reason behind these evolutions. very well explained in a effortless manner. Cheers!

[@BarbaraAnne]

Many thanks!

[@liferone]

Thank you Barbara!, a pleasure to understand the way you explained all concepts!. It helped me a lot. Keep doing these kind of videos hahaha.

[@BarbaraAnne]

You are so welcome!

[@OnlyTheTruth007]

You have made one of the best video explanations of this journey of networking . Kudos . Pls make note of these . You style and explanation are great !👏🏽👏🏽👏🏽👏🏽

[@BarbaraAnne]

Thanks a ton

[@cesarmaranomaranio9606]

L

[@boonlengong1939]

Amazing video. Maps out the entire SP core history

[@BarbaraAnne]

Thanks Boon!

[@IrfanAli-jl7vb]

Brilliant video Barbara. Thank you for providing the problem statements that these various updates were trying to solve. Thank you for motivating all of this with an easy to understand example that yet captures the essence of the problem statements and then providing a high level overview of the solution provided by the various solutions and their short-commings. So much knowledge poured into this video. Thank you.

[@BarbaraAnne]

Thanks so much Irfan!

[@kdesro8138]

Great video! I think this video is a good one for beginners and for experienced tech/ing too. I'm 50 yo I've worked with many different technologies before getting to MPLS-TE and VLL. I am pretty impressed that you could fit so much information in less than 30 minutes! bravo! :)

[@BarbaraAnne]

Thanks so much!

[@kamranmughal6462]

Excellent demonstration of network evolution 👍👍👍

[@BarbaraAnne]

Thanks Kamran!

[@samadwani405]

One of the best video on SR

[@BarbaraAnne]

Thank you!

[@limberfuture]

Excellent video Barbara! Quite easy to follow and very nicely explained! Loved it and would love to see more contents. Maybe switching concepts and evolution similar to this. Thank you!

[@BarbaraAnne]

Great suggestion!

[@willygodo]

I think this is so far the easiest video to understand for mpls. great work! although might need some basic understanding before watching the video

[@BarbaraAnne]

Glad to hear that!

[@tobiaskloy5613]

Visually boring, but such a good presenting Voice in a clear structered manner. Chapeau to you, Babara!

[@BarbaraAnne]

Thanks! I'm old and boring so it works!

[@jamesmajani218]

Brilliant, by understanding of SRv6 is significantly enhanced

[@BarbaraAnne]

Glad it helped!

[@vrushalisawant6185]

This is amazing! Thank you so much for this.

[@BarbaraAnne]

Glad you liked it!

[@mangathala2002]

Thanks for sharing, very well explained

[@BarbaraAnne]

Thanks so much!

[@VandersonT_]

Great lesson!! Thanks very much!

[@BarbaraAnne]

Glad you liked it, Vanderson!

[@vanbaole8415]

Hi Anne so for RSVP-TE the FRR is only configured in the LSR's?

[@BarbaraAnne]

For FRR, the P routers need to have a facility bypass profile configured on their interfaces that will support FRR. Then the PE router will signal the tunnel with a request for FRR support. Then the P routers know they need to fix the connection if they become the point of local repair.

[@crazygamiiing]

very well explained, thank you !

[@BarbaraAnne]

Glad you enjoyed it!

[@ozacuna4026]

Really good explanation, thanks

[@BarbaraAnne]

Glad you liked it

[@abdulrahmansattar2873]

Thanks for this great video. Just subscribed

[@BarbaraAnne]

Awesome, thank you!

[@Soundwave-F7Z]

You are awesome! So the adjacency SIDS are generally just used for TE?

[@BarbaraAnne]

Thanks! If you're just using the default path, you don't need adjacency SIDs.

[@Soundwave-F7Z]

@@BarbaraAnne let’s say you want to go to a node SID which is a few hops away. How does the ingress router know how to get there when it adds the node SID to the label stack?

[@BarbaraAnne]

@@Soundwave-F7Z The Node SID is global in the IGP - so all nodes know which node the node SID applies too. They're all use the same SID for that node.

[@Alestrix76]

22:45 - why does router 6 not chose to be identified by SID=6 and instead that strange SID 16006 is used? And how does Segment Routing differ from MPLS with a label stack?

[@BarbaraAnne]

There is a base SID value that is added to the node SID value. This way we can break the label space up by the supported protocol. The labels look the same as the MPLS labels so we don't want them to collide. By creating a base value, you can say all Segment Routing labels are in a particular label space, or between 2 known values - like 16000 to 18000. It will avoid problems between control protocols and make debugging easier.

[@bgaabab]

Good and simple!

[@BarbaraAnne]

Glad you think so! thanks!

[@swamysrk5082]

Excellent video for beginners

[@BarbaraAnne]

Glad you liked it

[@touliverkhang1320]

hi bro. thank you for your helpful post. i have a question hoping u to answer me. adj -SID u know it is a local significance so why a remote router knows this value. For example, in SRTE we use this value to choose the path. is there any mechanism or way that a remote router knows that cause i think a remote router doesn't need to install this value in its forward plane? thank u in advance.

[@BarbaraAnne]

The adj-SID is locally significant so each router can reuse the same SID values to identify their adjacencies. The reason that it has to be known at the source is so a source route can be created - if it wants to steer traffic through a particular path. If the source is not going to do source routing, it doesn't need to know the adjacency SIDs, it will just send the traffic down the routed path using the end node's SID.

[@praneelp9]

thank you soo much, loved it

[@BarbaraAnne]

So glad! Thanks!

[@sheikwaris]

amazing. thanks

[@BarbaraAnne]

Thank you!

[@BG-su1lv]

Thank you

[@BarbaraAnne]

You're welcome

[@touliverkhang1320]

hi miss thank you for your sharing but I have a graduate seminar about segment routing so can u summary me sth like what different between MPLS and Segment routing.? thank u

[@BarbaraAnne]

Segment routing gets its routing information and labels from the IGPs (OSPF or ISIS). MPLS uses LDP as well. MPLS labels are unique to a particular node, they change along the route. SR SIDs for a particular node are global in the routing domain, they don't change, although the SR range to which it is applied may change per node. MPLS uses RSVP to create a traffic engineered path. SR uses a centralized path computation engine and PCEP to communicate the path to the source node. This is a big topic. I suggest you read information on the web. When I googled MPLS vs Segment Routing, I found this site: segmentroutingexpert.com/faq/what-is-the-difference-between-segment-routing-and-mpls/ When googling PCEP, I found this on packet pushers. I have not read this particular article yet but Diptanshu Singh, the author, writes very good and clear descriptions. You should read this as well: packetpushers.net/pce-pcep-overview/ Good luck with your seminar!

[@touliverkhang1320]

@@BarbaraAnne hi miss. thank you for your help. i think I write seminar about SR-MPLS. can u give me some files to me read more about this topic.?. thank u

[@tridang4714]

i invented this...