eG Monitoring
 

Measures reported by CtxCdFMachTest

Using this test, administrator can figure out how many machines of which type are currently in a state of failure. The names of these machines and the precise failure state they are in presently can also be ascertained.

Outputs of the test :One set of results for each delivery group configured for the site.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Failed_to_start Indicates the number of machines in this delivery group that failed to start. Number A high value for these measures is a cause for concern. Use the detailed diagnosis of each of these measures to know which machines failed to start and which ones are stuck on boot.

A machine may fail to start or get stuck on boot owing to any of the following reasons:

Cause Description
Hypervisor Reported Failure The hypervisor reported an error
Agent Shutdown The VDA experienced a graceful shutdown
Agent Suspended The VDA is in hibernation or sleep mode.
Power Off The VDA did not shut down gracefully.


To know what action to take against each of the reasons discussed above, use the table below:

Cause Action
Hypervisor Reported Failure Escalate to hypervisor support team to review hypervisor settings
Agent Shutdown Power on the VDA if it should not be off based on existing power management policies. Review any errors in the event logs.
Agent Suspended

  • Take the VDA out of hibernation mode if it should be active.

  • Consider disabling hibernation for XenApp/XenDesktop VDA’s via power settings.
Power Off

  • If the VDA is supposed to be powered on, attempt to start the VDA within Studio and validate it boots up and registers correctly. Troubleshoot any boot or registration issues.

  • Review the event logs on the VDA once it is back up to help determine the root cause of the shutdown.

  • Review the hypervisor activity logs for information related to the VDA machine.
Stuck_on_boot Indicates the number of machines that are stuck on boot. Number
Unregistered Indicates the number of machines in this delivery group that are not registered with the controller. Number A high value for this measure is a cause for concern. In such situations, refer to Troubleshooting Unregistered Machines to know the probable causes for this anomaly and tips for troubleshooting it.

Use the detailed diagnosis of this measure to identify the unregistered machines.
Maximum_load Indicates the number of machines in this delivery group that have violated their maximum load limit. Number This measure applies only to Server OS Machines.

Ideally, the value of this measure should be low. If this measure reports a high value, then use the detailed diagnosis of this measure to identify the loaded machines.

To know what could have caused this problem condition, use the table below:

Cause Description
Hypervisor Reported Failure The hypervisor reported an error
Send settings failure The Broker failed to send settings and configuration data to the VDA. As part of the hard registration process, the Broker gathers and sends settings and configurations to the VDA. If the Broker is able to gather the data, but is unable to send it, hard registration fails and this failure reason results.
Session Prepare Failure The Broker failed to notify the VDA to prepare to host a session. When a user requests a connection to a VDA and the VDA is hard registered, the broker notifies the VDA to prepare to be contacted by a receiver instance. If the call fails, the VDA is forcibly deregistered, resulting in this failure.
Session Audit Failure The broker failed to complete an audit of the sessions that are running on the VDA.
Recently_failed_to_start Indicates the number of machines that failed to start during the last measurement period. Number Use the detailed diagnosis of this measure to identify the machines that failed to start in the recent past. For the reasons for this failure and how to fix it, refer to the Interpretation for the Machines that failed to start measure.
Recently_stuck_on_boot Indicates the number of machines that stuck on boot during the last measurement period. Number Use the detailed diagnosis of this measure to identify the machines that stuck on boot in the recent past. For the reasons for this failure and how to fix it, refer to the Interpretation for the Machines stuck on boot measure.
Recently_unregistered Indicates the number of machines that were not registered with the controller during the last measurement period. Number Use the detailed diagnosis of this measure to identify the machines that were not registered with the controller in the recent past. For the reasons for this failure and how to fix it, refer to Troubleshooting Unregistered Machines.
Recently_maximum_load Indicates the number of machines that violated their maximum load limit during the last measurement period. Number Use the detailed diagnosis of this measure to identify the loaded machines in the recent past.