Configuring the First SM Node and Creating a New Cluster Definition
To configure the new software on the first SM node and create a new cluster definition:
Configure the new software with the new cluster definition on each SM node.
Execute:
root@uranus-js: ./configureReview and accept the Steel-Belted Radius Carrier license agreement and create a new cluster definition by entering 2 Generate Cluster Definition.
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
--------------------------------------------------------------------------- SBR 8.60.50006 cluster on SunOS 5.10 Generic_141444-09 node uranus-js.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): 2Create a new cluster definition by entering 2 Generate Cluster Definition. This example creates a cluster named “junCluster” that contains two SM nodes named “uranus-js” and “sbrha-3”, and two data nodes named “sbrha-9” and “sbrha-7”.
Note If you use the original cluster name, the system attempts to use the original configuration files, which may contain pre-8.6.0 values. You must either back up and remove the old cluster definition, or use a new cluster name. However, you can use the same node names.
--------------------------------------------------------------------------- SBR 8.60.50006 cluster on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net is not configured and processes are down, needs to be configured --------------------------------------------------------------------------- Generating Cluster Definition...
When prompted, enter the new name for the cluster and the node names.
Enter SBR cluster name [uranus-js]: junCluster
The SBR Cluster Starter Kit license allows you to create a minimal cluster of 2 SBR nodes, 2 management nodes, and 2 data nodes. When each node is installed on a separate machine the cluster topology is denoted as {2s,2m,2d}. When SBR nodes are paired with management nodes on the same machines the cluster topology is denoted as {2sm,2d}. An optional SBR Cluster Management Expansion Kit allows you to add a third management node for {2sm,1m,2d} and an optional Data Expansion Kit allows you to add 2 more data nodes for {2sm,1m,4d} clusters. Additional SBR licenses allow you to add up to 18 more SBR nodes to obtain a maximal cluster {18s,2sm,1m,4d} and/or enable extra features. While it is not difficult to add management and/or SBR nodes to an existing cluster, adding data nodes is more difficult and may require you to shutdown the entire cluster as opposed to a rolling restart.When prompted, enter the license key.
Enter Starter Kit license: xxxx xxxx xxxx xxxx
Enter Management Expansion Kit license, if any: Enter Data Expansion Kit license, if any:
When prompted, enter the number of SBR (S) nodes.
Enter total number of SBR nodes to be configured [2]:2
When prompted, enter the number of management (M) nodes.
Enter number of management nodes to be paired with SBR nodes [2]:2
Creating cluster junCluster{0s,2sm,0m,2d} will require 4 machines total. Do you wish to continue? [y]:When prompted whether you wish to continue, enter y to continue.
All cluster nodes will share the same Session State Register (SSR). Do you wish to continue? [y]:y
When prompted whether you wish to continue, enter y to continue.
All cluster nodes will share the same Session State Register (SSR). Setting password for SSR admin account hadmsql Password: Again: Setting password for SSR software account hadmsbr Password: Again:
When prompted, enter the password for the account.
Information will now be gathered for each machine in the cluster. You will have a chance to review all information at least once before any machines are modified.
Enter the information to re-create each node in your cluster.
--------------------------------------------------------------------------- SBR 8.60.50006 cluster junCluster{0s,2sm,0m,2d} on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net Partial configuration at present is {0s,0sm,0m,0d} of {0s,2sm,0m,2d} --------------------------------------------------------------------------- IMPORTANT: node names must be entered as reported by 'uname -n'. Enter node name [junCluster-1]: uranus-js.englab.juniper.net Enter node type (sm,d) [sm]: Enter SBR node ID (100-149) [100]: Enter SBR node IP address by which it is known to management nodes. Enter SBR node IP address: 10.13.20.89 Enter SBR licenses meant only for this particular SBR node. Enter one license per line and an empty line when finished. Enter SBR full license: xxxx xxxx xxxx xxxx Enter SBR feature license: Enter MGMT node ID (51-59) [51]: Enter MGMT node IP address by which it is known to other nodes. Enter MGMT node IP address: 10.13.20.89 --------------------------------------------------------------------------- SBR 8.60.50006 cluster junCluster{0s,2sm,0m,2d} on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net Partial configuration at present is {0s,1sm,0m,0d} of {0s,2sm,0m,2d} --------------------------------------------------------------------------- IMPORTANT: node names must be entered as reported by 'uname -n'. Enter node name [junCluster-2]: sbrha-3.englab.juniper.net Enter node type (sm,d) [sm]: Enter SBR node ID (100-149) [101]: Enter SBR node IP address by which it is known to management nodes. Enter SBR node IP address: 10.13.20.77 Enter SBR licenses meant only for this particular SBR node. Enter one license per line and an empty line when finished. Enter SBR full license: xxxx xxxx xxxx xxxx Enter SBR feature license: Enter MGMT node ID (51-59) [52]: Enter MGMT node IP address by which it is known to other nodes. Enter MGMT node IP address: 10.13.20.77 --------------------------------------------------------------------------- SBR 8.60.50006 cluster junCluster{0s,2sm,0m,2d} on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net Partial configuration at present is {0s,2sm,0m,0d} of {0s,2sm,0m,2d} --------------------------------------------------------------------------- IMPORTANT: node names must be entered as reported by 'uname -n'. Enter node name [junCluster-3]: sbrha-9.englab.juniper.net Enter node type (d) [d]: Enter DATA node ID (1-40) [1]: Enter DATA node IP address by which it is known to management nodes. Enter DATA node IP address: 10.13.20.83 --------------------------------------------------------------------------- SBR 8.60.50006 cluster junCluster{0s,2sm,0m,2d} on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net Partial configuration at present is {0s,2sm,0m,1d} of {0s,2sm,0m,2d} --------------------------------------------------------------------------- IMPORTANT: node names must be entered as reported by 'uname -n'. Enter node name [junCluster-4]: sbrha-7.englab.juniper.net Enter node type (d) [d]: Enter DATA node ID (1-40) [2]: Enter DATA node IP address by which it is known to management nodes. Enter DATA node IP address: 10.13.20.81 --------------------------------------------------------------------------- SBR 8.60.50006 cluster junCluster{0s,2sm,0m,2d} on SunOS 5.10 Generic_141444-09 node uranus-js.englab.juniper.net Generated configuration is {0s,2sm,0m,2d} of {0s,2sm,0m,2d} --------------------------------------------------------------------------- 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.genAfter reviewing the information you entered for each node, accept the configuration files.
View (v), accept (a), or reject (r) configuration files: a WARNING: No such directory: /opt/JNPRshare/install/junCluster
(Optional) If prompted to create a shared directory for collecting and distributing the shared configuration of the cluster, enter y.
It is recommended that you create a shared directory owned by hadm for the purposes of collecting and distributing shared configuration among the various nodes of your clusters. Create this directory now, along with the OS user account hadm if required? [y]: y Writing shared configuration to /opt/JNPRshare/install/junCluster --------------------------------------------------------------------------- SBR 8.60.50006 cluster on SunOS 5.10 Generic_141444-09 node uranus-js.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 READY: last operation succeeded, generated cluster definition. Enter the number of the desired configuration task or quit (2,q):Proceed to Configuring the SBRC Software on the SM Nodes.