InfoScale™ 9.0 Cluster Server Agent for Sybase Installation and Configuration Guide - Solaris
- Introducing the Cluster Server for Sybase
- About the Sybase agent functions
- Monitoring options for the Sybase agent
- Installing and configuring Sybase
- Installing, upgrading, and removing the agent for Sybase
- Configuring VCS service groups for Sybase
- Before configuring the service group for Sybase
- About setting up detail monitoring for the agent for Sybase
- Administering VCS service groups for Sybase
- Appendix A. Resource type definitions for Sybase
- Appendix B. Sample configurations for Sybase
- Resource dependency graph for the Sybase agent
- Sample main.cf files for Sybase ASE CE configurations
Configuring the service group for Sybase using the command line
The VCS agent for Sybase contains a sample configuration file that can be used as reference to directly modify your present configuration file. This method requires you to restart VCS before the configuration takes effect.
To configure a service group for Sybase from the command line
- Log in to a cluster system as superuser.
- Make sure the Sybase type definition is imported into VCS engine.
Edit the main.cf file at
/etc/VRTSvcs/conf/config/main.cf
. For reference, use the sample files at/etc/VRTSagents/ha/conf/Sybase
.Create a Sybase service group.
Create the Sybase and SybaseBk resources.
Edit the default attributes to match the parameters in your configuration.
For added security, you must always provide a secure value for passwords.
Assign dependencies to the newly created resources. Refer to the sample file at
/etc/VRTSagents/ha/conf/Sybase/
.See the Cluster Server Administrator’s Guide for more information on assigning dependencies.
- Save and close the file.
- Verify the syntax of the file /etc/VRTSvcs/conf/config/main.cf
# cd /etc/VRTSvcs/conf/config # hacf -verify .
- Start VCS on the local node.
# hastart
- Start VCS on the other nodes.
- If the system is listed in AutoStartList attribute of the Sybase service group, verify that all Sybase service group resources are brought online.
# hagrp -state
- Take the service group offline and verify that all the resources are stopped.
# hagrp -offline service_group -sys system_name
# hagrp -state
- Bring the service group online again and verify that all the resources are available.
# hagrp -online service_group -sys system_name
# hagrp -state
- Switch the Sybase service group to the other node.
# hagrp -switch service_group -to system_name
- Verify that all Sybase service group resources are brought online on the other node.
# hagrp -state
- On all systems, look at the following log files for any errors or status.
/var/VRTSvcs/log/engine_A.log /var/VRTSvcs/log/Sybase_A.log /var/VRTSvcs/log/SybaseBk_A.log