Hung-Wei Chiu | 77c969e | 2020-10-23 18:13:07 +0000 | [diff] [blame] | 1 | .. |
| 2 | SPDX-FileCopyrightText: © 2020 Open Networking Foundation <support@opennetworking.org> |
| 3 | SPDX-License-Identifier: Apache-2.0 |
| 4 | |
Hung-Wei Chiu | 77c969e | 2020-10-23 18:13:07 +0000 | [diff] [blame] | 5 | Overview |
| 6 | ======== |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 7 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 8 | There are many ways to deploy Aether, depending on the requirements of the edge |
| 9 | site. The Reliability, Availability, and Serviceability (RAS) of each set of |
| 10 | equipment will differ depending on the characteristics of each edge. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 11 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 12 | This document provides several hardware deployment options and explains the |
| 13 | differences between them. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 14 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 15 | Deployment Options |
| 16 | ------------------ |
| 17 | |
| 18 | Development Environments |
| 19 | """""""""""""""""""""""" |
| 20 | |
| 21 | For users looking for a development or fully software-simulated environment, |
| 22 | there is ``Aether-in-a-Box (AiaB)`` - instructions for running this can be |
| 23 | found in the :doc:`Aether SD-Core Developer Guide </developer/sdcore>`. AiaB |
| 24 | is only suitable for testing and developing software, and can't connect to |
| 25 | physical hardware, but is a good choice for learning about the different |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 26 | software components within Aether. |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 27 | |
| 28 | Production Environments |
| 29 | """"""""""""""""""""""" |
| 30 | |
| 31 | Deploying Aether on hardware is required for both production deployments and |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 32 | hardware testing. Before deploying Aether, a detailed plan including the |
| 33 | network topology, hardware, and all cabling needs to be created. |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 34 | |
| 35 | For redundancy of workloads running in Kubernetes, at least 3 compute nodes |
| 36 | must be available. A single or pair of compute nodes can be used, but software |
| 37 | would need to be configured without High Availability (HA) enabled. |
Zack Williams | e8c3b2c | 2021-02-01 12:47:28 -0700 | [diff] [blame] | 38 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 39 | The topologies below are *simplified physical topologies* to show the equipment |
| 40 | needed and the minimal connectivity between devices. Within these topologies, |
| 41 | multiple VLANs, routing, and other network-level configuration is required to |
| 42 | make a functional Aether edge. |
| 43 | |
| 44 | There are also possible RAS improvements that can be done at a topology level - |
| 45 | for example, fabric switch connections can be made with using two cables, and |
| 46 | configured to tolerate the failure or replacement of one cable or NIC port, |
| 47 | which is recommended especially for inter-switch links. |
| 48 | |
| 49 | Edge Connectivity |
| 50 | ----------------- |
| 51 | |
| 52 | Aether's is a managed service, and Aether Edges require a constant connection |
| 53 | via VPN to the 4G and 5G core in Aether Central for managing subscriber |
| 54 | information. |
| 55 | |
| 56 | At a minimum, the site must provide a public static IP address that can be used |
| 57 | for the VPN connection. This can be behind NAT using port forwarding can be |
| 58 | configured to the Aether Edge within the network. |
| 59 | |
| 60 | Additionally, for initial installation and setup and and managing |
| 61 | updates to the edge sites, access via SSH (public key only) is required. |
| 62 | |
| 63 | BESS-based Network Topology |
| 64 | --------------------------- |
| 65 | |
| 66 | The :doc:`Software-only BESS UPF |
| 67 | </edge_deployment/bess_upf_deployment>`, which can be used for deployments that |
| 68 | do not have P4 switching hardware. |
| 69 | |
| 70 | .. image:: images/edge_mgmt_only.svg |
| 71 | :alt: BESS network topology |
| 72 | |
| 73 | |
| 74 | BESS runs on an x86 compute server, and is deployed using Kubernetes. In |
| 75 | production it requires a SR-IOV capable network card, and specific K8s CNIs to |
| 76 | be used. |
| 77 | |
| 78 | The Management Server and Switch must be configured with multiple VLANs which |
| 79 | provide subnets required for routing within the BESS UPF. |
| 80 | |
| 81 | P4-based Network Topology |
| 82 | ------------------------- |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 83 | |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 84 | If only a single P4 switch is used, the :doc:`Simple |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 85 | <trellis:supported-topology>` topology can be used, but provides no network |
| 86 | redundancy: |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 87 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 88 | .. image:: images/edge_single.svg |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 89 | :alt: Single Switch Topology |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 90 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 91 | If another switch is added, and a "Paired Leaves" (aka :doc:`Paired Switches |
| 92 | <trellis:supported-topology>`) topology is used, which can tolerate the loss of |
| 93 | a leaf switch and retain connections for all dual-homed devices. Single homed |
| 94 | devices on the failed leaf would need another form of HA, for example, |
| 95 | deploying multiple eNBs where some are connected to each leaf, and can provide |
| 96 | radio coverage.: |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 97 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 98 | .. image:: images/edge_paired_leaves.svg |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 99 | :alt: Paired Leaves Topology |
Zack Williams | e8c3b2c | 2021-02-01 12:47:28 -0700 | [diff] [blame] | 100 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 101 | For larger deployments, a 2x2 fabric can be configured (aka :doc:`Single-Stage |
| 102 | Leaf-Spine <trellis:supported-topology>`), which provide Spine redundancy, but |
| 103 | does not support dual-homing of devices. |
| 104 | |
| 105 | .. image:: images/edge_2x2.svg |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 106 | :alt: 2x2 Fabric Topology |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 107 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 108 | Other topologies as described in the :doc:`Trellis Documentaiton |
| 109 | <trellis:supported-topology>` can possibly be used, but are not actively being |
| 110 | tested at this time. |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 111 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 112 | Additionally, the P4-based topologies can support running both the BESS UPF and |
| 113 | P4 UPF on the same hardware at the same time if desired (for testing, or |
| 114 | simultaneous 4G/5G support). |
Zack Williams | e8c3b2c | 2021-02-01 12:47:28 -0700 | [diff] [blame] | 115 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 116 | Hardware Descriptions |
| 117 | --------------------- |
Zack Williams | e8c3b2c | 2021-02-01 12:47:28 -0700 | [diff] [blame] | 118 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 119 | Fabric Switch |
| 120 | """"""""""""" |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 121 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 122 | To use the P4 UPF, you must use fabric switches based on the `Intel (previously |
| 123 | Barefoot) Tofino chipset |
| 124 | <https://www.intel.com/content/www/us/en/products/network-io/programmable-ethernet-switch/tofino-series.html>`_. |
| 125 | There are two variants of this switching chipset, with different resources and |
| 126 | capabilities. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 127 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 128 | Aether currently supports these P4 switch models: |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 129 | |
| 130 | * `EdgeCore Wedge100BF-32X |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 131 | <https://www.edge-core.com/productsInfo.php?cls=1&cls2=180&cls3=181&id=335>`_, |
| 132 | a Dual Pipe Tofino ASIC |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 133 | |
| 134 | * `EdgeCore Wedge100BF-32QS |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 135 | <https://www.edge-core.com/productsInfo.php?cls=1&cls2=180&cls3=181&id=770>`_, |
| 136 | a Quad Pipe Tofino ASIC, which has more chip resources and a faster embedded |
| 137 | system with more memory and storage. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 138 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 139 | The P4 UPF and SD-Fabric features run within the constraints of the Dual Pipe |
| 140 | system for production deployments, but for development of features in P4, the |
| 141 | larger capacity of the Quad Pipe is desirable. |
| 142 | |
| 143 | These switches feature 32 QSFP+ ports capable of running in 100GbE, 40GbE, or |
| 144 | 4x 10GbE mode (using a split DAC or fiber cable) and have a 1GbE management |
| 145 | network interface. |
| 146 | |
| 147 | See also the :ref:`Rackmount of Eqiupment |
| 148 | <edge_deployment/site_planning:rackmount of equipment>` for how the Fabric |
| 149 | switches should be rackmounted to ensure proper airflow within a rack. |
| 150 | |
| 151 | Compute Server |
| 152 | """""""""""""" |
| 153 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 154 | These servers run Kubernetes, Aether connectivity apps, and edge applications. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 155 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 156 | Minimum hardware specifications: |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 157 | |
| 158 | * AMD64 (aka x86-64) architecture |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 159 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 160 | * 8 CPU Cores (minimum), 16-64 recommended |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 161 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 162 | * 32GB of RAM (minimum), 128GB+ recommended |
| 163 | |
| 164 | * 250 GB of storage (SSD preferred), 1TB+ recommended |
| 165 | |
| 166 | * 2x 40GbE or 100GbE Ethernet network card to P4 switches, with DPDK support |
| 167 | |
| 168 | * 1x 1GbE management network port. 2x required for BESS UPF. |
| 169 | |
| 170 | Optional but highly recommended: |
| 171 | |
| 172 | * Lights out management support, with either a shared or separate NIC and |
| 173 | support for HTML5 console access. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 174 | |
| 175 | Management Server |
| 176 | """"""""""""""""" |
| 177 | |
| 178 | One management server is required, which must have at least two 1GbE network |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 179 | ports, and runs a variety of network services to bootstrap and support the |
| 180 | edge. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 181 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 182 | In current Aether deployments, the Management Server also functions as a router |
| 183 | and VPN gateway back to Aether Central. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 184 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 185 | Minimum hardware specifications: |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 186 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 187 | * AMD64 (aka x86-64) architecture |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 188 | |
| 189 | * 4 CPU cores, or more |
| 190 | |
| 191 | * 8GB of RAM, or more |
| 192 | |
| 193 | * 120GB of storage (SSD preferred), or more |
| 194 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 195 | * 2x 1GbE Network interfaces (one for WAN, one to the management switch) |
| 196 | |
| 197 | Optional: |
| 198 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 199 | * 10GbE or 40GbE network card with DPDK support to connect to fabric switch |
| 200 | |
| 201 | * Lights out management support, with either a shared or separate NIC and |
| 202 | support for HTML5 console access. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 203 | |
| 204 | Management Switch |
| 205 | """"""""""""""""" |
| 206 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 207 | A managed L2/L3 management switch is required to provide connectivity within |
| 208 | the cluster for bootstrapping equipment. It is configured with multiple VLANs |
| 209 | to separate the management plane, fabric, and the out-of-band and lights out |
| 210 | management connections on the equipment. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 211 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 212 | Minimum requirements: |
| 213 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 214 | * 8x 1GbE Copper ports (adjust to provide a sufficient number for every copper |
| 215 | 1GbE port in the system) |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 216 | |
| 217 | * 2x 10GbE SFP+ or 40GbE QSFP interfaces (only required if management server |
| 218 | does not have a network card with these ports) |
| 219 | |
| 220 | * Managed via SSH or web interface |
| 221 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 222 | * Support the LLDP protocol for debugging cabling issues |
| 223 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 224 | * Capable supporting VLANs on each port, with both tagged and untagged traffic |
| 225 | sharing a port. |
| 226 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 227 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 228 | Optional: |
| 229 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 230 | * PoE+ support, which can power eNB and monitoring hardware, if using |
| 231 | Management switch to host these devices. |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 232 | |
| 233 | eNB Radio |
| 234 | """"""""" |
| 235 | |
| 236 | The LTE eNB used in most deployments is the `Sercomm P27-SCE4255W Indoor CBRS |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 237 | Small Cell |
| 238 | <https://www.sercomm.com/contpage.aspx?langid=1&type=prod3&L1id=2&L2id=1&L3id=107&Prodid=751>`_. |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 239 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 240 | While this unit ships with a separate power brick, it also supports PoE+ power |
| 241 | on the WAN port, which provides deployment location flexibility. Either a PoE+ |
| 242 | capable switch or PoE+ power injector should be purchased. |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 243 | |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 244 | If connecting directly to the fabric switch through a QSFP to 4x SFP+ splitter |
| 245 | cable, a 10GbE SFP+ to 1GbE Copper media converter should be purchased. The `FS |
| 246 | UMC-1S1T <https://www.fs.com/products/101476.html>`_ has been used for this |
| 247 | purpose successfully. |
| 248 | |
| 249 | Alternatively, the Fabric's 10GbE SFP+ could be connected to another switch |
| 250 | (possibly the Management Switch) which would adapt the speed difference, and |
| 251 | provide PoE+ power, and power control for remote manageability. |
| 252 | |
| 253 | |
| 254 | Testing Hardware |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 255 | ---------------- |
| 256 | |
| 257 | The following hardware is used to test the network and determine uptime of |
| 258 | edges. It's currently required, to properly validate that an edge site is |
| 259 | functioning properly. |
Zack Williams | 9026f53 | 2020-11-30 11:34:32 -0700 | [diff] [blame] | 260 | |
Hyunsun Moon | 2b62676 | 2021-03-26 16:21:14 -0700 | [diff] [blame] | 261 | Monitoring Raspberry Pi and CBRS dongle |
| 262 | """"""""""""""""""""""""""""""""""""""" |
| 263 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 264 | One pair of Raspberry Pi and CBRS band supported LTE dongle is required to |
| 265 | monitor the connectivity service at the edge. |
Hyunsun Moon | 2b62676 | 2021-03-26 16:21:14 -0700 | [diff] [blame] | 266 | |
| 267 | The Raspberry Pi model used in Pronto is a `Raspberry Pi 4 Model B/2GB |
| 268 | <https://www.pishop.us/product/raspberry-pi-4-model-b-2gb/>`_ |
| 269 | |
| 270 | Which is configured with: |
| 271 | |
| 272 | * HighPi Raspberry Pi case for P4 |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 273 | |
| 274 | * Either a: |
| 275 | |
| 276 | * PoE Hat used with a PoE switch (recommended, allows remote power control) |
| 277 | |
| 278 | * USB-C Power Supply |
| 279 | |
Hyunsun Moon | 2b62676 | 2021-03-26 16:21:14 -0700 | [diff] [blame] | 280 | * MicroSD Card with Raspbian - 16GB |
| 281 | |
Zack Williams | 1ae109e | 2021-07-27 11:17:04 -0700 | [diff] [blame] | 282 | One LTE dongle model supported in Aether is the `Sercomm Adventure Wingle |
Hyunsun Moon | 2b62676 | 2021-03-26 16:21:14 -0700 | [diff] [blame] | 283 | <https://www.sercomm.com/contpage.aspx?langid=1&type=prod3&L1id=2&L2id=2&L3id=110&Prodid=767>`_. |
Zack Williams | 589ac23 | 2021-08-19 08:52:18 -0700 | [diff] [blame^] | 284 | |
| 285 | |
| 286 | Example BoMs |
| 287 | ------------ |
| 288 | |
| 289 | To help provision a site, a few example Bill of Materials (BoM) are given |
| 290 | below, which reference the hardware descriptions given above. |
| 291 | |
| 292 | Some quantities are dependent on other quantities - for example, the number of |
| 293 | DAC cables frequently depends on the number of servers in use. |
| 294 | |
| 295 | These BOMs do not include UE devices. It's recommended that the testing |
| 296 | hardware given above be added to every BoM for monitoring purposes. |
| 297 | |
| 298 | |
| 299 | BESS UPF Testing BOM |
| 300 | """""""""""""""""""" |
| 301 | |
| 302 | The following is the minimum BoM required to run Aether with the BESS UPF. |
| 303 | |
| 304 | ============ ===================== =============================================== |
| 305 | Quantity Type Purpose |
| 306 | ============ ===================== =============================================== |
| 307 | 1 Management Switch Must be Layer 2/3 capable for BESS VLANs |
| 308 | 1 Management Server |
| 309 | 1-3 Compute Servers Recommended at least 3 for Kubernetes HA |
| 310 | 1 (or more) eNB |
| 311 | 1x #eNB PoE+ Injector Required unless using a PoE+ Switch |
| 312 | Sufficient Cat6 Network Cabling Between all equipment |
| 313 | ============ ===================== =============================================== |
| 314 | |
| 315 | P4 UPF Testing BOM |
| 316 | """""""""""""""""" |
| 317 | |
| 318 | ============ ===================== =============================================== |
| 319 | Quantity Type Description/Use |
| 320 | ============ ===================== =============================================== |
| 321 | 1 P4 Fabric Switch |
| 322 | 1 Management Switch Must be Layer 2/3 capable |
| 323 | 1 Management Server At least 1x 40GbE QSFP ports recommended |
| 324 | 1-3 Compute Servers Recommended at least 3 for Kubernetes HA |
| 325 | 2x #Server 40GbE QSFP DAC cable Between Compute, Management, and Fabric Switch |
| 326 | 1 QSFP to 4x SFP+ DAC Splitter between Fabric and eNB |
| 327 | 1 (or more) eNB |
| 328 | 1x #eNB 10GbE to 1GbE Media Required unless using switch to convert from |
| 329 | converter fabric to eNB |
| 330 | 1x #eNB PoE+ Injector Required unless using a PoE+ Switch |
| 331 | Sufficient Cat6 Network Cabling Between all equipment |
| 332 | ============ ===================== =============================================== |
| 333 | |
| 334 | P4 UPF Paired Leaves BOM |
| 335 | """""""""""""""""""""""" |
| 336 | |
| 337 | ============ ===================== =============================================== |
| 338 | Quantity Type Description/Use |
| 339 | ============ ===================== =============================================== |
| 340 | 2 P4 Fabric Switch |
| 341 | 1 Management Switch Must be Layer 2/3 capable |
| 342 | 1 Management Server 2x 40GbE QSFP ports recommended |
| 343 | 3 Compute Servers |
| 344 | 2 100GbE QSFP DAC cable Between Fabric switches |
| 345 | 2x #Server 40GbE QSFP DAC cable Between Compute, Management, and Fabric Switch |
| 346 | 1 (or more) QSFP to 4x SFP+ DAC Splitter between Fabric and eNB |
| 347 | 1 (or more) eNB |
| 348 | 1x #eNB 10GbE to 1GbE Media Required unless using switch to convert from |
| 349 | converter fabric to eNB |
| 350 | 1x #eNB PoE+ Injector Required unless using a PoE+ Switch |
| 351 | Sufficient Cat6 Network Cabling Between all equipment |
| 352 | ============ ===================== =============================================== |
| 353 | |
| 354 | |
| 355 | P4 UPF 2x2 Leaf Spine Fabric BOM |
| 356 | """""""""""""""""""""""""""""""" |
| 357 | |
| 358 | ============ ===================== =============================================== |
| 359 | Quantity Type Description/Use |
| 360 | ============ ===================== =============================================== |
| 361 | 4 P4 Fabric Switch |
| 362 | 1 Management Switch Must be Layer 2/3 capable |
| 363 | 1 Management Server 2x 40GbE QSFP ports recommended |
| 364 | 3 Compute Servers |
| 365 | 8 100GbE QSFP DAC cable Between Fabric switches |
| 366 | 2x #Server 40GbE QSFP DAC cable Between Compute, Management, and Fabric Switch |
| 367 | 1 (or more) QSFP to 4x SFP+ DAC Splitter between Fabric and eNB |
| 368 | 1 (or more) eNB |
| 369 | 1x #eNB 10GbE to 1GbE Media Required unless using switch to convert from |
| 370 | converter fabric to eNB |
| 371 | 1x #eNB PoE+ Injector Required unless using a PoE+ Switch |
| 372 | Sufficient Cat6 Network Cabling Between all equipment |
| 373 | ============ ===================== =============================================== |
| 374 | |