Storage Foundation for Sybase ASE CE 7.4 Administrator's Guide - Linux
- Overview of Storage Foundation for Sybase ASE CE
- About Storage Foundation for Sybase ASE CE
- About SF Sybase CE components
- About optional features in SF Sybase CE
- Administering SF Sybase CE and its components
- Administering SF Sybase CE
- Starting or stopping SF Sybase CE on each node
- Administering VCS
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Administering CVM
- Changing the CVM master manually
- Administering CFS
- Administering the Sybase agent
- Administering SF Sybase CE
- Troubleshooting SF Sybase CE
- About troubleshooting SF Sybase CE
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting Cluster Volume Manager in SF Sybase CE clusters
- Troubleshooting interconnects
- Troubleshooting Sybase ASE CE
- Prevention and recovery strategies
- Prevention and recovery strategies
- Managing SCSI-3 PR keys in SF Sybase CE cluster
- Prevention and recovery strategies
- Tunable parameters
- Appendix A. Error messages
Enabling or disabling the preferred fencing policy
You can enable or disable the preferred fencing feature for your I/O fencing configuration.
You can enable preferred fencing to use system-based race policy, group-based race policy, or site-based policy. If you disable preferred fencing, the I/O fencing configuration uses the default count-based race policy.
Preferred fencing is not applicable to majority-based I/O fencing.
To enable preferred fencing for the I/O fencing configuration
- Make sure that the cluster is running with I/O fencing set up.
# vxfenadm -d
- Make sure that the cluster-level attribute UseFence has the value set to SCSI3.
# haclus -value UseFence
To enable system-based race policy, perform the following steps:
Make the VCS configuration writable.
# haconf -makerw
Set the value of the cluster-level attribute PreferredFencingPolicy as System.
# haclus -modify PreferredFencingPolicy System
Set the value of the system-level attribute FencingWeight for each node in the cluster.
For example, in a two-node cluster, where you want to assign system1 five times more weight compared to system2, run the following commands:
# hasys -modify system1 FencingWeight 50 # hasys -modify system2 FencingWeight 10
Save the VCS configuration.
# haconf -dump -makero
Verify fencing node weights using:
# vxfenconfig -a
To enable group-based race policy, perform the following steps:
Make the VCS configuration writable.
# haconf -makerw
Set the value of the cluster-level attribute PreferredFencingPolicy as Group.
# haclus -modify PreferredFencingPolicy Group
Set the value of the group-level attribute Priority for each service group.
For example, run the following command:
# hagrp -modify service_group Priority 1
Make sure that you assign a parent service group an equal or lower priority than its child service group. In case the parent and the child service groups are hosted in different subclusters, then the subcluster that hosts the child service group gets higher preference.
Save the VCS configuration.
# haconf -dump -makero
To enable site-based race policy, perform the following steps:
Make the VCS configuration writable.
# haconf -makerw
Set the value of the cluster-level attribute PreferredFencingPolicy as Site.
# haclus -modify PreferredFencingPolicy Site
Set the value of the site-level attribute Preference for each site.
For example, # hasite -modify Pune Preference 2
Save the VCS configuration.
# haconf -dump - makero
- To view the fencing node weights that are currently set in the fencing driver, run the following command:
# vxfenconfig -a
To disable preferred fencing for the I/O fencing configuration
- Make sure that the cluster is running with I/O fencing set up.
# vxfenadm -d
- Make sure that the cluster-level attribute UseFence has the value set to SCSI3.
# haclus -value UseFence
- To disable preferred fencing and use the default race policy, set the value of the cluster-level attribute PreferredFencingPolicy as Disabled.
# haconf -makerw # haclus -modify PreferredFencingPolicy Disabled # haconf -dump -makero