ESnet
Joint Techs, Feb. 2005

William E. Johnston, ESnet Dept. Head and Senior Scientist

R. P. Singh, Federal Project Manager

Michael S. Collins, Stan Kluz,
Joseph Burrescia, and James V. Gagliardi, ESnet Leads

Gizella Kapus, Resource Manager

and the ESnet Team

Lawrence Berkeley National Laboratory

ESnet’s Mission

Support the large-scale, collaborative science of DOE’s Office of Science

Provide high reliability networking to support the operational traffic of the DOE Labs

Provide network services to other DOE facilities

Provide leading-edge network and Grid services to support collaboration

ESnet is a component of the Office of Science infrastructure critical to the success of its research programs (program funded through Office of Advanced Scientific Computing Research / MICS; managed and operated by ESnet staff at LBNL)

ESnet Traffic

Since BaBar (SLAC high energy physics experiment) production started, the top 100 ESnet flows have consistently accounted for 30% - 50% of ESnet’s monthly total traffic

As LHC (CERN high energy physics accelerator) data starts to move, this will increase a lot (200-2000 times)

Both LHC tier 1 (primary U.S. experiment data centers) are at DOE Labs – Fermilab and Brookhaven

U.S. tier 2 (experiment data analysis) centers will be at universities – when they start pulling data from the tier 1 centers the traffic distribution will change a lot

Monitoring DOE Lab ↔ University Connectivity

ESnet Evolution

With the current architecture ESnet cannot address

the increasing reliability requirements

Labs and science experiments are insisting on network redundancy

the long-term bandwidth needs

LHC will need dedicated 10/20/30/40 Gb/s into and out of FNAL and BNL

Specific planning drivers include HEP, climate, SNS, ITER and SNAP, et al

The current core ring cannot handle the anticipated large science data flows at affordable cost

The current point-to-point tail circuits are neither reliable nor scalable to the required bandwidth

ESnet Strategy – A New Architecture

Goals derived from science needs

Fully redundant connectivity for every site

High-speed access to the core for every site (at least 20 Gb/s)

100 Gbps national bandwidth by 2008

Three part strategy

1) Metropolitan Area Network (MAN) rings to provide dual site connectivity and much higher site-to-core bandwidth

2) A Science Data Network core for

large, high-speed science data flows

multiply connecting MAN rings for protection against hub failure

a platform for provisioned, guaranteed bandwidth circuits

alternate path for production IP traffic

3) A High-reliability IP core (e.g. the current ESnet core) to address Lab operational requirements

ESnet MAN Architecture

New ESnet Strategy:
Science Data Network + IP Core + MANs

Tactics for Meeting Science Requirements – 2007/2008

ESnet Services Supporting Science Collaboration

In addition to the high-bandwidth network connectivity for DOE Labs, ESnet provides several other services critical for collaboration

That is ESnet provides several “science services” – services that support the practice of science

Access to collaborators (“peering”)

Federated trust

identity authentication

PKI certificates

crypto tokens

Human collaboration – video, audio, and data conferencing

DOEGrids CA Usage Statistics

DOEGrids CA Usage - Virtual Organization Breakdown

ESnet Collaboration Services: Production Services

ESnet Collaboration Services: H.323 Video Conferencing

Radvision and Codian

70 ports on Radvision available at 384 kbps

40 ports on Codian at 2 Mbps plus streaming

Usage leveled, but, expect increase in early 2005 (new groups joining ESnet Collaboration)

Radvision increase to 200 ports at 384 kbps by mid-2005

Conclusions

ESnet is an infrastructure that is critical to DOE’s science mission and that serves all of DOE

ESnet is working on providing the DOE mission science networking requirements with several new initiatives and a new architecture

ESnet is very different today in both planning and business approach and in goals than in the past


	William E. Johnston, ESnet Dept. Head and Senior Scientist
	R. P. Singh, Federal Project Manager
	Michael S. Collins, Stan Kluz, Joseph Burrescia, and James V. Gagliardi, ESnet Leads
	Gizella Kapus, Resource Manager
	and the ESnet Team
	Lawrence Berkeley National Laboratory


	Support the large-scale, collaborative science of DOE’s Office of Science
	Provide high reliability networking to support the operational traffic of the DOE Labs
	Provide network services to other DOE facilities
	Provide leading-edge network and Grid services to support collaboration
	ESnet is a component of the Office of Science infrastructure critical to the success of its research programs (program funded through Office of Advanced Scientific Computing Research / MICS; managed and operated by ESnet staff at LBNL)


	Since BaBar (SLAC high energy physics experiment) production started, the top 100 ESnet flows have consistently accounted for 30% - 50% of ESnet’s monthly total traffic
	As LHC (CERN high energy physics accelerator) data starts to move, this will increase a lot (200-2000 times)
		Both LHC tier 1 (primary U.S. experiment data centers) are at DOE Labs – Fermilab and Brookhaven
	U.S. tier 2 (experiment data analysis) centers will be at universities – when they start pulling data from the tier 1 centers the traffic distribution will change a lot


With the current architecture ESnet cannot address
	the increasing reliability requirements
		Labs and science experiments are insisting on network redundancy
	the long-term bandwidth needs
		LHC will need dedicated 10/20/30/40 Gb/s into and out of FNAL and BNL
		Specific planning drivers include HEP, climate, SNS, ITER and SNAP, et al
The current core ring cannot handle the anticipated large science data flows at affordable cost
The current point-to-point tail circuits are neither reliable nor scalable to the required bandwidth


Goals derived from science needs
	Fully redundant connectivity for every site
	High-speed access to the core for every site (at least 20 Gb/s)
	100 Gbps national bandwidth by 2008
Three part strategy
	1) Metropolitan Area Network (MAN) rings to provide dual site connectivity and much higher site-to-core bandwidth
	2) A Science Data Network core for
		large, high-speed science data flows
		multiply connecting MAN rings for protection against hub failure
		a platform for provisioned, guaranteed bandwidth circuits
		alternate path for production IP traffic
	3) A High-reliability IP core (e.g. the current ESnet core) to address Lab operational requirements


In addition to the high-bandwidth network connectivity for DOE Labs, ESnet provides several other services critical for collaboration
That is ESnet provides several “science services” – services that support the practice of science
	Access to collaborators (“peering”)
	Federated trust
		identity authentication
			PKI certificates
			crypto tokens
	Human collaboration – video, audio, and data conferencing


	Radvision and Codian
		70 ports on Radvision available at 384 kbps
		40 ports on Codian at 2 Mbps plus streaming
		Usage leveled, but, expect increase in early 2005 (new groups joining ESnet Collaboration)
		Radvision increase to 200 ports at 384 kbps by mid-2005


	ESnet is an infrastructure that is critical to DOE’s science mission and that serves all of DOE
	ESnet is working on providing the DOE mission science networking requirements with several new initiatives and a new architecture
	ESnet is very different today in both planning and business approach and in goals than in the past