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
- How SF Sybase CE works (high-level perspective)
- About SF Sybase CE components
- About optional features in SF Sybase CE
- How the agent makes Sybase highly available
- About Veritas InfoScale Operations Manager
- Administering SF Sybase CE and its components
- Administering SF Sybase CE
- Setting the environment variables for SF Sybase CE
- Starting or stopping SF Sybase CE on each node
- Applying operating system updates on SF Sybase CE nodes
- Adding storage to an SF Sybase CE cluster
- Recovering from storage failure
- Enhancing the performance of SF Sybase CE clusters
- Verifying the nodes in an SF Sybase CE cluster
- Administering VCS
- Viewing available Veritas device drivers
- Starting and stopping VCS
- Environment variables to start and stop VCS modules
- Adding and removing LLT links
- Configuring aggregated interfaces under LLT
- Displaying the cluster details and LLT version for LLT links
- Configuring destination-based load balancing for LLT
- Enabling and disabling intelligent resource monitoring for agents manually
- Administering the AMF kernel driver
- Administering I/O fencing
- About administering I/O fencing
- About the vxfentsthdw utility
- General guidelines for using the vxfentsthdw utility
- About the vxfentsthdw command options
- Testing the coordinator disk group using the -c option of vxfentsthdw
- Performing non-destructive testing on the disks using the -r option
- Testing the shared disks using the vxfentsthdw -m option
- Testing the shared disks listed in a file using the vxfentsthdw -f option
- Testing all the disks in a disk group using the vxfentsthdw -g option
- Testing a disk with existing keys
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- Enabling or disabling the preferred fencing policy
- About I/O fencing log files
- Administering CVM
- Establishing CVM cluster membership manually
- Changing the CVM master manually
- Importing a shared disk group manually
- Deporting a shared disk group manually
- Verifying if CVM is running in an SF Sybase CE cluster
- Verifying CVM membership state
- Verifying the state of CVM shared disk groups
- Verifying the activation mode
- Administering CFS
- Administering the Sybase agent
- Sybase agent functions
- Monitoring options for the Sybase agent
- Using the IPC Cleanup feature for the Sybase agent
- Configuring the service group Sybase using the command line
- Bringing the Sybase service group online
- Taking the Sybase service group offline
- Modifying the Sybase service group configuration
- Viewing the agent log for Sybase
- Administering SF Sybase CE
- Troubleshooting SF Sybase CE
- About troubleshooting SF Sybase CE
- Restarting the installer after a failed network connection
- Installer cannot create UUID for the cluster
- Troubleshooting I/O fencing
- The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
- Node is unable to join cluster while another node is being ejected
- System panics to prevent potential data corruption
- Cluster ID on the I/O fencing key of coordinator disk does not match the local cluster's ID
- Fencing startup reports preexisting split-brain
- Registered keys are lost on the coordinator disks
- Replacing defective disks when the cluster is offline
- Troubleshooting Cluster Volume Manager in SF Sybase CE clusters
- Restoring communication between host and disks after cable disconnection
- Shared disk group cannot be imported in SF Sybase CE cluster
- Error importing shared disk groups in SF Sybase CE cluster
- Unable to start CVM in SF Sybase CE cluster
- CVM group is not online after adding a node to the SF Sybase CE cluster
- CVMVolDg not online even though CVMCluster is online in SF Sybase CE cluster
- Shared disks not visible in SF Sybase CE cluster
- Troubleshooting interconnects
- Troubleshooting Sybase ASE CE
- Prevention and recovery strategies
- Prevention and recovery strategies
- Verification of GAB ports in SF Sybase CE cluster
- Examining GAB seed membership
- Manual GAB membership seeding
- Evaluating VCS I/O fencing ports
- Verifying normal functioning of VCS I/O fencing
- Managing SCSI-3 PR keys in SF Sybase CE cluster
- Identifying a faulty coordinator LUN
- Starting shared volumes manually
- Listing all the CVM shared disks
- I/O Fencing kernel logs
- Prevention and recovery strategies
- Tunable parameters
- Appendix A. Error messages
Replacing the coordinator disk group in a cluster that is online
You can also replace the coordinator disk group using the vxfenswap utility. The following example replaces the coordinator disk group vxfencoorddg with a new disk group vxfendg.
To replace the coordinator disk group
- Make sure system-to-system communication is functioning properly.
- Determine the value of the FaultTolerance attribute.
# hares -display coordpoint -attribute FaultTolerance -localclus
- Estimate the number of coordination points you plan to use as part of the fencing configuration.
- Set the value of the FaultTolerance attribute to 0.
Note:
It is necessary to set the value to 0 because later in the procedure you need to reset the value of this attribute to a value that is lower than the number of coordination points. This ensures that the Coordpoint Agent does not fault.
- Check the existing value of the LevelTwoMonitorFreq attribute.
# hares -display coordpoint -attribute LevelTwoMonitorFreq -localclus
Note:
Make a note of the attribute value before you proceed to the next step. After migration, when you re-enable the attribute you want to set it to the same value.
- Disable level two monitoring of CoordPoint agent.
# haconf -makerw
# hares -modify coordpoint LevelTwoMonitorFreq 0
# haconf -dump -makero
- Make sure that the cluster is online.
# vxfenadm -d
I/O Fencing Cluster Information: ================================ Fencing Protocol Version: 201 Fencing Mode: vxfen_mode Fencing SCSI3 Disk Policy: dmp Cluster Members: * 0 (system1) 1 (system2) RFSM State Information: node 0 in state 8 (running) node 1 in state 8 (running)
- Find the name of the current coordinator disk group (typically vxfencoorddg) that is in the
/etc/vxfendgfile.# cat /etc/vxfendg vxfencoorddg
- Find the alternative disk groups available to replace the current coordinator disk group.
# vxdisk -o alldgs list
DEVICE TYPE DISK GROUP STATUS sda auto:cdsdisk - (vxfendg) online sdb auto:cdsdisk - (vxfendg) online sdc auto:cdsdisk - (vxfendg) online sdx auto:cdsdisk - (vxfencoorddg) online sdy auto:cdsdisk - (vxfencoorddg) online sdz auto:cdsdisk - (vxfencoorddg) online
- Validate the new disk group for I/O fencing compliance. Run the following command:
# vxfentsthdw -c vxfendg
See Testing the coordinator disk group using the -c option of vxfentsthdw.
- If the new disk group is not already deported, run the following command to deport the disk group:
# vxdg deport vxfendg
- Perform one of the following:
Create the
/etc/vxfenmode.testfile with new fencing mode and disk policy information.Edit the existing the
/etc/vxfenmodewith new fencing mode and disk policy information and remove any preexisting/etc/vxfenmode.testfile.
Note that the format of the /etc/vxfenmode.test file and the /etc/vxfenmode file is the same.
See the Storage Foundation for Sybase ASE CE Configuration Guide for more information.
- From any node, start the vxfenswap utility. For example, if vxfendg is the new disk group that you want to use as the coordinator disk group:
# vxfenswap -g vxfendg [-n]
The utility performs the following tasks:
Backs up the existing
/etc/vxfentabfile.Creates a test file
/etc/vxfentab.testfor the disk group that is modified on each node.Reads the disk group you specified in the vxfenswap command and adds the disk group to the
/etc/vxfentab.testfile on each node.Verifies that the serial number of the new disks are identical on all the nodes. The script terminates if the check fails.
Verifies that the new disk group can support I/O fencing on each node.
- If the disk verification passes, the utility reports success and asks if you want to replace the coordinator disk group.
Confirm whether you want to clear the keys on the coordination points and proceed with the vxfenswap operation.
Do you want to clear the keys on the coordination points and proceed with the vxfenswap operation? [y/n] (default: n) y
- Review the message that the utility displays and confirm that you want to replace the coordinator disk group. Else skip to step 21.
Do you wish to commit this change? [y/n] (default: n) y
If the utility successfully commits, the utility moves the
/etc/vxfentab.testfile to the/etc/vxfentabfile.The utility also updates the
/etc/vxfendgfile with this new disk group. - Import the new disk group if it is not already imported before you set the coordinator flag "on".
# vxdg -t import vxfendg
- Set the coordinator attribute value as "on" for the new coordinator disk group.
# vxdg -g vxfendg set coordinator=on
Set the coordinator attribute value as "off" for the old disk group.
# vxdg -g vxfencoorddg set coordinator=off
- Deport the new disk group.
# vxdg deport vxfendg
- Verify that the coordinator disk group has changed.
# cat /etc/vxfendg vxfendg
The swap operation for the coordinator disk group is complete now.
- If you do not want to replace the coordinator disk group, answer n at the prompt.
The vxfenswap utility rolls back any changes to the coordinator disk group.
- Re-enable the LevelTwoMonitorFreq attribute of the CoordPoint agent. You may want to use the value that was set before disabling the attribute.
# haconf -makerw
# hares -modify coordpoint LevelTwoMonitorFreq Frequencyvalue
# haconf -dump -makero
where Frequencyvalue is the value of the attribute.
- Set the FaultTolerance attribute to a value that is lower than 50% of the total number of coordination points.
For example, if there are four (4) coordination points in your configuration, then the attribute value must be lower than two (2).If you set it to a higher value than two (2) the CoordPoint agent faults.