(All) opareports is a front end to opareport that provides many of the same options and capabilities. It can also run a report against multiple fabrics or subnets (for example, local host HFI ports). opareports can use an input file to augment the reports using additional details from the topology_input file.
opareports [-t portsfile] [-p ports] [opareport arguments] [-T topology_input]
or
opareports --help
List of local HFI ports used to access fabric for counter clear. Default is first active port. The first HFI in the system is 1. The first port on an HFI is 1.
Uses the format hfi:port, for example:
First active port in system.
Port y within system.
First active port on HFI x.
HFI x, port y.
When run against multiple fabrics, the -F option is applied to all fabrics. See opareport for more information.
The following environment variables are also used by this command:
For simple fabrics, the Intel® Omni-Path Fabric Suite FastFabric Toolset host is connected to a single fabric. By default, the first active port on the FastFabric Toolset host is used to analyze the fabric.
However, in more complex fabrics, the FastFabric Toolset host may be connected to more than one fabric or subnet. In this case, you can specify the ports or HFIs to use with one of the following methods:
If the specified port does not exist or is empty, the first active port on the local system is used. In more complex configurations, you must specify the exact ports to use for all fabrics to be analyzed.
You can specify the topology_input file to be used with one of the following methods:
If the specified file does not exist, no topology_input file is used. Alternately the filename can be specified as NONE to prevent use of an input file.