Creating a Test Database
If all the nodes come up correctly and see each other, you can create a test database with the DemoSetup.sh script.
To create a test database, on each management node:
Log in as root. (You use both root and hadm accounts; using two windows makes this easier.)
Stop the SBR Carrier node.
Change directories to /opt/JNPRsbr/radius/.
sbrd stop radius
Log in (using the second window) as hadm.
Create a database with the DemoSetup.sh script, using the default values.
Respond to the script prompts with yes.
SBRs must be offline, do you want to proceed? <yes|no> yes
This will destroy the “ SteelBeltedRadius” database (if it exists), OK? <yes|no> yes
In the hadm window, check the status of all nodes as they come online.
Results similar to this example are displayed:
[ndbd(NDB)] 2 node(s) id=10 @172.28.84.163 (mysql-5.7.18 ndb-7.5.6, Nodegroup: 0, Master) id=11 @172.28.84.113 (mysql-5.7.18 ndb-7.5.6, Nodegroup: 0)
[ndb_mgmd(MGM)] 2 node(s) id=1 @172.28.84.36 (mysql-5.7.18 ndb-7.5.6) id=2 @172.28.84.166 (mysql-5.7.18 ndb-7.5.6)
[mysqld(API)] 4 node(s) id=21 @172.28.84.36 (mysql-5.7.18 ndb-7.5.6) id=22 @172.28.84.166 (mysql-5.7.18 ndb-7.5.6) id=30 @172.28.84.36 (mysql-5.7.18 ndb-7.5.6) id=31 @172.28.84.166 (mysql-5.7.18 ndb-7.5.6)
Examine the line starting with “id=”, and verify that there are no references to starting, connecting, or not connected. Any of these references indicate the process has either not finished starting, or the node is not connected properly. You may need to execute the sbrd status command more than once because it only shows a snapshot of activity; the display does not refresh. Do not proceed to the next node until you are sure the process has started properly and the node is connected.