Versions Compared

Old Version 1

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
JIRAIDAUTHSBX-95024
REV5UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a0c85fd202bb0160132c449a0026, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cdb30a83, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ca1903b3, userName='null'}


Panel

In this section...

Table of Contents
maxLevel3


Overview

The

Spacevars
0product2
 performance metrics for simultaneous sessions for various call scenarios are summarized in the "Benchmarking Results" section of the following pages. Note that these numbers apply to our recommended CPU and memory configurations, and the results may vary depending on the actual CPUs used. Exceeding these simultaneous sessions metrics may result in poor call performance, including longer call setup times and/or poor voice quality.
Spacevars
0company
 recommends maintaining call rates within the performance limits benchmarked below.

Server and VM Details

Div
classpdf6pttext


Caption
0Table
1Server and VM Details



Configuration

Server DetailVM Details


Max Link
Size

Server TypeCPU Speed
(GHz)		Processor
sockets		RAM
(GB)		HyperthreadingvCPUs
allocated		Memory
(GB)		Disk Size
(GB)		Network
Interface Mode
Config-1HP DL380 Gen10
Gold 6140		2.32256ACTIVE432100Pass-Through Mode
 (Direct I/O)		10 Gbps
Config-28Pass-Through Mode
 (Direct I/O)
Config-320SR-IOV
Config-432SR-IOV




Info
titleNote

For deployments that require it, you can instantiate the SBC SWe in smaller-sized configurations that use limited memory and vCPU resources. 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.

Benchmarking Setup

The two test beds used to collect benchmarking data are depicted below.


Info

The VM is hosted on a single NUMA node, where the NIC is connected.


Caption
0Figure
1Benchmarking Setup for SBC SWe Using SR-IOV interfaces



Caption
0Figure
1Benchmarking Setup for SBC SWe Configured in Pass-Through Mode (Direct I/O)

 


Performance Metrics

This section includes benchmarking results using the following configurations with and without DoS. Contact your

Spacevars
0company
 representative if you are interested in benchmarking data for other call scenarios.

Multiexcerpt include
MultiExcerptNameVMware Hypervisor Performance Metrics
PageWithExcerptVMware Hypervisor Performance Metrics

Multiexcerpt include
MultiExcerptNameKVM Hypervisor Performance Metrics
PageWithExcerptKVM Hypervisor Performance Metrics

       

Increasing RAM on Active SBC SWe Systems

Use the following procedure to increase RAM size on active (live) systems to increase SBC SWe session capacity.

Info
titleNote

The SBC SWe requires a minimum memory reservation of 6 GB.


StepAction
1

Power down the designated standby SBC.

2

Increase the RAM size of the VM system, and then power-on the standby SBC.

3

Perform a manual switchover, and then power-down the previously active SBC. Refer to the following pages for details:

EMA: System - Admin

CLI: Admin - CLI

4

Increase the RAM size of the VM system for the powered-down SBC, and then power it back up.

5Manually switchover to revert the active/standby SBCs back to their original states prior to beginning this procedure.
6Follow LSWU steps if you are upgrading to the next release.

Pagebreak