Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

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

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

  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

  3. Stop the RADIUS process in the SM node.

    Execute:

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

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

    Execute:

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

  4. Navigate to the install directory.

    Execute:

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

  5. Unconfigure the node.

    Execute:

    root@sbr1:./unconfigure

  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

  8. Enter 1 to install the JNPRsbr.pkg. The system installs the new software.

  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

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

  2. Enter y to accept the license agreement.

  3. Enter 3 to select option 3. Configure Cluster Node.

  4. Specify the name of your existing cluster. In this example the cluster name is “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

  6. Enter a to accept the configuration files.

  7. Enter y to continue.

  8. Press Enter through the following prompts to keep your configuration.

  9. Enter e when prompted to enable the autoboot scripts.

  10. The main configuration menu is displayed.

    Enter q to quit.

  11. Start the SSR process on the SM node.

    Execute:

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

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

  13. Execute the UpdateSchema.pl utility for 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. This command returns a list of schemas which need to be updated.

      Execute:

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

      Note

      Future SBR Carrier 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 to which you are upgrading. For example, if you are upgrading to SBR Carrier Release 8.6.0:

      Execute:

      hadm@sbr1:~>perl ./UpdateSchema.pl 8.6 ColumnUpdate:Sbr_AcctSessionId

      Note

      The time required for altering the CST depends on the number of sessions stored in the CST. For example, SBR Carrier takes approximately 30 minutes to update a CST that contains 5 million sessions.

  14. Start the RADIUS process on the SM node.

    Execute:

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

  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

  16. (Optional) Make any modifications to the config.ini file in the /opt/JNPRhadm directory. For example, you may need to make adjustments to DataMemory based on the previous value 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.