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
Changing the CVM master manually
You can change the Cluster Volume Manager (CVM) master manually from one node in the cluster to another node, while the cluster is online. CVM migrates the master node, and reconfigures the cluster.
Veritas recommends that you switch the master when the cluster is not handling Veritas Volume Manager (VxVM) configuration changes or cluster reconfiguration operations. In most cases, CVM aborts the operation to change the master, if CVM detects that any configuration changes are occurring in the VxVM or the cluster. After the master change operation starts reconfiguring the cluster, other commands that require configuration changes will fail until the master switch completes.
See Errors during CVM master switching.
To change the master online, the cluster must be cluster protocol version 100 or greater.
To change the CVM master manually
- To view the current master, use one of the following commands:
# vxclustadm nidmap Name CVM Nid CM Nid State system1 0 0 Joined: Slave system2 1 1 Joined: Master
# vxdctl -c mode mode: enabled: cluster active - MASTER master: system2
In this example, the CVM master is system2.
- From any node on the cluster, run the following command to change the CVM master:
# vxclustadm setmaster nodename
where nodename specifies the name of the new CVM master.
The following example shows changing the master on a cluster from system2 to system1:
# vxclustadm setmaster system1
- To monitor the master switching, use the following command:
# vxclustadm -v nodestate state: cluster member nodeId=0 masterId=0 neighborId=1 members[0]=0xf joiners[0]=0x0 leavers[0]=0x0 members[1]=0x0 joiners[1]=0x0 leavers[1]=0x0 reconfig_seqnum=0x9f9767 vxfen=off state: master switching in progress reconfig: vxconfigd in joinIn this example, the state indicates that switching of the master is in progress.
- To verify whether the master has successfully changed, use one of the following commands:
# vxclustadm nidmap Name CVM Nid CM Nid State system1 0 0 Joined: Master system2 1 1 Joined: Slave
# vxdctl -c mode mode: enabled: cluster active - MASTER master: system1