Before configuring the cluster, create a cluster input file that specifies the name of the cluster, the number of instances in the cluster, the path to the directories containing the interfaces file, log files, and quorum disk devices, and other required configuration information. You can choose any name for the cluster configuration file (for example, mycluster.inp).
When you configure the cluster, Adaptive Server reads the information from the cluster input file and stores it securely in the quorum device. Adaptive Server subsequently retrieves the cluster configuration information from the quorum device.
See “Reconfiguring the cluster” for information about changing configuration information after the cluster has been initialized.
You can configure one cluster with each cluster input
file.
The cluster input file is distinct from the server configuration file, which stores Adaptive Server configuration values associated with sp_configure.
This is the syntax for the cluster input file:
# all input files must begin with a comment[cluster] name = cluster name max instances = number master device = path to the master device primary protocol = udp | tcp | other secondary protocol = udp | tcp | other config file = Adaptive Server configuration file name interfaces path = interfaces file path traceflags = trace flag number, trace flag number, . . . additional run parameters = any additional run parameters [management nodes] hostname = node_name hostname = node_name hostname = node_name hostname = node_name [instance] id = instance ID name = instance name node = name of node on which this instance runs primary address = primary interconnect address primary port start = port number secondary address = secondary interconnect address secondary port start = port number errorlog = file name config file = Adaptive Server configuration file name interfaces path = interfaces file path traceflags = trace flag number, trace flag number, . . . additional run parameters = any additional run parameters [instance] id = instance ID name = instance name node = name of node on which this instance runs primary address = primary interconnect address primary port start = port number secondary address = secondary interconnect address secondary port start = port number errorlog = file name config file = Adaptive Server configuration file name interfaces path = interfaces file path traceflags = trace flag number, trace flag number, . . . additional run parameters = any additional run parameters
Where:
name – name of the cluster.
max instances – The maximum number of instances in the cluster that your version of Adaptive Server supports. See the Release Bulletin for the maximum number of instances your version of Adaptive Server supports.
master device – path to the master device.
primary protocol – protocol used for the primary interconnect.
secondary protocol – protocol used for the secondary interconnect.
config file – path to the Adaptive Server configuration file. This file is used by all instances in the cluster unless an individual instance overrides this setting.
interfaces path – path to the interfaces file. Omit this parameter if you are using an LDAP environments. This interfaces file is used by all instances unless an individual instance overrides this setting.
traceflags – comma-separated list of traceflags used at instance startup.
additional run parameters – additional parameters passed to instances during startup.
hostname – name of the node. This name should be the same as returned by the hostname command when run on this node. There is one hostname field for each node that must be registered. That node only needs to be specified once in the management node section.
name – name of the instance.
ID – ID of the instance.
node – name of the node on which this instance runs.
primary address – address of this instance on the primary interconnect.
primary port start – starting port number on the primary interconnect.
secondary address – address of this instance on the secondary interconnect. Required if a secondary is defined in the interconnect section or if a secondary protocol is specified. Ignored if a secondary is not defined.
secondary port start – starting port number on the secondary interconnect. Required if secondary address or a secondary protocol is specified.
error log – full path to the error log for this instance.
config file – path to an Adaptive Server configuration file. This file overrides the configuration file field specified in the cluster section of the cluster input file.
interfaces path – path to the server-side interfaces file. This file overrides the interfaces file field in the cluster section of the cluster input file. Do not include the interfaces file name in the path.
traceflags – comma-separated list of traceflags used at instance startup. These are used in addition to, not in place of, the trace flags specified in the cluster section of the cluster input file.
additional run parameters – additional
parameters passed to instances during startup.
The formula for finding the socket port range is:
start_port_number + (max_instances * 5) – 1
If you do not use an ADO.NET, ensure that the port numbers
you choose are not in use by any other process.
In this example, the cluster input file defines a cluster named “mycluster” with two instances, “ase1” on node “blade1” and “ase2” on node “blade2.” The addresses on the private interconnects are 192.169.0.1 and 192.169.0.2. The name of the server configuration file is mycluster.cfg. The maximum instances is 2. “ase1” has a starting port range of 15015, and “ase2” has a starting port range of 16015.This adds additional information to the mycluster cluster:
#input for a 2 node / 2 instance cluster [cluster] name = mycluster max instances = 2 master device = /opt/sybase/rawdevices/mycluster.master config file = /opt/sybase/ASE-15_0/mycluster.config interfaces path = /opt/sybase primary protocol = udp seconday protocol = udp [management nodes] hostname = blade1.sybase.com hostname = blade2.sybase.com [instance] id = 1 name = ase1 node = blade1.sybase.com primary address = 192.169.0.1 primary port start = 15015 secodary address = 192.169.1.1 secondary port start = 15015 errorlog = /opt/sybase/ASE-15_0/install/ase1.log additional run parameter = -M/opt/sybase/ASE-15_0 [instance] id = 2 name = ase2 node = blade2.sybase.com primary address = 192.169.0.2 primary port start = 16015 secondary address = 192.169.1.2 secondary port start = 16015 errorlog = /opt/sybase/ASE-15_0/install/ase2.log additional run parameter = -M/opt/sybase/ASE-15_0
For an example of cluster input file where all instances are located on a single node, see the Users Guide.
