1 / 10

LAT Environmental Test Planning and Design Review 3-4 May 2005 NRL-SLAC Networking

LAT Environmental Test Planning and Design Review 3-4 May 2005 NRL-SLAC Networking. Brian Grist (650) 926-2998 bgrist@slac.stanford.edu. Agenda. Requirements / Implementation Overview LAT Data Flow Diagram Network Diagram (LAT Data and Office Computing) Areas of Responsibility

heather-sweet
Télécharger la présentation

LAT Environmental Test Planning and Design Review 3-4 May 2005 NRL-SLAC Networking

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LAT Environmental Test Planning and Design Review 3-4 May 2005 NRL-SLAC Networking Brian Grist (650) 926-2998 bgrist@slac.stanford.edu

  2. Agenda • Requirements / Implementation Overview • LAT Data Flow Diagram • Network Diagram (LAT Data and Office Computing) • Areas of Responsibility • LAT Mobile Computing Rack Schedule, Dataflow checkout • Memorandum of Understanding / Security Requirements • Issues / Questions • Contact Information

  3. Requirements / Implementation Overview • What are the network connections for? • Send instrument data back to SLAC during Environmental Tests as file transfers. • Support Data Volumes on the order of 15 GB/day • Transfer LAT Temperature telemetry to the NRL T/V Data Acquisition Computer. • Send Test S/W upgrades/fixes to Test Stands from SLAC as file transfers. • Support for ISOC testing • General Office Computing • Implementation Overview • 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 • The link is managed and will be set up to notify network and LAT Test Personnel of scheduled outages. • DREN peers (connects) with ESnet at several points. • The LAT test equipment would have its firewall “registered” with the NRL network to allow a VPN connection to SLAC. • The link rate will be 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. • General office computers in building 209 will be supported via guest access.

  4. LAT Data Flow Diagram

  5. Network Diagram

  6. Areas of Responsibility

  7. LAT Mobile Computing Rack Schedule • The schedule for the LAT Mobile Test Rack shows it completely built and tested so that can be shipped to NRL in early December. • This will allow several weeks to checkout the network and be ready before the end of the year which is still before the LAT ships in January. • There is a weekly meeting to status the progress of the LAT Mobile Test Rack • There is a website (internal to SLAC) to track the progress and information about the rack. • https://www-internal.slac.stanford.edu/comp/windows/admin/Documentation/projects/GLAST%20Mobile%20Rack/mobile%20rack.htm

  8. Memorandum of Understanding / Security Requirements • The firewall in the LAT Mobile Computing Rack must be accredited by NRL networking in order to connect to the NRL switch in building A59. • The firewall is the only device in the LAT data path that will need to be accredited. • The accreditation process will require a signed Memo of Understanding (MOU) between SLAC/Project management, NRL sponsor (Code 7650) and NRL Network Security. • The MOU will be stating that LAT would conform to NRL Computer Security requirements for a VPN service. • Now that a networking diagram is complete, Daryl Yentis will be talking with NRL networking this week to determine the exact paperwork needed for the agreement. • He will send that paperwork to SLAC next week and we will schedule a meeting between SLAC Computing Services and GLAST Management to determine who needs to sign the MOU. • Once the MOU paperwork is in place preliminary accreditation can occur, the final accreditation would not occur until the LAT Mobile Test Rack is physically at NRL. • The office network in building 209 will be handled as guest computers and will have to conform to those rules. • Guest access is via the NRL Beta Wireless network. • Each computer must have a special software package installed • Guest privileges have to be applied for on a machine by machine basis

  9. Issues / Questions • The details still need to be worked out to move the data files to transmit the LAT temperature telemetry from the LAT mobile computing rack to the NRL thermal monitoring computer. • Who will need to sign the MOU with NRL to allow that firewall in the LAT Mobile Computing Rack to be accredited by the NRL network?

  10. Contact Information

More Related