Storage Foundation for Sybase ASE CE 7.4.1 Configuration and Upgrade Guide - Linux
- Section I. Configuring SF Sybase ASE CE
- Preparing to configure SF Sybase CE
- Configuring SF Sybase CE
- Configuring the SF Sybase CE components using the script-based installer
- Configuring the SF Sybase CE cluster
- Configuring SF Sybase CE in secure mode
- Configuring a secure cluster node by node
- Configuring the SF Sybase CE cluster
- Configuring SF Sybase CE clusters for data integrity
- Setting up disk-based I/O fencing using installer
- Performing an automated SF Sybase CE configuration
- Performing an automated I/O fencing configuration using response files
- Configuring a cluster under VCS control using a response file
- Section II. Post-installation and configuration tasks
- Section III. Upgrade of SF Sybase CE
- Planning to upgrade SF Sybase CE
- Performing a full upgrade of SF Sybase CE using the product installer
- Performing an automated full upgrade of SF Sybase CE using response files
- Performing a phased upgrade of SF Sybase CE
- Performing a phased upgrade of SF Sybase CE from version 6.2.1 and later release
- Performing a rolling upgrade of SF Sybase CE
- Performing post-upgrade tasks
- Section IV. Installation and upgrade of Sybase ASE CE
- Installing, configuring, and upgrading Sybase ASE CE
- Preparing to configure the Sybase instances under VCS control
- Installing, configuring, and upgrading Sybase ASE CE
- Section V. Adding and removing nodes
- Adding a node to SF Sybase CE clusters
- Adding the node to a cluster manually
- Setting up the node to run in secure mode
- Adding the new instance to the Sybase ASE CE cluster
- Removing a node from SF Sybase CE clusters
- Adding a node to SF Sybase CE clusters
- Section VI. Configuration of disaster recovery environments
- Section VII. Installation reference
- Appendix A. Installation scripts
- Appendix B. Sample installation and configuration values
- Appendix C. Tunable files for installation
- Appendix D. Configuration files
- Sample main.cf files for Sybase ASE CE configurations
- Appendix E. Configuring the secure shell or the remote shell for communications
- Appendix F. High availability agent information
Verifying GAB
Verify the GAB operation using the gabconfig -a command. This command returns the GAB port membership information. The output displays the nodes that have membership with the modules you installed and configured. You can use GAB port membership as a method of determining if a specific component of the SF Sybase CE stack communicates with its peers.
Table: GAB port description lists the different ports that the software configures for different functions.
Port | Function |
---|---|
a | GAB |
b | I/O fencing |
f | Cluster File System (CFS) |
h | Cluster Server (VCS: High Availability Daemon) |
m | Cluster Volume Manager (CVM) CVM uses port m for SmartIO VxVM cache coherency using Group Lock Manager (GLM). |
u | Cluster Volume Manager (CVM) (to ship commands from slave node to master node) Port u in the gabconfig output is visible with CVM protocol version >= 100. Run the vxdctl protocolversion command to check the protocol version. |
v | Cluster Volume Manager (CVM) |
w | vxconfigd (module for CVM) |
y | Cluster Volume Manager (CVM) I/O shipping |
For more information on GAB, refer to the Cluster Server Administrator's Guide.
To verify GAB
- To verify the GAB operation, type the following command on each node:
# /sbin/gabconfig -a
For example, the command returns the following output:
GAB Port Memberships =============================================================== Port a gen fd6a01 membership 01 Port b gen fd6a03 membership 01 Port f gen fd6a12 membership 01 Port h gen fd6a06 membership 01 Port m gen fd6a0b membership 01 Port u gen fd6a10 membership 01 Port v gen fd6a09 membership 01 Port w gen fd6a0d membership 01 Port y gen fd6a08 membership 01