1 / 7

Framework for Proposed TE and QoS Tests - Project Deliverables -

Framework for Proposed TE and QoS Tests - Project Deliverables -. * To demonstrate end-to-end traffic management across multiple domains using live Grid traffic (TM2) To demonstrate end-to-end QoS and traffic management between the UK and USA (TM3)

toshi
Download Presentation

Framework for Proposed TE and QoS Tests - Project Deliverables -

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. Framework for Proposed TE and QoS Tests- Project Deliverables - *To demonstrate end-to-end traffic management across multiple domains using live Grid traffic(TM2) To demonstrate end-to-end QoS and traffic management between the UK and USA(TM3) To demonstrate end-to-end QoS and traffic management to CERN(TM4) - e-2-e services - separate administrative domains - diffserv, “other” packet marking, TE etc * To understand the use of MPLS as a traffic engineering tool within the CORE SJDN(TM1) - understanding of MPLS - as a basis to configure traffic management for “guaranteed” bandwidth and QoS

  2. Framework for Proposed TE and QoS Tests (1)- Broad Work Areas - Using the defined test traffic The proposed framework falls into two broad areas, 1. Policy-based tests, 1. With and withoutMPLS using Basic packet marking techniques, i.e. using diffserv and QBSS across the extended SJ4/MG-NG test network; 2. Bandwidth broker developments using Expect scripts to make real-time adjustments to router configurations, i.e. policy mapped to scripts leads to router/network reconfig’s. (see work done an U Michigan in this area) 2. Cisco guaranteed b/w developments using MPLS/diffserv/rsvp to model the VPN

  3. Basic Packet Marking Tests - Configuration -

  4. Basic Packet Marking Tests - Test Proposals (1) - For testing between, for example, Manchester and UCL and for each specified Policy - P(C), P(M1), P(M2), P(M3), withoutMPLS enabled in AD(C), and withMPLS enabled in AD(C) the following configurations are required for , 1. diffserv tests 1. diffserv operation in AD(C) only, and 2. diffserv operation in AD(C) plus AD(M1) and AD(M3) 2. QBSS tests 1. QBSS operation in AD(C) only, and 2. QBSS operation in AD(C) plus AD(M1) and AD(M3)

  5. Basic Packet Marking Tests- Test Proposals (2) - For thetest data flows where, for example, Manchester to UCL is being tested, Man -> UCL; Man -> UCL; RAL -> UCL; Man -> UCL; RAL -> Man; Man -> UCL; RAL -> UCL; RAL -> Man; Man->UCL; UCL -> Man; Man->UCL; UCL -> Man; RAL -> UCL; Man->UCL; UCL -> Man; RAL -> Man; Man->UCL; UCL -> Man; RAL -> UCL; RAL -> Man;

  6. Framework for Proposed TE and QoS Tests (2)- Broad Work Areas - Using the defined test traffic The proposed framework falls into two broad areas, 1. Policy-based tests, 1. With and without MPLS using Basic packet marking techniques, i.e. using diffserv and QBSS across the extended SJ4/MG-NG test network; 2. Bandwidth broker developments using Expect scripts to make real-time adjustments to router configurations, i.e. policy mapped to scripts leads to router/network reconfig’s. (see work done an U Michigan in this area) 2. Cisco guaranteed b/w developments using MPLS/diffserv/rsvp to model the VPN

More Related