Veritas High Availability 7.3.1 Solution Guide for VMware - Linux
- Introducing the Veritas High Availability solution for VMware
- How the Veritas High Availability solution works in a VMware environment
- How the Veritas HA Plug-in for vSphere Web Client works with VCS
- How the VMwareDisks agent communicates with the vCenter Server instead of the ESX/ESXi host
- Getting started with vCenter-integrated Veritas High Availability solution
- Getting started with the VIOM-integrated Veritas High Availability solution
- Understanding Veritas High Availability terminology
- Supported VMware versions
- Important release information
- How the Veritas High Availability solution works in a VMware environment
- Deploying the Veritas High Availability solution
- Administering application availability from the vSphere Client
- Accessing the Veritas High Availability view
- Administering application monitoring from the Veritas High Availability view
- Understanding the Veritas High Availability view
- Configuring a cluster by using the VCS cluster configuration wizard
- To configure or unconfigure application monitoring
- Adding a system to a VCS cluster
- 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
- Accessing the dashboard
- 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. Roles and privileges
- Appendix B. Troubleshooting
- Agent logging on virtual machine
- Troubleshooting wizard-based 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 issues with the Veritas High Availability view
- Veritas high availability view is not visible from a cluster system
- Veritas High Availability view does not display the application monitoring status
- Veritas High Availability view may freeze due to special characters in application display name
- If the Console host abruptly restarts, the high availability view may disappear
- Veritas high availability view may fail to load or refresh
- Operating system commands to unmount resource may fail
Veritas high availability view may fail to load or refresh
The Veritas High Availability view displays health information of monitored applications in a VCS cluster. The tab display may fail to load. It may alternatively fail to refresh itself after the default interval of 60 seconds. (2932028)
Workaround:
Restarting the xprtld service may resolve the issue.
To restart the xprtld service
- Stop the xprtld service:
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl stop xprtld
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/xprtld stop
- Ensure that xprtld is stopped:
# ps -ef | grep xprtld
If the services is not stopped, terminate the process:
# kill -9 xprtld_pid_value
Where pid is the process ID of the xprtld process.
- Start xprtld service:
For RHEL 7, SLES 12, and supported RHEL distributions:
# systemctl stop xprtld
For earlier versions of RHEL, SLES, and supported RHEL distributions:
# /etc/init.d/xprtld start