Download Control System Network

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Wake-on-LAN wikipedia , lookup

Distributed firewall wikipedia , lookup

Computer network wikipedia , lookup

Zero-configuration networking wikipedia , lookup

Cracking of wireless networks wikipedia , lookup

Piggybacking (Internet access) wikipedia , lookup

Network tap wikipedia , lookup

Airborne Networking wikipedia , lookup

Transcript
Control System Network
• Requirements
• Development Network
• Operations Network
• Physically
• Logically
• Technology
• Schedule
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
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 current
EPICS 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)
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Four Subnets
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Development Subnet
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
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
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
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.
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
The Ideal Network
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Star Configuration
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Fiber to Every Third Area
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Distribution Layer
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Physical Layout
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
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
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
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
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Physical Hardware
2 x Cisco 6509
(MCC)
Stackable; rear panel cabling
allows 32 Gb/sec Interconnect
36 x Cisco 3750
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Schedule
This was a first attempt given known dates
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Schedule (v2)
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]
Network Overview
February 22, 2006
LCLS Controls Network
Doug Murray
[email protected]