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
About element attributes values
Table: VCWsilent - variables and values describes the variables that are used in the XML format and their possible values:
* "n" is the sequence number for the systems, nodes, adapters, and MAC addresses.
Table: VCWsilent - variables and values
Variables | Description |
---|---|
domain_name | Replace this variable with the fully qualified name of a domain in which the systems reside. |
sys_name_<n*> | Replace this with name of the system in the domain for which relevant information will be discovered. Note: For each system, you must have a System child element under the SystemList element. |
clus_name | Replace this with the name of the cluster to be created. |
clus_ID | Replace this with the cluster ID. Make sure you specify a unique cluster ID between 0 and 65535. |
SingleNodeValue | Replace this "1" or "0." The value "1" indicates that it is a single-node cluster. The value "0" indicates that it is a multi-node cluster. |
node_name_<n*> | Replace this with the name of the system that will be part of the cluster. Make sure that you provide system names from the list of systems that are specified under the SystemList element. For example, if you specified SysA and SysB in the SystemList element, you can specify one or both the systems for the node names. However, you should not specify another system, say SysC, which was not specified in the SystemList element. Note: For each node, you must have a Node child element along with the LLTLink subchild element under the Cluster element. |
adp_name_<n*> | Replace this with the name of the adapter where the LLT link will be configured. Note: For each node, you must specify a minimum of two adapters. Each adapter must be specified as an attribute of the LLTLink element. |
MAC_address_<n*> | Replace this with the MAC address of the adapter. |
Pri | Replace this with either "1" or "0." Value "1" indicates that the adapter is assigned a low priority. Value "0" indicates otherwise. You can assign a low priority to an adapter to use it for both private and public network communication. |
admin_user_name | Replace this with a user name for the cluster administrator. You can use this user name to log on to a cluster that uses Cluster Manager. Note: This user name is applicable only for a non-secure cluster. |
root_name | Replace this with the host name of one of the systems selected for the cluster configuration. It should be one of the systems specified for the SystemList element. Note: This system name is applicable only for a secure cluster. |
HAD_user_name | Replace this with a domain user name in whose context the VCS Helper service will run. The VCS High Availability Daemon, which runs in the context of the local system built-in account, uses the VCS Helper service user context to access the network. |
password | Replace this with a plain-text password for HAD_user_name. |
ConnecttoClustervalue | Replace this with "Yes" if you want to connect to the cluster before you delete it. If the connection fails, the cluster deletion does not proceed. The default value is "No." This default value indicates that the cluster is deleted without connecting to it. |
IgnoreOfflineGroupsvalue | Replace this with "Yes" if you wish to delete the cluster along with the service groups that are configured in the cluster. The default value is "No". This means that the cluster deletion does not proceed if there are service groups in the cluster. |
Removevalue | Replace this with "Yes" if you want to delete the VCS Helper Service account along with the cluster. The default value is "No." This default value indicates that the VCS Helper account will not be deleted. |