In this section:
This section describes
To install and configure
The recommended hardware and software settings are intended to ensure optimum
SBC SWe for KVM Hypervisor – Server Hardware Requirements
The following table lists the server hardware requirements. Intel Xeon processors (Nehalem micro-architecture or above) with 6 cores and above (processors should support hyper threading). Ribbon recommends using Westmere (or newer) processors for better SRTP performance. These processors have the AES-NI instruction set for performing cryptographic operations in hardware. The supported CPU Family number is 6 and CPU Model number must be newer than 26. Refer to the Intel Architecture and Processor Identification document for more information. Make sure NICs have 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, x710, and 82599 Ethernet adapters are supported for configuring as SR-IOV and DirectPath I/O pass-through devices. Number of ports allowed:Configuration Requirement Processor RAM Minimum 24 GB Hard Disk Minimum 500 GB Network Interface Cards (NICs) Ports
The
BIOS Setting Recommendations
Ribbon recommends the following BIOS settings for optimum performance:
Disable Sub-NUMA Clustering for servers that provide it as an option in BIOS.
For example, the BIOS settings shown below are recommended for HP DL380p Gen8 servers. For BIOS settings of other servers, refer to the respective vendor's website.
BIOS Setting Recommendations for HP DL380p Gen8 Servers
BIOS Parameter | Recommended Setting | Default Value |
---|---|---|
HP Power Profile | Maximum Performance | Balanced Power and Performance |
Thermal Configuration | Maximum Cooling | Optimal Cooling |
HW Prefetchers | Disabled | Enabled |
Adjacent Sector Prefetcher | Disabled | Enabled |
Processor Power and Utilization Monitoring | Disabled | Enabled |
Memory Pre-Failure Notification | Disabled | Enabled |
Memory Refresh Rate | 1x Refresh | 2x Refresh |
SBC SWe for KVM Hypervisor – Software Requirements
The SBC SWe requirements for a KVM hypervisor environment are listed in the following table:
Downloading the SBC SWe Software Package
For more information, see Downloading the SBC SWe Software Package.
Ensure Processors and VM configuration (CPUs, RAM, Virtual Hard Disk, NICs, and Bridge settings) are identical for an SBC SWe HA pair.
Do not change BIOS settings once they are applied on the server.
KVM Configuration and Settings
Configuration | Settings |
---|---|
vCPU | Minimum 4 vCPUs required. Any number of vCPUs may be configured depending upon the call capacity requirements, but the number should be even (4, 6, 8, etc.) to avoid impacting performance. Note: CPU resource reservation and pinning are required. |
vRAM | Reserve the memory based on call capacity and configuration requirements. Refer to benchmarking data for supported call capacities with different configuration limits. Note: Memory resource reservation is required. |
Virtual Hard Disk | Set Hard Disk (virtual) size as 100 GB or more (based on requirements of retaining CDRs, logs, etc. for number of days). Note: Hard disk size cannot be changed after the SBC SWe software is installed. |
vNICs | Set number of virtual NICs as 4 (1-MGMT, 1-HA, 1-PKT0 and 1-PKT1).
|
You can instantiate the SBC SWe in smaller-sized configurations that use limited memory and vCPU resources, if required. However, the limited resources place some restrictions on capacity and capabilities. Refer to Small SBC SWe Deployment Characteristics and Performance Metrics for Small SBC SWe Configurations for more information.
- Ensure Processors, KVM hypervisor version and VM configuration (vCPUs, vRAM, Virtual Hard Disk, vNICs, and vSwitch Settings) are identical for an SBC SWe HA pair.
- Do not change BIOS and KVM hypervisor settings and recommendations once they are applied on the server.
To configure VLAN on SRIOV and PCI Passthrough Ethernet interfaces, disable the Data Center Bridging (DCB) on the switch connected to the interfaces.