Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Setting Up a Starter Kit’s First SBR/Management Node

 

This section describes installing software on the first server in a Starter Kit cluster, usually a server that you want to host a SBR node/management node (sm). The procedure for this first server is unique because it includes creating configuration files for all nodes in the cluster.

Tip

If you are going to use centralized Configuration Management (CCM) to share SBR Carrier configuration files between SBR nodes, remember that the primary server must be installed before replicas. You want the first server you work on in the cluster to be the CCM primary server.

Configuring the Host Software on the First Server in the Cluster

Configuring the Host Software on the First Server in the Cluster

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

To install software on the first server in a cluster, which you want to host a SBR Carrier and a Management Node:

  1. As root, navigate to the directory where you installed the Steel-Belted Radius Carrier package. For information about directory in which Steel-Belted Radius Carrier package is installed, see Unpacking Session State Register Software.

    Then, navigate to the radius/install subdirectory and run:

    Execute:

    cd /opt/JNPRsbr/radius/install/

  2. Run the configure script:

    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 2 to specify “Generate Cluster Definition.”

  5. Specify the name of the cluster.

    Enter the name exactly as you specified it in Table 9.

    Enter SBR cluster name [MyCluster]: MyCluster

  6. Enter SSR license numbers and the number and type of nodes in the cluster.

    If a Restricted Cluster license is provided as input for a Starter Kit license, you are not prompted for an Expansion Kit license. By default, you have a minimal cluster of two SBR nodes, two management nodes, and two data nodes.

  7. Verify the configuration that you specified is accurate, and enter y to continue.

  8. Enter, for each node:

    • The node name

    • Type of node

    • Node ID

    • SBR Carrier license numbers (if required)

    • The IP address for each node

    The information you need is in Table 9.

  9. The system generates the required configuration files and prompts you to view, accept, or reject them. Enter a to accept them 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.

  10. From the menu of configuration tasks, enter 3 to specify “Configure Cluster Node.”

  11. Specify the name of the cluster.

    Enter the name exactly as you specified it in Table 9.

    Enter SBR cluster name [MyCluster]: MyCluster

  12. Specify whether you want to use the JRE installed in your system to enable JDBC plug-ins and JavaScript implementation.

    • If no, press Enter to proceed to the next prompt. SBR Carrier does not support JDBC plug-ins unless you specify a valid JRE path.

    • If yes, type y and press Enter. You are prompted to specify the path where the JRE is installed in your system. The Java Virtual Machine (JVM) architecture should be compatible with SBR Carrier.

      Note

      Java 1.8.0 or a later version is required to access the Web GUI. To support both JDBC plug-ins and Web GUI, it is recommended to use Java 1.8.0 or a later version with the JVM architecture compatible with your SBR Carrier. For example, if you are using the 64-bit version of SBR Carrier, you must use the 64-bit version of Java 1.8.0 or later.

      Note

      If you enter an incorrect JVM path three times, SBR Carrier proceeds to the next step. In this case, you will not be able to use JDBC plug-ins. To specify the valid JVM path, you need to run the configure script again.

  13. The script prompts for the type of installation, either a new installation or a migration from an earlier release:

    • For a new installation, enter n.

    • If you are migrating an existing Steel-Belted Radius Carrier installation and have copied a previous release’s files to the Release 8.6.0 server (in Creating a Copy of Existing SBR Server Release Files for Migration), enter the directory path to the copy of the old installation.

      For example:

    • If you want to search well known locations in the file system for pre-existing installations or backups of SBR software, enter s. You are presented with a list of directories from which you may choose to migrate, if any are found.

  14. Specify the username of the UNIX account that you intend to use to gain access to this machine using the Web GUI. The UNIX account must be defined on this machine (for example by /etc/passwd or NIS) and must have a valid, non-empty password. Additional accounts may be specified using the Web GUI.

    Press Enter to accept the default, root.

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

    CCM allows you to replicate substantial portions of a particular SBR node's configuration across multiple SBR nodes. The SBR node to be replicated is known as the primary and the SBR nodes on which the primary configuration is replicated are known as replicas. The entire set of an SBR primary and all of its replicas are known as an SBR replication group. Although any given SBR replication group typically includes all SBR nodes in a particular SSR cluster, an SBR replication group can span multiple clusters (including standalone SBR nodes) or can span only a few SBR nodes in a cluster. SBR nodes for which CCM is not enabled are known as autonomous because they are configured independently of one another.

    The rest of this task assumes that you want to configure a typical SBR replication group that includes all SBR nodes in this cluster. If you do not want to enable CCM then skip the rest of this task.

  16. Specify the server role.

    1. When CCM is enabled, configure this first SBR/management (sm) node as an SBR primary.

    2. You are prompted to configure the primary secret you want to use on this SBR replication group:

      Type the secret string and press Enter.

    3. You are prompted to confirm the primary secret.

      Confirm primary host secret:

      Type the secret string again and press Enter.

  17. Specify whether you want to use the auto-restart module that automatically restarts the SBR Carrier server in case of an unexpected shutdown.

    Note

    If Perl version 5 is not installed, the radiusd script will not run, even if enabled by configuration, and SBR Carrier will operate without the auto-restart module running.

  18. Specify whether you want to configure SBR Carrier to provide LDAP server emulation for configuration and statistics using the LCI.

    • If no, press Enter to accept the default.

    • If yes, enter y and press Enter. You are prompted to provide information for LCI configuration.

      1. When you are prompted for the port number, enter the port number that is used for communication between SBR Carrier and the LDAP client.

        Note

        SBR Carrier uses port 667 as the default for LDAP emulation to avoid conflict with other LDAP servers.

      2. The script displays the interfaces available in the system. When you are prompted to enter interface addresses on which Steel-Belted Radius Carrier should listen for LCI requests, enter the addresses you want to use from the Available Interfaces list.

        Note

        SBR Carrier uses all interfaces for listening to LCI requests if you do not enter any interfaces.

      3. Specify whether you want to change the default LCI password to prevent unauthorized LDAP clients from accessing your database.

        • If no, press Enter to accept the default password.

        • If yes, enter y and press Enter. You are prompted to enter a new password.

        Note

        Make sure that the entered password is at least 6 alphanumeric characters and not more than 8 characters in length. The password should not include any special characters other than underscore (’_’).

        Note

        The configure script also checks whether the LDAP utilities (such as ldapdelete, ldapmodify, and ldapsearch) are installed in your system. For Linux, a warning message is displayed if you have not installed any of these utilities in your system. For Solaris, LDAP utilities are shipped with SBR Carrier package.

  19. 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).)

    If no, press Enter to accept the default.

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

Note

You must configure 64-bit Oracle client for 64-bit SBR Carrier.

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

    If your SBR Carrier is using the optional SIM authentication module, or the WiMAX module with the EAP-AKA protocol, or the server is interfacing with a UMA or Femtocell network, you need to have Signalware installed to communicate with the SS7 network.

    To support this option, the server must already be configured to support SIGTRAN using Signalware. (See Installing the SIGTRAN Interface (Optional) for an overview, and SIGTRAN Support for Steel-Belted Radius Carrier for specific instructions.)

  2. Specify whether you want to start the GWrelay process while executing the ./sbrd start script.

  3. 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 SNMP management station 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 SNMP management station needs to be configured to the same setting.

        Specify SNMP agent listening port[161]: 24161

      5. 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.

  4. The script searches for the Java 1.8.0 or later version in the default system path and displays a confirmation message if found.

    If the specific version is not found, the script prompts you to enter the path where the specific Java version is installed in your system.

  5. Specify whether you want to install a custom SSL certificate for the Web GUI.

    • If no, press Enter. A self-signed certificate is created and installed in your server.

    • If yes, enter y and press Enter. You are prompted to enter the absolute path where the SSL certificate is available. For example, /opt/customSSLCert.pfx.

      When you are prompted for the password, enter the password to open the SSL certificate.

  1. 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 autoboot 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 the Steel-Belted Radius Carrier.

    • If you enter p (preserve), the configure script does nothing, thereby leaving your previous autoboot scripts unchanged.

    When you finish entering settings, the script configures Steel-Belted Radius Carrier with the specified settings and then displays:

  2. Configure the second SBR/management node in the Starter Kit by following the procedure described in Setting Up the Second SBR/Management Node in a Starter Kit.