Steel-Belted Radius Carrier 7.2.x Installaion Guide > Installing Session State Register Nodes > Setting Up the Second SBR/Management Node in a Starter Kit

Setting Up the Second SBR/Management Node in a Starter Kit

This section describes installing the software on the second SBR/management node host in a Starter Kit cluster, following the initial combined SBR/management node installation. (See Setting Up a Starter Kit's First SBR/Management Node.)

CAUTION: If you have not installed the Cluster's first server yet, do not proceed with the cluster installation.

Populating the JNPRShare Directory

Before running the configure script, make a local copy of the configuration files that were created during installation on the first server. (In the following procedures, FTP is used to copy files. You may use whatever distribution mechanism you want to keep the share directories synchronized, so long as all /JNPRshare directories on all servers are readable and writable by the root and hadm accounts.)

To copy the cluster's base configuration files to this target machine:

1. Log in as hadm.
2. Change directories to the install directory on the local server.

Execute:
cd /opt/JNPRshare/install/<cluster_name> 

For example:
cd /opt/JNPRshare/install/blue

3. Use FTP binary mode to connect to the first server that was set up and navigate to the radius/install subdirectory of the directory in which the JNPRsbr package was installed (/opt/JNPRsbr/radius/install by default) on the source server.
4. Execute a get command to transfer the configure.<cluster name>.tar file to the local directory.

For example:
bin
get configure.blue.tar

5. Extract the configuration files from the archive.

For example:
tar xvf configure.blue.tar

The output display includes five files similar to this example:

$ tar xvf configure.blue.tar 

x dbcluster.rc, 1925 bytes, 4 tape blocks

x config.ini, 2435 bytes, 5 tape blocks

x my.cnf, 1017 bytes, 2 tape blocks

x dbclusterndb.gen, 33474 bytes, 66 tape blocks

x dbcluster.dat, 921 bytes, 2 tape blocks

Configuring Host Software on the Second SBR Carrier and Management Node

Before starting this procedure, review Before You Install Software. In particular, review requirements for: Setting Up External Database Connectivity (Optional) and Installing Signalware and SS7 Interfaces (Optional), as steps in this procedure require the server to be preconfigured for these capabilities.

To configure SSR software on the second SBR Carrier and management node host in a Starter Kit cluster:

1. As root, navigate to the directory where you installed the Steel-Belted Radius Carrier package in Step 3, Extract the Steel-Belted Radius Carrier installation package.

Navigate to the radius/install subdirectory and run:

Execute:

cd /opt/JNPRsbr/radius/install/

2. Execute the configure script to install the Steel-Belted Radius Carrier server software:

Execute:

./configure

3. Review and accept the Steel-Belted Radius Carrier license agreement.

Press the spacebar to move from one page to the next. When you are prompted to accept the terms of the license agreement, enter y.

Do you accept the terms in the license agreement? [n] y

4. From the menu of configuration tasks, enter 3 to specify Configure Cluster Node.

Configuring SBR Software

---------------------------------------------------------------------------

SBR 7.20.4712 cluster 

on SunOS 5.10 Generic_120011-14 node blue-2

is not configured and processes are down, needs to be configured

---------------------------------------------------------------------------

1.  Unconfigure Cluster Node

        Not used when merely updating existing cluster definitions.

2.  Generate Cluster Definition

        Creates new or updates existing cluster definitions.

        Modifies the shared directory but does not modify this node.

3.  Configure Cluster Node

        To be preceded by 'Generate Cluster Definition' on any node.

        Must be invoked on each and every node of the cluster.

4.  Reconfigure RADIUS Server

        Only on SBR nodes, updates the existing SBR configuration.

5.  Create Temporary Cluster

        Used to approximate a cluster using only this one machine.

        Intended for migration and demonstration purposes only.

Enter number of desired configuration task, or q to quit [2]: 3

5. Specify the name of the cluster.

Enter the name exactly as you specified it in Table 10, "Starter Kit Cluster, Machine, and Interface Naming Worksheet" .

Enter SBR cluster name [blue]: blue

You are prompted to verify whether you want to proceed, unless the script detects any unusual installation conditions (a pre-existing directory, for example). In some cases, you may be prompted to resolve or ignore them.

6. The system reads the configuration files that you copied to the server and prompts you to change some settings from the original server's to adapt them to this server. Enter y to proceed.

WARNING: You are about to make irreversible changes to this node.

Are you sure that you wish to continue? [n]: y

Cleaning old directories

/opt/JNPRhadm

---------------------------------------------------------------------------

SBR 7.20.4712 cluster blue{0s,2sm,0m,2d}

on SunOS 5.10 Generic_120011-14 node blue-2.spgma.juniper.net(sm)

Reviewing Configuration Files...

---------------------------------------------------------------------------

/opt/JNPRsbr/radius/install/tmp/dbcluster.rc

/opt/JNPRsbr/radius/install/tmp/config.ini

/opt/JNPRsbr/radius/install/tmp/my.cnf

/opt/JNPRsbr/radius/install/tmp/dbclusterndb.gen

View (v), accept (a), or reject (r) configuration files: a

7. Enter a to accept the modified configuration files and continue or v to view them.
   

   CAUTION: We recommend that you enter an r to reject them only if a serious error was made when you provided information. We recommend that you not edit these files.

   
   
8. Specify the server's initial admin user.

Enter initial admin user (UNIX account must have a valid password) [root]: 

Press Enter to accept the default, root.

9. Specify whether you want to set up Centralized Configuration Management (CCM).

Enable Centralized Configuration Management (CCM) for this SBR node? [n]: y

Then specify the server role.

Configure SBR node as CCM primary (p) or replica (r)? [r]: r

1. Because this is not the first server to be installed, if CCM is used, this server cannot be the primary. Enter r to set the role as replica.
2. Specify the primary CCM server's hostname.

Enter primary host name: 

For example:
Enter primary host name: blue-1.juniper.net

1. Specify the primary CCM server's IP address.

Enter primary host IPv4 address [172.28.84.35]: 

For example:
Enter primary host IPv4 address [172.28.84.35]: 198.168.0.1

1. Specify the primary host secret string.
   Enter primary host secret:
   
   Type the secret string and press Enter.
2. Confirm the host secret string.
   Confirm primary host secret:
   
   Type the secret string again and press Enter.

10. Specify whether you want to configure Steel-Belted Radius Carrier for use with an Oracle database.

To support this option, the server must already be configured as an Oracle client (See Setting Up External Database Connectivity (Optional).).

Configuring for use with generic database

Do you want to configure for use with Oracle? [n]:

If no, press Enter.

If yes, type y and press Enter. You are prompted for version and path information for the Oracle library files.

Do you want to configure for use with Oracle? [n]: y

Supported Oracle versions:  9, 10

What version of Oracle will be used? [9]: 10

Configuring for use with Oracle 10

Setting the environment variable ORACLE_HOME

Enter ORACLE_HOME [/dbms/u10/app/oracle/product/10.2.0]: 

Enter path for Oracle shared libraries 
[/dbms/u10/app/oracle/product/10.2.0/lib32]: 

Setting the environment variable TNS_ADMIN

Enter TNS_AMDIN [/dbms/u10/app/oracle/product/10.2.0/network/admin]:

NOTE: Starting with some Oracle 9 releases, Oracle began shipping 32-bit libraries in a new /lib32 directory that is separate from the traditional /lib directory which now contains only 64-bit binaries. As Steel-Belted Radius Carrier is a 32-bit application, it requires the 32-bit Oracle libraries. Specify the Oracle /lib directory only if no /lib32 directory is present.

11. Specify whether you want the Steel-Belted Radius Carrier server to communicate with an SS7 system.

To support this option, the server must already be configured with Signalware and, if required, an SS7 communication interface. (See Installing Signalware and SS7 Interfaces (Optional) for an overview, and Signalware 9 Support for Steel-Belted Radius Carrier for specific instructions.)

Do you want to configure for use with SS7? [n]: y

Configuring for use with SS7

Setting the environment variable OMNI_HOME

Enter OMNI_HOME [/opt/JNPRss7]: 

12. Specify whether you want to install the optional SNMP module to monitor your Steel-Belted Radius Carrier server from an SNMP management station.

Do you want to configure SNMP? [n]:

• If no, press Enter to proceed to the next prompt.
• If yes, type y and press Enter. The installer prompts you for the information it needs to configure the jnprsnmpd.conf and startsnmp.sh files.

1. When you are prompted for a community string, enter the community string used to validate information sent from the SNMP subagent on the Steel-Belted Radius Carrier server to your SNMP management station.

Choose a community string: public

2. When you are prompted for a range of IPv4 addresses, specify a starting IP address in Classless Inter-Domain Routing format. To specify that only one host may query the agent, enter the IP address of the host followed by /32. To specify that any host on a designated class C network may query the agent, enter the starting address of the network followed by /24.

Specify the range of IPv4 addresses that may query this agent, such as 
1.2.3.0/24.

Address range: 192.168.70.0/24

3. If you are using SNMPv2, enter the DNS name or IP address of the trap sink that you want to receive trap information from the SNMP subagent on the Steel-Belted Radius Carrier server.

SNMPv2 trap sink: 192.168.70.86

4. Set the SNMP agent port.

Although you may specify the default SNMP port, 161, we recommend that you specify a different port to avoid contention with other agents that are likely to already be using 161. If you choose an alternate port, make a note of it because your MIB browser needs to be configured to the same setting.

Specify SNMP agent listening port[161]: 24161

1. Specify a trap sink address, if required.

Optionally specify a trap sink address that will receive SNMPv2 trap 
[localhost]: 172.28.72.83 2

SNMPv2 trap sink port[162]: 

Configuration of SNMP complete.

13. Specify whether you want the Steel-Belted Radius Carrier server to communicate with an RSA server.

To support this option, the server must already be configured as an RSA Client. See Setting Up RSA Authorization Client (Optional).

Do you want to register SBR with an RSA server (requires RSA Auth Manager 
6.1 or later)? [n]: y

 NOTE: When you register your Steel-Belted Radius Carrier master or replica server as an Agent Host with an RSA SecurID server, it registers itself as an RSA replica. This is normal behavior.



 

14. Specify whether you want to configure the Steel-Belted Radius Carrier software (both RADIUS and SSR processes as appropriate for the given node type) to autoboot (restart automatically when the operating system is restarted). We recommend that you enable this behavior.

Enable (e), disable (d), or preserve (p) autoboot scripts [e]: e

A local /radiusdir/radius/sbrd script is always created, and /opt/JNPRhadm/sbrd is always a symbolic link to this local copy.

• If you enter e (enable), the configure script copies the local sbrd script to /etc/init.d, where it is automatically invoked by the OS whenever the OS is stopped or started.
• If you enter d (disable), the configure script removes all copies of the sbrd script from /etc/init.d, thus, disabling autoboot for all versions of Steel-Belted Radius Carrier.
• If you enter p (preserve), the configure script does nothing, thereby leaving your previous autoboot scripts unchanged.

15. When prompted, confirm that you want the installation to proceed and to configure Steel-Belted Radius Carrier with the specified settings. When the script finishes, it displays:

The SBR Administrator can be launched using the following URL:

http://<servername>:1812

Configuration complete

16. Configure the two data nodes in the Starter Kit using the procedure described in Setting Up Data Node Hosts Included with the Starter Kit.