4 October 2001Smith/Germain/Loiacono1 Earth Observing System: Measuring the Benefit of Internet2 for Science Data Distribution Jeff Smith Joe Loiacono Andy Germain NASA EOS - GSFC

4 October 2001Smith/Germain/Loiacono2 Outline EOS Overview –EOS Program –EOS Data and Information System Network Measurements –Data Collection Abilene Traffic Loads Abilene Utilization Server Statistics –Active Testing Future Plans

4 October 2001Smith/Germain/Loiacono3 The Earth Observing System (EOS) is the centerpiece of NASA's Earth Science Enterprise (ESE). It consists of a science component and a data system supporting a coordinated series of polar-orbiting and low inclination satellites for long-term global observations of the land surface, biosphere, solid Earth, atmosphere, and oceans. By enabling improved understanding of the Earth as an integrated system, the EOS program has benefits for us all. The EOS Project Science Office (EOSPSO) is committed to helping bring program information and resources to program scientists and the general public alike. EOS Overview

4 October 2001Smith/Germain/Loiacono4 Terra Mission - launched December 1999 The Terra (formerly AM-1) satellite is the flagship of NASA's ESE (Earth Science Enterprise). Terra is the first EOS platform and provides global data on the state of the atmosphere, land, and oceans, as well as their interactions with solar radiation and with one another. Aqua Mission - rescheduled: early 2002 Aqua will collect climate-related data. Its on-board sensors will measure clouds, precipitation, atmospheric temperature/moisture content, terrestrial snow, sea ice, and sea surface temperature during its six-year mission. Flying in low-earth orbit, Aqua will pass over the equator at the same time each afternoon, allowing the comprehensive measurements needed to assess long-term change. Aura ICEsat Mission - scheduled: July, 2003 The EOS - Chemistry satellite hosts a suite of scientific instruments designed to make the most comprehensive measurements ever undertaken of atmospheric trace gases. Its objective is to study the chemistry and dynamics of the Earth's atmosphere with emphasis on the upper troposphere and lower stratosphere (0-30km). The mission will measure ozone, aerosols, and several key atmospheric constituents that play an important role in atmospheric chemistry, air quality, and climate. Current and Upcoming EOS Missions

4 October 2001Smith/Germain/Loiacono5 EOS Missions

4 October 2001Smith/Germain/Loiacono6 EOS Platforms, Instruments, and Science Objectives

4 October 2001Smith/Germain/Loiacono7 The EOS Data and Information System (EOSDIS) is designed to operate the satellites and instruments, capture the satellite data, generate useful Earth science data products, and make the products available to users in the U.S. and throughout the world. The two major parts of EOSDIS are Mission System and Science System. The Mission System commands and controls EOS spacecraft and instruments, monitors their health and safety, and performs mission planning and scheduling, initial data capture, and initial data processing. The Science System generates higher level data products suitable for analysis by NASA principal investigators and the general scientific community. EOSDIS - EOS Data Infrastructure

4 October 2001Smith/Germain/Loiacono8 NASA EOS Satellites and Instruments Other NASA Satellites with EOS Instruments ESA Satellites with EOS Instruments NASDA Satellites with EOS Instruments EOSDISCommuicationsEOSDISCommuications NSIDC ASF EDC GSFC JPL LaRC ORNL ExternalCommunicationsExternalCommunications Value Added Providers Investigators Instrument Support Terminals Science Computing Facilities External Data Users Science Computing Facilities Distributed Active Archive Centers EMSnet ESSnet EDOSEDOS EBnet EOSDIS Enterprise

4 October 2001Smith/Germain/Loiacono9 Mid-Atlantic Crossroads EOSDIS Network Architecture vBNS+ Chi NISN

4 October 2001Smith/Germain/Loiacono10 Data Product Levels Raw Telemetry - as transmitted from spacecraft –Instruments multiplexed, CCSDS frames Level 0: Instrument telemetry –Time stamped, Reed-Solomon decoded, fill data, etc. Level 1: Instrument Measurements –Calibrated, georeferenced Level 2: Scientific Parameter Retrieval –Inferred geophysical properties –Corresponding to individual instrument measurements Level 3: Gridded –Interpolated / extrapolated to useful space/time coordinates Level 4: Integrated –E.g., Multiple instruments, movie loops

NET DAAC QA SCF EOS LaRC

4 October 2001Smith/Germain/Loiacono12 Data Collection Overview Data Collected –Traffic loads on key interfaces –Traffic volumes overall –Traffic volumes to sites –Traffic per host (sender & receivers - not included) –Traffic characteristics (ports, types - not included) Purposes –Historical data and trends vs. requirements –Planning –Troubleshooting –Security –Who’s doing what to whom on the EOS network

4 October 2001Smith/Germain/Loiacono13 GSFC DAAC Router interface to Abilene - Science data product transfers from GSFC to Principal investigator sites located at Abilene member universities continues to grow. - Note: Traffic loading on other key interfaces is not included in presentation Abilene Traffic Loads

4 October 2001Smith/Germain/Loiacono14 EROS Data Center Sioux Falls, SD NSIDC Colorado Springs, CO LARC Langley, VA GSFC Greenbelt, MD NetFlow Collector: cflowd ARTS reports and Custom Scripts EOS Performance Web-site - Cisco NetFlow data is sent from EOS routers at above locations to ‘cflowd’ collector at GSFC every few seconds throughout the day. ARTS and custom scripts are run automatically every night producing web-based reports. Data is compressed and archived every week. * ‘cflowd’ and ARTS software is maintained by CAIDA. Utilization Data Collection Process

4 October 2001Smith/Germain/Loiacono15 - EOS use of Abilene for science data product transfers from GSFC to Abilene partner institutions is significant Daily Quantities of EOS Science Data to Abilene Partners Abilene Science Data Utilization

4 October 2001Smith/Germain/Loiacono16 Top EOS Partner Institutions using Abilene - Custom scripts that interpret Cisco’s NetFlow data keep track of major EOS Partners using Abilene to efficiently retrieve data from GSFC Top Users of Traffic to Abilene

4 October 2001Smith/Germain/Loiacono17 EOS Science data products delivered to U. Miami over Abilene - University researchers use Abilene for efficient retrieval of large science data sets. U Miami is largest single EOS partner institution using Abilene to retrieve science data products from GSFC, often extracting over 50 Gigabytes daily Utilization for Single Abilene Site

4 October 2001Smith/Germain/Loiacono18 Abilene Statistics for router: GSFC This Abilene Flow Distribution Report was generated at 09/04/ :15:00 for Router: gsfc Total Bytes to Abilene : 173,127,413,068 Pct.: 99 Total Bytes to NSI Router: 670,153,399 Pct.: 0 Organization Name Network Science Bytes Pct. Test Bytes PI Total University of Miami ,163,427, ,098,222, ,261,649,879 University of Wisconsin ,543,093, ,598,416 2,730,692,409 Oregon State University ,157,704, ,779,053,008 3,936,757,009 NCAR ,818, ,936,226,700 5,068,044,868 ECS (2) ,145, ,145,462 University of Alaska ,497, ,497,758 NASDA ,447, ,447,226 University of Maryland (2) ,783, ,000 1,789,506 ECS ,667, ,880 1,673,675 University of Arizona ,627, ,208,195,612 4,209,823,241 JPL ,121, ,604,571,172 2,605,692,507 UC Santa Barbara (2) ,071, ,782, ,853,837 University of Montana ,070, ,665, ,736,366 University College (SCF) , ,299, ,238,160 Ohio State University , ,255, ,061,432 Boston University , ,031,575,652 7,032,322,036 ECS (3) , ,139 University of Alabama (UAH) , ,336 UMBC , ,441 University of Colorado , ,123 UC Berkeley University of Hawaii University of Delaware Total PI data flows (see above) 127,018,694, ,136,457, ,155,152,166 Non-PI data flows (various) 13,363,794, ,608,466,556 20,972,260,902 Total Abilene bytes 140,382,488, ,744,924, ,127,413,068 PI Bytes as pct. of total (Abilene and NSI) 127,018,694, Abilene Daily Report

4 October 2001Smith/Germain/Loiacono19 Customized ARTS Network Report Network Statistics for router: GSFC router: ifIndex: User Network (Fddi1/0/0 198.xxx.yyy.65) period: 09/25/ :58: /26/ :58:41 EDT Src Network Pkts Bytes Destination xxx.yyy.64/ /24 -- NSI Netblock 198.xxx.yyy.64/ /19 -- University of Miami (NET-MIAMI) 198.xxx.yyy.64/ /16 -- NASA Headquarters (NET-JPL-NET) 198.xxx.yyy.64/ /32 -- miracle.rsmas.miami.edu -- University of Miami (NET-MIAMI) 198.xxx.yyy.64/ /24 -- National Aeronautics and Space Administration (NETBLK-NASA-CN 198.xxx.yyy.64/ /16 -- NASA Goddard Space Flight Center (NET-GSFC) 198.xxx.yyy.64/ /16 -- University of Texas (NET-CHPCHYPERHOSE) 198.xxx.yyy.64/ /16 -- University of California, San Diego (NET-UCSD-SUBNETS) 198.xxx.yyy.64/ /16 -- Boston University (NET-BU-NET) 198.xxx.yyy.64/ /16 -- Jet Propulsion Laboratory (NET-JPL-NET2) 198.xxx.yyy.64/ /16 -- National Center for Atmospheric Research (NET-UCAR) 198.xxx.yyy.64/ /16 -- University of Arizona (NET-UNIV-ARIZ) 198.xxx.yyy.64/ /32 -- taichi.icess.ucsb.edu -- University of California, Santa ) 198.xxx.yyy.64/ /16 -- MACC (NET-UWMSN-NET) 198.xxx.yyy.64/ /16 -- CSIRO IT Services (NET-CSIRO-CLAYTON) 198.xxx.yyy.64/ /16 -- Naval Ocean Systems Center (NET-NOSC-ETHER) 198.xxx.yyy.64/ /16 -- University of Utah (NET-UTAH-NET) 198.xxx.yyy.64/ /16 -- Oregon State University (NET-ORST) 198.xxx.yyy.64/ /16 -- University of California, Santa Barbara (NET-UCSB) 198.xxx.yyy.64/ /32 -- matrix4.nsstc.uah.edu -- National Aeronautics and Space 198.xxx.yyy.64/ /24 -- NASA Ames Research Center (NET-EOS-DAAC-NET2) 198.xxx.yyy.64/ /24 -- NSI Netblock 198.xxx.yyy.64/ /16 -- University of Colorado (NET-COLORADO) 198.xxx.yyy.64/ /16 -- University College London (NET-UCL-NET-A) 198.xxx.yyy.64/ / Front Range Internet, Inc. (NETBLK-NET-RII- 198.xxx.yyy.64/ /16 -- Ohio State University (NET-OHIO-STATE)

4 October 2001Smith/Germain/Loiacono20 Sample from Custom Flow Report Detailed Flow Data for External Destinations Source Port Bytes Destination xxx.yyy D 2930 memberdir.netscape.com -- Netscape Communications Corp. (NETBLK- 198.xxx.yyy D (web requests out) 198.xxx.yyy D 6012 (secure web in) 198.xxx.yyy D (web requests out) 198.xxx.yyy D (secure web in) 198.xxx.yyy D (web requests out) 198.xxx.yyy D 2382 (ftp control out) 198.xxx.yyy D (ftp sent out) 198.xxx.yyy D (web requests out) 198.xxx.yyy D NASA Ames Research Center (NET-NSN-NET) 198.xxx.yyy D NASA Ames Research Center (NET-NSN-NET) 198.xxx.yyy.153 0D 720 polaris.umuc.edu -- University of Maryland University College 198.xxx.yyy D polaris.umuc.edu -- University of Maryland University College 198.xxx.yyy D 352 polaris.umuc.edu -- University of Maryland University College 198.xxx.yyy D Cisco Systems, Inc. (NET-SWLAB1) 198.xxx.yyy D 1794 u1.abs.net -- ABSnet Internet Services, Inc. (NETBLK-ABS-NET- 198.xxx.yyy D 1931 mail1.abs.net -- ABSnet Internet Services, Inc. (NETBLK-ABS-NET- 198.xxx.yyy D idyle.com -- Cable & Wireless USA (NETBLK-CW-10BLK) CW-10BLK 198.xxx.yyy D 4066 aim1.radiate.com -- Abovenet Communications, Inc. (NETBLK- 198.xxx.yyy D 234 so mp2.Washington1.Level3.net -- Level 3 Communications, 198.xxx.yyy D 5148 p2.my.vip.snv.yahoo.com -- GeoCities (NETBLK-NETBLK-GEO-1) 198.xxx.yyy D ns1.solarwinds.net -- Southwestern Bell Internet Services 198.xxx.yyy D 468 so mp2.SanJose1.Level3.net -- Level 3 Communications, Inc. 198.xxx.yyy D 468 gigabitethernet9-0.ipcolo1.SanJose1.Level3.net -- Level xxx.yyy D (web requests out) 198.xxx.yyy D 176 polaris.umuc.edu -- University of Maryland University College 198.xxx.yyy D 9151 eos.east.hitc.com -- Performance Systems International (NET-

4 October 2001Smith/Germain/Loiacono21 Server Statistics

4 October 2001Smith/Germain/Loiacono22 Active Testing Overview End-to-end user level test –“Active” testing –little or no visibility into network internals Purposes –EOS: assess whether networks as implemented meet EOS requirements –CEOS: assess whether networks can support intended applications –Resolve user complaints: Network problems -- or somewhere else?? –Determine bottlenecks -- seek routing alternatives –Provide a basis for allocation of additional resources

4 October 2001Smith/Germain/Loiacono23 Active Testing - Process Test script runs hourly to each site: Traceroute (1 way) –Number of hops -- route stability --> Hops Chart Pings –100 pings prior to thruput test or 100/300 during –Round Trip Time --> RTT Chart –Packet Loss --> Packet Loss Chart TCP Throughput –TCPwatch, Iperf, or FTP --> Thruput Chart –requires cooperating client at destination –TCPwatch / Iperf keeps send buffer full for 30 Seconds –Netstat -> packets retransmitted (if pings blocked)

4 October 2001Smith/Germain/Loiacono24 EOS DAAC NASA Nodes SCFs QA Other Key: ORST UCSB Ariz LANL Wisc Miami SUNY-SB BU GSFC LaRC EDC MSFC, NSSTC NCAR Mont JPL Toronto Colo St. Niagara ASF Chicago Other Nodes SLAC NSIDC NMEX CCRS UVA UMD GPN NGDC, NOAA USF RSS US Active Test Sites Texas UCSD Wash Mich NOAA Ohio

4 October 2001Smith/Germain/Loiacono25 On line results Updated Daily – –"Network Health Statistics" GSFC Sites EOS Sites EMSNet Sites CEOS Sites Other sites –Charts: All sources to specified destination Thruput, RTT, Packet Loss, Hop Count –Weekly: 24 measurements per day from each source –60 day: Daily Average –Yearly (RSN)

4 October 2001Smith/Germain/Loiacono26 Sample Chart: BU Thruput (current week)

4 October 2001Smith/Germain/Loiacono27 Sample Chart: BU RTT, Loss (current week)

4 October 2001Smith/Germain/Loiacono28 Sample Chart: BU Thruput (2 months)

4 October 2001Smith/Germain/Loiacono29 Sample Chart: UCSD Thruput (current week)

4 October 2001Smith/Germain/Loiacono30 Sample Chart: UCSD Thruput (2 months)

Mbps Minimum Maximum Median Thruput Range: GSFC to Abilene Sites AZ, Tucson (U of AZ) CA, UCSB CA, UCSD - SIO CO, Colo State Univ CO, NCAR - Boulder FL, Univ. of Miami MA, Boston Univ MD, UMD- College Park MT, Univ of Montana NY, SUNY Stony Brook OH, Ohio State Univ OR, Oregon State Univ. TX, U Texas - Austin VA, UVA

4 October 2001Smith/Germain/Loiacono32 POCs Jeff Smith Joe Loiacono Andy Germain