GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 1 GLAST Large Area Telescope: SLAC – NRL Data Connection for the GLAST LAT Environmental Test Status report for the Environmental Test Planning Meeting March 16 th, 2005 Brian Grist GLAST LAT Integration and Test Gamma-ray Large Area Space Telescope

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 2 Overview NRL-SLAC Network Working Group Contact Information When, Where, What Proposed Solution Network Connection Rate Security Requirements Test Area Network Diagram at SLAC Other Options Explored Meeting Schedule

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 3 NRL-SLAC Network Working Group A working group has been set up to plan the NRL-SLAC network connection. There have been many over the last few weeks getting the points of contact identified (see next page) and to exchange of concepts. The first teleconference/meeting was held yesterday (March 15 th ) to talk about a proposed solution and to capture action items. –Attendees were: Brian Grist (I&T), Bryson Lee (ISOC), Daryl Yentis (NRL), Bill Johnston (ESnet), Jim Gagliardi (ESnet)

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 4 Group Contact Information NRL –Daryl Yentis Naval Research Laboratory (202) ESNet –Bill Johnston ESnet Dept. Head and Senior Scientist Lawrence Berkeley National Laboratory –Jim Gagliardi Energy Sciences Network (ESnet) Lawrence Berkeley National Laboratory (510) SLAC –Brian Grist GLAST LAT Integration and Test (650) –Rob Cameron GLAST LAT Instrument Operations Center (ISOC) (650) –Bryson Lee GLAST LAT Instrument Operations Center (ISOC) (650) –Les Cottrell SLAC Computing Services (650) –Richard Dubois GLAST LAT Science Analysis Software (650)

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 5 When, Where, What When –December 2005 through April 2006 Needs to be available from setup through all tests at NRL Where –NRL - building A59 Action: Daryl to talk to Paul Dizon about locations within building A59 where the test equipment will be located. What does the network connection need to support –Send instrument data back to SLAC during Environmental Tests as file transfers. –Send Test S/W upgrades/fixes to Test Stands from SLAC as file transfers. –Support for ISOC testing

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 6 Proposed Solution Use the existing network infrastructure for file transfer. –NRL DREN ESnet SLAC NRL - Naval Research Laboratory internal network DREN - Defense Research Engineering Network ESnet - Energy Science network SLAC - Stanford Linear Acceleratory Center internal network This is provide a high-speed, two-way connection at little cost to the project The LAT test equipment would have its firewall and machines “registered” with the NRL network. –This will allow us to have specific nodes within the collection of I&T computers made visible for direct access here at SLAC; for example the data server (DMZ) to allow the test data to flow to SLAC. The link is managed and could be set up to notify network and LAT Test Personnel of scheduled outages. –Outages are scheduled and last in the ½ hour timeframe and usually on the weekends. –The LAT does not need a real-time connection as we are only talking about simple file transfers. DREN peers (connects) with ESnet at several points. –Action: Bill Johnston to talk to DREN to discuss which connection point to use. Additionally, access to NRL computers can me made with a VPN account. This is the preferred solution.

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 7 Network Connection Rate 100 Mbps –Same as we currently have at SLAC between the Test Equipment (building 33) and SLAC Computing Services. –NRL can easily support 100 Mbps; This is the standard setup within buildings Between buildings is faster and out of the facility is faster still –DREN and ESnet can support this rate.

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 8 Security Requirements –The LAT systems must conform to NRL/Navy Computer Security requirements. For this, a Memo of Understanding (MOU) between SLAC/Project management, your NRL sponsor (Code 7650) and NRL Network Security would be issued stating that LAT would conform to all NRL Computer Security requirements. Action: Daryl to help setup the MOU –There is an NRL publication with all the specifics will be sent Action: Daryl to send publication –Identify responsible Network Security POCs, list systems, O/S, versions, etc. and certify that the systems have been patched as required. Action: Will need to identify the POC for this activity.

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 9 Test Area Network Diagram at SLAC The current GLAST LAT test setup is isolated by firewall from the rest of SLAC Some subset of this equipment would be traveling to NRL (only an example) From: LAT-PS

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 10 Other Options Explored (not recommended) Direct T3 connection to ESnet –This option would be to connect the GLAST LAT Test equipment directly to ESnet with a rented T3 line. –The initial cost estimate is outside of the scope feasibility with the current funding. Approx. $70,700 – ($48,400 in non-recurring and a total of $22,300 for 5 months in recurring) The possibility of using a recycled router could lower the cost –Would only provide less than 43Mbps. –This choice was deemed to costly and would not provide the same capacity connection so is NOT recommended.

GLAST LAT Project SLAC-NRL Data Connection for GLAST Environmental Test 3/15/05 11 Meeting Schedule NRL-SLAC Network Working Group (COMPLETED) –Tuesday, March 15 th LAT Environmental Test Planning Meeting –Wednesday, March 16 th - 8 AM PST (11 PM EST) –NRL Bldg 209 Rm 321A –Call-in number: Passcode: NRL- SLAC Network Working Group –Tuesday March 29th, 2005 Environmental Test Planning Review –April 15th NRL-SLAC Network Working Group Meeting –???