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

Related Documentation

    Starting the SSR Processes

    Start the SSR process on each node in the cluster, one at a time. Start the SSR process on the nodes in the following order:

    • SM nodes
    • D nodes

    After you start the SSR process on the node, check the status of the node and wait for the process to finish starting before moving on to the next node.

    1. Log in to the first SM node.

      Execute:
      root@uranus-js: /opt/JNPRsbr/radius/sbrd start ssr

      Starting ssr management processes
      MySQL Cluster Management Server mysql-5.6.28 ndb-7.4.10
      -Node 51: connected (Version 7.1.8)
      
      Starting ssr auxiliary processes
      root@uranus-js: 
      
    2. After starting the SSR process on the node, monitor the status of the node and make sure that it reconnects to the cluster.

      Execute:
      root@uranus-js: /opt/JNPRsbr/radius ./sbrd status

      ---------------------------------------------------------------------------
      SBR 8.30.50006 cluster junCluster{0s,2sm,0m,2d}
      on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net(sm)
      ---------------------------------------------------------------------------
      
      Connected to Management Server at: 10.13.20.89:5235
      
      [ndbd(NDB)]     2 node(s)
      id=1 (not connected, accepting connect from 10.13.20.83)
      id=2 (not connected, accepting connect from 10.13.20.81)
      
      [ndb_mgmd(MGM)] 2 node(s)
      id=51   @10.13.20.89  (mysql-5.6.28 ndb-7.4.10)
      id=52 (not connected, accepting connect from 10.13.20.77)
      
      [mysqld(API)]   4 node(s)
      id=61 (not connected, accepting connect from 10.13.20.89)
      id=62 (not connected, accepting connect from 10.13.20.77)
      id=100 (not connected, accepting connect from 10.13.20.89)
      id=101 (not connected, accepting connect from 10.13.20.77)
      
      
          hadm  8216 /bin/sh /opt/JNPRmysql/install/bin/mysqld_safe
          hadm  8195 ndb_mgmd --config-cache=0
          hadm  8281 /opt/JNPRmysql/install/bin/mysqld --basedir=/opt/JNPRmysql/install --datadir=/o
      
      
      [07:47:02][root@uranus-js:/opt/JNPRsbr/radius]$
      
    3. On the second SM:

      Execute:
      root@sbrha-3: /opt/JNPRsbr/radius/sbrd start ssr

      root@sbrha-3: /opt/JNPRsbr/radius/sbrd status

    4. Start the SSR process on the first D node.
      20:57:47][root@sbrha-9:/opt/JNPRsbr/radius]$ ./sbrd start ssr
      Starting ssr data processes
      You have mail.
      2010-10-21 20:57:50 [ndbd] INFO     -- Angel connected to '10.13.20.89:5235'
      2010-10-21 20:57:50 [ndbd] INFO     -- Angel allocated nodeid: 1
      Initializing ssr
      [20:57:50][root@sbrha-9:/opt/JNPRsbr/radius
      
    5. After starting the SSR process on the node, monitor the status of the node and make sure that it reconnects to the cluster.

      Execute:
      root@sbrha-9: /opt/JNPRsbr/radius ./sbrd status

      ---------------------------------------------------------------------------
      SBR 8.30.50006 cluster junCluster{0s,2sm,0m,2d}
      on SunOS 5.10 Generic_141444-09 node sbrha-9.englab.juniper.net(d)
      ---------------------------------------------------------------------------
      
      
          root  6025 ndbmtd --initial --ndb-connectstring=nodeid=1;10.13.20.89:5235,10.13.20.77:5235
          root  6026 ndbmtd --initial --ndb-connectstring=nodeid=1;10.13.20.89:5235,10.13.20.77:5235
      
    6. On the second D node:

      Execute:
      root@sbrha-7: /opt/JNPRsbr/radius/sbrd start ssr

      root@sbrha-7: /opt/JNPRsbr/radius/sbrd status

    7. After the SSR process has been started on all four nodes, check the status of the cluster from one of the SM nodes.

      Execute:
      root@uranus-js: /opt/JNPRsbr/radius ./sbrd status

      The status of the cluster should look similar to the following example. Notice that all nodes are connected except for (in this example) node IDs 100 and 101. These will be connected after you re-create and restore the cluster database and start the RADIUS processes.

      [07:49:09][root@uranus-js:/opt/JNPRsbr/radius]$ ./sbrd status
      
      ---------------------------------------------------------------------------
      SBR 8.30.50006 cluster junCluster{0s,2sm,0m,2d}
      on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net(sm)
      ---------------------------------------------------------------------------
      
      Connected to Management Server at: 10.13.20.89:5235
      
      [ndbd(NDB)]     2 node(s)
      id=1    @10.13.20.83  (mysql-5.6.28 ndb-7.4.10, Nodegroup: 0, Master)
      id=2    @10.13.20.81  (mysql-5.6.28 ndb-7.4.10, Nodegroup: 0)
      
      [ndb_mgmd(MGM)] 2 node(s)
      id=51   @10.13.20.89  (mysql-5.6.28 ndb-7.4.10)
      id=52   @10.13.20.77  (mysql-5.6.28 ndb-7.4.10)
      
      [mysqld(API)]   4 node(s)
      id=61   @10.13.20.89  (mysql-5.6.28 ndb-7.4.10)
      id=62   @10.13.20.77  (mysql-5.6.28 ndb-7.4.10)
      id=100 (not connected, accepting connect from 10.13.20.89)
      id=101 (not connected, accepting connect from 10.13.20.77)
      
      
          hadm  8216 /bin/sh /opt/JNPRmysql/install/bin/mysqld_safe
          hadm  8195 ndb_mgmd --config-cache=0
          hadm  8281 /opt/JNPRmysql/install/bin/mysqld --basedir=/opt/JNPRmysql/install --datadir=/o
      
      
      [07:49:48][root@uranus-js:/opt/JNPRsbr/radius]$
      

    Modified: 2017-03-07