Cluster Server 7.4 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 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
- Configuring the service group in a non-shared storage environment
- About the VCS Application Manager utility
- About testing resource failover using virtual fire drills
- HA and DR configurations using InfoScale in AWS
- HA and DR configurations in Azure environment
- 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
Failover within the same subnet using a private IP
InfoScale clusters let you fail over IPs - and thereby, the application configured for HA - within the same subnet in the same VNet.
The following information is required:
A private IP (secondary private IP) address to be failed over
The device to which the IP should be plumbed
The following graphic depicts a sample failover configuration within the same subnet using a private IP:
The sample configuration includes the following elements:
A Azure virtual network (VNet) is configured in Region A of the Azure cloud
An application is configured for HA using a cluster that comprises two nodes, Node1 and Node2, which are Azure virtual machines
Both the cluster nodes exist in the same subnet
A private IP is configured, which is failed over from one node to the other as part of the failover or the failback operations
The following snippet is a service group configuration from a sample configuration file (main.cf):
group AzureAuthGrp ( SystemList = { AzureVM1 = 0, AzureVM2 = 1 } Parallel = 1 ) AzureAuth azureAuth ( SubscriptionId = 640a326-fga6-90gh-b616-c1e9bb ClientId = e8d899-d32a-47d04-8986-be739104d SecretKey = fntPgnUnhTprQrqTRonSlpRhnGrrNklFngLs TenantId = 9fjkabae-2348-4308-b503-6667d61 ) Phantom phres ( ) group AzureIPGrp ( SystemList = { AzureVM1 = 0, AzureVM2 = 1 } ) IP IP_res ( Address = "10.1.5.67" SubNetMask = "255.255.255.0" MACAddress @AzureVM1 = 00-0D-3A-91-73-A0 MACAddress @AzureVM2 = 00-0D-3A-92-03-DC ) NIC NIC_res ( MACAddress @AzureVM1 = 00-0D-3A-91-73-A0 MACAddress @AzureVM2 = 00-0D-3A-92-03-DC ) AzureIP AzureIP_res ( PrivateIP = "10.1.5.42" MACAddress @AzureVM1 = 00-0D-3A-91-73-A0 MACAddress @AzureVM2 = 00-0D-3A-92-03-DC AzureAuthResName = azureAuth ) IP_res requires AzureIP_res AzureIP_res requires NIC_res