InfoScale™ 9.0 Cluster Server Administrator's Guide - Windows
- 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
- Agent classifications
- About cluster control, communications, and membership
- About security services
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Getting started with VCS
- Administering the cluster from the command line
- About administering VCS from the command line
- Stopping the VCS engine and related processes
- 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
- About administering resource types
- About administering clusters
- Configuring resources and applications in VCS
- About configuring resources and applications
- About Virtual Business Services
- About Intelligent Resource Monitoring (IMF)
- About fast failover
- How VCS monitors storage components
- About storage configuration
- About configuring network resources
- About configuring file shares
- About configuring IIS sites
- About configuring services
- Before you configure a service using the GenericService agent
- About configuring processes
- About configuring Microsoft Message Queuing (MSMQ)
- About configuring the infrastructure and support agents
- About configuring applications using the Application Configuration Wizard
- Adding resources to a service group
- About application monitoring on single-node clusters
- Configuring the service group in a non-shared storage environment
- About the VCS Application Manager utility
- About testing resource failover using virtual fire drills
- Modifying the cluster configuration
- Section III. Administration - Beyond the basics
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- Customized behavior diagrams
- VCS behavior for resources that support the intentional offline functionality
- About controlling VCS behavior at the resource level
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- VCS event notification
- VCS event triggers
- List of event triggers
- Controlling VCS behavior
- Section IV. 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
- Configuring replication resources in VCS
- 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 Cluster Manager (Java console)
- 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
- Connecting clusters–Creating global clusters
- Section V. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- VCS agent statistics
- Troubleshooting and recovery for VCS
- VCS message logging
- Handling network failure
- Troubleshooting VCS startup
- Troubleshooting service groups
- Troubleshooting and recovery for global clusters
- VCS utilities
- VCS performance considerations
- Section VI. Appendixes
- Appendix A. VCS user privileges—administration matrices
- Appendix B. Cluster and system states
- Appendix C. VCS attributes
- Appendix D. Configuring LLT over UDP
- Appendix E. Handling concurrency violation in any-to-any configurations
- Appendix F. Accessibility and VCS
- Appendix G. Executive Order logging
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:
Arctera 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
- Add a new IPv6 resource.
# hares -add resourceName resourceType groupName
For example:
hares -add csg_ipv6 IPv6 ClusterService
- Enable the resource.
# hares -modify resourceName Enabled 1
For example:
# hares -modify csg_ipv6 Enabled 1
- Set all the required attribute values.
# hares -modify resourceName attributeName attributeValue
For example:
# hares -modify csg_ipv6 Address 2620:128:f0a2:9005::130
# hares -modify csg_ipv6 Prefix 2620:128:f0a2:9005::/64
# hares -local csg_ipv6 MACAddress
# hares -modify csg_ipv6 MACAddress 00:50:56:99:2B:F9 -sys vcscortech1-vm2
- Bring the IPv6 resource online.
# hares -online resourceName -sys systemName
For example:
# hares -online csg_ipv6 -sys vcscortech1-vm2
- Set the value of the ClusterAddress attribute to IPv6 address.
# haclus -modify ClusterAddress IPv6Address
For example:
haclus -modify ClusterAddress 2620:128:f0a2:9005::130
- Remove the dependency of the IP resource.
# hares -unlink parentResourceName childResourceName
For example:
# hares -unlink wac csg_ip
# hares -unlink csg_ip csg_nic
- Add the dependency of the IPv6 resource.
# hares -link parentResourceName childResourceName
For example:
# hares -link csg_ipv6 csg_nic
# hares -link wac csg_ip
- 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::130 -clus spclsS2
- 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::130 -clus spcls2
- 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
After the primary and the secondary sites are completely migrated to IPv6, you can remove the old IP resources from all the cluster nodes.
To remove the IP resources from the cluster
- Set the cluster to read-write mode.
# haconf -makerw
- Delete the IPv4 resource.
# hares -delete resourceName
For example:
hares -delete csg_ip
- Save the modified cluster configuration and make it read only.
# haconf -dump -makero
Note:
Remove the old IP resources before you disable IPv4 on the cluster nodes. Otherwise, the IP resources are faulted, and if they are set as critical resources, a service group failover is triggered.