EPOC and NetSage

for WestNet

Jennifer Schopf Jason Zurawski

TACC / UT Austin ESnet

EPOC/NetSage is supported NSF award #1826994

Thermodynamics, Economics, and Gravity win

(Dec 1, 2020)

© 2021, Engagement and Performance Operations Center (EPOC)

4

5/12/2021

Data Center Building 1.

….Let me tell you a story….

5

Today’s Discussion

• 5 minutes about EPOC
• Overview of NetSage and its architecture
• Use Cases Walk Through

​

​

​

6

Why an Engagement Operations Center?

• Today’s science is collaborative science
• Collaborative science
• Multiple partners
• Multiple data sets
• Many points of connection
• Cross agency cooperation
• With better access to data we ask harder questions
• Interactive data sources change the science we do

7

Because, remember….

…..We’re building networks to support research and education, not just to have cool networks

8

Engagement and Performance

Operations Center (EPOC)

• Now joint project between Texas Advanced Computing Center (TACC) and ESnet
• Part of CC* program for domestic science support
• Partnerships with regional, infrastructure, and science communities that span the NSF and DOE continuum of funding
• Focus on Smallest Difference for the Biggest Change

​

Core Mission

• Understanding and supporting science use cases
• “Smallest difference for the biggest change”
• Campus, regional, national, and international support
• Debugging any and all network complications via established measurement and monitoring infrastructure
• Data mobility at all layers of the ecosystem:
• Software, hardware, and network
• Work with anyone, focusing mostly on those who aren’t affiliated with an R1 or a large NSF center

10

Current Regional Partners (13)

• Front Range GigaPop (FRGP)
• Great Plains Network (GPN)
• iLight
• KINBER
• Lonestar Education and Research Network (LEARN)
• NJEdge
• NOAA N-wave
• NYSERNet

• Ohio Academic Resources Network (OARnet)
• Pacific Northwest GigaPop (PNWGP)
• Southern Crossroads (SoX)
• Sun Corridor Network (SCN)
• Texas Advanced Computing Center (TACC)

11

EPOC Six Focus Areas Currently

1. Roadside Assistance and Consulting
2. Application Deep Dives
3. Network Analysis (NetSage)
4. Data Mobility Exhibition/Baseline Testing
5. Managed Services
6. Training

​

Roadside Assistance

• “This file transfer worked last week, but it doesn’t anymore?”
• Think of this like a flat tire, crash repair
• Anyone can submit
• Contact epoc@tacc.utexas.edu
• Within 24 hours, gets triaged
• Some initial investigation to verify the issues
• A Case Manager and Lead Engineer are assigned
• Shareable infrastructure set up
• Centralization of Researcher Assistance

​

13

Roadside Assistance - Consulting

• EPOC is an “Ask Me Anything” help desk
• Often simpler questions:
• Suggestions for data architecture choices
• DTNs, DMZs, firewalls
• Data projections for science fields
• Expected (real) performance between two sites
• Advice on how to conduct a performance assessment
• Or others!
• Same operations center approach, aim for 1 business day turnaround for first response

Roadside Assistance is not “normal network engineering problem solving”

• We don’t own any of the resources having problems
• We coordinate with the resource owners and the other networks/systems people
• We can’t always run the tests ourselves
• Must be a collaborative effort
• ​

Soft Failures are Different from Hard Failures

• Many problems are separated in time
• 2 weeks to 2 months or more?
• Many of the problems aren’t just on/off
• Soft failures or decreased performance
• Start of problem almost never clear
• End goal often isn’t clear either

16

EPOC Year 3 RA Overview- 97 Cases

• 28 states including 21 EPSCOR
• 12 countries
• Less than half associated with existing EPOC partner

17

RA Focus: Routing Issues

• End-to-end performance debugging often shows a routing issue

​

• Asymmetric Routes
• Commercial/Commodity paths chosen over R&E
• Smaller pipe chosen due to stale routing configuration
• BGP routing not normalizing to best path after outage

18

Routing Working Group

• Joint Working Group between GNA-G and APAN
• Led by Warrick Mitchell, AARNet, Brenna Meade, IU
• ~150 members
• Monthly meetings with discussions of ongoing routing cases and occasional tool talks
• https://www.gna-g.net/join-working-group/gna-g-routing-wg/
• List: routing-wg@lists.gna-g.net
• Contact meadeb@iu.edu to join

19

RA Focus: MTU settings impacting performance

​

• MTU mismatches between networks AND internal to networks
• Non standard MTU changes made or required by commercial DDOS scrubbing services
• Path MTU Discovery blocked by security appliances and ACL’s

​

• Quick guide to explain and help fix: https://epoc.global/wp-content/uploads/About-MTUs.pdf

20

RA Current Lessons Learned

• Soft failures are hard (and can come back)
• Smallest change for the biggest difference
• This is NEVER the optimal change for the BEST outcome
• Socio-political issues are always in play
• We try to document common problems to help as many others as we can
• Huge need in the community for this type of work

21

EPOC Deep Dive Vision

• Think of this as regular maintenance,

oil change, or planning to buy a car

• Based on ESnet facility req’ts reviews
• Walk through science workflow with the

actual scientists

• Way to understand needs and planning
• Often identifies issues that have nothing to do with networks, and everything to do with sociology

​

Deep Dive Overview

• Formal mechanism via structured conversations to determine shared understanding of CI needs
• Bring together a cross section of campus
• Network users (researchers)
• Administrators
• Technology providers
• Try to find common problems and paths forward
• In-person component a significant value add
• Eighteen Deep Dive reports available at https://epoc.global/materials

Deep Dive: Face-to-Face Discussion

• Bring together researchers, IT staff, research admin
• Create a shared vision to go forward
• Share information for strategic programs, initiatives
• Guide organizational strategy
• Build relationships with constituents
• Identify and resolve network-related issues, existing or anticipated

We Walk Through Scientific Components…

1. Background information
• Brief overview of the facility, nature of the science being performed
2. Collaborators
• Identify people and institutions that a science group interacts with
3. Instrumentation
• Local and remote scientific instruments and facilities.
4. Process of Science
• Explain ‘a day in the life’ of the science group
• Should tie together the instruments, the people, and the resources

​

And Also More Technical Aspects…

5. Software Infrastructure

6. Network and Data Architecture

7. Cloud Services

8. Outstanding Issues and Pain Points

​

Local and regional IT staff are critical for this information, and help form valuable partnerships that may not exist or could use strengthening

Virtual Deep Dives (Shallow Splash)

• Streamlined Case Study document
• Video sessions
• Walk local IT staff through process
• Local IT work with application folks (usually only 1 or 2)
• Series of Focus Group video calls
• walk through the data
• identify the CI needs and requirements
• Combine the data and observations into a report
• Sometimes another video session
• Report made public

27

Deep Dive: Outputs

• Identify and analyze technical gaps/bottlenecks or opportunities
• Forecast technology/network capacity needs, particularly in regions where a site is anticipating increases or decreases in data l
• Help inform investments in network improvements, bandwidth needs, or other application services
• Create long-term, relationships with researchers, IT staff and administration to provide ongoing consultation and support

Deep Dives So Far

• Eighteen Deep Dive reports available at https://epoc.global/materials
• Four more in various stages
• prep, meeting, writing
• We get MANY more requests than we can do

​

• Train the trainers with regional partners going slowly

29

Deep Dive Futures

• Producing a “horizontal cut” for specific instrument-based research
• General recommendations for an instrument workflow
• Base on several specific use cases and institutions
• Producing “vertical cuts” for specific disciplines, that may be advancing faster than CI team can support
• eg. Lessons learned across institutions related to the fields of genomics

30

Deep Dive Futures (2)

• How to address the technology concerns
• HIPAA-compliant computing and storage
• Secure data transfer
• Policies for information sharing
• Streamline Publication of Results
• Organization of published results in the Knowledge Store for easy searching and reuse

31

Data Mobility Exhibition (DME)/

Baseline Performance Testing

• One TeraByte of data in an hour
• Equivalent to 2.22 Gb/s average
• Achievable for institutions connected at 10G
• How to find out?
• DME has known good endpoints to test against
• Variety of data sizes you can transfer
• Standard Globus set up
• And if you can’t?
• Work with EPOC to find the bottlenecks!

Example: University Idaho to UCAR/NCAR

33

EPOC Going Forward

• Proactively work with people, using NetSage and DME, to understand and correct performance BEFORE someone complains
• What if we had expected transfer rates between major sites or for identified large users?
• Helping even a subset has the side effect of helping others

34

Training

• Follow on to OIN (http://oinworkshop.com)
• Reached over 750 people in 3 years
• Hands on perfSONAR sessions
• Especially for small nodes, includes file transfer tests
• “How to talk to Scientists”
• DMZ/DTN Set Up
• Hard part - shifting to more use, less install

Joint work with University South Carolina

• Two-day online hands-on workshops
• Often joint with a regional network
• Introduction to tools and techniques for the design, implementation, and monitoring
• Lab exercises on “pods” emulating networks and tools
• Topics
• Network tools and architecture
• Use of perfSONAR
• BGP attributes and configuration

http://ce.sc.edu/cyberinfra/workshop_2022.html

36

How EPOC Relates

37

EPOC:

Understanding and supporting science use cases

Smallest difference for the biggest change

Debugging any and all network complications�Data mobility across ecosystem: sw, hw. nw

Targeted work with anyone, focusing mostly on those who aren’t affiliated with an R1 or a large center

CaRCC/RCD:

CI community for Research Data Computing

Broad set of focus areas, including workforce, emerging centers, practitioners

CI focused, not science focused

NRP:

National overlay network that joins distributed computational resources

Novel tech and connections

Focus on largest of large applications

XSEDE/ACCESS:

Links and supports NSF computational & storage resources

Robust and broad communities

Networking and data mobility are not a core focus

TrustedCI

NSF #1920430

​

XSEDE/ ACCESS

NSF #1548562

CaRCC

CI CoE:

RCD Resource & Career Ctr

NSF #2100003

CI CoE:

CI Compass

NSF #2127548

​

NRP

NSF #2112167

​

​

​

​

EPOC

NSF #1826994

CI Compass:

Support NSF Major Facilities

Focus - data lifecycle

Not looking at data movement, smaller projects

Trusted CI:

All aspects of the cybersecurity landscape and how it relates to R&E use

Library of training and reference materials built internally, and through community collaboration

Any Questions on the Rest of EPOC Before I go into NetSage in detail?

1. Roadside Assistance and Consulting
2. Application Deep Dives
3. Network Analysis (NetSage)
4. Data Mobility Exhibition/Baseline Testing
5. Managed Services
6. Training

​

Monitoring using NetSage

• NetSage advanced measurement services for R&E traffic
• Better understanding of current traffic patterns across instrumented circuits
• Better understanding of large flow sources/sinks
• Performance information for data transfers
• Started as collaboration between Indiana University, LBNL, and University Hawaii Manoa
• Now all development at TACC
• Backend support/Deployments at both TACC and IU
• 2021: 2,500+ unique users in 85+ different countries

39

NetSage Data Sources

• SNMP data (Passive)
• Basic bandwidth data
• perfSONAR (Active)
• Active tests between sites
• Flow data from routers (Passive)
• Only de-identified data collected by NetSage
• Tstat-based traffic analysis for archives (Passive)
• TCP flow statistics: congestion window size, number of packets retransmitted, etc
• Also de-identified before stored

40

NetSage Ingest

41

Ingest Pipeline

Ingest Pipeline

Flow Data collection

• Flow data is redirected to a collection point, de-identified, and then sent to NetSage archive
• Collection point
• IU collection point - BEING DISCONTINUED
• Docker container on resources at site’s institution
• https://netsage-project.github.io/netsage-pipeline/docs/deploy/docker_install_simple
• Docker container run as a service on an existing server
• Linux or MacOS
• Can be anywhere your router has access to across regular IP routing
• If you choose this option, you have to do updates, not us

42

NetSage Privacy

• NetSage is committed to privacy, and preemptively addressing any security or data sharing concerns
• No Personally Identifiable Information (PII) collected
• Remove the last octet from IP address
• Only keep data on flows over 10M for circuits
• 1M for archives
• Data Privacy Policy
• http://www.netsage.global/home/netsage-privacy-policy
• Data Flow Data Retention (De-Identification) Policy
• https://tinyurl.com/netsage-deid
• Prototypes are behind a password until we’re told to make it public

​

43

NetSage - Built around answering questions

• Answers questions asked by network engineers, network owners, and end-users
• Human-readable summaries and patterns
• Big picture overview helps highlight trends and events that can make in-depth analysis of local data more fruitful

44

Built around answering questions:

45

Interesting pattern. What does it mean?

Singapore to Taiwan via LA?

Why so slow?

NetSage Focus on Use Cases and Questions

• Flow Data Dashboards
• What are the top sites using my circuits?
• What are the top sources/destinations for an organization?
• Who’s using my archive?
• Debugging dashboards
• What are the flows like between these two orgs?
• There was a performance spike on my circuit – what was it?
• Who’s transferring a lot of data really slowly?
• If SNMP data then Bandwidth Dashboard:
• How much are the links used?
• Where are congestion points?

​

​

46

EPOC NetSage Deployments

FRGP: SNMP, Flow

GPN: SNMP, Flow

iLight: Flow

LEARN: SNMP, Flow

PNWGP: SNMP, Flow

SoX: SNMP, Flow

Sun Corridor: Flow

TACC: Flow

47

Sample NetSage - FRGP

https://frgp.netsage.global/grafana/d/xk26IFhmk/flow-data-for-circuits?orgId=1&from=1673762400000&to=1674453599000

​

48

FRGP Front Page: https://frgp.netsage.global

49

Pick the question to answer

Change the timeframe

50

Top Pairs as a table

51

52

53

54

55

Bandwidth Data from SNMP

56

Bandwidth data from SNMP per-circuit

57

What do flows like like for my institution?

58

59

Sun Corridor - Top Senders over Time

60

Sun Corridor - Top Receivers over Time

61

62

Sun Corridor General Information

63

64

65

Click on institution

OR

Click on spinning S, then pick “What are top flows by organization”;

then type in institution’s name

​

66

67

Click on UT Austin (or Individual Flows and set the other end to UT Austin…)

68

69

Protocols and Ports

70

Everything we know about one of the flows

71

72

NetSage Great Plains Network

73

74

From another example -

Regular backup/sync with the cloud…

…but, did we know this was happening? Should the performance be better?

75

76

Using SWIP for better Organizational Detail

• NetSage pipeline Does IP -> ASN -> Organization
• Any organization that doesn't have its own ASN, gets reported as the ASN in the flow
• Example: Instead of "Anderson Univ.", those flows get classified as I-Light
• But we can use SWIP to specify these secondary organizations
• FRGP example: UCAR uses SWIP to map a portion of the IP space to AHEC
• We can do the same elsewhere if networks they tell us which netblocks have been SWIP’d

77

Adding Data to the Science Registry

• Science Registry data contributions are done by resource owners generally
• NetSage staff never has access to the full IP
• Simple Excel spreadsheet
• IP # (or range)
• Project name
• Science disciplines (based on NSF list)
• We collect additional data, if available
• Contact us if you’d like to contribute

78

Global Science Registry

• Maps flows to specific resources to Project name
• DTN
• Instrument
• Compute
• Contributions come from resource owners
• Currently matched by IP, however packet marking is in the roadmap for development

79

Heat Map - Darker is more by volume

80

Sun Corridor - Geo traffic

81

Science Data Patterns

82

83

84

85

If we also had SNMP Data: Analysis

• Analysis board
• https://nea3r.netsage.global/grafana/d/VuuXrnPWz/flow-analysis?from=now-7d&to=now

​

• You can zoom in on a time frame to see what flows relate to a SNMP burst

​

86

Things that we’ve added…

• Who is transferring a lot of data to/from my organization but getting poor performance?
• Set an end point
• Pick a minimum data size
• Pick a maximum transfer rate
• Longer term viewpoints
• How have my Top Talkers changed over the last 2 years?

​

87

88

Another Use Case

• A Regional Network asked EPOC for help in understanding the science drivers prior to submitting to the CC* program
• Working with 4-5 smaller schools
• Marla Meehl
• Colorado Mesa, Colorado Community College, Western Colorado, etc
• FRGP NetSage page (https://frgp.netsage.global)
• Select by organization, type in school name
• Expand the dates
• Click to see some details
• However-
• Only to subnet
• Only flows over 10M

89

90

91

Sometimes the heatmap is more helpful to see patterns

92

93

• If you don’t have NetSage in your area yet, you can try the “all” portal (https://all.netsage.global)
• Look at sensor name at bottom to drill down and broaden dates etc

94

Who’s transferring data to/from U Wyoming?

On the “all” portal

95

On the “all”portal

​

96

On the CENIC portal

97

Ah - CENIC in Denver, that makes more sense

98

99

NOAA and NetSage

• Organization name comes from AS Number (WhoIs DB)
• Blocks of IPs
• NOAA has a lot of these:
• NOAA
• NOAA-Boulder
• NOAA Geophysical Fluid Dynamics Laboratory
• NOAA / PMEL
• National Oceanic and Atmospheric Administration
• NIST/U.S. Dept. of Commerce

…. And more!

​

100

What orgs connected to iLight are transferring data with NOAA in Boulder?

101

102

What orgs connected to iLight are transferring data with NOAA in Boulder? (2)

103

What orgs connected to iLight are transferring data with NOAA in Boulder? (3)

• But we’ve been collecting more data for the NSF International Links for longer…

104

NSF International Circuits – Flow Data Collectors

105

NOAA over NSF International Links- To

106

What orgs connected to NSF links are transferring data with NOAA in Boulder?

107

What orgs connected to NSF links are transferring data with NOAA in Boulder? (2)

108

What orgs connected to NSF links are transferring data to NOAA GFDL?

109

What orgs connected to NSF links are transferring data from NOAA GFDL?

What else can I see about the GFDL-Chonbuk flows?

110

Set Source

Set Dest

111

What else can I see about the GFDL-Chonbuk flows? (2)

112

What do the GFDL-Chonbuk flows look like over time? - Volume

113

What do the GFDL-Chonbuk flows look like over time? - Rate

NSF International Circuits – Flow Data Collectors

114

What path?

115

Change Sensor

What path? (2)

116

Change Sensor

Jason Zurawski [4:10 PM]: the path is just a bit weird in general…

​

6 irb.3901.brtr.denv.nwave.noaa.gov (137.75.72.10) 6.926 ms 6.906 ms 6.911 ms

7 137.75.72.131 (137.75.72.131) 7.157 ms 7.160 ms 7.151 ms

8 et-4-3-0.3532.rtsw.seat.net.internet2.edu (198.71.46.247) 32.380 ms 32.397 ms 32.390 ms

9 et-4-0-0.4070.rtsw.port.net.internet2.edu (162.252.70.82) 36.150 ms 36.090 ms 36.160 ms

10 et-3-0-0.4070.rtsw.sunn.net.internet2.edu (162.252.70.85) 49.405 ms 49.428 ms 49.405 ms

11 et-2-1-0.4070.rtsw.losa.net.internet2.edu (162.252.70.71) 56.335 ms 56.352 ms 56.347 ms

12 vlan-966.rtr.hong.transpac.org (198.71.45.137) 255.984 ms 256.047 ms 233.723 ms

13 134.75.107.17 (134.75.107.17) 196.534 ms 219.096 ms 219.091 ms

14 kreonet2-hongkong.daej.kreonet2.net (134.75.105.17) 226.032 ms 194.154 ms 194.062 ms

15 kreonet-dj-bb1-kreonet2-gr-bb2.daej.kreonet2.net (134.75.105.113) 215.589 ms 193.395 ms 193.388 ms

16 134.75.8.22 (134.75.8.22) 217.603 ms 195.386 ms 195.470 ms

17 210.98.55.2 (210.98.55.2) 224.620 ms 247.868 ms 246.877 ms

so NOAA TIC in Denv to Seat, then down to LOSA, then across transpac to hong kong

117

Path….

• NOAA TIC in Denv
• Seattle
• Down to Los Angeles
• Across the Hawaii-Guam-Hong Kong link (sensor in Hong Kong)
• Hong Kong to KREONet/S. Korea

​

• But then we tried another endpoint…

118

• 2 ae-6.705.rtr.boul.nwave.noaa.gov (137.75.72.65) 0.206 ms 1.459 ms 1.487 ms
• 3 ae-7.0.rtr.denv.nwave.noaa.gov (140.172.88.18) 7.162 ms 7.192 ms 7.243 ms
• 4 lo-0.1.rtr3.denv.nwave.noaa.gov (140.172.112.9) 7.222 ms 7.161 ms 7.261 ms
• 5 137.75.72.13 (137.75.72.13) 6.742 ms 6.768 ms 6.767 ms
• 6 irb.3901.brtr.denv.nwave.noaa.gov (137.75.72.10) 18.788 ms 7.000 ms 17.452 ms
• 7 137.75.72.131 (137.75.72.131) 7.128 ms 7.175 ms 7.110 ms
• 8 et-4-3-0.3532.rtsw.seat.net.internet2.edu (198.71.46.247) 32.134 ms 32.192 ms 32.166 ms
• 9 kreonet-1-lo-jmb-706.sttlwa.pacificwave.net (207.231.240.6) 32.326 ms 32.302 ms 32.299 ms
• 10 kreonet2-seattle.daej.kreonet2.net (134.75.105.81) 141.961 ms 141.974 ms 141.923 ms
• 11 kreonet-dj-bb1-kreonet2-gr-bb2.daej.kreonet2.net (134.75.105.113) 142.153 ms 142.065 ms 142.127 ms
• 12 134.75.8.22 (134.75.8.22) 143.961 ms 144.067 ms 143.814 ms
• 13 ps.jenj.kreonet.net (210.98.55.18) 143.810 ms 143.663 ms 143.720 ms

119

So this path was…

• Nwave to Seattle
• Over KREONet Seattle-Daejong S. Korea
• Then to the university

​

​

​

120

Return Path:

1 gateway (210.117.228.1) 0.299 ms 0.461 ms 0.626 ms

2 134.75.14.6 (134.75.14.6) 0.429 ms 0.556 ms 0.736 ms

3 134.75.105.241 (134.75.105.241) 0.755 ms 0.814 ms 0.836 ms

4 seattle-kreonet2.seat.kreonet2.net (134.75.105.82) 110.118 ms 110.131 ms 110.119 ms

5 abilene-1-lo-jmb-706.sttlwa.pacificwave.net (207.231.240.8) 110.211 ms 110.228 ms 110.223 ms

6 et-4-0-0.4079.rtsw.miss2.net.internet2.edu (162.252.70.0) 120.847 ms 120.765 ms 120.814 ms

7 et-4-0-0.4079.rtsw.minn.net.internet2.edu (162.252.70.58) 144.183 ms 144.208 ms 143.942 ms

8 et-1-1-5.4079.rtsw.eqch.net.internet2.edu (162.252.70.106) 152.047 ms 152.062 ms 152.116 ms

9 ae-0.4079.rtsw3.eqch.net.internet2.edu (162.252.70.163) 152.113 ms 152.021 ms 152.060 ms

10 ae-1.4079.rtsw.clev.net.internet2.edu (162.252.70.130) 177.572 ms 160.933 ms 160.930 ms

11 ae-0.4079.rtsw.ashb.net.internet2.edu (162.252.70.128) 168.358 ms 168.397 ms 168.263 ms

12 et-11-3-0-1275.clpk-core.maxgigapop.net (206.196.177.2) 170.035 ms 170.070 ms 170.126 ms

13 nwave-clpk-re.demarc.maxgigapop.net (206.196.177.189) 169.990 ms 170.215 ms 170.180 ms

14 lo-0.1.brtr.wash.nwave.noaa.gov (137.75.100.7) 170.921 ms 170.969 ms 171.090 ms

15 137.75.68.19 (137.75.68.19) 170.778 ms 170.804 ms 170.721 ms

16 irb.3903.rtr3.wash.nwave.noaa.gov (137.75.68.22) 171.369 ms 171.201 ms 171.932 ms

17 ae-3.2.rtr.wash.nwave.noaa.gov (140.172.70.100) 175.550 ms 175.488 ms 175.806 ms

18 140.208.63.9 (140.208.63.9) 176.860 ms 176.797 ms 175.603 ms

121

Return Path

• KREONet to Seattle
• I2 Seattle to Maryland
• Nwave Maryland to GFDL

122

123

What else can I learn about this interaction – zooming in

124

Lets Zoom In

Zoom In

125

Time Frame

Zoom In (2) – Every 5 minutes…?

126

Zoom In (3)

127

Other Time Frame

Performance of the Individual Flows

• 336 Flows
• Rate: 67Mbps to 7.3Mbps (Average - 52.6 Mbps)
• Volume: 11.1GB down to 253 MB
• Duration: 2min to 20 min

​

128

So…. Now what?

• Would be interesting to figure out what the most effective path is, and make sure it’s being used
• Would be interesting to look at the performance
• Would be interesting to find out what the science is

​

129

130

What NetSage Does Best

• Answers questions asked by network engineers and network owners
• Human-readable summaries and patterns
• Gives people the higher level pattern so they can narrow down a time frame and then use local tools that have more detail
• Simplifies and makes accessible basic data

​

131

Takeaways

• EPOC resources are available to anyone and everyone
• NetSage can help you understand data transfers - when your data touches one of our collection points

​

• FRGP NetSage Dashboard: http://frgp.netsage.global
• Sun Corridor NetSage Dashboard: http://suncorridor.netsage.global
• Questions? Contact:
• Jennifer Schopf - jms@tacc.utexas.edu

​

​

NetSage is funded by US NSF award #1540933

EPOC is funded by US NSF award #1826994

132

Acknowledgements

• NetSage is funded by
• US NSF award #1826994 for EPOC
• US NSF award #2137603, subaward to TACC, for NetSage on ACCESS
• ​

​

133