4.2. Hardware Requirements

FRAFOS ABC SBC is based on CentOS 7 release 7.4 64bit operating system (x86_64 architecture).

Capacity and performance of the system depends mainly on the number and type of processors (CPU), available operating memory (RAM) and the number and performance of network cards (NIC).

There are no specific constraints for vendors of hardware and components, but we do have some suggestions and recommendations for the used hardware and its settings. Generally amount of memory and CPU power increases system resilience against load peaks, Ethernet cards with high packet rate facilitate high media anchoring throughput and fast solid-state drives facilitate WAV and PCAP recording.

Minimum hardware:

  • CPU: 1x processor - 64bit architecture
  • RAM: 4 GB
  • NIC: 1x 1Gb network card
  • HDD: 10 GB

Recommended / reference hardware: Dell PowerEdge R420

  • CPU: 2x Intel® Xeon® processor E5-2400
  • RAM: 16 GB (1066 MHz)
  • NIC: 1x Intel I350 dual-port 1Gb adapter
  • SSD: 2x 256 GB

For more details about system capacity and dimensioning, see Sec. SBC Dimensioning and Performance Tuning.

4.3. OS Tuning

This section only describes OS tuning options that – if chosen to be applied – must be performed` during the system installation. Various other parameters can be optimized later, see Section Low-level Parameters.

Correct hostname, and fully qualified domain name optionally, have to be set, as ABC SBC functionality depends on it. The current short and long (fqdn) hostname can be checked using:

% hostname
% hostname -f

The hostname and long hostanme have to be unique per ABC SBC node. If just short hostname is used, the command for long one should return also the short hostname.

If the hostname has to be changed, the following Centos command can be used:

% hostnamectl set-hostname <new_hostname>

4.3.1. Disk Partitioning

Depending on the configuration, running ABC SBC may be fairly disk-space-consuming. The ABC SBC collects all kind of diagnostics data (events, PCAP files), records and archives Call Detail Records and audio WAV files), maintains internal logs. To make sure that a configuration which produces extensive data will not interfere with vital system functions we recommend creating the following partitioning schema:

  • / ... for the OS and application. Recommended size at least 5GB.
  • /var ... Recommended size at laest 10GB.
  • /var/log ... includes internal logs and CDR files. Recommended size at least 20GB.
  • /var/lib/mysql ... for sql database, includes configuration and events. Recommended size at least 50GB.
  • /data ... includes traffic data such as recorded WAV-files, PCAP files and CDRs. Recommended size at least 50GB.
  • no swap partition ... For best operation the system should be equipped with enough RAM memory and no swap area used.

The recommended filesystem to be used is ext4.

Table Of Contents

Previous topic

4.1. Types of Installations: Hardware-based, Virtualized, and Cloud-based

Next topic

4.4. Deployment Modes

This Page