ESnet On-Demand Secure Circuits and Advance Reservation System (OSCARS)

1. Internet2 Joint Techs Workshop July 18, 2005 ESnet On-Demand Secure Circuits and Advance Reservation System (OSCARS) David Robertson (dwrobertson@lbl.gov)

2. Components That Make Up OSCARS (1/2) Guaranteed Bandwidth Circuit • Multi-Protocol Label Switching (MPLS) and Resource Reservation Protocol (RSVP) is used to create a Label Switched Path (LSP) • Quality-of-Service (QoS) level is assign to the LSP to guarantee bandwidth. LSP between ESnet border routers Source Sink RSVP, MPLS enabled on internal interfaces MPLS labels are attached onto packets from Source and placed in separate queue to ensure guaranteed bandwidth. Regular production traffic queue. Interface queues

3. Components That Make Up OSCARS (2/2) Reservation Manager • Web-Based User Interface (WBUI) will prompt the user for a username/password and forward it to the AAAS. • Authentication, Authorization, and Auditing Subsystem (AAAS) will handle access, enforce policy, and generate usage records. • Bandwidth Scheduler Subsystem (BSS) will track reservations and map the state of the network (present and future). • Path Setup Subsystem (PSS) will setup and teardown the on-demand paths (LSPs). Reservation Manager User request via WBUI Web-Based User Interface Path Setup Subsystem User Instructions to setup/teardown LSPs on routers User feedback Authentication, Authorization, And Auditing Subsystem Bandwidth Scheduler Subsystem User Application User app request via AAAS

4. ESnet OSCARS Collaboration with Internet2 (2Q05) • ESnet hosted a 2-day working meeting with Internet2’s Bandwidth Reservation for User Work (BRUW) project. • A decision to jointly develop code for OSCARS and BRUW was agreed upon. This is possible because OSCARS and BRUW have very similar architectures. We have adopted their WBUI, but are rewriting a substantial portion of the back-end. They are interested in using our PSS and potentially the BSS. Joint development of the AAAS may be complicated by different security requirements. • Dynamic setup of an inter-domain LSP circuit (between ESnet and Internet2) is targeted for the SC05 timeframe.

5. ESnet OSCARS First Production Use of OSCARS Circuits (2Q05) • OSCARS functionality was pressed into service when the production LHC 10GE connectivity between FNAL and CERN was disrupted due to a fishing boat severing CERN’s link to Chicago. • As a result of the cut link, LHC Service Challenge data was rerouted over FNAL’s production OC12 (622mb/s) causing severe congestion. • As a temporary measure, an OSCARS circuit carrying only LHC traffic was configured between 32AoA (in New York) and Starlight (in Chicago). This caused the LHC traffic to traverse FNAL’s non-production connection at Starlight, offloading the production OC12.

6. ESnet OSCARS First Beta Tests with End Users (2Q05) General Atomics (GA) • Sean Flanagan of GA performed several tests transferring fusion data from an MDSPlus server in GA to a client at the NERSC facility in Oakland (OSF) using OSCARS reserved circuit. Internet End-to-end Performance Monitoring (IEPM) • Les Cottrell of SLAC performed several tests with and without the set up of OSCARS reservations http://www-iepm.slac.stanford.edu/dwmi/oscars/. • The next slide shows a graph of jitter measurement with and without an OSCARS reservation.

7. IEPM OSCARS-91 Jitter Measurement

8. ESnet OSCARS Additional Collaborations: • TeraPaths: A QoS Enabled Collaborative Data Sharing Infrastructure for Peta-scale Computing Research (Dantong Yu, Brookhaven National Lab) • Network Quality of Service for Magnetic Fusion Research (David Schissel, General Atomics) • Internet End-to-end Performance Monitoring (Les Cottrell, SLAC) • Bandwidth on Demand (GN2-JRA3) (Maarten Büchli, Michael Enrico, DANTE)

9. ESnet OSCARS Web site: • http://www.es.net/oscars/ Contacts: • Chin Guok (chin@es.net) • David Robertson (dwrobertson@lbl.gov)