Configuring the Cluster Using sybcluster

Configure the cluster using the information you gathered for your worksheet.

1. Start sybcluster using uafadmin, the Unified Agent administrative login:

    sybcluster -U uafadmin -P -C clustername -F "hostname:9999"

2. Run 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. Complete the fields in sybcluster using the information from Worksheet for Creating a Cluster.

   Fields	Description
   Cluster name	The name of the cluster to create if you did not set the default cluster on the command line.
   Instances	The maximum number of instances to create for the cluster.
   SCC agents	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 a Sybase Control Center remote command and control agent. Select agents from this list. The number representing the cluster agent – sybcluster assigns numbers to the remaining agents in the cluster based on this number.
   Configuration type	Is the cluster using private installation mode? The default value is no [N]; the cluster is to be configured for a shared installation.
   Quorom device	The full path for the quorum device (such as /dev/raw/raw11).
   Trace flags	Any required trace flags.
   Page size	The page size of the master database, in kilobytes.
   Master device	The full path for the master device. For example, /dev/raw/raw12. The size of the master device. The size of the master database.
   Sybase system procedure device	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.
   System database device	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.
   PCI device	(Optional) Enable the pluggable component interface (PCI) to support Java in the database? 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)
   Secondary network	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 interconnect. 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.

4. Skip this step if the cluster uses a private installation. For shared installations, provide:
   • The $SYBASE home directory (such as /remote/var/sybase).
   • The full path to the “.sh” environment shell script (such as /remote/var/sybase/SYBASE.sh).
   • The Adaptive Server home directory (such as /remote/var/sybase/ASE-15_0).
   • The directory containing the interfaces file (such as /remote/var/sybase). sybcluster adds the correct cluster and instance information during configuration.
     Note: Ensure that the interfaces file does not already contain the cluster or instance information.
   • The full path to the dataserver configuration file (such as /remote/var/sybase/mycluster.cfg). sybcluster must be able to find this file during configuration.
5. sybcluster displays the node name and prompts for values for each instance, one node at a time. If you are using:
   
   • A shared configuration, provide:
     • 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. 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.
   • A private configuration, provide:
     • Instance name
     • 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.
   • Interfaces files for server lookup, provide:
     • Instance name.
     • The interface file query port number
     • The primary protocol address
     • The secondary protocol address
   • A local system temporary database device, provide:
     • The name of the Adaptive Server database device for the local system temporary (LST) database.
       Note: 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.
   Note: sybcluster asks if you want to add another instance. If you enter Y, sybcluster repeats this step for the next instance.
6. sybcluster asks if you want to save the cluster configuration.
   
   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, the configuration process begins, and sybcluster:
   1. Checks to see if VCS is supported on your system. If so, 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. sybcluster asks if you want to check if each cluster device supports I/O fencing. If you answer yes, sybcluster checks all devices and reports the I/O fencing capability of each one.