1 / 17

Cutting-Edge Network Infrastructure Development for LCLS Facility

Plan and implement advanced network system for LCLS with focus on network requirements, operations, physical layout, technology upgrades, and future expansion. Ensure seamless connectivity, reliability, and adaptability for 30-year equipment lifecycle.

mindy
Télécharger la présentation

Cutting-Edge Network Infrastructure Development for LCLS Facility

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. Control System Network • Requirements • Development Network • Operations Network • Physically • Logically • Technology • Schedule

  2. Background Ideas • LCLS will have 30 year lifetime • Best equipment now will be obsolete in 5 years • Invest in Infrastructure which allows expansion • More complex than currentEPICS networks for SLC or SPEAR • Not a typical “enterprise network” • Need bandwidth between IOCs for fast feedback or localized control, not just to central “server” • The servers are in the field, and clients are centralized (although we have centralized boot and file servers)

  3. Four Subnets

  4. Development Subnet

  5. Operations Network • Must be able to operate LCLS if network is disconnected from SLAC or Internet • Able to stand alone, must have servers • Must have machines to run EPICS clients • Access allowed only from Access Subnet • SSH Servers, Web Servers • EPICS Gateway Servers • Offline Data Cache Servers

  6. Operations Network • Must also support access from the existing SLC network for SLC-aware IOCs (SAI). • A proxy server on the SLC network must have access to all SAIs on the operations network • SAIs must also be fully accessible from the operations network, as would any normal IOC.

  7. The Ideal Network

  8. Star Configuration

  9. Fiber to Every Third Area

  10. Distribution Layer

  11. Physical Layout

  12. Private IP Address Ranges • Class A • 10.0.0.0 to 10.255.255.255 • Class B • 172.16.0.0 to 172.31.255.255 • Class C • 192.168.0.0 to 192.168.255.255 • Operations Network, Class A • Not because of the number of nodes allowed, but because we can better organize and classify

  13. Private IP Address Range • Class A Operations Network • Format is 10.10.X.Y • 10.10.20.Y - Node on the Injection Subnet • 10.10.21.Y - Node on the subnet for Sector 21 • 10.10.30.Y - Node on the subnet for Sector 30 • 10.10.33.Y - Node in Undulator Hall • 10.10.35.Y - Node in Front-end Enclosure • 10.10.100.Y - Node in Fast Feedback Subnet • 10.10.120.Y - Node in LLRF Subnet for Injector

  14. Physical Hardware 2 x Cisco 6509(MCC) Stackable; rear panel cabling allows 32 Gb/sec Interconnect 36 x Cisco 3750

  15. Schedule • This was a first attempt given known dates

  16. Schedule (v2)

  17. Network Overview

More Related