Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX README: Release B.06.00

are updated and present on each node in the cluster or accessible
through
shared storage. It is the user’s responsibility to replicate all
files
across all nodes, when using local configuration.
I. Error-Handling
During start up, the ASE server would require the IP/hostname that
is
mentioned in the interfaces file to be associated with a node name
that
it is configured to run on. If the IP is not configured, or ping-
able,
the ASE instance may fail to come up. Please correct this using
the
guidelines specified in the next section.
Please ensure that the setup has been done for all nodes in the
cluster
(or on shared storage) as specified by Sybase. Contact Sybase support
on
1-800-8SYBASE between 8 am and 5.30 pm PST for support issues.
J. Network Configuration
It is beyond the scope of this document to give detailed instructions
on
how to configure the Sybase ASE for a Serviceguard cluster. This
section
contains a few basic steps that user would require to do for setting
up a
single instance of ASE for failover in a Serviceguard cluster.
Please
consult Sybase ASE documentation for a detailed description on how
to
setup ASE in a cluster.
- Sybase ASE interfaces file
For setting up a single instance of ASE in a Serviceguard cluster,
the
ASE instance should be available at the same IP address across
all
nodes in the cluster. To achieve this, the interfaces file of the
ASE
instance, located at the $SYBASE directory of that instance, should
be
edited. For example, a default setup of ASE would have an
interface
entry for the dataserver as:
MIG29
master tcp ether mig29 5000
query tcp ether mig29 5000