Session State Register Cluster Installation Checklist
Before You Begin
Before You Begin
Before you begin to install the Session State Register software and after you read all of this chapter, perform these preliminary tasks or verify that they have been accomplished:
Review the Steel-Belted Radius Carrier Release Notes for up-to-date information that became available after the Steel-Belted Radius Carrier guides were published.
Download the most recent Release Notes file from:
If the information in the Release Notes differs from the information in any Steel-Belted Radius Carrier guide, follow the Release Notes.
Read the next chapter, Planning Your Session State Register Cluster, and fill out the provided worksheet so you have all required information ready to use during the installation.
If you are migrating settings from a SBR/HA 5.5 server installation, put a copy of that installation on the system that you want to host Release 8.4.1.
The recommended method is:
As root on the old server, shut down the SBR daemon.
Execute: /radiusdir /sbrd stop.
Create a gzip archive of the radiusdir directory, preserving the file structure.
Change directories to /opt/JNPRsbr/ and execute (for example):
tar cfE - radius |gzip > 55_radius.tgz
As root on the Release 8.4.1 host, create a working directory for the archive:
mkdir -p /opt/JNPRsbr/PreviousRelease_backup
Use FTP binary mode to copy the archive file to the Release 8.4.1 host.
Gunzip the archive in the working directory. This does not create a working installation, but serves as a source of files that can be reused by the Release 8.4.1 server.
Execute (using the example file name):
gunzip 55_radius.tgz |tar xf -
Check the file permissions on the unzipped archive to ensure that the files are writable.
See Creating a Copy of Existing SBR Server Release Files for Migration for more information.
Ensure that all server chassis are physically secure.
To review recommendations on the server’s characteristics, see Selecting an Appropriate Server.
Verify root access on all servers.
Confirm that all server chassis provide at least the minimum hardware and software requirements.
Verify that all servers meet basic network requirements:
Verify the server role in the centralized configuration management (CCM) environment. The installation script can configure a Steel-Belted Radius Carrier server as:
An autonomous server that does not use CCM.
The primary server supplying a group of replication servers.
A replication server.
In an environment that uses replication servers, the primary server must be configured first to provide a base for replication.
If you are migrating from a SBR/HA 5.5 environment and CCM was in use, you may only migrate the same server type: autonomous to autonomous, primary to primary, and replica to replica.
(Optional) If you want the server to interact with a Lightweight Directory Access Protocol (LDAP) directory service agent, verify or record the path to the LDAP library files. (The default path is /usr/lib.)
(Optional) If you intend the Steel-Belted Radius Carrier server to authenticate using an external database, you need to:
Verify database compatibility and interoperability.
If the external database is Oracle, the Steel-Belted Radius Carrier server must be configured as a client of the Oracle server.
As you set up the client, collect this information, or if the client is already installed, record this information to use while installing SBR software:
Record the path to the local Oracle Home directory (for example: /opt/10g/app/oracle/product/10.2.0.3).
Record the path to the local Oracle shared library (for example: /opt/10g/app/oracle/product/10.2.0.3/lib32)
Record the path to the local TNS_ADMIN (for example: /opt/10g/app/oracle/product/10.2.0.3/network/admin)
SIM / WiMAX / SIGTRAN
(Required only for these modules) Install and configure Signalware 9 with Service Pack 6V software, following the product documentation and the guidelines in SIGTRAN Support for Steel-Belted Radius Carrier.
This step is only required for the optional WiMAX mobility module if using EAP-AKA, which requires the optional SIM authentication module. This step is mandatory for the SIM authentication module and any other SIGTRAN applications.
Installing Session State Register Software
Installing Session State Register Software
If you have completed all items on the “Before You Begin” list (for each item for each server in the cluster), you are ready to install the software. The servers must be installed in a particular order, so you perform this portion of the list four times for a Starter Kit.
The order of installation for a four-server Starter Kit cluster is:
First SBR Carrier/management node host. This server is also the primary server if CCM is used because it must be installed before the replica nodes.
Second SBR Carrier/management node host.
First data node host.
Second data node host.
Repeat these key steps on each server:
Unpack the Session State Register software.
If you are not familiar with UNIX package management commands, see Package Management Commands.
Run the Session State Register configure script to set up or read in cluster and server configuration files.
Restart the Session State Register configure script.
After the Session State Register software is on all servers in the cluster, you can ensure that the base software runs properly and then perform basic configuration steps:
Start the cluster.
Launch the Web GUI.
Use an HTML browser to address one of the Steel-Belted Radius Carrier servers. Download the Administrator client application and log in as root. Also confirm that the links to the documentation work. See Launching Web GUI.
Verify that you can download and run the application both from the local host and from a workstation on the network.
Configure the server.
For a new installation, configuring the environment includes basic low-level configuration tasks such as:
Configuring communications between any additional devices and the Steel-Belted Radius Carrier servers.
Adding additional users to the server.
Configure SNMP. If you elected not to configure the Steel-Belted Radius Carrier SNMP agent during software installation and other agents also run on the server (such as the Solaris operating system agent), you must adjust the ports the agents use so multiple agents do not contend for the same resource.
See Configuring SNMP.
Set up shared SSR IP address pools and a local emergency pool. See Setting Up IP Address Pools.