Cluster Server 8.0.1 Configuration Guide for Custom Applications - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.1)
Platform: Windows
  1. Introducing the Veritas High Availability solution for VMware
    1. How does the Veritas High Availability solution work
      1.  
        How the VMwareDisks agent communicates with the vCenter Server instead of the ESX/ESXi host
      2.  
        Typical VCS cluster configuration in a virtual environment
      3.  
        How does the Veritas High Availability solution integrate with vSphere Web Client
    2.  
      Supported VMware versions
    3.  
      Managing storage
  2. Configuring application monitoring using the Veritas High Availability solution
    1.  
      Deploying the Veritas High Availability solution for configuring application monitoring
    2. Notes and recommendations
      1. Assigning privileges for non-administrator ESX/ESXi user account
        1.  
          Creating a role
        2.  
          Integrating with Active Directory or local authentication
        3.  
          Creating a new user
        4.  
          Adding a user to the role
    3. Configuring application monitoring
      1.  
        Configuring the VCS cluster
      2.  
        Configuring the application
    4.  
      Modifying the ESXDetails attribute
  3. Administering application monitoring
    1.  
      About the various interfaces available for performing application monitoring tasks
    2. Administering application monitoring using the Veritas High Availability tab
      1. Understanding the Veritas High Availability tab work area
        1.  
          To view the status of configured applications
      2.  
        To configure or unconfigure application monitoring
      3.  
        To start or stop applications
      4.  
        To switch an application to another system
      5.  
        To add or remove a failover system
      6.  
        To suspend or resume application monitoring
      7.  
        To clear Fault state
      8.  
        To resolve a held-up operation
      9.  
        To determine application state
      10.  
        To remove all monitoring configurations
      11.  
        To remove VCS cluster configurations
    3.  
      Administering application monitoring settings
    4. Administering application availability using Veritas High Availability dashboard
      1. Understanding the dashboard work area
        1.  
          Aggregate status bar
        2.  
          ESX cluster/host table
        3.  
          Taskbar
        4.  
          Filters menu
        5.  
          Application table
      2.  
        Monitoring applications across a data center
      3.  
        Monitoring applications across an ESX cluster
      4.  
        Searching for application instances by using filters
      5.  
        Selecting multiple applications for batch operations
      6.  
        Starting an application using the dashboard
      7.  
        Stopping an application by using the dashboard
      8.  
        Entering an application into maintenance mode
      9.  
        Bringing an application out of maintenance mode
      10.  
        Switching an application
      11.  
        Resolving dashboard alerts
  4. Appendix A. Troubleshooting
    1. Troubleshooting application monitoring configuration issues
      1.  
        Veritas High Availability Configuration Wizard displays the "hadiscover is not recognized as an internal or external command" error
      2.  
        Running the 'hastop - all' command detaches virtual disks
      3.  
        Validation may fail when you add a failover system
      4.  
        Adding a failover system may fail if you configure a cluster with communication links over UDP
    2. Troubleshooting Veritas High Availability view issues
      1.  
        Veritas High Availability tab not visible from a cluster node
      2.  
        Veritas High Availability tab does not display the application monitoring status
      3.  
        Veritas High Availabilitytab may freeze due to special characters in application display name
      4.  
        Veritas High Availability view may fail to load or refresh
      5.  
        Operating system commands to unmount resource may fail

How does the Veritas High Availability solution integrate with vSphere Web Client

The Veritas High Availability solution integrates with a vSphere Web Client to enable you to perform the application monitoring tasks from within a vSphere Web Client interface.

The following diagram illustrates how the Veritas High Availability solution integrates with vSphere Web Client:

The Veritas High Availability solution provides a Veritas HA Plug-in for integration with VMware vSphere Web Client, and adds the following interfaces for performing the application monitoring tasks:

  • Veritas High Availability tab: From this view you configure application monitoring and then monitor and control the configured application on that virtual machine. After configuring application monitoring, the Veritas High Availability tab view displays the state of the configured application.

  • Veritas High Availability dashboard: This view appears at an ESX cluster or datacenter-level. The Veritas High Availability Dashboard displays aggregate health information for all the monitored applications running in that cluster or datacenter.

These interfaces appear in the Monitor tab of vSphere Web Client, after you install the Veritas HA Plug-in for vSphere Web Client add-on for the Veritas InfoScale Operations Manager (VIOM) Management Server. You must install this add-on on a VIOM Management Server and register the Veritas HA Plug-in for vSphere Web Client with all the required vCenter servers.

If you add the VCS guests (virtual machines) to Veritas InfoScale Operations Manager Management Server as managed hosts, the management server discovers the health status of the applications monitored by VCS. The Management Server relays this information to the vCenter Server and displays the information in the Veritas High Availability tab and the dashboard.