Cluster Server 7.4.1 Administrator's Guide - Linux
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- Predicting VCS behavior using VCS Simulator
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About configuring a CP server to support IPv6 or dual stack
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Veritas High Availability Configuration wizard
- Introducing the Veritas High Availability Configuration wizard
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Section VI. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VII. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting issues with systemd unit service files
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- Troubleshooting wizard-based configuration issues
- Troubleshooting issues with the Veritas High Availability view
- VCS message logging
- VCS performance considerations
- Section VIII. Appendixes
Launching the Veritas High Availability Configuration wizard
In a physical Linux environment, VMware virtual environment, logical domain, or LPAR, you can launch the Veritas High Availability Configuration wizard using:
A browser window: To launch the wizard from a browser window
In addition, in a Linux environment, you can also launch the wizard using:
haappwizard utility: To launch the wizard using the haappwizard utility
In addition, in a VMware virtual environment, you can also launch the wizard using:
VMware vSphere Client: To launch the wizard from the VMware vSphere Client
To launch the wizard from the Client
- Log in to the Management Server console.
- In the home page, click the Availability icon from the list of perspectives.
- In the Data Center tree under the Manage pane, locate the cluster.
- Navigate to the Systems object under the cluster.
- Locate the system on which the application is running or application prerequisites are met.
- Right-click on the system, and then click Configure Application.
To launch the wizard from a browser window
- Open a browser window and enter the following URL:
https://system_name_or_IP:5634/vcs/admin/application_health.html
system_name_or_IP is the system name or IP address of the system on which you want to configure application monitoring.
- In the Authentication dialog box, enter the username and password of the user who has administrative privileges.
- Depending on your setup, use one of the following options to launch the wizard:
If you have not configured a cluster, click the Configure a VCS Cluster link.
If you have already configured a cluster, click Actions > Configure Application for High Availability or the Configure Application for High Availability link.
If you have already configured a cluster and configured an application for monitoring, click Actions > Configure Application for High Availability.
Note:
In the Storage Foundation and High Availability (SFHA) 6.2 release and later, the haappwizard utility has been deprecated.
To launch the wizard using the haappwizard utility
The haappwizard utility allows you to launch the Veritas High Availability Configuration wizard. The utility is part of the product package and is installed in the /opt/VRTSvcs/bin directory.
- Enter the following command to launch the Veritas High Availability Configuration wizard:
happwizard [-hostname host_name] [-browser browser_name] [-help]
The following table describes the options of the happwizard utility:
Table: Options of the happwizard utility
- hostname | Allows you to specify the host name or IP address of the system from which you want to launch the Veritas High Availability Configuration wizard. If you do not specify a host name or IP address, the Veritas High Availability Configuration wizard is launched on the local host. |
-browser | Allows you to specify the browser name. The supported browsers are Internet Explorer and Firefox. For example, enter iexplore for Internet Explorer and firefox for Firefox. Note: The value is case-insensitive. |
-help | Displays the command usage. |
To launch the wizard from the VMware vSphere Client
- Launch the VMware vSphere Client and connect to the VMware vCenter Server that hosts the virtual machine.
- From the vSphere Client's Inventory view in the left pane, select the virtual machine where you want to configure application monitoring.
- Skip this step if you have already configured single sign-on during guest installation.
Select the Veritas High Availability tab and in the Veritas High Availability View page, specify the credentials of a user account that has administrative privileges on the virtual machine and click Configure.
The Veritas High Availability console sets up a permanent authentication for the user account on that virtual machine.
- Depending on your setup, use one of the following options to launch the wizard:
If you have not configured a cluster, click the Configure a VCS Cluster link.
If you have already configured a cluster, click Actions > Configure Application for High Availability or the Configure Application for High Availability link.
If you have already configured a cluster and configured an application for monitoring and to configure another application for monitoring, click Actions > Configure Application for High Availability.