Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
  
[+] Expand All
[-] Collapse All

Meeting System Requirements

This section describes the hardware and software requirements for running Steel-Belted Radius Carrier on the following server and operating system combinations:

  • Oracle Sparc server and Solaris operating system
  • x86 server and Linux operating system

Standalone SBR Carrier Server Hardware

These basic specifications may be used for any standalone Steel-Belted Radius Carrier server—one that does not participate in a Session State Register cluster.

Session State Register servers have additional system requirements, such as dual Gigabit Ethernet NICs (to provide redundant communication links). These additional requirements are discussed in Supported SBR Carrier SSR Cluster Configurations.

Table 11 and Table 12 respectively list the hardware requirements for 32-bit and 64-bit standalone SBR Carrier servers.

Note: These hardware requirements are also applicable to VMs hosting standalone SBR Carrier in virtualized environments. Overprovisioning is not recommended.

Table 11: 32-Bit Version of Standalone SBR Carrier Server Hardware Configurations

Server

RAM

Solaris CPU

Linux CPU

Free Disk Space

32-Bit Standalone SBR Carrier Server (Minimum Configuration)

2 GB RAM.1

Two-CPU UltraSPARC III or better, running at 1.5 GHz.

Xeon 2-core at 2.0 GHz supported for testing.

Xeon 4-core or 2x2-core at 2.4 GHz supported for limited performance production use.

At least 1 GB of local hard disk space (not NFS).

For Linux, at least 2 GB of local hard disk space is required.

32-Bit Standalone SBR Carrier Server (Recommended Configuration)

8 GB RAM or more.

If Mitel’s Signalware communication stack is used, for systems processing a heavier-than-normal load (for instance, with WiMAX or additional session licenses), or when configuring a large number of threads (for example, to accommodate high latency of proxy targets), more memory produces better performance.

UltraSPARC T1 or better
SPARC64 VII or better
SPARC T3 or better

Xeon 2x6-core at 3.6 GHz or higher.

Higher core counts with lower processing speeds may not improve throughput in certain cases. See the Performance, Planning, and Tuning Guide for more information.

At least 1 GB of local hard disk space (not NFS).

For Linux, at least 2 GB of local hard disk space is required.

Table 12: 64-Bit Version of Standalone SBR Carrier Server Hardware Configurations

Server

RAM

Linux CPU

Free Disk Space

64-Bit Standalone SBR Carrier Server (Minimum Configuration)

8 GB RAM.1

Xeon 2-core at 2.0 GHz supported for testing.

Xeon 4-core or 2x2-core at 2.4 GHz supported for limited performance production use.

At least 8 GB of local hard disk space (not NFS).

64-Bit Standalone SBR Carrier Server (Recommended Configuration)

16 GB RAM or more.

If Mitel’s Signalware communication stack is used, for systems processing a heavier-than-normal load (for instance, with WiMAX or additional session licenses), or when configuring a large number of threads (for example, to accommodate high latency of proxy targets), more memory produces better performance.

Xeon 2x6-core at 3.6 GHz or higher.

Higher core counts with lower processing speeds may not improve throughput in certain cases. See the Performance, Planning, and Tuning Guide for more information.

At least 16 GB of local hard disk space (not NFS).

1. The memory size can be increased based on the subscriber count.

Session State Register Host Hardware

SBR Carrier and Management Node Hosts

Table 13 and Table 14 list the hardware requirements for Session State Register cluster SBR Carrier and management node hosts for 32-bit and 64-bit SBR Carrier servers.

Table 13: Session State Register SBRC and Management Node Host Hardware Configurations for 32-Bit SBR Carrier

Server

RAM

Solaris CPU

Linux CPU

Free Disk Space

Network Interfaces

32-Bit SBRC and/or Management Node Host (Minimum Configuration)

4 GB RAM.

UltraSPARC T1 or better
SPARC64 VII or better
SPARC T3 or better

Xeon 2-core at 2 GHz supported for testing and M-only node.

Xeon 4-core or 2x2-core supported for production for a single SM node.

At least 1 GB of local hard disk space (not NFS).

For Linux, at least 2 GB of hard disk space is required.

Two physical interfaces on a 100 Base-T network.

Multipath configuration is required.

32-Bit SBRC and/or Management Node Host (Recommended Configuration)

8 GB RAM or more.

If Mitel’s Signalware communication stack is used, for systems processing a heavier-than-normal load (for instance, with WiMAX or additional session licenses), or when configuring a large number of threads (for example, to accommodate high latency of proxy targets), more memory produces better performance.

UltraSPARC T1 or better
SPARC64 VII or better
SPARC T3 or better

Xeon 2x4-core at 3.6 GHz or higher.

Higher core counts do not improve performance. See the Performance, Planning, and Tuning Guide for more information.

At least 1 GB of local hard disk space (not NFS).

For Linux, at least 2 GB of hard disk space is required.

Two physical interfaces on a Gigabit Ethernet network.

Multipath configuration is required.

Table 14: Session State Register SBRC and Management Node Host Hardware Configurations for 64-Bit SBR Carrier

Server

RAM

Linux CPU

Free Disk Space

Network Interfaces

64-Bit SBRC and/or Management Node Host (Minimum Configuration)

8 GB RAM.

Xeon 2-core at 2 GHz supported for testing and M-only node.

Xeon 4-core or 2x2-core supported for production for a single SM node.

At least 8 GB of local hard disk space (not NFS).

Two physical interfaces on a 100 Base-T network.

Multipath configuration is required.

64-Bit SBRC and/or Management Node Host (Recommended Configuration)

16 GB RAM or more.

If Mitel’s Signalware communication stack is used, for systems processing a heavier-than-normal load (for instance, with WiMAX or additional session licenses), or when configuring a large number of threads (for example, to accommodate high latency of proxy targets), more memory produces better performance.

Xeon 2x4-core at 3.6 GHz or higher.

Higher core counts do not improve performance. See the Performance, Planning, and Tuning Guide for more information.

At least 16 GB of local hard disk space (not NFS).

Two physical interfaces on a Gigabit Ethernet network.

Multipath configuration is required.

Data Node Hosts

Table 15 lists the hardware requirements for Session State Register data node hosts.

All data node hosts in a cluster must have the same configuration. Because they collaborate to keep a shared database in virtual shared memory, the processing power, RAM, and communications capability of all the machines need to be very similar.

Note: This free disk space shown in Table 15 must be available specifically to the /opt file system for installation of the SSR software.

Table 15: Session State Register Data Node Host Hardware Configurations

Server

RAM

Solaris CPU

Linux CPU

Free Disk Space

Network Interfaces

Data Node Host (Minimum Configuration)

10 GB RAM.

SPARC64 VII or better. T-series is supported for low-throughput environments.

Xeon 2-core at 2.0 GHz supported for testing.

Xeon 4-core or 2x2-core at 2.4 GHz supported for production.

The local disk space requirement is related to the amount of RAM in the system. To calculate the minimum requirement for the amount of RAM on the system, use the formula: (RAM - 4 GB) * 12.

For example, a system with 16 GB of RAM requires a minimum of (16 GB - 4 GB) * 12, or 144 GB of local disk storage space.

Two physical interfaces on a 100 Base-T network.

Multipath configuration is required.

Data Node Host (Recommended Configuration)

More than 10 GB RAM.

More than the minimum of 10 GB of RAM supports more connections because more of the SSR database can be held in memory. More database in memory may translate into faster processing because disk operations are minimized.

Note: In particular, more memory is required if you want the SSR to store more CST data; that is, if config.ini DataMemory and IndexMemory parameters are manually increased.

SPARC64 VII 2.53 GHz or better. 2xSPARC64 VII for highest throughput.

Xeon 2X4-core at 3.6 GHz or higher for highest throughput.

Two physical interfaces on a Gigabit Ethernet network.

Multipath configuration is required.

Checking Free Disk Space

Use the df command to verify the amount of free disk space on a potential server.

Execute:
df -hk

Figure 11: Checking Free Disk Space with the df Command

Checking Free Disk Space with the df
Command

Software

The Steel-Belted Radius Carrier software can be installed on both Solaris and Linux operating systems.

Note: You cannot run multiple instances of SBR Carrier on Solaris and Linux platforms.

Solaris

Specific versions of the Solaris operating system, patches, and Perl are required for all machines. SBR Carrier has been qualified and is supported on Oracle Solaris 10, 11.0, and 11.1 (SPARC). SBR Carrier requires Solaris operating system with kernel patch version 141444-09 or later. You can use the uname –a command to check the kernel patch version. SBR Carrier requires Oracle Solaris 10 10/08 for SPARC platforms with the appropriate patches. Table 16 lists the patches (or higher-numbered equivalent patches) required for Solaris 10.

Table 16: Required Patches

Patch Number

Name

117461-08

ld.so

119963-13

libC

Checking System Patch Levels

Gather the system’s patch information with the showrev command.

Note: The showrev command and patches are specific to Oracle Solaris 10 and are not supported on an Oracle Solaris 11 platform.

Execute:
showrev -a |sed -e 's/Obsoletes:.*$//'

Figure 12: Checking Server Patch Status with the showrev Command

Checking Server Patch Status with the showrev Command

This is not a complete listing; many patches are already present because they are bundled with the Oracle Solaris Update.

Special Notes on Solaris Platform Support

You need to consider the following special notes while using SBR Carrier on a Solaris platform:

  • To use the command-line tools (snmpget, scriptcheck, ldapsearch, and so on) for 64-bit Solaris, first set the library path environment variable and then run the command.

    To set the library path environment variable for 64-bit Solaris, execute the following strings:

    LD_LIBRARY_PATH_64=radiusdir:radiusdir/system/lib/:radiusdir
    /openldap:/usr/sfw/lib/sparcv9:/usr/lib/mps/sparcv9/:/usr/sbin/lib/sparcv9:/lib/sparcv9:/
    usr/lib/sparcv9:/usr/openwin/lib/sparcv9:/usr/dt/lib/sparcv9:/usr/proc/lib:/
    usr/local/lib/sparcv9:/opt/sfw/lib/sparcv9:/usr/ccs/lib/sparcv9:/usr/ucblib/sparcv9:

Linux

SBR Carrier supports Red Hat Enterprise Linux 6.1, 6.5, 6.6, 6.7, 7.0, and 7.2 on Intel (Xeon) hardware.

The SBR standalone configuration is supported on both 32-bit and 64-bit versions of the Linux operating system. The SBR cluster configuration is supported only on the 64-bit version of the Linux operating system.

Note: The 32-bit version of SBR Carrier is not supported on Red Hat Enterprise Linux 7.0 and 7.2.

SBR automatically updates the required shared packages from the Red Hat repository. A current Red Hat Enterprise Linux support subscription and an access to the Red Hat repository or a local repository are required to get the latest updates to shared packages. See the appropriate Red Hat administration manuals for more information.

SBR Carrier has been qualified only with NSS 3.19 or an earlier version.

Special Notes on Linux Platform Support

You need to consider the following special notes while using SBR Carrier on a Linux platform.

  • Oracle front ends are not supported on a Linux platform. The sqlaccessor.so and sqlaccessor.gen files are specific to Oracle plug-ins and should not be installed on a Linux platform. You must instead use the sqlaccessor_jdbc.gen file.
  • The authGateway and GWrelay processes must be restarted whenever SBR restarts. This is applicable only on Linux.
  • SMS authentication is deprecated and SMS libraries are not installed on a Linux platform.
  • SBR installation depends on the binary calculator (bc) command-line tool because the AddPools.sh script fails to run if the “bc” tool did not exist.

Table 17 lists the features that are limited to support on specific operating systems.

Table 17: Features and Their Supported OS

Feature

Linux Support?

32-bit Solaris Support?

64-bit Solaris Support?

VM Support?

32-bit SBR on 32-bit Linux

32-bit SBR on 64-bit Linux

64-bit SBR on 64-bit Linux

authGateway application

No

Yes

Yes

Yes

Yes

Yes

SIM authentication module and GWrelay application

No

Yes (RHEL 6 only)

Yes (RHEL 6 only)

Yes

Yes

Yes

SSR cluster

No

Yes

Yes

Yes

Yes

No*

Separate session database process for standalone version

No

Yes

No

No

No

Yes

Customer-written SDK plug-ins

Yes

Yes

No

Yes

No

Yes

*SSR cluster in virtualized environments is not officially supported. Juniper Networks may still provide support for known issues and for those where you can demonstrate the issue exists on the native OS.

Subject to the preceding limitation, SBR Carrier supports virtualization on Linux, VMware hypervisor, and logical domains on Solaris. SBR Carrier has been tested with the VMware ESXi 5.1 version. For more information on planning and tuning the performance of SBR Carrier running on the Linux and Solaris operating systems, see the Performance, Planning, and Tuning Guide.

Perl

Oracle Solaris 10 and 11 are shipped with Perl 5.8.4 and 5.8.8 respectively, and Steel-Belted Radius Carrier has been tested with these versions. Multiple Perl installations in discrete directories are supported, but attempting to use other versions of Perl with SBR Carrier may cause problems.

After installation, be sure that the first line of the radiusd script specifies the correct path to the Perl 5.8.4 executable. For example, if Perl 5.8.4 is installed in the default location, /usr/bin/perl, then the first line of the radiusd script must be:

#!/usr/bin/perl

LDAP Plug-in

The LDAP plug-in requires SASL, which is included with the SBR Carrier package only for Solaris versions and not for Linux versions. For a Linux machine, you must ensure that you have the SASL package installed before starting SBR.

Modified: 2017-03-07