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

Cleaning the Transition Server

To free the licenses used by the transition server, and clean up installed software, uninstall the SBR Carrier software. See Uninstalling Steel-Belted Radius Carrier Software.

  1. Log in as root.
  2. Navigate to the directory where you installed the Steel-Belted Radius Carrier package, usually /opt/JNPRsbr. Then, navigate to the /opt/JNPRsbr/radius subdirectory.
  3. Stop the RADIUS processes.

    Execute:
    ./sbrd stop radius

  4. Stop the ssr processes:
    ./sbrd stop ssr
  5. Navigate to the /opt/JNPRsbr/radius/install directory and run the configure script:

    Execute:
    ./configure

  6. From the menu of configuration tasks, enter 1 to specify Unconfigure Cluster Node.
    Configuring SBR Software
    ---------------------------------------------------------------------------
    SBR 8.30.50006 cluster 
    on SunOS 5.10 Generic_141444-09 node sbrha-4
    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.
    6.  Upgrade From Restricted Cluster License
            Used to upgrade from restricted cluster to regular cluster.
            Removes database restriction on the number of concurrent
            sessions and enables the addition of an expansion kit license
    Enter the number of the desired configuration task or quit (2,q): 1
    
  7. A warning message is displayed. Enter y to proceed.
    ---------------------------------------------------------------------------
    SBR 8.30.50006 temporary cluster cambridge
    on SunOS 5.10 Generic_141444-09 node sbrha-4(smdt)
    is configured and processes are down, may be reconfigured if desired
    ---------------------------------------------------------------------------
    Unconfiguring Cluster Node...
    WARNING: You are about to make irreversible changes to this node.
    Are you sure that you wish to continue? (y,n): y
    
  8. Clean up the user accounts.

    A prompt is displayed to delete or preserve and clean up the hadm user account and associated directories.

    • If you are going to reconfigure this server to serve as a standalone SBR Carrier server or become a node host in a cluster, enter n.
    • If you want the server to be used for other purposes, enter y.
    Locating OS user account and home directory...
    hadm:x:16666:65536::/opt/JNPRhadm:/bin/bash
    hadmg::65536:
    drwxrwx---   2 hadm     hadmg       1536 Mar 28 10:59 /opt/JNPRhadm
    WARNING: If you remove the OS user account hadm you will have
    to recreate it, the associated OS group account hadmg, and
    the associated home directory /opt/JNPRhadm
    This is neither necessary nor recommended if you are updating
    an existing configuration.  Remove the OS user account? [n]: 
  9. Enter q to end the script.
    Cleaning directories
    /opt/JNPRhadm
    /opt/JNPRmysql
    /opt/JNPRmysqld
    /opt/JNPRndb_mgmd
    /opt/JNPRndbd
    ---------------------------------------------------------------------------
    SBR 8.30.50006 cluster 
    on SunOS 5.10 Generic_141444-09 node sbrha-4
    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.
    6.  Upgrade From Restricted Cluster License
            Used to upgrade from restricted cluster to regular cluster.
            Removes database restriction on the number of concurrent
            sessions and enables the addition of an expansion kit license
    READY: last operation succeeded, node unconfigured.
    Enter the number of the desired configuration task or quit (2,q): q

Four-Server Strategy Only

  1. You can now set up the server as the second SBR/management node in the new cluster. Because all preparatory steps have already been performed, follow the steps in Setting Up the Second SBR/Management Node in a Starter Kit, with the exception of the last step for configuring the data nodes. After completing these steps, remember to return to this procedure to complete the remaining steps.
  1. Start the second SBR/management node using this sequence of commands:
    1. Log in to the SBR/management node as root.
    2. Change directories to /opt/JNPRsbr/radius/.
    3. Execute:
      ./sbrd start ssr
    4. Execute:
      ./sbrd status
    5. Examine each line and ensure the SSR process is running without error.
  2. Create the database on the SBR/management (sm) node:
    1. Log in as hadm.
    2. Execute:
      ./CreateDB.sh

      If you need to customize the sessions database, see Customizing the SSR Database Current Sessions Table.

  3. Start the RADIUS process on the SBR/management node:
    1. Log in as root.
    2. Change directories to /opt/JNPRsbr/radius/.
    3. Execute:
      ./sbrd start radius
    4. Execute:
      ./sbrd status
    5. Examine each line and ensure the RADIUS process is running without error.
  4. Now that the RADIUS process is running, you can complete the configuration using Web GUI. See Basic SBR Carrier Node Configuration. For complete details, see the SBR Carrier Administration and Configuration Guide.

Modified: 2017-03-07