All LLT links fail simultaneously in a two-mode cluster with disk-based fencing configured. Node0 won the race for the coordinator disks, and Node1 panics and restarts as a result of losing the race. Node1 is now unable to join Node0 to form a cluster.
What happens if the administrator forces GAB to seed on Node1?
Consider the following service group configuration from main.cf
Both groups are online on server1, and the administrator executes the following command.
What is the result?
An administrator is bringing a service group online. One of the resources is remaining offline, and is shown in ‘waiting to go online’ state.
Which command should the administrator run to stop Veritas Cluster Server from attempting to bring the resource online to troubleshoot the issue?
Which behavior should an administrator expect when performing the Veritas InfoScale Availability online upgrade process using the installer?
Which action should an administrator perform to ensure the coordination point (CP) service is highly available when adding a CP server into a Veritas Cluster Server environment?
The hastatus command shows a service group in the AutoDisabled state, and Veritas Cluster Server is unsuccessful in bringing the service group online automatically.
Which command can the administrator use to reset the AutoDisabled attribute?
What are two effects of a failed resource in the service group configuration below? (Choose two.)
Consider the following resource dependency tree.
What is the correct order for Infoscale Availability to take the service group offline?