01-12-2025 08:54 PM
Good day everyone
I'm struggling to understand the concept of the Bandwidth in Segment Routing on-demand policy and wanted to clarify some use-cases.
For example, there is a part of config based on IOS-XE.
!
segment-routing traffic-eng
segment-list name BANDWIDTH_1
index 10 mpls label 16044
index 20 mpls label 16023
!
segment-list name BANDWIDTH_2
index 10 mpls label 16012
index 20 mpls label 16011
index 30 mpls label 16021
index 40 mpls label 16022
index 50 mpls label 16023
!
!
on-demand color 100
authorize
candidate-paths
preference 20
constraints
bandwidth 15000
segments
dataplane mpls
!
!
preference 10
explicit segment-list BANDWIDTH_1
!
constraints
bandwidth 5000
!
preference 5
explicit segment-list BANDWIDTH_2
!
constraints
bandwidth 10000
!
!
1. What is the purpose of the of bandwidth command in each case? And how can I use them?
2. Is it possible to make a route, for example, BANDWIDTH_1 list takes a primary route with the 5000 bandwidth and after full utilization it goes through BANDWIDTH_2 list?
Thank you in advance
02-03-2025 01:56 AM
Hello @dundient
1. What is the purpose of the of bandwidth command in each case? And how can I use them?
The bandwidth
command in the context of Segment Routing Traffic Engineering (SR-TE) on-demand policies is used to define the bandwidth constraints for a specific candidate path. This is part of the Traffic Engineering (TE) mechanism, where the network can dynamically select paths based on available resources and constraints.
bandwidth
command specifies the minimum bandwidth requirement for a path to be considered valid. The SR-TE controller (or headend router) will evaluate the available bandwidth on the links along the candidate path and only select paths that meet the specified bandwidth constraint.
2. Is it possible to make a route, for example, BANDWIDTH_1 list takes a primary route with the 5000 bandwidth and after full utilization it goes through BANDWIDTH_2 list?
2. The behavior you're describing is not directly achievable with the configuration as it stands. Here's why:
bandwidth
constraint in SR-TE on-demand policies is not a dynamic load-balancing mechanism. It does not monitor the actual utilization of the path in real-time. Instead, it evaluates the available bandwidth on the links (as advertised by IGP extensions like OSPF-TE or IS-IS-TE) when selecting a path.However, you can achieve a similar behavior by using multiple candidate paths with different preferences and bandwidth constraints, as you have configured.
Let me know if you need more detailed analysis of this.
Hope This Helps!!!
AshSe
Forum Tips:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide