HP XC System Software Administration Guide Version 3.1

To verify HP XC licensing, enter a command in the following format:
# ovp -v=license
By default, if any part of the verification fails, the ovp command ignores the test failure and continues
with the next test. You can use the --failure_action option to control how the ovp command treats
test failures.
When you run the ovp command as superuser (root), it stores a record of the verification in a log file in
the /hptc_cluster/adm/logs/ovp directory. The file name for log files has the form
ovp_nodename_mmddyyrnn; the mmddyy portion is a date stamp in month, day, year form and rnn
identifies subsequent runs of the ovp command. The file named current_ovp_log in that directory is
a symbolic link to the most recent log file.
See ovp(8) for more information about the ovp command and its options.
Performance Health Tests
Any user can run the ovp command to generate reports on the performance health of the nodes independent
from the other tests described. Use the following format to run a specific performance health test:
ovp [options] [-verify=perf_health/test]
where:
options Specifies additional command-line options for the test. The ovp --help perf_health
command lists the command-line options for each test.
The following options apply to all the tests:
• The --nnodes=n option runs the test on n compute nodes.
NOTE: Use --opts= to pass this option.
• The --nodelist=nodelist option specifies the compute nodes to use.
NOTE: The --nodelist=nodelist option is particularly useful for determining
problematic nodes.
If you use this option and the --nnodes=n option, the --nnodes=n option is ignored.
• The --user=user option enables you to run the test as the specified user. This option
applies only to the superuser (root).
test
Indicates the test to perform. The following tests are available:
cpu
Tests CPU core performance using the Linpack benchmark.
cpu_usage
Tests CPU core usage. All CPU cores should be idle during
the test. This test reports a node if it is using more than 10
percent (by default) of its CPU cores.
The head node is excluded from this test.
memory
Uses the streams benchmark to test memory performance.
memory_usage
Tests memory usage. This test reports a node that uses
more than 25 percent (by default) of its memory.
network_stress
Tests network performance. Check network performance
under stress using the Pallas benchmark's Alltoall,
Allgather, and Allreduce tests. Perform these tests on a
large number of nodes for the most accurate results.
The default value for the number of nodes is 4, which is
the minimum value to use.
The --all_group option enables you to select the node
grouping size.
network_bidirectional
Tests network performance between pairs of nodes using
the Pallas benchmark's Exchange test.
218 Using Diagnostic Tools