This section describes the hardware and software requirements for SBC SWe Cloud on an OpenStack platform. The SBC SWe supports the following OpenStack environments: The SBC SWe Cloud was tested on OpenStack Queens with RHOSP 13 and RHEL 7.5. Server Hardware Requirements Intel Xeon processors (Nehalem micro-architecture or above) with 6 cores and above (processors should support hyper threading). Ribbon recommends Westmere (or newer) processors for better SRTP performance. These processors have the AES-NI instruction set for performing cryptographic operations in hardware. Minimum 4 NICs. Make sure NIC has multi-queue support which enhances network performance by allowing RX and TX queues to scale with the number of CPUs on multi-processor systems. The Intel I350, x540, x550, and 82599 Ethernet adapters are supported for configuring as SR-IOV and DirectPath I/O pass-through devices. The PKT ports must be 10 Gbps SR-IOV enabled port. 6 NICs are required for supporting PKT port redundancy. The system hosting the SBC SWe must meet the following requirements to achieve the performance targets listed: S-SBC SWe Requirement 32 vCPUs Due to the workload characteristics, allocate 20 physical cores with two hyper-threaded CPUs from each core to the SBC. 128 GiB RAM 100 GB Disk None 4 vNICs/6 vNICs Attach MGT0 port to the Management VirtIO Tenant network. HA port has to be on IPv4 VirtIO Tenant network. Attach PKT0 and PKT1 ports to SR-IOV and Provider network. You must require 6 vNICs for enabling PKT port redundancy. For more information, refer to SBC SWe Cloud Features Guide.OpenStack Requirements
Note
Configuration Requirement Processor
Note
RAM Minimum 24 GiB Hard Disk Minimum 100 GB Network Interface Cards (NICs)
Note
Note
Note
Note
S-SBC SWe Requirements
for 1000 CPS/120K Signaling Sessions Notes Must be Huge Page memory. The minimum page size is 2048 KiB, but 1048576 is recommended.
Note
All NIC ports must come from the NUMA node 0. The S-SBC SWe instance is hosted on dual-socket physical server with 10 physical cores coming from each NUMA node.
M-SBC SWe Requirement 20 vCPUs Due to the workload characteristics, allocate 10 physical cores with two hyper-threaded CPUs from each core and from single NUMA node to the SBC. 32 GiB RAM 100 GB Disk None 4 vNICs/ 6 vNICs Attach MGT0 port to the Management VirtIO Tenant network. HA port has to be on IPv4 VirtIO Tenant network. Attach PKT0 and PKT1 ports to SR-IOV and Provider network. All NIC ports must come from the same NUMA node from which the M-SBC SWe instance is hosted. OAM Node Requirements 4 vCPUs None 16 GiB RAM 80 GB Disk None 4 vNICs None I-SBC SWe Requirement 20 vCPUs 32 GiB RAM 100 GB Disk None 4 vNICs/ 6 vNICs Attach MGT0 port to the Management VirtIO Tenant network. HA port has to be on IPv4 VirtIO Tenant network. Attach PKT0 and PKT1 ports to SR-IOV and Provider network.
M-SBC SWe Requirements
for 30K Media SessionsNotes Must be Huge Page memory. The minimum page size is 2048 KiB, but 1048576 is recommended.
You must require 6 vNICs for enabling PKT port redundancy. For more information, refer to SBC SWe Cloud Features Guide.
Note
OAM Node (minimum) Notes None
I-SBC SWe Requirements Notes Must be Huge Page memory. The minimum page size is 2048 KiB, but 1048576 is recommended.
You must require 6 vNICs for enabling PKT port redundancy. For more information, refer to SBC SWe Cloud Features Guide.
Overview
Content Tools