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

Upgrading the SM Nodes in the Cluster

After all M nodes in the cluster are upgraded, you need to upgrade the software in SM nodes. To perform a rolling restart upgrade in SM nodes of your cluster, install the new software and configure it on each SM node in the cluster.

Note: Execute this procedure on each SM node, one at a time. This example procedure uses one SM node sbr1.englab.juniper.net (10.212.10.213).

Note: If you have limited disk space, you can just copy the file *mysqlcluster*.tar.gz to every SM node, or mount it over NFS. Refer to Installing Only the Latest MySQL Package.

Installing the New SBRC Software on the SM Node

Execute the following steps to install the new SBRC software package on the SM node:

  1. Stop the SSR process.

    Log in to the node as root and execute:
    root@sbr1: /opt/JNPRsbr/radius/sbrd stop ssr

    Stopping ssr auxiliary processes
    Stopping ssr management processes
    Connected to Management Server at: 10.212.10.213:5235
    Node 51 has shutdown.
    Disconnecting to allow Management Server to shutdown
    
    
  2. Log in to a M node and execute ./sbrd status. Verify that the SM node is disconnected from the other nodes.

    Execute:
    root@bng-mars: /opt/JNPRsbr/radius/sbrd status

    ---------------------------------------------------------------------------
    SBR 7.60-R1.50242 cluster 6node_cluster{1s,1sm,2m,2d}
    on SunOS 5.10 Generic_120011-14 node bng-mars.englab.juniper.net(m)
    ---------------------------------------------------------------------------
    
    Connected to Management Server at: 10.212.10.66:5235
    
    [ndbd(NDB)]	2 node(s)
    id=1	@10.212.10.188  (mysql-5.5.20 ndb-7.2.5, Nodegroup: 0, *)
    id=2	@10.212.10.67  (mysql-5.5.20 ndb-7.2.5, Nodegroup: 0)
    
    [ndb_mgmd(MGM)]	3 node(s)
    id=51 (not connected, accepting connect from 10.212.10.213)
    id=52	@10.212.10.68  (mysql-5.6.28 ndb-7.4.10)
    id=53	@10.212.10.66  (mysql-5.6.28 ndb-7.4.10)
    
    [mysqld(API)]	5 node(s)
    id=61 (not connected, accepting connect from 10.212.10.213)
    id=62	@10.212.10.68  (mysql-5.6.28 ndb-7.4.10)
    id=63	@10.212.10.66  (mysql-5.6.28 ndb-7.4.10)
    id=100 (not connected, accepting connect from 10.212.10.213)
    id=101	@10.212.10.65  (mysql-5.5.20 ndb-7.2.5)
    
    hadm     17775 ndb_mgmd --config-cache=0 --configdir=/opt/JNPRhadm
    hadm     17849 /bin/sh /opt/JNPRmysql/install/bin/mysqld_safe
    hadm     18196 /opt/JNPRmysql/install/bin/mysqld --basedir=/opt/JNPRmysql/install 
    --datadir=/opt/JNPRmysqld/data --plugin-dir=/opt/JNPRmysql/install/lib/plugin --log-error=/opt/JNPRmysqld/mysqld_safe.err
     --pid-file=/opt/JNPRmysqld/mysqld.pid --socket=/opt/JNPRhadm/.mysql.sock --port=3001
    
  3. Stop the RADIUS process in the SM node.

    Execute:
    root@sbr1: /opt/JNPRsbr/radius/sbrd stop radius

    Stopping radius server processes
    waiting for radius
    10 seconds elapsed, still waiting
    radius stopped
    

    Check the status of the SM node after stopping the RADIUS process.

    Execute:
    root@sbr1: /opt/JNPRsbr/radius/sbrd status

    ---------------------------------------------------------------------------
    SBR 7.60-R1.50242 cluster 6node_cluster{1s,1sm,2m,2d}
    on SunOS 5.10 Generic_120011-14 node sbr1.englab.juniper.net(sm)
    ---------------------------------------------------------------------------
    
  4. Navigate to the install directory.

    Execute:
    root@sbr1: /opt/JNPRsbr/radius/install

  5. Unconfigure the node.

    Execute:
    root@sbr1:./unconfigure

    Unconfiguring SBR Software
    
    ---------------------------------------------------------------------------
    SBR 7.60-R1.50242 cluster 6node_cluster{1s,1sm,2m,2d}
    on SunOS 5.10 Generic_120011-14 node sbr1.englab.juniper.net(sm)
    is configured and processes are down, may be reconfigured if desired
    ---------------------------------------------------------------------------
    
    Unconfiguring Cluster Node...
    
    WARNING: You are about to unconfigure this node.
    Are you sure that you wish to continue? (y,n): y
    
    Cleaning directories
    /opt/JNPRhadm
    /opt/JNPRmysql
    /opt/JNPRmysqld
    /opt/JNPRndb_mgmd
    /opt/JNPRndbd
    
    Locating shared directory...
    drwxrwxr-x   2 hadm     hadmg        512 Jan 11 02:32 /opt/JNPRshare/install/6node_cluster
    
    WARNING: If you remove the shared directory for this cluster, you
    will either have to recover the data from another cluster node or
    reconfigure the entire cluster again.  This is neither necessary
    nor recommended if you are updating an existing configuration.
    Remove the shared directory for this cluster? [n]:
    
    Locating OS user account and home directory...
    hadm:x:50025:65540:SBR software:/opt/JNPRhadm:/bin/bash
    hadmg::65540:
    drwxrwx---   2 hadm     hadmg       1536 Jan 11 06:54 /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]:
    
    Unconfigured
    
  6. Move your original installation to a different location to prevent the removal of files. Be sure not to move the /opt/JNPRshare directory, which should contain your original cluster configuration files. For example, if you previously installed Release 7.6.0, execute the following as root:
    1. Navigate to the opt directory: root@sbr1: cd /opt.
    2. Create a new directory: root@sbr1: mkdir 760.
    3. Move the configuration files to the new directory: root@sbr1: mv JNPRsbr JNPRmysql JNPRmysqld JNPRhadm JNPRndb_mgmd JNPRndbd 760.
    4. Remove the old software package: root@sbr1: pkgrm JNPRsbr.
  7. Install the new SBRC software distribution package.

    Execute:
    root@sbr1: cd /opt/tmp pkgadd –d

    The following packages are available:
      1  JNPRsbr.pkg     JNPRsbr - Juniper Networks Steel-Belted Radius (Carrier Cluster Edition)
                         (sparc) 8.30.50242
    
    Select package(s) you wish to process (or 'all' to process
    all packages). (default: all) [?,??,q]: 1
    
  8. Enter 1 to install the JNPRsbr.pkg. The system installs the new software.
    Processing package instance JNPRsbr.pkg 
    .
    .
    .
    Installation of JNPRsbr.pkg was successful.
  9. Once the system displays the message Installation of JNPRsbr.pkg was successful, repeat this procedure on the next SM node. Once the new software is installed on each SM node, proceed to Configuring the New SBRC Software on the SM Node.

Configuring the New SBRC Software on the SM Node

Configure the new software on each SM node, one at a time:

  1. Configure the SBRC software on the SM node, using the original cluster configuration files.

    Execute:
    root@sbr1: ./configure

    Configuring SBR Software
    
    
    
    END USER LICENSE AGREEMENT READ THIS END USER LICENSE AGREEMENT ("AGREEMENT") …………
    .
    .
    .
    .Do you accept the terms in the license agreement? [n]:    y
    
  2. Enter y to accept the license agreement.
    ---------------------------------------------------------------------------
    SBR 8.30-R1.50765 cluster
    on SunOS 5.10 Generic_141444-09 node sbr1.englab.juniper.net
    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 one 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): 3
    
  3. Enter 3 to select option 3. Configure Cluster Node.
    ---------------------------------------------------------------------------
    SBR 8.30-R1.50765 cluster
    on SunOS 5.10 Generic_141444-09 node sbr1.englab.juniper.net
    is not configured and processes are down, needs to be configured
    ---------------------------------------------------------------------------
    
    Configuring Cluster Node...
    
    
  4. Specify the name of your existing cluster. In this example the cluster name is “6node_cluster”.
    Enter SBR cluster name [sbr1]: 6node_cluster
    Reading shared configuration from /opt/JNPRshare/install/6node_cluster
    ......
    
  5. Migrate the configuration from your previous software release to the new software package. In most cases, you simply need to identify your previous installation. In this example, the cluster configuration is named configure.6node_cluster.tar (see the previous step), and is stored in the /opt/JNPRsbr/radius/install directory. Once you specify the configuration, SBRC migrates your configuration.

    Enter:
    root@sbr1: /opt/JNPRsbr/radius/install

    Reading shared configuration from /opt/JNPRshare/install/6node_cluster
    
    Enter absolute path to configure.6node_cluster.tar
    if you have it, or quit (q) so that you can get it from
    /opt/JNPRsbr/radius/install on the first cluster node.
    
    Generating configuration files
    
    Reviewing configuration files
    /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
    
  6. Enter a to accept the configuration files.
    WARNING: You are about to make irreversible changes to this node.
    Are you sure that you wish to continue? (y,n): y
    
  7. Enter y to continue.
    Cleaning directories
    /opt/JNPRhadm
    /opt/JNPRmysql
    /opt/JNPRmysqld
    /opt/JNPRndb_mgmd
    /opt/JNPRndbd
    
    Applying configuration
    
    Initializing Session State Register, please wait a few minutes...
    19949 Killed
    
    Do you want to configure Java Runtime Environment for JDBC Feature [n] :
    
    Please enter backup or radius directory from which to migrate.
    Enter n for new configuration, s to search, or q to quit
    [/opt/JNPRsbr/radius/install/backups/2010:10:21-08:31:21]:
    
    Migrating files, please wait...
    -
    
    WARNING: A manual merge may be required between the files located in
    /opt/JNPRsbr/radius (working files) and
    /opt/JNPRsbr/radius/install/backups/2010:10:21-08:32:18 (shipped files)
    
  8. Press Enter through the following prompts to keep your configuration.
    Enter initial admin user (UNIX account must have a valid password) [root]:
    Configuring for use with generic database
    Do you want to enable "Radius WatchDog" Process? [n]: 
    Do you want to enable "GWrelay" Process? [n]:
    Do you want to enable LCI? [n]: 
    Do you want to configure for use with Oracle? [n]:
    Removing oracle references from startup script
    Do you want to configure for use with SS7? [n]:
    Removing SS7 references from startup script
    Do you want to configure SNMP? [n]:
    Configuring Admin GUI Webserver
    Compatible Java version found : 
    Do you want to install custom SSL certificate for Admin WebServer? [n]:
  9. Enter e when prompted to enable the autoboot scripts.
    Enable (e), disable (d), or preserve (p) autoboot scripts [e]: e
  10. The main configuration menu is displayed.

    Enter q to quit.

    The SBR Admin Web GUI can be launched using the following URL:
    https://<servername>:2909
    
    ---------------------------------------------------------------------------
    SBR 8.30-R1.50765 cluster 6node_cluster{1s,1sm,2m,2d}
    on SunOS 5.10 Generic_141444-09 node sbr1.englab.juniper.net(sm)
    is configured and processes are down, may be reconfigured if desired
    ---------------------------------------------------------------------------
    
    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 one 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 configured.
    Enter the number of the desired configuration task or quit (4,q): q
    
  11. (Optional) A new utility, UpdateSchema.pl, has been added and will be used for future schema upgrades.
    1. First, you need to determine whether your schema needs to be updated for this release by executing UpdateSchema with no arguments as the hadm user.

      Execute:
      hadm@sbr1:~>perl ./UpdateSchema.pl

      Usage: perl UpdateSchema.pl [from version], where [from version] is SBR/HA 5.4 or 5.5. Other versions do not require a schema update. This command returns a list of schemas which need to be updated.

      Note: Future SBRC software releases may require additional updates, we recommend you execute this step every time you upgrade to determine if a schema upgrade is required.

    2. If you are running a software release that requires a schema change, execute the command again with the version from which you are upgrading. For example, from SBR/HA 5.5:

      Execute:
      hadm@sbr1:~>perl ./UpdateSchema.pl 5.5

      Altering Tables - Please wait...Done
  12. Start the SSR process on the SM node.

    Execute:
    root@sbr1: /opt/JNPRsbr/radius/sbrd start ssr

    Starting ssr management processes
    MySQL Cluster Management Server mysql-5.6.28 ndb-7.4.10
    2016-01-11 07:18:49 [MgmtSrvr] INFO     -- Skipping check of config directory since config cache is disabled.
    -Node 51: connected (Version 7.4.10)
    
    Starting ssr auxiliary processes
    
  13. Log in as the user ‘hadm’, navigate to the hadm user's home directory (/opt/JNPRhadm/ by default), and re-create the stored procedures by executing CreateDB.sh.

    If you need to customize the sessions database to match your existing cluster session database, see Customizing the SSR Database Current Sessions Table. Any customization must be done prior to running the CreateDB.sh script.

    Note: Despite its name, this command does not change the contents of your database, since the database already exists. However, it re-creates the stored procedures that are required by the administration scripts. Failure to execute this step results in inoperable management scripts, such as ShowSessions.sh, DelSession.sh, and CreateDB.sh.

  14. Start the RADIUS process on the SM node.

    Execute:
    root@sbr1:/opt/JNPRsbr/radius/sbrd start radius

    Starting radius server processes
    RADIUS: Process ID of daemon is 5405
    RADIUS: Starting DCF system
    RADIUS: Configuration checksum: 6A 3B 7A D5
    
    root@sbr1 [/opt/JNPRsbr/radius]
    $Starting webserver
    Document Root: /opt/JNPRsbr/radius/
    . 2016-01-11 07:21:17.217:INFO::main: Logging initialized @4945ms
    . . . . . . Webserver started
    
    root@sbr1 [/opt/JNPRsbr/radius]
    $AppleTalk
    AppleTalk
    AppleTalk
    RADIUS:
    RADIUS: Steel-Belted Radius licenses
    RADIUS: License String:                          Additional Info:
    RADIUS: XXXXXXXXXXXXXXXXXXXX                 SSR Cluster & Management Expansion
    RADIUS: XXXXXXXXXXXXXXXXXXXX                 SSR Management Expansion
    RADIUS: XXXXXXXXXXXXXXXXXXXX                 Run license - 50k sessions
    RADIUS:
    RADIUS: Total concurrent sessions licensed: 50000
    RADIUS:
    RADIUS: Unlimited Transactions Per Second is Allowed
    RADIUS:
    RADIUS: Licenses enable this server to:
    RADIUS:         Run
    RADIUS:         use Multi Node Cluster
    RADIUS:         connect '3' management and '2' cluster nodes to database
    RADIUS:
    RADIUS: Licensed for Steel-Belted Radius Carrier
    
    
    root@sbr1 [/opt/JNPRsbr/radius]
    $RADIUS: Attribute Editing enabled
    RADIUS: DCF system started
    
  15. Check the status of the SM node and verify it has properly reconnected to the cluster.

    Execute:
    root@sbr1: /opt/JNPRsbr/radius/sbrd status

    ---------------------------------------------------------------------------
    SBR 8.30-R1.50765 cluster 6node_cluster{1s,1sm,2m,2d}
    on SunOS 5.10 Generic_141444-09 node sbr1.englab.juniper.net(sm)
    ---------------------------------------------------------------------------
    
    Connected to Management Server at: 10.212.10.213:5235
    
    [ndbd(NDB)]     2 node(s)
    id=1    @10.212.10.188  (mysql-5.5.20 ndb-7.2.5, Nodegroup: 0, *)
    id=2    @10.212.10.67  (mysql-5.5.20 ndb-7.2.5, Nodegroup: 0)
    
    [ndb_mgmd(MGM)] 3 node(s)
    id=51   @10.212.10.213  (mysql-5.6.28 ndb-7.4.10)
    id=52   @10.212.10.68  (mysql-5.6.28 ndb-7.4.10)
    id=53   @10.212.10.66  (mysql-5.6.28 ndb-7.4.10)
    
    [mysqld(API)]   5 node(s)
    id=61   @10.212.10.213  (mysql-5.6.28 ndb-7.4.10)
    id=62   @10.212.10.68  (mysql-5.6.28 ndb-7.4.10)
    id=63   @10.212.10.66  (mysql-5.6.28 ndb-7.4.10)
    id=100  @10.212.10.213  (mysql-5.6.28 ndb-7.4.10)
    id=101  @10.212.10.65  (mysql-5.5.20 ndb-7.2.5)
    
    ---------------------------------------------------------------------------
    Current state of network interfaces:
    
    10.212.10.213.1646                        Idle
    10.212.10.213.1813                        Idle
    10.212.10.213.1645                        Idle
    10.212.10.213.1812                        Idle
          *.1812               *.*                0      0 49152      0 LISTEN
          *.1813               *.*                0      0 49152      0 LISTEN
    ---------------------------------------------------------------------------
    
        hadm  4761 ndb_mgmd --config-cache=0 --configdir=/opt/JNPRhadm
        hadm  4779 /bin/sh /opt/JNPRmysql/install/bin/mysqld_safe
        hadm  4968 /opt/JNPRmysql/install/bin/mysqld --basedir=/opt/JNPRmysql/install --datadir=/o
        root  5405 radius sbr.xml
        root  5475 webserver
    
  16. (Optional) Make any modifications to the config.ini file in the /opt/JNPRhadm directory. For example, you may need to make adjustments to items like DataMemory and IndexMemory based on previous values recommended for your existing cluster.

    Once you make any adjustments to the config.ini file, you must restart each node hosting a management server (SM nodes).

    Execute:
    root@sbr1:/opt/JNPRsbr/radius/sbrd restart

    Note: All SM nodes must have the same values in the config.ini file.

  17. Verify that SBRC is performing correctly by checking logs and counters.
  18. Repeat this process on the other SM node; see Upgrading the SM Nodes in the Cluster.

Modified: 2017-03-07