HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

Table 8 Parameters in USER_ROLE
DescriptionUser Role
Can perform cluster and package view operations.MONITOR
Can perform package administration, and use cluster and package view commands.PACKAGE_ADMIN
Can to perform cluster administration, package administration, and cluster and package view
operations.
FULL_ADMIN
Assign any of these roles to users who are not configured as root users. Root users are usually
given complete control on the cluster using the FULL_ADMIN value.
When any of these values are specified for users who are not root users, they can view the Sybase
administrator password using the cmviewclcommand. Users who are not configured with any of
these values cannot view the Sybase administrator password using the cmviewcl command.
For more information on configuring security for a Serviceguard cluster, see the Securing
Serviceguard, March 2009 whitepaper available at http://www.hp.com/go/
hpux-serviceguard-docs —>HP Serviceguard .
Serviceguard allows the Role Based Access feature to be switched off, in which case only the root
user is able to view the package attributes.
As the Sybase administrator password is also entered in the package configuration ASCII file, you
secure this file either by using file permissions feature provided by the operating system or by
deleting the file after the package is applied.
Node-specific Configuration
Ensure that all files that are required by Sybase ASE to start up cleanly are updated and present
on each node in the cluster or accessible through shared storage. You must replicate all files across
all nodes, when using local configuration.
Error-Handling
To start up the ASE server the IP/hostname that is mentioned in the interfaces file must be associated
with a node name for which it is configured to run. If you are unable to ping the IP address or if
the IP is not configured, the ASE instance might fail to come up. The corrective guidelines for this
error are specified in the next section.
Ensure that the setup is done for all nodes in the cluster (or on shared storage) as specified by
Sybase. Contact Sybase support for any issues.
Network configuration
Detailed instructions on how to configure the Sybase ASE for a Serviceguard cluster is not provided
in this document. However, this section provides the basic steps that user would require to setup
a single-instance of ASE for failover in a Serviceguard cluster. For more information on how to
setup ASE in a cluster, see the Consult Sybase ASE documentation.
Sybase ASE interfaces file
For setting up a single-instance of ASE in a Serviceguard cluster, the ASE instance must be available
at the same IP address across all nodes in the cluster. To achieve this, you must edit the interfaces
file of the ASE instance, available on the $SYBASE directory of that instance. For example, a
default setup of ASE has an interface entry for the dataserver as:
MIG29
master tcp ether mig29 5000
query tcp ether mig29 5000
For a re-locatable IP-address, you must edit this interface entry, as follows:
Node-specific Configuration 71