Veritas™ High Availability 8.0.2 Solution Guide for VMware - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (8.0.2)
Platform: Linux
  1. Introducing the Veritas High Availability solution for VMware
    1. How the Veritas High Availability solution works in a VMware environment
      1.  
        How the VMwareDisks agent communicates with the vCenter Server instead of the ESX/ESXi host
      2. Getting started with the VIOM-integrated Veritas High Availability solution
        1.  
          About administering high availability with VOM
      3. Understanding Veritas High Availability terminology
        1.  
          Understanding operation names
      4.  
        Supported VMware versions
      5.  
        Important release information
  2. Deploying the Veritas High Availability solution
    1.  
      Managing storage
    2.  
      Installing the Veritas High Availability guest components
    3.  
      Upgrading Veritas High Availability guest components
  3. Administering application availability
    1.  
      Accessing the Veritas High Availability view
    2. Administering application monitoring from the Veritas High Availability view
      1. Understanding the Veritas High Availability view
        1.  
          To view the status of configured applications
      2.  
        Configuring a cluster by using the VCS cluster configuration wizard
      3.  
        To configure or unconfigure application monitoring
      4.  
        Adding a system to a VCS cluster
      5.  
        To start or stop applications
      6.  
        To switch an application to another system
      7.  
        To add or remove a failover system
      8.  
        To suspend or resume application monitoring
      9.  
        To clear Fault state
      10.  
        To resolve a held-up operation
      11.  
        To determine application state
      12.  
        To remove all monitoring configurations
      13.  
        To remove VCS cluster configurations
    3.  
      Administering application monitoring settings
  4. Appendix A. Roles and privileges
    1.  
      About the roles and privileges assigned in vCenter
    2. Assigning customized privileges to VMwareDisks agent
      1.  
        About assigning privileges to VMwareDisks agent
      2.  
        Creating a role with customized privileges for VMwareDisks agent
      3.  
        Creating an ESX user account
      4.  
        Integrating an ESX user account with Active Directory
      5.  
        Assigning a role to an ESX user account
  5. Appendix B. Troubleshooting
    1.  
      Agent logging on virtual machine
    2. Troubleshooting wizard-based 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
    3. Troubleshooting issues with the Veritas High Availability view
      1.  
        Veritas high availability view is not visible from a cluster system
      2.  
        Veritas High Availability view does not display the application monitoring status
      3.  
        Veritas High Availability view may freeze due to special characters in application display name
      4.  
        If the Console host abruptly restarts, the high availability view may disappear
      5.  
        Veritas high availability view may fail to load or refresh
      6.  
        Operating system commands to unmount resource may fail

If the Console host abruptly restarts, the high availability view may disappear

If the system that hosts the Veritas High Availability Console abruptly restarts, then the registration of the Veritas High Availability plugin with the VMware vCenter Server does not persist.

As a result, the Veritas High Availability vew does not appear on the vSphere Client GUI. (2919549)

Workaround:

Repair the Console installation.