Setting Up Data Node Hosts Included with the Starter Kit
Use this procedure for any data node host installation. The examples in this section install and set up each of the two data nodes in a Starter Kit, using the
bluecluster example, but the procedure is the same for expansion kit installations.Populating the JNPRShare Directory
Before running the
configurescript, make a local copy of the configuration files that were created during installation on the first combined .To copy the cluster's base configuration files to this target machine:
Execute:
cd /opt/JNPRshare/install/<cluster_name>For example:
cd /opt/JNPRshare/install/blue
- Use FTP binary mode to connect to the first server that was set up and navigate to the
radius/installsubdirectory of the directory in which theJNPRsbrpackage was installed (/opt/JNPRsbr/radius/installby default) on the source server.- Execute a
getcommand to transfer theconfigure.<cluster name>.tarfile to the local directory.For example:
bin
get configure.blue.tarFor example:
tar xvf configure.blue.tarThe output display includes five files similar to this example:
$tar xvf configure.cambridge.tarx dbcluster.rc, 1925 bytes, 4 tape blocksx config.ini, 2435 bytes, 5 tape blocksx my.cnf, 1017 bytes, 2 tape blocksx dbclusterndb.gen, 33474 bytes, 66 tape blocksx dbcluster.dat, 921 bytes, 2 tape blocksConfiguring the Host Software on the Data Nodes
To configure the software on a data node in a Starter Kit cluster:
NOTE: You must repeat this procedure on every data node in the cluster.
- 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/installsubdirectory and run:Execute:cd /opt/JNPRsbr/radius/install/
- Execute the
configurescript to install the Steel-Belted Radius Carrier server software:Execute:./configure- 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
- From the menu of configuration tasks, enter
3to specifyConfigure Cluster Node.Configuring SBR Software---------------------------------------------------------------------------SBR 7.20.4712 clusteron SunOS 5.10 Generic_120011-14 node blue-18is not configured and processes are down, needs to be configured---------------------------------------------------------------------------1. Unconfigure Cluster NodeNot used when merely updating existing cluster definitions.2. Generate Cluster DefinitionCreates new or updates existing cluster definitions.Modifies the shared directory but does not modify this node.3. Configure Cluster NodeTo be preceded by 'Generate Cluster Definition' on any node.Must be invoked on each and every node of the cluster.4. Reconfigure RADIUS ServerOnly on SBR nodes, updates the existing SBR configuration.5. Create Temporary ClusterUsed 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- 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]:
blueYou 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.
- The system reads the configuration files that you copied to the server and prompts you to change some settings to adapt them to this server. Enter
yto proceed.WARNING: You are about to make irreversible changes to this node.Are you sure that you wish to continue? [n]: yCleaning old directories/opt/JNPRhadm---------------------------------------------------------------------------SBR 7.20.4712 cluster blue{0s,2sm,0m,2d}on SunOS 5.10 Generic_120011-14 node blue-18.spgma.juniper.net(d)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.genView (v), accept (a), or reject (r) configuration files:a- Enter
ato accept the modified configuration files and continue orvto view them.
CAUTION: We recommend that you enter an
rto reject them only if a serious error was made when you provided information. We recommend that you not edit these files.
- Specify that you want to configure the data node host to autoboot (restart automatically when the operating system is restarted).
Enable (e), disable (d), or preserve (p) autoboot scripts [e]: eA local
/radiusdir/radius/sbrdscript is always created, and/opt/JNPRhadm/sbrdis always a symbolic link to this local copy.
- If you enter e (enable), the
configurescript copies the localsbrdscript 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
configurescript removes all copies of thesbrdscript from/etc/init.d, thus, disabling autoboot for all versions of Steel-Belted Radius Carrier.- If you enter p (preserve), the
configurescript does nothing, thereby leaving your previous autoboot scripts unchanged.
- Repeat this procedure on each data node in the cluster.
- Now that the two SBR/management (sm) nodes and two data (d) nodes are configured, start the cluster following the procedure described in Initial Cluster Startup Procedure.