Jeremy Johnson

XYZ.com measured from netVMG

Product Overview—Flow Control Platform

Flow Collector - Measurement Active Probes –UDP/ICMP All available paths –Some router config. Measure: –Topology –Performance (Loss, Latency, Jitter) Passive Analysis –User Data Active Path Physical Tap or Spanned switch port Reconstruct Flows Aggregate by prefix Measure: –RTT –Volume

Some Pictures and Stats Active Probes

Some Pictures and Stats Active Probes The best path at any given time yields average latency improvements between 25% and 40% vs. the median and worst paths respectively.

Some Pictures and Stats Passive Analysis

What’s Measured Operator specified list Active prefix by volume or frequency (from netflow/Passive analysis) Active prefix by performance violation

Process Control - Automated Performance Baseline Static thresholds only useful if operator knows what the threshold should be… Proprietary process control algorithms applied to both active and passive measurement provide dynamic thresholds

Flow Director - Route Insertion Route Server injects routes via iBGP –Usually full mesh –No-Export by default ensures routes do not ‘leak’ onto public Internet Routes selected –Via longer prefix (system default /24) –Configurable local preference Internal loop detection and probe feedback ensure destination is reachable and performing well.

Monitoring of key performance, usage/cost, and route change activity indicators Flowview - Summary Reports

Detailed reporting on loss, latency performance, by destination prefix and provider Flowview - Detailed Reports

Path Diversity - How many connections is enough? Convergence point analysis has proven that for a given distribution of prefixes there is an optimal combination of ISPs. Diversity is the key…fewer shared hops generally means more choices and the possibility of better performance. Two ISPs may be enough!

Path Diversity - How many connections is enough? Violations lift Latency lift Of course…the more the better!

For our current customers in the last 30 days… 100% Product Uptime Over 295,000 route changes Average Violation is 40ms 30mb/s Average traffic using the product 99% of detected service level violations fixed 40% Average increase in performance Average decrease in latency is 41ms Highest daily average decrease was 62ms The FCP in action (macro view) 8