Cluster Server 7.4.1 Administrator's Guide - Linux
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- Predicting VCS behavior using VCS Simulator
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- 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
- About administering the coordination point server
- About configuring a CP server to support IPv6 or dual stack
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Veritas High Availability Configuration wizard
- Introducing the Veritas High Availability Configuration wizard
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Section VI. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VII. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting issues with systemd unit service files
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- Troubleshooting wizard-based configuration issues
- Troubleshooting issues with the Veritas High Availability view
- VCS message logging
- VCS performance considerations
- Section VIII. Appendixes
Migrating an InfoScale Availability cluster to IPv6 in a GCO deployment
The following graphic shows a sample migration scenario where two InfoScale Availability clusters are a part of an existing global cluster. The clusters are configured using IPv4, and the GCO IP is configured for each cluster.
Migrating clusters to IPv6 in a GCO deployment involves the following steps:
Updating the secondary cluster to IPv6.
Updating the primary cluster with the details of the IP changes in the secondary cluster.
To update the remote cluster with the details of the IP changes on the local cluster
Updating the primary cluster to IPv6.
Updating the secondary cluster with the details of the IP changes in the primary cluster.
To update the remote cluster with the details of the IP changes on the local cluster
Note:
Veritas recommends that you update the secondary cluster to IPv6 first. Doing so ensures that the primary cluster is operational while the update of the secondary cluster is in progress. It also allows for an easy rollback in case of issues with the update.
To migrate a local VCS cluster to IPv6
- Set the cluster to read-write mode.
# haconf -makerw
- Replace the virtual IP address of the IP resource in the cluster with an IPv6 address.
# hares -modify IPResourceName Address IPv6Address
For example:
# hares -modify gcoip Address 2620:128:f0a2:9005::117
- Add the PrefixLen attribute to the IP resource and assign appropriate value to it.
# hares -modify IPResourceName PrefixLen prefixLength
For example:
# hares -modify gcoip PrefixLen 64
- Remove the NetMask attribute of the IP resource from the configuration.
# hares -modify IPResourceName NetMask ""
For example:
# hares -modify gcoip NetMask ""
- Set the value of the ClusterAddress attribute to IPv6 address.
# haclus -modify ClusterAddress IPv6Address
For example:
haclus -modify ClusterAddress 2620:128:f0a2:9005::117
- Ensure that all cluster nodes are now configured using IPv6 addresses.
- Save the modified cluster configuration and make it read only.
# haconf -dump -makero
- Restart the WAC resource.
- Check WAC communication and ICMP status.
# hastatus -sum
To update the remote cluster with the details of the IP changes on the local cluster
- Make cluster configuration writable.
# haconf -makerw
- Modify the remote cluster address with an IPv6 address.
# haclus -modify ClusterAddress IPv6Address -clus remoteClusterName
For example:
# haclus -modify ClusterAddress 2620:128:f0a2:9005::117 -clus gcocluster2
- Modify the IP address of the ICMP agent with the IPv6 address of the remote cluster.
# hahb -modify Icmp Arguments IPv6Address -clus remoteClusterName
For example:
# hahb -modify Icmp Arguments 2620:128:f0a2:9005::117 -clus gcocluster2
- Update the cluster configuration with the modified data.
# haconf -dump -makero
- Restart the WAC resource on the secondary sites.
- Check WAC communication and ICMP status.
# hastatus -sum