MeasuRouting: A Framework for Routing Assisted Traffic Monitoring – projects 2012
Technology Used: Java
Monitoring transit traffic at one or more points in a network is of interest to network operators for reasons of traffic accounting, debugging or troubleshooting, forensics, and traffic engineering. Previous research in the area has focused on deriving a placement of monitors across the network towards the end of maximizing the monitoring utility of the network operator for a given traffic routing. However, both traffic characteristics and measurement objectives can dynamically change over time, rendering a previously optimal placement of monitors suboptimal. It is not feasible to dynamically redeploy/reconfigure measurement infrastructure to cater to such evolving measurement requirements. This problem is addressed by strategically routing traffic sub-populations over fixed monitors. This approach is MeasuRouting. The main challenge for MeasuRouting is to work within the constraints of existing intra-domain traffic engineering operations that are geared for efficiently utilizing bandwidth resources, or meeting Quality of Service (QoS) constraints, or both. A fundamental feature of intra-domain routing, that makes MeasuRouting feasible, is that intra-domain routing is often specified for aggregate flows. MeasuRouting, can therefore, differentially route components of an aggregate flow while ensuring that the aggregate placement is compliant to original traffic engineering objectives.
Several past research efforts have focused on the optimal deployment of monitoring infrastructure in operational networks for accurate and efficient measurement of network traffic. Such deployment involves both monitoring infrastructure placement as well as configuration decisions. An example of the former includes choosing the interfaces at which to install DAG cards, and the latter includes tuning the sampling rate and sampling scheme of the DAG cards. The optimal placement and configuration of monitoring infrastructure for a specific measurement objective typically assumes a priori knowledge about the traffic characteristics. Furthermore, these are typically performed at longer time scales to allow provisioning of required physical resources. However, traffic characteristics and measurement objectives may evolve dynamically, potentially rendering a previously determined solution suboptimal.
MeasuRouting forwards network traffic across routes where it can be best monitored.
MeasuRouting takes monitor deployment as an input and decides how to route traffic to optimize measurement objectives.
Since routing is dynamic in nature (a routing decision is made for every packet at every router), MeasuRouting can conceptually adjust to changing traffic patterns and measurement objectives.
The overall monitoring utility, defined as a weighted sum of the monitoring achieved over all flows, is the primary concern.
The framework is generic
It can be leveraged for a wide variety of measurement scenarios.
The main challenge for MeasuRouting is to work within the constraints of existing intra-domain traffic engineering (TE) operations that are geared for efficiently utilizing bandwidth resources, or meeting Quality of Service (QoS) constraints, or both. This paper presents a framework for MeasuRouting that allows rerouting traffic towards the end of optimizing an ISP’s measurement objectives, while being compliant to TE constraints.