For complete details about the hardware and software requirements for running a standalone Steel-Belted Radius Carrier server or the optional SBR Carrier Session State Register (SSR), see “Meeting System Requirements” in the Steel-Belted Radius Carrier Installation Guide.
SBR Carrier has been qualified and is supported on Oracle Solaris 126.96.36.199.0 (SPARC) and Red Hat Enterprise Linux 7.3, 7.4, 7.5, and 7.6 on Intel (Xeon) platforms.
SBR Carrier does not support RHEL 6.x, 7.0, 7.1, and 7.2.
SBR Carrier supports Oracle Solaris 188.8.131.52.0 or later version.
You cannot run multiple instances of SBR Carrier on Solaris and Linux platforms.
Make sure that nss-util, nss, nspr, gcc, openldap, Kerberos, cyrus-sasl, and zlib libraries are installed on your system before installing the SBR Carrier software. The libraries are normally available and installed with the OS base bundle. SBR Carrier supports the package versions of preceding libraries that are provided with Solaris 184.108.40.206.0 or later and RHEL 7.3 or later.
We recommend you to update the OS regularly for security reasons. Any questions concerning vulnerabilities of libraries that are not distributed by Juniper Networks should be addressed to the OS vendor (Red Hat or Oracle).
SBR Carrier supports virtualization on Linux, VMware hypervisor, Kernel-based Virtual Machine (KVM) hypervisor, and logical domains on Solaris. SBR Carrier has been tested with VMware ESXi 5.1, 5.5, 6.0, and 6.5 versions and KVM hypervisor on RHEL 7.3. 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.
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.
Steel-Belted Radius Carrier has been tested with Perl 5.8.4 and 5.8.8. Multiple Perl installations in discrete directories are supported, but attempting to use other versions of Perl with SBR Carrier may cause problems.
The LDAP plug-in requires SASL, which is not included with the SBR Carrier package. You must ensure that you have the SASL package installed before starting SBR Carrier.
The Web GUI can be launched in different browsers across different platforms. Table 2 lists the tested browser versions and the operating systems.
Table 2: Web GUI—Tested Browsers
36 and later
9 and later
31 and later
23 and later
12 and later
Java 1.8.0 or a later version is required to be installed in the server to access the Web GUI.
When you upgrade from an earlier SBR Carrier version to the current version, clear your browser’s cache before launching the Web GUI.
External Database Requirements
Steel-Belted Radius Carrier supports:
Any external database with a compatible JDBC connector.
Oracle native client versions 11 and 12 to connect Oracle database versions 11 and 12 on Solaris.
Oracle native client versions 11 and 12 to connect Oracle database versions 11 and 12 on Linux.
For SBR Carrier to act as an Oracle native client, the Oracle 64-bit client must be set up before installing 64-bit version of SBR Carrier, because the Oracle server location is used during installation.
SBR Carrier has been tested with MySQL version 5.1.69, Oracle database versions 11.2.0 and 220.127.116.11 on Solaris, and Oracle database versions 11.2.0 and 12.2.0 on Linux.
Signalware and SIM Requirements
To support the optional SIM authentication module, Signalware 9 with Service Pack 6.5 must be installed before installing SBR Carrier.
Service Pack 6.5 must be installed; otherwise, Steel-Belted Radius Carrier cannot use the Signalware communications stack.
For more information, see the SBR Carrier Installation Guide.
SBR Carrier does not support the Signalware communication stack on Solaris.
SS7 cards are no longer supported.