1. Traffic Engineering for ISP Networks Jennifer Rexford Internet and Networking Systems AT&T Labs - Research; Florham Park, NJ http://www.research.att.com/~jrex

2. Who am I, and Why am I Here?  Who am I? –Princeton EE class of ‘91, PhD in ‘96 from U. Michigan –AT&T Research from 1996, in the IP Network Measurement and Engineering Department –Joining the Princeton CS faculty in February 2005  Why am I here? –Working closely with operators of AT&T’s IP network –Creating tools for them to engineer the flow of traffic –Applying optimization techniques to real problems

3. Outline  Background –Internet architecture –Interdomain and intradomain routing –Internet service provider backbone  Traffic engineering –Optimizing routing to prevailing traffic –Local search to select the integer link weights  Inferring the traffic matrix –Working backwards from link loads  Conclusion and ongoing work

4. Internet Architecture  Divided into Autonomous Systems –Distinct regions of administrative control –Routers and links managed by an institution –Service provider, company, university, …  Hierarchy of Autonomous Systems –Large, tier-1 provider with nationwide backbone –Medium-sized regional provider with smaller backbone –Small network run by a single company or university  Interaction between Autonomous Systems –Internal topology is not shared between ASes –… but, neighboring ASes interact to coordinate routing

5. Autonomous Systems (ASes) 1 2 3 4 5 6 7 Client Web server Path: 6, 5, 4, 3, 2, 1

6. Interdomain Routing: Border Gateway Protocol  ASes exchange info about who they can reach –IP prefix: block of destination IP addresses –AS path: sequence of ASes along the path  Policies configured by the AS’s network operator –Path selection: which of the paths to use? –Path export: which neighbors to tell? 1 23 12.34.158.5 “I can reach 12.34.158.0/24” “I can reach 12.34.158.0/24 via AS 1” data traffic

7. Internet Service Provider Backbone modem banks, business customers, web/e-mail servers neighboring providers How should traffic be routed through the ISP backbone?

8. Interior Gateway Protocol (Within an AS)  Routers flood information to learn the topology –Routers determine “next hop” to reach other routers… –By computing shortest paths based on the link weights  Link weights configured by the network operator 3 2 2 1 1 3 1 4 5 3

9. Heuristics for Setting the Link Weights  Proportional to physical distance –Cross-country links have higher weights than local ones –Minimizes end-to-end propagation delay  Inversely proportional to link capacity –Smaller weights for higher-bandwidth links –Attracts more traffic to links with more capacity  Tuned based on the offered traffic –Network-wide optimization of weights based on traffic –Directly minimizes key metrics like max link utilization

10. Why Are the Link Weights Static?  Strawman alternative: load-sensitive routing –Link metrics based on traffic load –Flood dynamic metrics as they change –Adapt automatically to changes in offered load  Reasons why this is typically not done –Delay-based routing unsuccessful in the early days –Oscillation as routers adapt to out-of-date information –Most Internet transfers are very short-lived  Research and standards work continues… –… but operators have to do what they can today

11. Our Approach: Measure, Model, and Control Topology/ Configuration Offered traffic Changes to the network Operational network Network-wide “what if” model measure control

12. Traffic Engineering in an ISP Backbone  Topology –Connectivity and capacity of routers and links  Traffic matrix –Offered load between points in the network  Link weights –Configurable parameters for Interior Gateway Protocol  Performance objective –Balanced load, low latency, service level agreements …  Question: Given the topology and traffic matrix in an IP network, which link weights should be used?

13. Key Ingredients of Our Approach  Instrumentation –Topology: monitoring of the routing protocols –Traffic matrix: widely deployed traffic measurement  Network-wide models –Representations of topology and traffic –“What-if” models of shortest-path routing  Network optimization –Efficient algorithms to find good configurations –Operational experience to identify key constraints

14. Formalizing the Optimization Problem  Input: graph G(R,L) –R is the set of routers –L is the set of unidirectional links –c l is the capacity of link l  Input: traffic matrix –M i,j is traffic load from router i to j  Output: setting of the link weights –w l is weight on unidirectional link l –P i,j,l is fraction of traffic from i to j traversing link l

15. Multiple Shortest Path With Even Splitting 0.5 0.25 1.0 Values of P i,j,l

16. Defining the Objective Function  Computing the link utilization – Link load: u l =  i,j M i,j P i,j,l – Utilization: u l /c l  Objective functions – min l (u l /c l ) – min l (  f(u l /c l )) f(x) 1 x

17. Complexity of the Optimization Problem  NP-complete optimization problem –No efficient algorithm to find the link weights –Even for the simple convex objective functions  Why can’t we just do multi-commodity flow? –E.g., solve the multi-commodity flow problem… –… and the link weights pop out as the dual –Because IP routers cannot split arbitrarily over ties  What are the implications? –Have to resort to searching through weight settings

18. Optimization Based on Local Search  Start with an initial setting of the link weights –E.g., same integer weight on every link –E.g., weights inversely proportional to link capacity –E.g., existing weights in the operational network  Compute the objective function –Compute the all-pairs shortest paths to get P i,j,l –Apply the traffic matrix M i,j to get link loads u l –Evaluate the objective function from the u l /c l  Generate a new setting of the link weights repeat

19. Making the Search Efficient  Avoid repeating the same weight setting –Keep track of past values of the weight setting –… or keep a small signature (e.g., a hash) of past values –Do not evaluate a weight setting if signatures match  Avoid computing the shortest paths from scratch –Explore weight settings that changes just one weight –Apply fast incremental shortest-path algorithms  Limit the number of unique values of link weights –Do not explore all 2 16 possible values for each weight  Stop early, before exploring the whole search space

20. Incorporating Operational Realities  Minimize number of changes to the network –Changing just 1 or 2 link weights is often enough  Tolerate failure of network equipment –Weights settings usually remain good after failure –… or can be fixed by changing one or two weights  Limit dependence on measurement accuracy –Good weights remain good, despite random noise  Limit frequency of changes to the weights –Joint optimization for day and night traffic matrices

21. Application to AT&T’s Backbone Network  Performance of the optimized weights –Search finds a good solution within a few minutes –Much better than link capacity or physical distance –Competitive with multi-commodity flow solution  How AT&T changes the link weights –Maintenance done every night from midnight to 6am –Predict effects of removing link(s) from the network –Reoptimize the link weights to avoid congestion –Configure new weights before disabling equipment

22. Example from My Visit to Our Operations Center  Amtrak repairing/moving part of the train track –Need to move some of the fiber optic cables –Or, heightened risk of the cables being cut –Amtrak notifies us of the time the work will be done  AT&T engineers model the effects –Determine which IP links go over the affected fiber –Pretend the network no longer has these links –Evaluate the new shortest paths and traffic flow –Identify whether link loads will be too high

23. Example Continued  If load will be too high –Reoptimize the weights on the remaining links –Schedule the time for the new weights to be configured –Roll back to the old weight setting after Amtrak is done  Same process applied to other cases –Assessing the network’s risk to possible failures –Planning for maintenance of existing equipment –Adapting the link weights to installation of new links –Adapting the link weights in response to traffic shifts

24. Conclusion of This Part of the Talk  IP networks do not adapt on their own –Routers compute shortest paths based on static weights  Service providers need to adapt the weights –Due to failures, congestion, or planned maintenance  Leads to an interesting optimization problems –Optimize link weights based on topology and traffic  Optimization problem in NP-complete –Forces the use of efficient local-search techniques  Results of the local search are useful –Near-optimal solutions that minimize disruptions

25. Computing the Traffic Matrix M i,j  Hard to measure the traffic matrix –IP networks transmit data as individual packets –Routers do not keep traffic statistics, except link utilization on (say) a five-minute time scale  Need to infer the traffic matrix M i,j from –Current topology G(R,L) –Current routing P i,j,l –Current link load u l –Link capacity c l

26. 4Mbps 3Mbps5Mbps Inference: Network Tomography Sources Destinations From link counts to the traffic matrix

27. Tomography: Formalizing the Problem  Ingress-egress pairs –p is a ingress-egress pair of nodes (i,j) –x p is the (unknown) traffic volume for this pair M i,j  Routing –P lp is proportion of p’s traffic that traverses l  Links in the network –l is a unidirectional edge –u l is the observed traffic volume on this link  Relationship: u = Px (work backwards to get x)

28. Tomography: One Observation Not Enough  Linear system of n nodes is underdetermined –Number of links e is around O(n) –Number of ingress-egress pairs c is O(n 2 ) –Dimension of solution sub-space at least c - e  Multiple observations are needed –k independent observations (over time) –Stochastic model with Poisson iid counts –Maximum likelihood estimation to infer matrix  Doesn’t work all that well in practice…

29. Approach Used at AT&T: Tomo-gravity  Gravitational assumption –Ingress point a has traffic v i a –Egress point b has traffic v e b –Pair (a,b) has traffic proportional to v i a * v e b 9 20 10 6 3

30. Approach Used at AT&T: Tomo-gravity  Problem with gravity model –Gravity model ignores the load on the inside links –Gravity assumption isn’t always 100% correct –Resulting traffic matrix might not satisfy the link loads  Combining the two techniques –Gravity: find a traffic matrix using the gravity model –Tomography: find the family of traffic matrices consistent with all link load statistics –Tomo-gravity: find the tomography solution that is closest to the output of the gravity model  Works extremely well (and fast) in practice

31. Conclusions  Managing IP networks is challenging –Routers don’t adapt on their own to congestion –Routers don’t reveal much information about traffic  Measurement provides a network-wide view –Topology –Traffic matrix  Optimization enables the network to adapt –Inferring the traffic matrix from the link loads –Optimizing the link weights based on the traffic matrix