Professional Documents
Culture Documents
Xrdocs Io 8000 Tutorials Mpls Te Bin Packing Cisco8000 Auto Capacity
Xrdocs Io 8000 Tutorials Mpls Te Bin Packing Cisco8000 Auto Capacity
Bradley Riapolov
Technical Solutions Architect, Cisco Follow
Save to PDF
M P L S - T E A U T O - B A N D W I DT H T E + + O N C I S C O 8 0 0 0
INTRODUCTION
PROBLEM DESCRIPTION
C I S C O ’ S T E + + A U T O - C A PA C I T Y D E M O N S T R AT I O N
CONCLUSION
ACKNOWLEDGEMENT
Introduction
Building point-to-point Tra c Engineering LSPs can lead to ine cient total network bandwidth utilization. Cisco’s TE++
Auto-bandwidth Capacity allows an ingress router to interact with the other routers in the network, locate additional
available bandwidth and automatically create parallel LSPs to acquire all the necessary network resources possible until
they are no longer needed. This blog details one of the possible applications of this feature using a Cisco 8000
environment.
This blog post details Cisco’s TE++ Auto-bandwidth Capacity feature using a Cisco 8000 environment.
Problem Description
In MPLS Tra c Engineering, a Bin-Packing problem is the inability to e ciently allocate the total reserved bandwidth.
Observe the following:
Router A sends a 300Mbps RSVP reservation into the network destined somewhere beyond R4. Router R1 has three
paths to pick from:
Let’s say the network is setup that Path-1 is chosen. 700Mbps of reservable bandwidth remains on Path-1. Now Router
B sends an 800Mbps RSVP reservation into the network. Since Path-1 is out of reservable capacity (300Mbps +
800Mbps > 1Gbps), Path-2 (could be Path-3, but it does not matter) is chosen and 700Mbps remain. When an
additional 800Mbps ow is requested, we face a similar problem on Path-2 (800Mbps + 800Mbps > 1.5Gbps), Path-3
will be the only remaining choice. Given our demands we have booked a 1.9Gbps of reservations on a 3.5Gbps of
available capacity.
Should another 800Mbps be requested on the network, we will not be able to turn up this LSP on any of these links, even
though we have su cient resources to do so. You can do your own math on your network, but we are now sitting on a
46% of wasted unused reservation bandwidth in our scenario. We cannot e ciently “pack the bin.” We would like to
change this and get as close as possible to make dynamic provisions for the entire 3.5Gbps of available reservations that
will scale up and down without operator intervention.
We do this with a feature called “auto-capacity”. You will nd references to Container LSP or TE++ in other vendors’
documents, but the concept is the same. As tra c demands grow and shrink, we will use LSP splitting functionality to
e ciently ll our total reservable bandwidth, i.e bin-packing the links.
For this article, we run a customer demo using Cisco 8000 series routers which are powered by Silicon One ASICs. The
topology is the following:
Here is the relevant part of R1’s con guration where all the magic (dynamic tunnels) happens:
mpls traffic-eng
interface FortyGigE0/3/0/0
!
interface FortyGigE0/3/0/3
!
interface HundredGigE0/3/0/6
!
reoptimize 60
auto-bw collect frequency 1
named-tunnels
tunnel-te Cisco --------------------------- Name of the tunnel
path-option 10
preference 200
computation dynamic
!
auto-bw ---------------------------------- Adjust bandwidth needs dynamically
overflow threshold 30 min 10 limit 1
adjustment-threshold 20 min 10
application 5 --------------------------- Evaluate every 5min
auto-capacity --------------------------- Adjust capacity
merge-bandwidth 150000 ----------------- Combine LSPs at 150Mbps
split-bandwidth 300000 ----------------- Split LSPs at 300Mbps
max-clones 15 -------------------------- Create 15 child tunnels maximum
min-clones 0 --------------------------- Start with 0 tunnel
nominal-bandwidth 200000 --------------- Base bandwidth is 200Mbps
!
!
signalled-bandwidth 200000
autoroute announce ----------------------- Get TE-tunnel into IGP
!
destination 10.100.100.4 ----------------- R4 is tail-end of the tunnel
!
!
!
Please note that you will have to use di erent con guration values to suit your network needs – the ones we provide here
can help you see the full cycle of tunnel adjustments in less than 1 hour of your time as the network adjusts to various
tra c demands.
What are we doing here? We replaced routers A and B with a tra c generator. The logic is the following:
Let us see it in action: Sending ~200Mbps (on the interface and into tunnel Cisco) into the network:
Let us look at the how many tunnels (should be one, i.e. <200Mbps of nominal/starting bandwidth). Notice it is using the
1Gbps interface in the middle of our topology – Fo0/3/0/3:
Protocol:General
Interface In(bps) Out(bps) InBytes/Delta OutBytes/Delta
Fo0/3/0/3 1000/ 0% 979.9M/ 2% 231.6M/94 7.5T/245.1M
Cisco 0/ --% 216.9M/ --% 0/0 63.6G/0
If you quickly do the math 5x150Mbps = 750Mbps as we continue packing this link.
Let us add 3Gbps of tra c to exhaust our present link capacity and start packing the other two links and you will see the
following in a few min:
All 16 tunnels have been constructed and two other links are being used (Fo0/3/0/0 and Hu0/3/0/6). If you wait, the
bandwidth per tunnel will go up.
Let us lower the tra c to 500Mbps to make sure we can merge the tunnels back.
Our expectation is that after a few minutes we should be down to 3 tunnels (3x200Mbps since we are sending
~500Mbps into the tunnel):
If you are interested in running these tests yourself, compare it to an example of a timeline we observed.
0 1Gbps 1
+5 1Gbps 5
+1 3Gbps 5
+11 3Gbps 14
+4 3Gbps 16
+4 0.5Gbps 16
+1 0.5Gbps 14
+11 0.5Gbps 4
+13 0.5Gbps 3
Conclusion
Cisco auto-capacity features handles bin-backing automatically without operator intervention. This article covered a
practical example which was used for a customer demonstration. Experiment with the timers that work for your network
tra c demands. The con guration guide, available on cisco.com covers additional references: Con guring Auto-
Bandwidth TE++ on Cisco 8000
Acknowledgement
This article has been co-written with Thomas Peiyao Wang, Technical Marketing Engineer at Cisco. I’d like to thanks
Thomas for his support during the lab tests.
Tags: Auto-bandwidth Capacity Cisco 80000 iosxr TE++
SHARE ON
Leave a Comment
0 Comments
1 Login
Name
This site is maintained by Cisco Systems, Inc. employees. Powered by Jekyll & Minimal Mistakes.