Cluster Server 8.0.1 Configuration Guide for Custom Applications - Windows
- Introducing the Veritas High Availability solution for VMware
- Configuring application monitoring using the Veritas High Availability solution
- Administering application monitoring
- About the various interfaces available for performing application monitoring tasks
- Administering application monitoring using the Veritas High Availability tab
- Understanding the Veritas High Availability tab work area
- To configure or unconfigure application monitoring
- To start or stop applications
- To switch an application to another system
- To add or remove a failover system
- To suspend or resume application monitoring
- To clear Fault state
- To resolve a held-up operation
- To determine application state
- To remove all monitoring configurations
- To remove VCS cluster configurations
- Administering application monitoring settings
- Administering application availability using Veritas High Availability dashboard
- Understanding the dashboard work area
- Monitoring applications across a data center
- Monitoring applications across an ESX cluster
- Searching for application instances by using filters
- Selecting multiple applications for batch operations
- Starting an application using the dashboard
- Stopping an application by using the dashboard
- Entering an application into maintenance mode
- Bringing an application out of maintenance mode
- Switching an application
- Resolving dashboard alerts
- Appendix A. Troubleshooting
- Troubleshooting application monitoring configuration issues
- Veritas High Availability Configuration Wizard displays the "hadiscover is not recognized as an internal or external command" error
- Running the 'hastop - all' command detaches virtual disks
- Validation may fail when you add a failover system
- Adding a failover system may fail if you configure a cluster with communication links over UDP
- Troubleshooting Veritas High Availability view issues
- Veritas High Availability tab not visible from a cluster node
- Veritas High Availability tab does not display the application monitoring status
- Veritas High Availabilitytab may freeze due to special characters in application display name
- Veritas High Availability view may fail to load or refresh
- Operating system commands to unmount resource may fail
- Troubleshooting application monitoring configuration issues
Understanding the Veritas High Availability tab work area
The Veritas High Availability tab displays the consolidated health information for applications running in a Cluster Server (VCS) cluster. The cluster may include one or more systems.
When you click a system in the inventory view of the VMware vSphere Client, the Veritas High Availability tab displays application information for the entire VCS cluster, not just the selected system.
Note:
If you do not configure any application for monitoring in the VCS cluster, then the Veritas High Availability tab displays only the following link: .
The Veritas High Availability tab uses icons, color coding, dependency graphs, and tool tips to report the detailed status of an application.
The Veritas High Availability tab displays complex applications in terms of multiple interdependent instances of that application. These interdependent instances represent component groups of the application. The component groups are also known as "service groups" in VCS terminology.
Each service group in turn includes several critical components of the application. The components are known as "resources" in VCS terminology.
The following figure displays two instances of an application running in the Veritas High Availability tab:
Title bar | Actions menu |
Aggregate status bar | Application dependency graph |
Application table | Application-specific task menu |
Component dependency graph |
The Veritas High Availability tab graphic user interface (GUI) includes the following components:
Title bar: Displays the name of the VCS cluster, the Actions menu, the Refresh icon, the Alert icon. Note that the Alert icon appears only if the Veritas High Availability view fails to display a virtual machine, or displays stale data
Actions menu: Includes a drop-down list of operations that you can perform with effect across the cluster. These include: Configuring an application for high availability; Unconfigure all applications; and Unconfigure VCS cluster.
Aggregate status bar: Displays a summary of applications running in the cluster. This summary includes the total number of applications, and the state-wise breakdown of the applications in terms of the Online, Offline, Partial, and Faulted states.
Application dependency graph: Illustrates the order in which the applications or application instances, must start or stop.
If an application must start first for another application to successfully start, the former application appears at a lower level. A line connects the two applications to indicate the dependency. If no such dependency exists, all applications appear in a single horizontal line.
Application table: Displays a list of all applications that are configured in the VCS cluster that is associated with the system you selected in the inventory view.
Each application is listed in a separate row. Each row displays the systems where the application is configured for monitoring.
The title bar of each row displays the following entities to identify the application or the application instance (service group):
Display name of the application (for example, Payroll application)
Type of application (for example, Custom)
Service group name
Application-specific task menu: Appears in each application-specific row of the application table. The menu includes application-specific tasks such as Start, Stop, Switch, and a drop-down list of more tasks. The More drop-down list includes tasks such as Add a failover system, and Remove a failover system.
Component dependency graph: Illustrates the order in which application components (resources) must start or stop for the related application or application instance to respectively start or stop. The component dependency graph by default does not appear in the application table. To view the component dependency graph for an application, you must click a system on which the application is running.
The track pad, at the right-bottom corner helps you navigate through complex component dependency graphs.
If you do not want to view the component dependency graph, in the top left corner of the application row, click .