User Guide

  • 2021.6.0
  • 07/20/2022
  • Public Content


Intel® Cluster Checker discovery command analyzes the data collected to find out the devices installed on the system. Use this command as a precursor step wherein an output file with the provider configurations will be generated which can later be used for the execution of the main Cluster Checker run.
Currently, the scope of the discovery feature is limited to fabric detection only. The feature will continue to expand on various other types of devices.

Using the Discovery Subcommand

The typical example to invoke discovery is:
clck discovery -f nodefile <options>
The example above collects and analyzes the data to determine the devices present in the system. It then generates a provider configuration file and a template framework definition file (which includes the generated provider configuration file) for further use. All the files generated are located in the current working directory. Default files generated are node_capability_discovery_config.xml & node_capability_discovery.xml
Once the discovery command is complete, use the template framework definition generated in the main execution of the Cluster Checker run. Example:
clck -f nodefile -F health_user -F node_capability_discovery.xml <options>

The Discovery Provider Configuration File

The provider configuration file looks like below:
Example provider configuration file (node_capability_discovery_config.xml)
<?xml version="1.0" encoding="UTF-8"?> <collector><provider> . . . <imb_pingpong> <!--<fabrics>ofi<fabrics>--> <interface>eno1</interface> <!--<mpi_pin><mpi_pin>--> <ofi_provider>tcp</ofi_provider> <!--<options><options>--> <!--<tcp_netmask><tcp_netmask>--> <timeout scale="logarithmic">10</timeout> </imb_pingpong> . . . </provider></collector>
Example template framework definition file (node_capability_discovery.xml)
<?xml version="1.0" encoding="UTF-8"?> <configuration><framework_definition name="node_capability_discovery.xml"> <providers config_path="$HOME/clck" config_file="node_capability_discovery_config.xml"/> </framework_definition></configuration>
The provider configuration will be generated for all the benchmark providers using fabrics including but not limited to Intel® MPI Benchmarks, etc. For all the other providers, the configuration options will be generated with the default values.
For more information about the provider configuration options, see the Data Providers section in the Reference.

Product and Performance Information


Performance varies by use, configuration and other factors. Learn more at