InfoScale™ 9.0 Cluster Server Administrator's Guide - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (9.0)
Platform: Windows
  1. Section I. Clustering concepts and terminology
    1. Introducing Cluster Server
      1. About Cluster Server
        1.  
          How VCS detects failure
        2. How VCS ensures application availability
          1.  
            About switchover and failover
      2. About cluster control guidelines
        1.  
          Defined start, stop, and monitor procedures
        2.  
          Ability to restart the application in a known state
        3.  
          External data storage
        4.  
          Licensing and host name issues
      3. About the physical components of VCS
        1.  
          About VCS nodes
        2.  
          About shared storage
        3.  
          About networking
      4. Logical components of VCS
        1.  
          About resources and resource dependencies
        2.  
          Categories of resources
        3.  
          About resource types
        4.  
          About service groups
        5. Types of service groups
          1.  
            About failover service groups
          2.  
            About parallel service groups
          3.  
            About hybrid service groups
        6.  
          About the ClusterService group
        7.  
          About agents in VCS
        8.  
          About agent functions
        9. Agent classifications
          1.  
            About bundled agents
          2.  
            About enterprise agents
          3.  
            About custom agents
        10.  
          VCS agent framework
        11. About cluster control, communications, and membership
          1.  
            About the high availability daemon (HAD)
          2.  
            About Group Membership Services and Atomic Broadcast (GAB)
          3.  
            About Low Latency Transport (LLT)
        12. About security services
          1.  
            Digital certification structure
          2.  
            Components for secure communication
          3.  
            Restriction after failed user login attempts
        13.  
          Components for administering VCS
      5.  
        Putting the pieces together
    2. About cluster topologies
      1. Basic failover configurations
        1.  
          Asymmetric or active / passive configuration
        2.  
          Symmetric or active / active configuration
        3.  
          About N-to-1 configuration
      2. About advanced failover configurations
        1.  
          About the N + 1 configuration
        2.  
          About the N-to-N configuration
      3. Cluster topologies and storage configurations
        1.  
          About basic shared storage cluster
        2.  
          About campus, or metropolitan, shared storage cluster
        3.  
          About shared nothing clusters
        4.  
          About replicated data clusters
        5.  
          About global clusters
    3. VCS configuration concepts
      1.  
        About configuring VCS
      2.  
        VCS configuration language
      3. About the main.cf file
        1.  
          About the SystemList attribute
        2.  
          Initial configuration
        3.  
          Including multiple .cf files in main.cf
      4.  
        About the types.cf file
      5. About VCS attributes
        1.  
          About attribute data types
        2.  
          About attribute dimensions
        3.  
          About attributes and cluster objects
        4.  
          Attribute scope across systems: global and local attributes
        5.  
          About attribute life: temporary attributes
        6.  
          Size limitations for VCS objects
      6.  
        VCS keywords and reserved words
      7.  
        VCS environment variables
  2. Section II. Administration - Putting VCS to work
    1. About the VCS user privilege model
      1. About VCS user privileges and roles
        1.  
          VCS privilege levels
        2.  
          User roles in VCS
        3.  
          Hierarchy in VCS roles
        4.  
          User privileges for CLI commands
        5.  
          User privileges for cross-cluster operations
        6.  
          User privileges for clusters that run in secure mode
      2.  
        How administrators assign roles to users
      3.  
        User privileges for OS user groups for clusters running in secure mode
      4.  
        VCS privileges for users with multiple roles
      5. Restricted user privileges
        1.  
          Restricting user privileges
        2.  
          Limitations on restricting user privileges
    2. Getting started with VCS
      1. Configuring the cluster using the Cluster Configuration Wizard
        1.  
          Configuring notification
        2.  
          Configuring Wide-Area Connector process for global clusters
      2. About configuring a cluster from the command line
        1. About preparing for a silent configuration
          1.  
            About configuring a non-secure cluster
          2.  
            About configuring a secure cluster
          3.  
            About deleting a non-secure cluster
          4.  
            About deleting a secure cluster
          5.  
            About element attributes values
          6.  
            About sample XML configuration
        2.  
          Running the silent configuration utility
    3. Administering the cluster from the command line
      1. About administering VCS from the command line
        1.  
          Symbols used in the VCS command syntax
        2.  
          How VCS identifies the local system
        3.  
          About specifying values preceded by a dash (-)
        4.  
          About the -modify option
        5.  
          Encrypting VCS passwords
        6. Encrypting agent passwords
          1.  
            Generating a security key
          2.  
            Encrypting the agent password
          3.  
            Changing the security key
      2.  
        Starting VCS
      3. Stopping the VCS engine and related processes
        1.  
          About stopping VCS without the -force option
        2.  
          About stopping VCS with options other than the -force option
        3.  
          About controlling the hastop behavior by using the EngineShutdown attribute
        4.  
          Additional considerations for stopping VCS
      4. About managing VCS configuration files
        1.  
          About the hacf utility
        2.  
          About multiple versions of .cf files
        3.  
          Verifying a configuration
        4.  
          Scheduling automatic backups for VCS configuration files
        5.  
          Saving a configuration
        6.  
          Setting the configuration to read or write
        7.  
          Displaying configuration files in the correct format
      5. About managing VCS users from the command line
        1.  
          Adding a user
        2.  
          Assigning and removing user privileges
        3.  
          Modifying a user
        4.  
          Deleting a user
        5.  
          Displaying a user
      6. About querying VCS
        1.  
          Querying service groups
        2.  
          Querying resources
        3.  
          Querying resource types
        4.  
          Querying agents
        5.  
          Querying systems
        6.  
          Querying clusters
        7.  
          Querying status
        8.  
          Querying log data files (LDFs)
        9.  
          Using conditional statements to query VCS objects
      7. About administering service groups
        1.  
          Adding and deleting service groups
        2. Modifying service group attributes
          1.  
            Modifying the SystemList attribute
        3.  
          Bringing service groups online
        4.  
          Taking service groups offline
        5.  
          Switching service groups
        6.  
          Freezing and unfreezing service groups
        7.  
          Enabling and disabling priority based failover for a service group
        8.  
          Enabling and disabling service groups
        9.  
          Clearing faulted resources in a service group
        10.  
          Linking and unlinking service groups
      8.  
        Administering agents
      9. About administering resources
        1.  
          About adding resources
        2.  
          Adding resources
        3.  
          Deleting resources
        4.  
          Adding, deleting, and modifying resource attributes
        5.  
          Defining attributes as local
        6.  
          Linking and unlinking resources
        7.  
          Bringing resources online
        8.  
          Taking resources offline
        9.  
          Probing a resource
        10.  
          Clearing a resource
      10. About administering resource types
        1.  
          Adding, deleting, and modifying resource types
        2.  
          Overriding resource type static attributes
      11.  
        Administering systems
      12. About administering clusters
        1.  
          Retrieving version information
      13.  
        Using the -wait option in scripts that use VCS commands
      14.  
        About administering simulated clusters from the command line
    4. Configuring resources and applications in VCS
      1. About configuring resources and applications
        1.  
          Considerations for Windows Server systems
      2. About Virtual Business Services
        1.  
          Features of Virtual Business Services
        2.  
          Sample virtual business service configuration
      3. About Intelligent Resource Monitoring (IMF)
        1.  
          VCS changes to support IMF
        2.  
          VCS agents that support IMF
        3.  
          How IMF works
        4.  
          How to enable IMF
        5.  
          How to disable IMF
        6. Recommended settings
          1.  
            Modify the MountV resource attributes
          2.  
            Modify the attribute values for SQL Analysis Service and SQL Server Agent resources
          3.  
            Modify the NumThreads attribute for MountV and VMDg
      4. About fast failover
        1.  
          VCS changes for fast failover
        2.  
          Enabling fast failover for disk groups
      5. How VCS monitors storage components
        1.  
          Shared storage - if you use NetApp filers
        2.  
          Shared storage - if you use SFW to manage cluster dynamic disk groups
        3.  
          Shared storage - if you use Windows LDM to manage shared disks
        4.  
          Non-shared storage - if you use SFW to manage dynamic disk groups
        5.  
          Non-shared storage - if you use Windows LDM to manage local disks
        6.  
          Non-shared storage - if you use VMware storage
      6. About storage configuration
        1. About managing storage using Windows Logical Disk Manager
          1.  
            Reserving disks (if you use Windows LDM)
          2.  
            Creating volumes (if you use Windows LDM)
          3.  
            Mounting volumes (if you use Windows LDM)
          4.  
            Unassigning a drive letter
          5.  
            Releasing disks (if you use Windows LDM)
          6.  
            Configuration tasks
        2. About managing storage in a Network Appliance storage environment
          1.  
            Configuring Microsoft iSCSI Initiator
          2.  
            Connecting virtual disks to the cluster node
          3.  
            Disconnecting virtual disks from the cluster nodes
        3. About managing shared storage using Storage Foundation for Windows
          1.  
            Using SFW with VCS
          2.  
            Before you configure shared storage using SFW
          3.  
            Configuring shared storage
        4.  
          Managing storage
      7. About configuring network resources
        1. About configuring IP addresses on the systems
          1.  
            Before you configure IP addresses on the systems
          2.  
            Disabling DHCP
          3.  
            Configuring IP addresses on the systems
        2. About configuring virtual computer names
          1.  
            Before you configure virtual computer names
          2.  
            Configuring virtual computer names
      8. About configuring file shares
        1.  
          Before you configure a file share service group
        2.  
          Configuring file shares using the wizard
        3.  
          Modifying a file share service group using the wizard
        4.  
          Deleting a file share service group using the wizard
        5.  
          Creating non-scoped file shares configured with VCS
        6.  
          Making non-scoped file shares accessible while using virtual server name or IP address if NetBIOS and WINS are disabled
      9. About configuring IIS sites
        1.  
          Before you configure an IIS service group
        2.  
          Fixing the IPv6 address configuration for FTP sites
        3.  
          Installing IIS on Windows Server Core
        4.  
          Configuring an IIS service group using the wizard
        5.  
          Modifying an IIS service group using the wizard
        6.  
          Deleting an IIS service group using the wizard
      10. About configuring services
        1.  
          About configuring a service using the GenericService agent
        2. Before you configure a service using the GenericService agent
          1.  
            Changing a service startup type
          2.  
            Configuring a service to run in a user context
        3.  
          Configuring a service using the GenericService agent
        4.  
          About configuring a service using the ServiceMonitor agent
        5.  
          Before you configure a service using the ServiceMonitor agent
        6.  
          Configuring a service using the ServiceMonitor agent
      11. About configuring processes
        1.  
          Before you configure processes
        2.  
          Configuring processes using the Process agent
      12. About configuring Microsoft Message Queuing (MSMQ)
        1.  
          Before you configure the MSMQ service group
        2.  
          Configuring the MSMQ resource using the command-line utility
        3.  
          Configuring the MSMQ service group using the wizard
        4.  
          Modifying an MSMQ service group using the wizard
        5.  
          Configuring MSMQ agent to check port bindings more than once
        6.  
          Binding an MSMQ instance to the correct IP address
        7.  
          Checking whether MSMQ is listening for messages
      13. About configuring the infrastructure and support agents
        1.  
          About configuring notification
        2. Configuring registry replication
          1.  
            About registry hive abbreviations
          2.  
            About excluding keys
          3.  
            About ignoring subkeys
          4.  
            About additional considerations for using IgnoreSubKeys
        3.  
          Configuring a proxy resource
        4.  
          Configuring a phantom resource
        5.  
          Configuring file resources
        6.  
          Configuring a RemoteGroup resource
      14. About configuring applications using the Application Configuration Wizard
        1.  
          Before you configure service groups using the Application Configuration wizard
        2. Adding resources to a service group
          1.  
            Configuring a GenericService resource
          2.  
            Configuring processes
          3.  
            Configuring a ServiceMonitor resource
          4.  
            Configuring VCS components
        3.  
          Configuring service groups using the Application Configuration Wizard
        4.  
          Modifying an application service group
        5.  
          Deleting resources from a service group
        6.  
          Deleting an application service group
      15. About application monitoring on single-node clusters
        1.  
          Configuring application monitoring on a single-node cluster
        2.  
          Verifying whether application monitoring is enabled on the single-node cluster
        3.  
          Unconfiguring application monitoring on a single-node cluster
        4.  
          About reviewing and troubleshooting the configuration and monitoring activities
      16. Configuring the service group in a non-shared storage environment
        1.  
          Setting the timeout duration for which the VMNSDg agent waits for all the disks to arrive before importing the disk group
      17. About the VCS Application Manager utility
        1.  
          Managing applications in virtual server context
      18. About testing resource failover using virtual fire drills
        1.  
          About virtual fire drills
        2.  
          About infrastructure checks and fixes for supported agents
        3.  
          About running a virtual fire drill
    5. Modifying the cluster configuration
      1.  
        About modifying the cluster configuration
      2.  
        Adding nodes to a cluster
      3.  
        Removing nodes from a cluster
      4.  
        Reconfiguring a cluster
      5.  
        Configuring single sign-on for the cluster manually
      6. Configuring the ClusterService group
        1.  
          Configuring notification
        2.  
          Configuring the wide-area connector process for global clusters
      7.  
        Deleting a cluster configuration
  3. Section III. Administration - Beyond the basics
    1. Controlling VCS behavior
      1. VCS behavior on resource faults
        1.  
          Critical and non-critical resources
        2. VCS behavior diagrams
          1.  
            Example scenario 1: Resource with critical parent faults
          2.  
            Example scenario 2: Resource with non-critical parent faults
          3.  
            Example scenario 3: Resource with critical parent fails to come online
      2. About controlling VCS behavior at the service group level
        1.  
          About the AutoRestart attribute
        2.  
          About controlling failover on service group or system faults
        3.  
          About defining failover policies
        4.  
          About system zones
        5.  
          Load-based autostart
        6.  
          About freezing service groups
        7.  
          About controlling Clean behavior on resource faults
        8.  
          Clearing resources in the ADMIN_WAIT state
        9.  
          About controlling fault propagation
        10. Customized behavior diagrams
          1.  
            Example scenario: Resource with a critical parent and ManageFaults=NONE
          2.  
            Example scenario: Resource with a critical parent and FaultPropagation=0
        11. VCS behavior for resources that support the intentional offline functionality
          1.  
            About the IntentionalOffline attribute
          2.  
            About the ExternalStateChange attribute
      3. About controlling VCS behavior at the resource level
        1. Resource type attributes that control resource behavior
          1.  
            About the RestartLimit attribute
          2.  
            About the OnlineRetryLimit attribute
          3.  
            About the ConfInterval attribute
          4.  
            About the ToleranceLimit attribute
          5.  
            About the FaultOnMonitorTimeouts attribute
        2. How VCS handles resource faults
          1.  
            VCS behavior when an online resource faults
          2.  
            VCS behavior when a resource fails to come online
        3.  
          VCS behavior after a resource is declared faulted
        4. About disabling resources
          1.  
            When to disable a resource
          2.  
            Limitations of disabling resources
          3.  
            Additional considerations for disabling resources
          4.  
            How disabled resources affect group states
      4.  
        Changing agent file paths and binaries
      5. Service group workload management
        1.  
          About enabling service group workload management
        2. System capacity and service group load
          1.  
            Static load versus dynamic load
          2.  
            About overload warning
        3.  
          System limits and service group prerequisites
        4.  
          About capacity and limits
      6. Sample configurations depicting workload management
        1.  
          System and Service group definitions
        2. Sample configuration: Basic four-node cluster
          1.  
            About AutoStart operation
          2.  
            About the failure scenario
          3.  
            About the cascading failure scenario
        3. Sample configuration: Complex four-node cluster
          1.  
            About the AutoStart operation
          2.  
            About the normal operation
          3.  
            About the failure scenario
          4.  
            About the cascading failure scenario
        4. Sample configuration: Server consolidation
          1.  
            About the AutoStart operation
          2.  
            About the normal operation
          3.  
            About the failure scenario
          4.  
            About the cascading failure scenario
    2. The role of service group dependencies
      1. About service group dependencies
        1. About dependency links
          1.  
            Dependency categories
          2.  
            Dependency location
          3.  
            Dependency rigidity
        2.  
          About dependency limitations
      2. Service group dependency configurations
        1. About failover parent / failover child
          1.  
            About failover parent / parallel child
          2.  
            About parallel parent / failover child
          3.  
            About parallel parent / parallel child
      3.  
        Frequently asked questions about group dependencies
      4.  
        About linking service groups
      5. VCS behavior with service group dependencies
        1.  
          Online operations in group dependencies
        2.  
          Offline operations in group dependencies
        3.  
          Switch operations in group dependencies
    3. VCS event notification
      1. About VCS event notification
        1.  
          Event messages and severity levels
        2.  
          About persistent and replicated message queue
        3.  
          How HAD deletes messages
      2. Components of VCS event notification
        1. About the notifier process
          1.  
            Example of notifier command
        2. About the hanotify utility
          1.  
            Example of hanotify command
      3. About VCS events and traps
        1.  
          Events and traps for clusters
        2.  
          Events and traps for agents
        3.  
          Events and traps for resources
        4.  
          Events and traps for systems
        5.  
          Events and traps for service groups
        6.  
          SNMP-specific files
        7. Trap variables in VCS MIB
          1.  
            About severityId
          2.  
            EntityType and entitySubType
          3.  
            About entityState
      4. About monitoring aggregate events
        1.  
          How to detect service group failover
        2.  
          How to detect service group switch
      5.  
        About configuring notification
    4. VCS event triggers
      1.  
        About VCS event triggers
      2.  
        Using event triggers
      3. List of event triggers
        1.  
          About the dumptunables trigger
        2.  
          About the injeopardy event trigger
        3.  
          About the loadwarning event trigger
        4.  
          About the nofailover event trigger
        5.  
          About the postoffline event trigger
        6.  
          About the postonline event trigger
        7.  
          About the preonline event trigger
        8.  
          About the resadminwait event trigger
        9.  
          About the resfault event trigger
        10.  
          About the resnotoff event trigger
        11.  
          About the resrestart event trigger
        12.  
          About the resstatechange event trigger
        13.  
          About the sysoffline event trigger
        14.  
          About the unable_to_restart_agent event trigger
        15.  
          About the unable_to_restart_had event trigger
        16.  
          About the violation event trigger
  4. Section IV. Cluster configurations for disaster recovery
    1. Connecting clusters–Creating global clusters
      1.  
        How VCS global clusters work
      2. VCS global clusters: The building blocks
        1.  
          Visualization of remote cluster objects
        2.  
          About global service groups
        3. About global cluster management
          1.  
            About the wide-area connector process
          2.  
            About the wide-area heartbeat agent
        4. About serialization - The Authority attribute
          1.  
            About the Authority and AutoStart attributes
        5.  
          About resiliency and "Right of way"
        6.  
          VCS agents to manage wide-area failover
        7.  
          About the Steward process: Split-brain in two-cluster global clusters
        8.  
          Secure communication in global clusters
      3. Prerequisites for global clusters
        1.  
          Prerequisites for cluster setup
        2.  
          Prerequisites for application setup
        3.  
          Prerequisites for wide-area heartbeats
        4.  
          Prerequisites for ClusterService group
        5.  
          Prerequisites for replication setup
      4. Setting up a global cluster
        1.  
          Preparing the application for the global environment
        2.  
          Configuring the ClusterService group
        3. Configuring replication resources in VCS
          1.  
            About the prerequisites for configuring replication resources in VCS
        4.  
          Linking the application and replication service groups
        5.  
          Configuring the second cluster
        6.  
          Linking clusters
        7.  
          Configuring the Steward process (optional)
        8.  
          Stopping the Steward process
        9.  
          Configuring the global service group
      5. About IPv6 support with global clusters
        1.  
          Prerequisites for configuring a global cluster to support IPv6
        2.  
          Migrating an InfoScale Availability cluster from IPv4 to IPv6 when Virtual IP (ClusterAddress) is configured
        3.  
          Migrating an InfoScale Availability cluster to IPv6 in a GCO deployment
      6. About cluster faults
        1.  
          About the type of failure
        2.  
          Switching the service group back to the primary
      7. About setting up a disaster recovery fire drill
        1. About creating and configuring the fire drill service group manually
          1.  
            Creating the fire drill service group
          2.  
            Linking the fire drill and replication service groups
          3.  
            Adding resources to the fire drill service group
          4.  
            Configuring the fire drill service group
          5.  
            Enabling the FireDrill attribute
      8.  
        Multi-tiered application support using the RemoteGroup agent in a global environment
      9. Test scenario for a multi-tiered environment
        1.  
          About the main.cf file for cluster 1
        2.  
          About the main.cf file for cluster 2
        3.  
          About the main.cf file for cluster 3
        4.  
          About the main.cf file for cluster 4
    2. Administering global clusters from Cluster Manager (Java console)
      1.  
        About global clusters
      2.  
        Adding a remote cluster
      3.  
        Deleting a remote cluster
      4. Administering global service groups
        1.  
          Converting local and global groups
        2.  
          Bringing a service group online in a remote cluster
        3.  
          Taking a service group offline in a remote cluster
        4.  
          Switching a service group to a remote cluster
      5. Administering global heartbeats
        1.  
          Adding a global heartbeat
        2.  
          Modifying a global heartbeat
        3.  
          Deleting a global heartbeat
    3. Administering global clusters from the command line
      1.  
        About administering global clusters from the command line
      2. About global querying in a global cluster setup
        1.  
          Querying global cluster service groups
        2.  
          Querying resources across clusters
        3.  
          Querying systems
        4.  
          Querying clusters
        5.  
          Querying status
        6.  
          Querying heartbeats
      3.  
        Administering global service groups in a global cluster setup
      4.  
        Administering resources in a global cluster setup
      5. Administering clusters in global cluster setup
        1.  
          Managing cluster alerts in a global cluster setup
        2.  
          Changing the cluster name in a global cluster setup
      6.  
        Administering heartbeats in a global cluster setup
    4. Setting up replicated data clusters
      1.  
        About replicated data clusters
      2.  
        How VCS replicated data clusters work
      3.  
        About setting up a replicated data cluster configuration
  5. Section V. Troubleshooting and performance
    1. VCS performance considerations
      1. How cluster components affect performance
        1.  
          How kernel components (GAB and LLT) affect performance
        2.  
          How the VCS engine (HAD) affects performance
        3. How agents affect performance
          1.  
            Monitoring resource type and agent configuration
        4.  
          How the VCS graphical user interfaces affect performance
        5.  
          If the network adapters cannot ping each other, the cluster nodes may not get GAB membership
      2. How cluster operations affect performance
        1.  
          VCS performance consideration when booting a cluster system
        2.  
          VCS performance consideration when a resource comes online
        3.  
          VCS performance consideration when a resource goes offline
        4.  
          VCS performance consideration when a service group comes online
        5.  
          VCS performance consideration when a service group goes offline
        6.  
          VCS performance consideration when a resource fails
        7.  
          VCS performance consideration when a system fails
        8.  
          VCS performance consideration when a network link fails
        9. VCS performance consideration when a system panics
          1.  
            About GAB client process failure
          2.  
            About GAB client registration monitoring
          3.  
            About network failure and GAB IOFENCE message
          4.  
            About quick reopen
        10.  
          VCS performance consideration when a service group switches over
        11.  
          VCS performance consideration when a service group fails over
      3.  
        Monitoring CPU usage
      4. VCS agent statistics
        1.  
          Tracking monitor cycle times
        2.  
          VCS attributes enabling agent statistics
      5.  
        About VCS performance with non-HA products
      6.  
        About VCS performance with SFW
    2. Troubleshooting and recovery for VCS
      1. VCS message logging
        1.  
          VCW logs
        2.  
          VCWsilent logs
        3.  
          Solutions wizard logs
        4.  
          Message catalogs
      2. Handling network failure
        1.  
          Disabling failover
        2. Example of how VCS handles network failure
          1.  
            Jeopardy scenario: link failure
          2.  
            Jeopardy scenario: link and node failure
          3.  
            Jeopardy scenario: failure of all links
        3.  
          Network partitioning
        4.  
          When VCS shuts down a system
        5.  
          Pre-existing network partitions
        6.  
          Seeding of VCS clusters
        7.  
          Reconnecting the private network
      3. Troubleshooting VCS startup
        1. Low Latency Transport (LLT)
          1.  
            Common LLT directives
        2.  
          Group Membership Atomic Broadcast (GAB)
        3. Verifying LLT, GAB, and cluster operation
          1.  
            Verifying LLT
          2.  
            Setting the checksum option
          3.  
            Verifying GAB
          4.  
            Verifying HAD
          5.  
            Verifying the cluster
        4. VCS startup errors
          1.  
            Seeding the cluster
        5.  
          Cluster ID is not unique over a network
      4.  
        Troubleshooting secure clusters
      5. Troubleshooting service groups
        1.  
          ClusterService group configuration
      6.  
        Troubleshooting resources
      7.  
        Troubleshooting notification
      8. Troubleshooting and recovery for global clusters
        1.  
          Disaster declaration
        2.  
          Lost heartbeats and the inquiry mechanism
        3. VCS alerts
          1.  
            Types of alerts
          2.  
            Managing alerts
          3.  
            Actions associated with alerts
          4.  
            Negating events
      9.  
        Troubleshooting the steward process
      10. VCS utilities
        1. The getcomms utility
          1.  
            getcomms options
          2.  
            Log location
        2. The hagetcf utility
          1.  
            Log location
          2.  
            Options for the hagetcf utility
        3.  
          The NICTest utility
        4.  
          The VCSRegUtil utility
        5. The havol utility
          1.  
            Using the -getdrive option
          2.  
            Using the -scsitest option
          3.  
            Retrieving the disk number
          4.  
            The -scsitest command options
        6.  
          The vmgetdrive utility
        7. Configuring the VCS Helper service manually
          1.  
            Command syntax
          2.  
            Command options
  6. Section VI. Appendixes
    1. Appendix A. VCS user privileges—administration matrices
      1.  
        About administration matrices
      2. Administration matrices
        1.  
          Agent Operations (haagent)
        2.  
          Attribute Operations (haattr)
        3.  
          Cluster Operations (haclus, haconf)
        4.  
          Service group operations (hagrp)
        5.  
          Heartbeat operations (hahb)
        6.  
          Log operations (halog)
        7.  
          Resource operations (hares)
        8.  
          System operations (hasys)
        9.  
          Resource type operations (hatype)
        10.  
          User operations (hauser)
    2. Appendix B. Cluster and system states
      1. Remote cluster states
        1.  
          Examples of cluster state transitions
      2. System states
        1.  
          Examples of system state transitions
    3. Appendix C. VCS attributes
      1.  
        About attributes and their definitions
      2.  
        Resource attributes
      3.  
        Resource type attributes
      4.  
        Service group attributes
      5.  
        System attributes
      6.  
        Cluster attributes
      7.  
        Heartbeat attributes (for global clusters)
      8.  
        Remote cluster attributes
    4. Appendix D. Configuring LLT over UDP
      1.  
        About configuring LLT over UDP
      2.  
        When to use LLT over UDP
      3. LLT over UDP configuration
        1.  
          The link command in the llttab file
        2.  
          The set-addr command in the llttab file
        3.  
          Selecting UDP ports
      4.  
        Sample configuration: Direct-attached links
      5.  
        Sample configuration: Links crossing IP routers
      6. Issues and limitations
        1.  
          VCW does not support configuring broadcasting for UDP
        2.  
          If the network adapters are unable to ping each other, the cluster nodes may not get GAB membership
    5. Appendix E. Handling concurrency violation in any-to-any configurations
      1.  
        About handling concurrency violation
      2.  
        Concurrency violation scenario
      3.  
        About the vcsgensvc.vbs script
      4. Sample configuration to handle concurrency violation
        1.  
          Notes for using scripts with the Process agent
    6. Appendix F. Accessibility and VCS
      1.  
        About accessibility in VCS
      2. Navigation and keyboard shortcuts
        1.  
          Navigation in the Java Console
        2.  
          Navigation in the Web console
      3.  
        Support for accessibility settings
      4.  
        Support for assistive technologies
    7. Appendix G. Executive Order logging
      1.  
        Executive Order logging
      2.  
        Log formatting
      3.  
        Enabling cluster server logs
      4.  
        Log forwarding

Service group attributes

Table: Service group attributes lists the service group attributes.

Table: Service group attributes

Service Group Attributes

Definition

ActiveCount

(system use only)

Number of resources in a service group that are active (online or waiting to go online). When the number drops to zero, the service group is considered offline.

  • Type and dimension: integer-scalar

  • Default: Not applicable.

AdministratorGroups

(user-defined)

List of operating system user account groups that have administrative privileges on the service group.

This attribute applies to clusters running in secure mode.

  • Type and dimension: string-keylist

  • Default: {} (none)

Administrators

(user-defined)

List of VCS users with privileges to administer the group.

Note:

A Group Administrator can perform all operations related to a specific service group, but cannot perform generic cluster operations.

  • Type and dimension: string-keylist

  • Default: {} (none)

Authority

(user-defined)

Indicates whether or not the local cluster is allowed to bring the service group online. If set to 0, it is not, if set to 1, it is. Only one cluster can have this attribute set to 1 for a specific global group.

  • Type and dimension: integer-scalar

  • Default: 0

AutoClearCount

(System use only)

Indicates the number of attempts that the VCS engine made to clear the state of the service group that has faulted and does not have a failover target. This attribute is used only if the AutoClearLimit attribute is set for the service group.

AutoClearInterval

(user-defined)

Indicates the interval in seconds after which a service group that has faulted and has no failover target is cleared automatically. The state of the service group is cleared only if AutoClearLimit is set to a non-zero value.

Default: 0

AutoclearLimit

(user-defined)

Defines the number of attempts to be made to clear the Faulted state of a service group. Disables the auto-clear feature when set to zero.

AutoDisabled

(system use only)

Indicates that VCS does not know the status of a service group (or specified system for parallel service groups). This could occur because the group is not probed (on specified system for parallel groups) in the SystemList attribute. Or the VCS engine is not running on a node designated in the SystemList attribute, but the node is visible.

When VCS does not know the status of a service group on a node but you want VCS to consider the service group enabled, perform this command to change the AutoDisabled value to 0.

hagrp -autoenable grp -sys sys1

This command instructs VCS that even though VCS has marked the service group auto-disabled, you are sure that the service group is not online on sys1. For failover service groups, this is important because the service groups now can be brought online on remaining nodes.

  • Type and dimension: boolean-scalar

  • Default: 0

AutoFailOver

(user-defined)

Indicates whether VCS initiates an automatic failover if the service group faults.

The attribute can take the following values:

  • 0 - VCS does not fail over the service group.

  • 1 - VCS automatically fails over the service group if a suitable node exists for failover.

  • Type and dimension: boolean-scalar

  • Default: 1 (enabled)

AutoRestart

(user-defined)

Restarts a service group after a faulted persistent resource becomes online.

The attribute can take the following values:

  • 0 - Autorestart is disabled.

  • 1 - Autorestart is enabled.

  • 2 - When a faulted persistent resource recovers from a fault, the VCS engine clears the faults on all non-persistent faulted resources on the system. It then restarts the service group.

Note:

This attribute applies only to service groups containing persistent resources.

  • Type and dimension: integer-scalar

  • Default: 1 (enabled)

AutoStart

(user-defined)

Designates whether a service group is automatically started when VCS is started.

  • Type and dimension: boolean-scalar

  • Default: 1 (enabled)

AutoStartIfPartial

(user-defined)

Indicates whether to initiate bringing a service group online if the group is probed and discovered to be in a PARTIAL state when VCS is started.

  • Type and dimension: boolean-scalar

  • Default: 1 (enabled)

AutoStartList

(user-defined)

List of systems on which, under specific conditions, the service group will be started with VCS (usually at system boot). For example, if a system is a member of a failover service group's AutoStartList attribute, and if the service group is not already running on another system in the cluster, the group is brought online when the system is started.

VCS uses the AutoStartPolicy attribute to determine the system on which to bring the service group online.

Note:

For the service group to start, AutoStart must be enabled and Frozen must be 0. Also, beginning with 1.3.0, you must define the SystemList attribute prior to setting this attribute.

  • Type and dimension: string-keylist

  • Default: {} (none)

AutoStartPolicy

(user-defined)

Sets the policy VCS uses to determine the system on which a service group is brought online during an autostart operation if multiple systems exist.

This attribute has three options:

Order (default) - Systems are chosen in the order in which they are defined in the AutoStartList attribute.

Load - Systems are chosen in the order of their capacity, as designated in the AvailableCapacity system attribute. System with the highest capacity is chosen first.

Note:

You cannot set the value Load when the cluster attribute Statistics is set to Enabled.

Priority - Systems are chosen in the order of their priority in the SystemList attribute. Systems with the lowest priority is chosen first.

  • Type and dimension: string-scalar

  • Default: Order

CapacityReserved

(system use only)

Indicates whether capacity is reserved to bring service groups online or to fail them over. Capacity is reserved only when the service group attribute FailOverPolicy is set to BiggestAvailable.

This attribute is localized.

  • Type and dimension: Boolean

  • Default: ""

Possible values:

1: Capacity is reserved.

0: Capacity is not reserved.

The value can be reset using the hagrp -flush command.

To list this attribute, use the -all option with the hagrp -display command.

ClusterFailOverPolicy

(user-defined)

Determines how a global service group behaves when a cluster faults or when a global group faults. The attribute can take the following values:

Manual - The group does not fail over to another cluster automatically.

Auto - The group fails over to another cluster automatically if it is unable to fail over within the local cluster, or if the entire cluster faults.

Connected - The group fails over automatically to another cluster only if it is unable to fail over within the local cluster.

  • Type and dimension: string-scalar

  • Default: Manual

ClusterList

(user-defined)

Specifies the list of clusters on which the service group is configured to run.

  • Type and dimension: integer-association

  • Default: {} (none)

CurrentCount

(system use only)

Number of systems on which the service group is active.

  • Type and dimension: integer-scalar

  • Default: Not applicable.

DisableFaultMessages

(user-defined)

Suppresses fault and failover messages, for a group and its resources, from getting logged in the VCS engine log file. This attribute does not suppress the information messages getting logged in the log file.

The attribute can take the following values:

  • 0 - Logs all the fault and failover messages for the service group and its resources.

  • 1 - Disables the fault and failover messages of the service groups, but continues to log resource messages.

  • 2 - Disables the fault and failover messages of the service group resources, but continues to log service group messages.

  • 3 - Disables the fault and failover messages of both service groups and its resources.

DeferAutoStart

(system use only)

Indicates whether HAD defers the auto-start of a global group in the local cluster in case the global cluster is not fully connected.

  • Type and dimension: boolean-scalar

  • Default: Not applicable

Enabled

(user-defined)

Indicates if a service group can be failed over or brought online.

The attribute can have global or local scope. If you define local (system-specific) scope for this attribute, VCS prevents the service group from coming online on specified systems that have a value of 0 for the attribute. You can use this attribute to prevent failovers on a system when performing maintenance on the system.

  • Type and dimension: boolean-scalar

  • Default: 1 (enabled)

Evacuate

(user-defined)

Indicates if VCS initiates an automatic failover when user issues hastop -local -evacuate.

  • Type and dimension: boolean-scalar

  • Default: 1

Evacuating

(system use only)

Indicates the node ID from which the service group is being evacuated.

  • Type and dimension: integer-scalar

  • Default: Not applicable

EvacList

(system use only)

Contains list of pairs of low priority service groups and the systems on which they will be evacuated.

For example:

Grp1 EvacList  grp2 Sys0  grp3 Sys0  grp4 Sys4

Type and dimension: string-association

Default: Not applicable.

EvacuatingForGroup

(system use only)

Displays the name of the high priority service group for which evacuation is in progress. The service group name is visible only as long as the evacuation is in progress.

Type and dimension: string-scalar

Default: Not applicable.

Failover

(system use only)

Indicates service group is in the process of failing over.

  • Type and dimension: boolean-scalar

  • Default: Not applicable

FailOverPolicy

(user-defined)

Defines the failover policy used by VCS to determine the system to which a group fails over. It is also used to determine the system on which a service group has been brought online through manual operation.

The policy is defined only for clusters that contain multiple systems:

Priority - The system defined as the lowest priority in the SystemList attribute is chosen.

Load - The system with the highest value of AvailableCapacity is chosen.

RoundRobin - Systems are chosen based on the active service groups they host. The system with the least number of active service groups is chosen first.

BiggestAvailable - Systems are chosen based on the forecasted available capacity for all systems in the SystemList. The system with the highest available capacity forecasted is selected.

Note:

VCS selects the node in an alphabetical order when VCS detects two systems with same values set for the policy Priority, Load, RoundRobin, or BiggestAvailable.

Prerequisites for setting FailOverPolicy to BiggestAvailable:

  • The cluster attribute Statistics must be set to Enabled.

  • Arctera recommends that the cluster attribute HostMeters should contain at least one key.

  • The service group attribute Load must contain at least one key.

  • You cannot change the attribute from BiggestAvailable to some other value, when the service group attribute CapacityReserved is set to 1 because the VCS engine reserves system capacity when it determines BiggestAvailable for the service group.

    When the service group online transition completes and after the next forecast cycle, CapacityReserved is reset.

  • Type and dimension: string-scalar

  • Default: Priority

FaultPropagation

(user-defined)

Specifies if VCS should propagate the fault up to parent resources and take the entire service group offline when a resource faults.

The value 1 indicates that when a resource faults, VCS fails over the service group, if the group's AutoFailOver attribute is set to 1. If The value 0 indicates that when a resource faults, VCS does not take other resources offline, regardless of the value of the Critical attribute. The service group does not fail over on resource fault.

  • Type and dimension: boolean-scalar

  • Default: 1

FromQ

(system use only)

Indicates the system name from which the service group is failing over. This attribute is specified when service group failover is a direct consequence of the group event, such as a resource fault within the group or a group switch.

  • Type and dimension: string-association

  • Default: Not applicable

Frozen

(system use only)

Disables all actions, including autostart, online and offline, and failover, except for monitor actions performed by agents. (This convention is observed by all agents supplied with VCS.)

  • Type and dimension: boolean-scalar

  • Default: 0 (not frozen)

GroupOwner

(user-defined)

This attribute is used for VCS email notification and logging. VCS sends email notification to the person designated in this attribute when events occur that are related to the service group. Note that while VCS logs most events, not all events trigger notifications.

Make sure to set the severity level at which you want notifications to be sent to GroupOwner or to at least one recipient defined in the SmtpRecipients attribute of the NotifierMngr agent.

  • Type and dimension: string-scalar

  • Default: ""

GroupRecipients

(user-defined)

This attribute is used for VCS email notification. VCS sends email notification to persons designated in this attribute when events related to the service group occur and when the event's severity level is equal to or greater than the level specified in the attribute.

Make sure to set the severity level at which you want notifications to be sent to GroupRecipients or to at least one recipient defined in the SmtpRecipients attribute of the NotifierMngr agent.

  • Type and dimension: string-association

  • email id: The email address of the person registered as a recipient for notification.

    severity: The minimum level of severity at which notifications must be sent.

Guests

(user-defined)

List of operating system user accounts that have Guest privileges on the service group.

This attribute applies to clusters running in secure mode.

  • Type and dimension: string-keylist

  • Default: ""

IntentOnline

(system use only)

Indicates whether to keep service groups online or offline.

VCS sets this attribute to 1 if an attempt has been made to bring the service group online.

For failover groups, VCS sets this attribute to 0 when the group is taken offline.

For parallel groups, it is set to 0 for the system when the group is taken offline or when the group faults and can fail over to another system.

VCS sets this attribute to 2 for service groups if VCS attempts to autostart a service group; for example, attempting to bring a service group online on a system from AutoStartList.

  • Type and dimension: integer-scalar

  • Default: Not applicable.

IntentionalOnlineList

(system use only)

Lists the nodes where a resource that can be intentionally brought online is found ONLINE at first probe. IntentionalOnlineList is used along with AutoStartList to determine the node on which the service group should go online when a cluster starts.

  • Type and dimension: string-keylist

  • Default: Not applicable

LastSuccess

(system use only)

Indicates the time when service group was last brought online.

  • Type and dimension: integer-scalar

  • Default: Not applicable

Load

(user-defined)

Indicates the multidimensional value expressing load exerted by a service group on the system.

When the cluster attribute Statistics is not enabled, the allowed key value is Units.

  • Type and dimension: float-association

  • Default: Not applicable

The following additional considerations apply:

  • You cannot change this attribute when the service group attribute CapacityReserved is set to 1 in the cluster and when the FailOverPolicy is set to BiggestAvailable. This is because the VCS engine reserves system capacity based on the service group attribute Load.

    When the service group's online transition completes and after the next forecast cycle, CapacityReserved is reset.

ManageFaults

(user-defined)

Specifies if VCS manages resource failures within the service group by calling the Clean function for the resources. This attribute can take the following values.

NONE - VCS does not call the Clean function for any resource in the group. You must manually handle resource faults.

  • Type and dimension: string-scalar

  • Default: ALL

ManualOps

(user-defined)

Indicates if manual operations are allowed on the service group.

  • Type and dimension: boolean-scalar

  • Default = 1 (enabled)

MeterWeight

(user-defined)

Represents the weight given for the cluster attribute's HostMeters key to determine a target system for a service group when more than one system meets the group attribute's Load requirements.

  • Type and dimension: integer-association

  • Default: Not applicable

Additional considerations for configuring this attribute in main.cf or changing it at run time:

  • This is an optional service group attribute. If it is not defined for a group, the VCS considers the cluster attribute MeterWeight.

  • To override this attribute at an individual group level, define it at run time or in the main.cf file. Ensure that keys are subsets of the cluster attribute HostAvailableMeters.

  • You cannot change this attribute when the service group attribute CapacityReserved is set to 1 in the cluster.

  • The values for the keys represent weights of the corresponding parameters. It should be in range of 0 to 10.

MigrateQ

(system use only)

Indicates the system from which the service group is migrating. This attribute is specified when group failover is an indirect consequence (in situations such as a system shutdown or another group faults and is linked to this group).

  • Type and dimension: string-association

  • Default: Not applicable

NumRetries

(system use only)

Indicates the number of attempts made to bring a service group online. This attribute is used only if the attribute OnlineRetryLimit is set for the service group.

  • Type and dimension: integer-scalar

  • Default: Not applicable

OnlineAtUnfreeze

(system use only)

When a node or a service group is frozen, the OnlineAtUnfreeze attribute specifies how an offline service group reacts after it or a node is unfrozen.

  • Type and dimension: integer-scalar

  • Default: Not applicable

OnlineClearParent

When this attribute is enabled for a service group and the service group comes online or is detected online, VCS clears the faults on all online type parent groups, such as online local, online global, and online remote.

  • Type and dimension: boolean-scalar

  • Default: 0

For example, assume that both the parent group and the child group faulted and both cannot failover. Later, when VCS tries again to bring the child group online and the group is brought online or detected online, the VCS engine clears the faults on the parent group, allowing VCS to restart the parent group too.

OnlineRetryInterval

(user-defined)

Indicates the interval, in seconds, during which a service group that has successfully restarted on the same system and faults again should be failed over, even if the attribute OnlineRetryLimit is non-zero. This prevents a group from continuously faulting and restarting on the same system.

  • Type and dimension: integer-scalar

  • Default: 0

OnlineRetryLimit

(user-defined)

If non-zero, specifies the number of times the VCS engine tries to restart a faulted service group on the same system on which the group faulted, before it gives up and tries to fail over the group to another system.

If this attribute is set for a service group, then set a non-zero value for the OnlineRetryInterval attribute. This ensures that the service group does not fault and restart on the same node.

  • Type and dimension: integer-scalar

  • Default: 0

OperatorGroups

(user-defined)

List of operating system user groups that have Operator privileges on the service group. This attribute applies to clusters running in secure mode.

  • Type and dimension: string-keylist

  • Default: ""

Operators

(user-defined)

List of VCS users with privileges to operate the group. A Group Operator can only perform online/offline, and temporary freeze/unfreeze operations pertaining to a specific group.

  • Type and dimension: string-keylist

  • Default: ""

Parallel

(user-defined)

Indicates if service group is failover (0), parallel (1), or hybrid(2).

  • Type and dimension: integer-scalar

  • Default: 0

PathCount

(system use only)

Number of resources in path not yet taken offline. When this number drops to zero, the engine may take the entire service group offline if critical fault has occurred.

  • Type and dimension: integer-scalar

  • Default: Not applicable

PolicyIntention

(system use only)

Functions as a lock on service groups listed in the hagrp -online -propagate command and hagrp -offline -propagate command:

  • Type and dimension: integer-scalar

When PolicyIntention is set to a non-zero value for the service groups in dependency tree, this attribute protects the service groups from any other operation. PolicyIntention can take three values.

  • The value 0 indicates that the service group is not part of the hagrp -online -propagate operation or the hagrp -offline -propagate operation.

  • The value 1 indicates that the service group is part of the hagrp -online -propagate operation.

  • The value 2 indicates that the service group is part of the hagrp -offline -propagate operation.

PreOnline

(user-defined)

Indicates that the VCS engine should not bring online a service group in response to a manual group online, group autostart, or group failover. The engine should instead run the PreOnline trigger.

You can set a local (per-system) value or a global value for this attribute. A per-system value enables you to control the firing of PreOnline triggers on specific nodes in the cluster.

  • Type and dimension: boolean-scalar

  • Default: 0

You can change the attribute scope from local to global as follows:

# hagrp -local <service_group_name> <attribute_name>

You can change the attribute scope from global to local as follows:

# hagrp -global <service_group_name> <attribute_name>
<value> ... | <key> ... | {<key> <value>} ...

For more information about the -local option and the -global option, see the man pages associated with the hagrp command.

PreOnlining

(system use only)

Indicates that VCS engine invoked the preonline script; however, the script has not yet returned with group online.

  • Type and dimension: integer-scalar

  • Default: Not applicable

PreonlineTimeout

(user-defined)

Defines the maximum amount of time in seconds the preonline script takes to run the command hagrp -online -nopre for the group. Note that HAD uses this timeout during evacuation only. For example, when a user runs the command hastop -local -evacuate and the Preonline trigger is invoked on the system on which the service groups are being evacuated.

  • Type and dimension: integer-scalar

  • Default: 300

Prerequisites

(user-defined)

An unordered set of name=value pairs denoting specific resources required by a service group. If prerequisites are not met, the group cannot go online. The format for Prerequisites is:

Prerequisites() = {Name=Value, name2=value2}.

Names used in setting Prerequisites are arbitrary and not obtained from the system. Coordinate name=value pairs listed in Prerequisites with the same name=value pairs in Limits().

  • Type and dimension: integer-association

PrintTree

(user-defined)

Indicates whether or not the resource dependency tree is written to the configuration file. The value 1 indicates the tree is written.

Note:

For very large configurations, the time taken to print the tree and to dump the configuration is high.

  • Type and dimension: boolean-scalar

  • Default: 1

Priority

(user-defined)

Enables users to designate and prioritize the service group. VCS does not interpret the value; rather, this attribute enables the user to configure the priority of a service group and the sequence of actions required in response to a particular event.

  • Type and dimension: integer-scalar

  • Default: 0

Probed

(system use only)

Indicates whether all enabled resources in the group have been detected by their respective agents.

  • Type and dimension: boolean-scalar

  • Default: Not applicable

ProbesPending

(system use only)

The number of resources that remain to be detected by the agent on each system.

  • Type and dimension: integer-scalar

  • Default: Not applicable

Responding

(system use only)

Indicates VCS engine is responding to a failover event and is in the process of bringing the service group online or failing over the node.

  • Type and dimension: integer-scalar

  • Default: Not applicable

Restart

(system use only)

For internal use only.

  • Type and dimension: integer-scalar

  • Default: Not applicable

SourceFile

(user-defined)

File from which the configuration is read. Do not configure this attribute in main.cf.

Make sure the path exists on all nodes before running a command that configures this attribute.

Make sure the path exists on all nodes before configuring this attribute.

  • Type and dimension: string-scalar

  • Default: .\main.cf

State

(system use only)

Group state on each system:

OFFLINE - All non-persistent resources are offline.

ONLINE - All resources whose AutoStart attribute is equal to 1 are online.

FAULTED - At least one critical resource in the group is faulted or is affected by a fault.

PARTIAL - At least one, but not all, resources with Operations=OnOff is online, and not all AutoStart resources are online.

STARTING - Group is attempting to go online.

STOPPING - Group is attempting to go offline.

MIGRATING - Group is attempting to migrate a resource from the source system to the target system. This state should be seen only as a combination of multiple states such as, ONLINE|STOPPING|MIGRATING, OFFLINE|STARTING|MIGRATING, and OFFLINE|MIGRATING.

A group state may be a combination of multiple states described above. For example, OFFLINE | FAULTED, OFFLINE | STARTING, PARTIAL | FAULTED, PARTIAL | STARTING, PARTIAL | STOPPING, ONLINE | STOPPING

  • Type and dimension: integer-scalar

  • Default: Not applicable.

SysDownPolicy

(user-defined)

Determines whether a service group is autodisabled when the system is down and if the service group is taken offline when the system is rebooted or is shut down gracefully.

If SysDownPolicy contains the key AutoDisableNoOffline, the following conditions apply:

  • The service group is autodisabled when system is down, gracefully shut down, or is detected as down.

  • The service group is not taken offline when the system reboots or shuts down gracefully.

Valid values: Empty keylist or the key AutoDisableNoOffline

Default: Empty keylist

For example, if a service group with SysDownPolicy = AutoDisableNoOffline is online on system sys1, it has the following effect for various commands:

  • The hastop -local -evacuate command for sys1 is rejected

  • The hastop -sysoffline command is accepted but the service group with SysDownPolicy = AutoDisableNoOffline is not taken offline.

  • The hastop -all command is rejected.

SystemList

(user-defined)

List of systems on which the service group is configured to run and their priorities. Lower numbers indicate a preference for the system as a failover target.

Note:

You must define this attribute prior to setting the AutoStartList attribute.

  • Type and dimension: integer-association

  • Default: "" (none)

SystemZones

(user-defined)

Indicates the virtual sublists within the SystemList attribute that grant priority in failing over. Values are string/integer pairs. The string key is the name of a system in the SystemList attribute, and the integer is the number of the zone. Systems with the same zone number are members of the same zone. If a service group faults on one system in a zone, it is granted priority to fail over to another system within the same zone, despite the policy granted by the FailOverPolicy attribute.

  • Type and dimension: integer-association

  • Default: "" (none)

Note:

You cannot modify this attribute when SiteAware is set as 1 and Sites are defined.

Tag

(user-defined)

Identifies special-purpose service groups created for specific VCS products.

  • Type and dimension: string-scalar

  • Default: Not applicable.

TargetCount

(system use only)

Indicates the number of target systems on which the service group should be brought online.

  • Type and dimension: integer-scalar

  • Default: Not applicable.

TFrozen

(user-defined)

Indicates if service groups can be brought online or taken offline on nodes in the cluster. Service groups cannot be brought online or taken offline if the value of the attribute is 1.

  • Type and dimension: boolean-scalar

  • Default: 0 (not frozen)

ToQ

(system use only)

Indicates the node name to which the service is failing over. This attribute is specified when service group failover is a direct consequence of the group event, such as a resource fault within the group or a group switch.

  • Type and dimension: string-association

  • Default: Not applicable

TriggerEvent

(user-defined)

For internal use only.

  • Type and dimension: boolean-scalar

  • Default: Not applicable

TriggerPath

(user-defined)

Enables you to customize the trigger path.

If a trigger is enabled but the trigger path is "" (default), VCS invokes the trigger from the $VCS_HOME/bin/triggers directory. If you specify an alternate directory, VCS invokes the trigger from that path. The value is case-sensitive. VCS does not trim the leading spaces or trailing spaces in the Trigger Path value. If the path contains leading spaces or trailing spaces, the trigger might fail to get executed.

The path that you specify must be in the following format:

$VCS_HOME/TriggerPath/Trigger

For example, if TriggerPath is set to mytriggers/sg1, VCS looks for the preonline trigger scripts in the $VCS_HOME/mytriggers/sg1/preonline/ directory.

  • Type and dimension: string-scalar

  • Default: ""

TriggerResFault

(user-defined)

Defines whether VCS invokes the resfault trigger when a resource faults. The value 0 indicates that VCS does not invoke the trigger.

  • Type and dimension: boolean-scalar

  • Default: 1

TriggerResRestart

(user-defined)

Determines whether or not to invoke the resrestart trigger if resource restarts.

See About the resrestart event trigger.

To invoke the resrestart trigger for a specific resource, enable this attribute at the resource level.

See Resource attributes.

  • Type and dimension: boolean-scalar

  • Default: 0 (disabled)

TriggerResStateChange

(user-defined)

Determines whether or not to invoke the resstatechange trigger if resource state changes.

To invoke the resstatechange trigger for a specific resource, enable this attribute at the resource level.

See Resource attributes.

  • Type and dimension: boolean-scalar

  • Default: 0 (disabled)

TriggersEnabled

(user-defined)

Determines if a specific trigger is enabled or not.

Triggers are disabled by default. You can enable specific triggers on all nodes or on selected nodes. Valid values are VIOLATION, NOFAILOVER, PREONLINE, POSTONLINE, POSTOFFLINE, RESFAULT, RESSTATECHANGE, and RESRESTART.

To enable triggers on a node, add trigger keys in the following format:

TriggersEnabled@node1 = {POSTOFFLINE, POSTONLINE}

The postoffline trigger and postonline trigger are enabled on node1.

To enable triggers on all nodes in the cluster, add trigger keys in the following format:

TriggersEnabled = {POSTOFFLINE, POSTONLINE}

The postoffline trigger and postonline trigger are enabled on all nodes.

  • Type and dimension: string-keylist

  • Default: {}

You can change the attribute scope from local to global as follows:

# hagrp -local <service_group_name> <attribute_name>

You can change the attribute scope from global to local as follows:

# hagrp -global <service_group_name> <attribute_name>
<value> ... | <key> ... | {<key> <value>} ...

For more information about the -local option and the -global option, see the man pages associated with the hagrp command.

TypeDependencies

(user-defined)

Creates a dependency (via an ordered list) between resource types specified in the service group list, and all instances of the respective resource type.

  • Type and dimension: string-keylist

  • Default: ""

UnSteadyCount

(system use only)

Represents the total number of resources with pending online or offline operations. This is a localized attribute.

  • Type and dimension: integer

  • Default: 0

To list this attribute, use the -all option with the hagrp -display command.

The hagrp -flush command resets this attribute.

UserAssoc

(user-defined)

This is a free form string-association attribute to hold any key-value pair. "Name" and "UITimeout" keys are reserved by VCS health view. You must not delete these keys or update the values corresponding to these keys, but you can add other keys and use it for any other purpose.

  • Type and dimension: string-association

  • Default: {}

You can change the attribute scope from local to global as follows:

# hagrp -local <service_group_name> <attribute_name>

You can change the attribute scope from global to local as follows:

# hagrp -global <service_group_name> <attribute_name>
<value> ... | <key> ... | {<key> <value>} ...

For more information about the -local option and -global option, see the man pages associated with the hagrp command.

UserIntGlobal

(user-defined)

Use this attribute for any purpose. It is not used by VCS.

  • Type and dimension: integer-scalar

  • Default: 0

UserStrGlobal

(user-defined)

VCS uses this attribute in the ClusterService group. Do not modify this attribute in the ClusterService group. Use the attribute for any purpose in other service groups.

  • Type and dimension: string-scalar

  • Default: 0

UserIntLocal

(user-defined)

Use this attribute for any purpose. It is not used by VCS.

  • Type and dimension: integer-scalar

  • Default: 0

UserStrLocal

(user-defined)

Use this attribute for any purpose. It is not used by VCS.

  • Type and dimension: string-scalar

  • Default: ""

More Information

About VCS user privileges and roles

About serialization - The Authority attribute

About controlling failover on service group or system faults

About service group dependencies

About controlling Clean behavior on resource faults

About VCS user privileges and roles

???

About the resstatechange event trigger