Configuring the Cluster

Learn how to configure the cluster here.

  1. Start sybcluster. For example: 
    sybcluster -U uafadmin -P -C mycluster 
    -F "blade1,blade2,blade3"

    See the Clusters Users Guide for complete syntax and usage information for sybcluster.

  2. 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 value, press Enter. Otherwise, enter the correct value, then press Enter.
  3. sybcluster prompts for the following. See Worksheet for Creating a Cluter for more information.

    • 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 agents 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 . Select agents from this list.

      Note: 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, the default setting for the runnable process search count parameter is '3'. Sybase recommends using this default setting in this environment. This can be set using the sp_configure stored procedure.

    • The number representing the cluster agent. sybcluster numbers the remaining agents in the cluster starting with this number.
    • Is the cluster to be configured using private installation mode? The default value is no [N]; the cluster is to be configured for a shared installation.
    • The full path for the quorum device. For example, /dev/raw/raw11.
    • Trace flags.
    • The page size of the master database, in kilobytes.
    • The full path for the master device. For example, /dev/raw/raw12.
    • The size of the master device.
    • The size of the master database.
    • The full path to the system procedure database device, sysprocsdev. 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, systemdbdev. For example, /dev/raw/raw14.
    • The size of the system database device.
    • The size of the system database.
    • Enable the Pluggable Component Interface (PCI) to support Java in the database? [N]
      If you enter “Y”, enter:
      • The path to the PCI database device path. For example, /dev/raw/raw20.
      • The PCI database device size (24MB)
      • The PCI database size (24MB)
    • Does this cluster have a secondary network? (Y).
      • If you enter “Y” to a secondary network, sybcluster uses the default port number of 15100 as the starting port number for the range of port numbers required so that the instances can exchange messages, and reserves that number of ports, starting with the default value.
        Note: 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.
      • If you enter “N” to a secondary network, sybcluster asks for the beginning port number, and calculates the number of additional ports required and reserves that number of ports. The default value is 15100.
    • If the cluster uses a private installation, go to step 4. If the cluster uses a shared installation, sybcluster prompts for:
      • 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.
      • Note: Ensure that the interfaces file does not already contain the cluster or instance information. sybcluster adds this information 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.
  4. sybcluster displays the node name and prompts for values for each instance, one node at a time.

    • Instance name.
    • If the cluster supports a shared configuration, sybcluster prompts for:
      • 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. For example, 10.0.1.1.
      • The secondary protocol address for the instance (if you answered Y to a secondary network). For example, 10.0.1.2.
    • If the cluster supports a private configuration, sybcluster prompts for:
      • The $SYBASE home directory
      • The environmental shell script path
      • The Adaptive Server home directory
      • The full path to the server configuration file
        Note: The path for the server configuration file can be the same or different for each instance.
      If you are using interfaces files for server lookup, sybcluster prompts for:
      • The interface file query port number
      • The primary protocol address
      • The secondary protocol address
    • Local system temporary database device. The name of the Adaptive Server database device for the local system temporary (LST) database. You must create local system temporary database on a shared disk.
    • The LST device path. For example, /dev/raw/raw15.
    • The LST device size.
      Note: 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.
  5. sybcluster asks if you want to add another instance. If you enter Y, sybcluster repeats step 4 for the next instance.
  6. 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
  7. 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.
  8. While creating the cluster, sybcluster:
    1. Checks to see if VCS is supported on your system. If yes, sybcluster asks:

      • Whether to integrate the cluster database with VCS [Y]. If yes, sybcluster prompts for:
        • The path to the interfaces file for each instance, unless LDAP is supported.
        • Whether to check if the master database, system procedure device, and system database devices are managed by the VCS Volume Manager or Veritas Cluster File System [Y]. If yes, sybcluster reports status for each device and asks if you want to continue.
    2. If you answer no, sybcluster prompts for the path to the interfaces file for each instance, unless LDAP is supported.
    3. Asks if you want to check if each cluster device supports IO fencing. If you answer yes, sybcluster checks all devices and reports the IO fencing capability of each one.
Parent topic: Creating a Cluster Using sybcluster