This section describes how to use sybcluster to configure and start the cluster. Make sure you first follow the instructions in:
You can view a complete sybcluster session that includes answers to all the prompts in the Appendix C, “A sybcluster Sample Session.”
Use sybcluster to create and configure
a shared-disk cluster. To create logical clusters, use the Adaptive
Server plug-in or system stored procedures described in the “Managing
the Workload” chapter of the Users Guide to Clusters.
Start sybcluster. For example:
sybcluster -U uafadmin -P -C mycluster -F "blade1,blade2,blade3"
See “The sybcluster Utility” chapter in the Users Guide to Clusters for complete syntax and usage information.
Enter:
create cluster
sybcluster prompts you for all necessary information, one parameter at a time. If there is a default value, sybcluster displays it in the command prompt. To accept the default, press Enter. Otherwise, enter the correct value, then press Enter.
sybcluster prompts for the following. See “Worksheet for creating a cluster”.
The name of the cluster to create if you did not set the default cluster on the command line.
The maximum number of instances to create for the cluster.
The number of nodes in the cluster.
sybcluster displays a list of available host machines. In this list are all nodes specified by the -F and -d parameters on the sybcluster command line with a configured and running Unified Agent as set up in “Setting the environment and starting the Unified Agents”. Select nodes from this list.
You can create a simulated cluster by hosting all instances
on a single node. For best performance, make sure that the total
number of engines across all instances running on the single node
does not exceed the number of CPUs, or cores, on the host machine.
Additionally, Sybase strongly recommends tuning the runnable process search count parameter to '3' in such an environment. This can be set using the sp_configure stored procedure.
The number representing the cluster node. sybcluster numbers the remaining nodes in the cluster starting with this number.
The full path for the quorum device. For example, /dev/raw/raw11.
Trace flags.
The full path for the master database device, including the device name. For example, /dev/raw/raw12.
The size of the master database device.
The size of the master database.
The page size of the master database, in kilobytes.
The full path to the system procedure database device, sybsystemprocs. For example, /dev/raw/raw13.
The size of the system procedure database device.
The size of the system procedure database.
The full path to the Sybase system database device, sybsystemdb. For example, /dev/raw/raw14.
The size of the system database device.
The size of the system database.
Does the cluster have a private network? (Y or N)
If you enter Y to a private network, sybcluster asks:
Do you have a secondary network?
If you answer yes (Y), sybcluster asks
(in step 4, when configuring the instances) for the protocol address
or address of the private network interface on the host system for
each instance in the cluster.
If you enter “N” to a private network, sybcluster asks for:
The port number to which this range applies.
Enter a starting port number. sybcluster calculates the number of additional port numbers required so that the instances can exchange messages, and reserves that number of ports, starting with the port number you provide.
Adaptive Server uses several sockets for each interconnection.
The number of ports required for each instance is 5 multiplied by
the maximum number of instances.
Make sure the starting port number and the additional port numbers sybcluster requires are not used by another application.
The $SYBASE home directory. For example, /remote/var/sybase.
The full path to the “.sh” environment shell script. For example, /remote/var/sybase/SYBASE.sh.
The Adaptive Server home directory. For example, /remote/var/sybase/ASE-15_0.
Ensure that the interfaces file does not contain
the cluster or instance information. It will be added by sybcluster during
the Create Cluster process
The directory containing the interfaces file. For example, /remote/var/sybase. sybcluster adds the correct cluster and instance information during configuration.
The full path to the dataserver configuration file. For example, /remote/var/sybase/mycluster.cfg. sybcluster must be able to find this file during configuration.
sybcluster prompts for values for each instance, one node at a time:
Node name, if you are configuring more than one node.
Instance name.
Query port number for the instance. Ensure that it is available and not in use by other applications.
The primary protocol address for the instance (if you answered Y to a private network). For example, 10.0.1.1.
The secondary protocol address for the instance (if you answered Y to a secondary private network). For example, 10.0.1.2.
Local system temporary database device- The name of the Adaptive Server database device for the local system temporary (LST) database.
The LST device path. For example, /dev/raw/raw15.
The LST device size.
If you place all LST databases on the same device, the
device size must be large enough for all LST databases.
The LST database name.
The LST database size.
sybcluster asks if you want to add another instance. If you enter Y, sybcluster repeats step 4 for the next instance.
sybcluster asks if you want to save the cluster configuration you have entered.
If you enter Y, sybcluster stores the configuration in an XML file that you can edit and replay using the sybcluster command:
create cluster cluster_name file file_name
sybcluster asks if you want to create the cluster.
If you enter Y, sybcluster configures the cluster using the information you have entered. This may take several minutes.
Configuring the cluster