Segment Routing Basic Traffic Engineering
Vložit
- čas přidán 17. 09. 2020
- The Segment Routing Basic Traffic Engineering Learning Byte covers how to configure and verify segment routing traffic engineering. This Learning Byte is most appropriate for users who are new to working with segment routing.
• Presenter: Zach Gibbs / Content Developer
• Relevant to OS Releases: Junos 20.1R1 or later
• Relevant to Juniper Platforms: MX Series, vMX Series, PTX Series, T Series
• On-Demand Training: Take a hands-on course…now!
learningportal.juniper.net/ju...
• All-Access Training Pass: Access every course for a full year!
learningportal.juniper.net/ju...
• Juniper Certification: Get started with the Juniper Open Learning program:
learningportal.juniper.net/ju... - Věda a technologie
This would apply to all customers' VPN traffic between R1 and R4? so let's say I wanted to run some VPNs via this segmented path, but other VPNs between R1 and R4 take the other path. Is that possible?
Thank you for the explanation! I have a question related to this. In case we would have 2 links between R2-R5, could we use an adjacency SID in the hop1.5 of the segment list "LB-path" to choose the specific link we would like to use? If so, how can this be done? Thank you!
Yes, you have to use SR Adjacency-SID. They are automatically assigned to every interface but are not guaranteed the same after link-flaps or reboots. You can see them for an existing SR-enabled topology with [show isis adjacency details]. Best would be to assign static Adj-SID before doing this in production. Then you can use it in the Segment-List with the instructions from the video.
Why there is no cost associated with the interfaces on this topology? This help more understand the TE lab.
Thanks for taking time out but I am sorry but you are so fast and not taking your time to explain in detail. People can't follow properly.. just a constructive feedback. Your diagram as well doesn't tell the whole story. You referenced prefix sid which are not shown in the diagram as well.
Each node has a label by using the formula [5000 + Node_ID ] so router R4 == 5000 + 4 = SID 5004.