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
Removing preexisting keys
If you encountered a split-brain condition, use the vxfenclearpre utility to remove CP Servers, SCSI-3 registrations, and reservations on the coordinator disks, Coordination Point servers, as well as on the data disks in all shared disk groups.
You can also use this procedure to remove the registration and reservation keys of another node or other nodes on shared disks or CP server.
To clear keys after split-brain
- Stop VCS on all nodes.
# hastop -all
- Make sure that the port h is closed on all the nodes. Run the following command on each node to verify that the port h is closed:
# gabconfig -a
Port h must not appear in the output.
- Stop I/O fencing on all nodes. Enter the following command on each node:
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl stop vxfen
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/vxfen stop
- If you have any applications that run outside of VCS control that have access to the shared storage, then shut down all other nodes in the cluster that have access to the shared storage. This prevents data corruption.
- Start the vxfenclearpre script:
# /opt/VRTSvcs/vxfen/bin/vxfenclearpre
- Read the script's introduction and warning. Then, you can choose to let the script run.
Do you still want to continue: [y/n] (default : n) y
In some cases, informational messages resembling the following may appear on the console of one of the nodes in the cluster when a node is ejected from a disk/LUN. You can ignore these informational messages.
<date> <system name> scsi: WARNING: /sbus@3,0/lpfs@0,0/ sd@0,1(sd91): <date> <system name> Error for Command: <undecoded cmd 0x5f> Error Level: Informational <date> <system name> scsi: Requested Block: 0 Error Block 0 <date> <system name> scsi: Vendor: <vendor> Serial Number: 0400759B006E <date> <system name> scsi: Sense Key: Unit Attention <date> <system name> scsi: ASC: 0x2a (<vendor unique code 0x2a>), ASCQ: 0x4, FRU: 0x0
The script cleans up the disks and displays the following status messages.
Cleaning up the coordinator disks... Cleared keys from n out of n disks, where n is the total number of disks. Successfully removed SCSI-3 persistent registrations from the coordinator disks. Cleaning up the Coordination Point Servers... ................... [10.209.80.194]:50001: Cleared all registrations [10.209.75.118]:443: Cleared all registrations Successfully removed registrations from the Coordination Point Servers. Cleaning up the data disks for all shared disk groups ... Successfully removed SCSI-3 persistent registration and reservations from the shared data disks. See the log file /var/VRTSvcs/log/vxfen/vxfen.log You can retry starting fencing module. In order to restart the whole product, you might want to reboot the system.
- Start the fencing module on all the nodes.
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl start vxfen
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/vxfen start
- Start VCS on all nodes.
# hastart