100 likes | 225 Views
BGP – OSPF Experimentation. Murat Yuksel and David Bauer. Design 1: Baseline Performance. Perform RRS investigation of protocol input parameters Attempt to determine “baseline” performance of the models: BGP, OSPF
E N D
BGP – OSPF Experimentation Murat Yuksel and David Bauer
Design 1: Baseline Performance • Perform RRS investigation of protocol input parameters • Attempt to determine “baseline” performance of the models: BGP, OSPF • Question: What does the response plane look like when the BGP decision parameters are fixed?
Response Plane 1 • It appears that the number of updates is highest when the KeepAlive interval is small. • Makes sense because more link changes can be aggregated into a single update • BGP does not aggregate Update Adds, ever. It does aggregate Update Withdraws, but not in our model. • OSPF does, and OSPF updates are majority of Updates Figure 1. Response plane plotted versus MRAI and KeepAlive interval.
Response Plane 2 • Here the response is plotted with KeepAlive X Hold Interval for X-axis. • We see the same behaviour represented slightly differently, probably more clearly. • This response indicates that the earlier topology changes are detected, the greater the number of update messages created. Figure 2. Response plane plotted versus MRAI and now KeepAlive interval X Hold interval. This plot more clearly illustrates that the earlier topology changes are detected, the greater the number of update messages created.
Design 2: Decision Algorithm • Perform RRS investigation of protocol input parameters AND BGP4 Decision Algorithm Parameters • Attempt to determine effects of decision algorithm on “baseline” performance response. • Question: How might the response plane change when BGP decision parameters are not fixed?
Response Plane 1 • Same general behaviour as before Decision Algorithm searched. • Response appears dampened. I.e., most of the values are now below 150K updates as compared to 300K updates earlier. • BGP may not aggregate adds/withdraws, but it can “choose” not to add/remove a route based on the algorithm. Figure 1. Response plane plotted versus MRAI and KeepAlive interval. Response is dampened with BGP decision paramaters.
Response Plane 2 • Here the response is plotted with KeepAlive X Hold Interval for X-axis. • It is definitely clear that the response is dampened by the decision process. This plot illustrates the worst-cases dropped from 600K updates to < 350K updates. • This response indicates that the decision algorithm can impact the response plane by almost 50%! Figure 2. Response plane plotted versus MRAI and now KeepAlive interval X Hold interval. This plot more clearly illustrates that the earlier topology changes are detected, the greater the number of update messages created. Also, it is more clear that the response plane is dampened.
Next Designs • Need to plot different Parameter effects to try to determine “ad-hoc” which part of the BGP decision process is causing the # of updates to drop by so much • Once we have that information, we can create new designs which focus directly on our assumptions. New designs will: • In/Validate our assumptions • Quantify the affects of the feature • One statement that can be made already is: “Using the default decision-making algorithm in BGP4 is not a good idea!”