1 / 11

Hiroyuki Ohsaki Graduate School of Information Sci. & Tech. Osaka University, Japan

On Scalable Edge-based Flow Control Mechanism for VPN Tunnels --- Part 2: Scalability and Implementation Issues. Hiroyuki Ohsaki Graduate School of Information Sci. & Tech. Osaka University, Japan oosaki@ist.osaka-u.ac.jp. 1. State Goals and Define the System. Goals

woody
Télécharger la présentation

Hiroyuki Ohsaki Graduate School of Information Sci. & Tech. Osaka University, Japan

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. On Scalable Edge-based Flow Control Mechanism for VPN Tunnels --- Part 2: Scalability and Implementation Issues Hiroyuki Ohsaki Graduate School of Information Sci. & Tech. Osaka University, Japan oosaki@ist.osaka-u.ac.jp

  2. 1. State Goals and Define the System • Goals • Confirm validity of our I2VFC simulation results • Demonstrate usability of I2VFC in real networks • Examine I2VFC scalability and find its bottleneck in terms of... • Number of VPN flows • Number of TCP/UDP flows • Link bandwidth • System Definition • VPN service provider network including... • ingress and egress PE (Provider Edge) routers • core network devices (routers and links) • but excluding... • VPN sites (CE (Customer Edge) routers, end hosts)

  3. 2. List Services and Outcomes • Services Provided • Congestion control for VPN flows • Active fairness control among VPN flows • Passive fairness control among TCP/UDP flows • Outcomes • High link bandwidth utilization? • Low packet loss probability? • Low packet transfer delay?

  4. 3. Select Metrics • Speed (case of successful service case) • Individual • VPN throughput, round-trip time, packet loss probability • TCP/UDP goodput, round-trip time, packet loss probability • Global • PE router processing time, memory usage, queue occupancy • Reliability (case of error) • None • Availability (case of unavailability) • None

  5. 4. List Parameters • System parameters • Network related • Topology • Link bandwidth, latency, loss ratio • Queue size and discipline (e.g., DropTail or RED) • PE router related • Control parameters (D, a, b, Wmax, Wmin, W0) • Queue size • Workload parameters • # of VPN flows • # of TCP/UDP flows, TCP/UDP traffic pattern • Background traffic pattern

  6. 5. Select Factors to Study • System parameters • Network related • Topology • Link bandwidth, latency, loss ratio • Queue sizeand discipline (e.g., DropTail or RED) • PE router related • Fairness criteria • Control parameters (D, a, b, Wmax, Wmin, W0) • Queue size • Workload parameters • # of VPN flows • # of TCP/UDP flows, TCP/UDP traffic pattern • Background traffic pattern

  7. 6. Select Evaluation Technique • Use analytical modeling? • No • Use simulation? • No • Use measurement of real system? • Yes

  8. 7. Select Workload • # of VPN flows: 2 up to I2VFC limitation • TCP flows • Persistent traffic using iperf (TCP banchmarking tool) • # of TCP flows: 1 -- 100 • Bursty traffic using ? (HTTP traffic generator) • # of TCP flows: 100 • UDP flows • Persistent traffic using iperf (TCP banchmarking tool) • UDP traffic rate: 0 – 70% of the bottleneck link bandwidth • Persistent traffic using ? (VoIP traffic generator) • Background traffic • 30% of the bottleneck link bandwidth

  9. 8. Design Experiments

  10. 9. Analyze and Interpret Data

  11. 10. Present Results

More Related