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
Displaying the I/O fencing registration keys
You can display the keys that are currently assigned to the disks using the vxfenadm command.
The variables such as disk_7, disk_8, and disk_9 in the following procedure represent the disk names in your setup.
To display the I/O fencing registration keys
- To display the key for the disks, run the following command:
# vxfenadm -s disk_name
For example:
To display the key for the coordinator disk
diskpath_afrom the system with node ID 1, enter the following command:# vxfenadm -s diskpath_a key[1]: [Numeric Format]: 86,70,68,69,69,68,48,48 [Character Format]: VFDEED00 * [Node Format]: Cluster ID: 57069 Node ID: 0 Node Name: system1
The -s option of vxfenadm displays all eight bytes of a key value in three formats. In the numeric format,
The first two bytes, represent the identifier VF, contains the ASCII value 86, 70.
The next four bytes contain the ASCII value of the cluster ID 57069 encoded in hex (0xDEED) which are 68, 69, 69, 68.
The remaining bytes contain the ASCII value of the node ID 0 (0x00) which are 48, 48. Node ID 1 would be 01 and node ID 10 would be 0A.
An asterisk before the Node Format indicates that the vxfenadm command is run from the node of a cluster where LLT is configured and is running.
To display the keys on a CVM parallel disk group:
# vxfenadm -s /dev/vx/rdmp/disk_7 Reading SCSI Registration Keys... Device Name: /dev/vx/rdmp/disk_7 Total Number Of Keys: 1 key[0]: [Numeric Format]: 66,80,71,82,48,48,48,49 [Character Format]: BPGR0001 [Node Format]: Cluster ID: unknown Node ID: 1 Node Name: system2
To display the keys on a Cluster Server (VCS) failover disk group:
# vxfenadm -s /dev/vx/rdmp/disk_8 Reading SCSI Registration Keys... Device Name: /dev/vx/rdmp/disk_8 Total Number Of Keys: 1 key[0]: [Numeric Format]: 65,86,67,83,0,0,0,0 [Character Format]: AVCS [Node Format]: Cluster ID: unknown Node ID: 0 Node Name: system1
- To display the keys that are registered in all the disks specified in a disk file:
# vxfenadm -s all -f disk_filename
For example:
To display all the keys on coordinator disks:
# vxfenadm -s all -f /etc/vxfentab Device Name: /dev/vx/rdmp/disk_9 Total Number Of Keys: 2 key[0]: [Numeric Format]: 86,70,70,68,57,52,48,49 [Character Format]: VFFD9401 * [Node Format]: Cluster ID: 64916 Node ID: 1 Node Name: system2 key[1]: [Numeric Format]: 86,70,70,68,57,52,48,48 [Character Format]: VFFD9400 * [Node Format]: Cluster ID: 64916 Node ID: 0 Node Name: system1
You can verify the cluster ID using the lltstat -C command, and the node ID using the lltstat -N command. For example:
# lltstat -C 57069
If the disk has keys that do not belong to a specific cluster, then the vxfenadm command cannot look up the node name for the node ID, and hence prints the node name as unknown. For example:
Device Name: /dev/vx/rdmp/disk_7 Total Number Of Keys: 1 key[0]: [Numeric Format]: 86,70,45,45,45,45,48,49 [Character Format]: VF----01 [Node Format]: Cluster ID: unknown Node ID: 1 Node Name: system2
For disks with arbitrary format of keys, the vxfenadm command prints all the fields as unknown. For example:
[Numeric Format]: 65,66,67,68,49,50,51,45 [Character Format]: ABCD123- [Node Format]: Cluster ID: unknown Node ID: unknown Node Name: unknown