Please enter search query.
Search <book_title>...
Storage Foundation for Sybase ASE CE 7.4 Administrator's Guide - Linux
Last Published:
2018-05-30
Product(s):
InfoScale & Storage Foundation (7.4)
Platform: 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
Refreshing lost keys on coordinator disks
If the coordinator disks lose the keys that are registered, the cluster might panic when a network partition occurs.
You can use the vxfenswap utility to replace the coordinator disks with the same disks. The vxfenswap utility registers the missing keys during the disk replacement.
To refresh lost keys on coordinator disks
- Make sure system-to-system communication is functioning properly.
- 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)
- Run the following command to view the coordinator disks that do not have keys:
# vxfenadm -s all -f /etc/vxfentab
Device Name: /dev/vx/rdmp/disk_a Total Number of Keys: 0 No keys... ...
- Copy the
/etc/vxfenmode
file to the/etc/vxfenmode.test
file.This ensures that the configuration details of both the files are the same.
- On any node, run the following command to start the vxfenswap utility:
# vxfenswap -g vxfencoorddg [-n]
- Verify that the keys are atomically placed on the coordinator disks.
# vxfenadm -s all -f /etc/vxfentab
Device Name: /dev/vx/rdmp/disk_a Total Number of Keys: 4 ...