Changes between Version 19 and Version 20 of Architecture/Network
- Timestamp:
- May 8, 2020, 8:05:45 PM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Architecture/Network
v19 v20 1 [[ TOC(WikiStartBeta,TestbedInformation*,depth=4)]]1 [[Include(WikiToC)]] 2 2 3 == =Networks3 == Networks 4 4 There exist three primary networks that are accessible by experimenters in COSMOS. Device connections to these networks are determined by the number of interfaces and their maximum bandwidth. Every device has at least a connection to the [#ControlPlane Control Plane]. Then depending on the number of additional interfaces, the device may have a connection to either one or both of the [#DataPlane Data Planes]. Please see the device specific pages for more detailed information. 5 5 6 === =Control Plane6 === Control Plane 7 7 The control plane is a physically separate network designed to facilitate infrastructure control and user access to end devices. The control plane network runs on top of Dell S4048-ON switches providing up to 10G connectivity between devices. Please note that performance on the control plane is not guaranteed or deterministic and the network is only meant for experiment coordination and debugging. 8 8 9 === =Data Plane9 === Data Plane 10 10 There exist two parallel data plane networks that are available to experimenters. The data plane networks are interconnected with Dell Z9100-ON switches providing up to 100G connectivity between devices. The switches are built on the Broadcom Tomahawk chipset and support Openflow 1.3 as well as ONIE. The data planes are meant for latency and bandwidth sensitive experiment traffic where performance is intended to be deterministic. 11 11 12 === =User facing network architecture12 === User facing network architecture 13 13 [[Image(cosmos_logical_net.png, 50%)]] 14 14 … … 18 18 Non-user facing networks connect services, and manage hardware. 19 19 20 ==== =Locality within the network20 ==== Locality within the network 21 21 While all devices within the network may be connected, there are bandwidth and latency considerations. 22 22 For convenience, devices within the same physical location / topology have matching suffixes. … … 26 26 27 27 28 === =Isolation and infrastructure28 === Isolation and infrastructure 29 29 30 30 We enforce a split between "Control", "Data", and "Infrastructure" networks. Control and Infrastructure share common physical hardware (Switches, cables, etc.), using VLANs to provide isolation. Together these provide services and user access to the testbed. … … 38 38 Consoles give users access from outside and communicate with services on the DMZ network, and access to the testbed devices over control. 39 39 40 === =Network Roles40 === Network Roles 41 41 [[Image(COSMOS Net Arch.png, 50%)]] 42 42 … … 51 51 52 52 53 === =Logical Sites53 === Logical Sites 54 54 55 55 Currently, there are two logically distinct sites. … … 63 63 * sb1 - sb10.orbit 64 64 65 === =Vlan Assignment65 === Vlan Assignment 66 66 67 67 {{{
