Skip to main content

Cornelis Technical Documentation

Name

opafabricinfo — Provides a brief summary of the components in the fabric, using the first active port on the given local host to perform its analysis.

Syntax

opafabricinfo [-t portsfile] [-p ports]

Description

opafabricinfo can be very useful as a quick assessment of the fabric state. It can be run against a known good fabric to identify its components and then later run to see if anything has changed about the fabric configuration or state.

opafabricinfo can be used to:

  • Manage more than one fabric (subnet).

  • Perform analysis against the first active port on the system only. It takes no options and uses no environment variables.

For more extensive fabric analysis, use opareport, opareports, and opatop.

Options

--help

Produces full help text.

-t portsfile

Specifies the file with list of local SuperNIC ports used to access fabric(s) for analysis. Default is /etc/opa/ports file.

-p ports

Specifies the list of local SuperNIC ports used to access fabric(s) for analysis. Default is the first active port. Specified as HFI:port as follows:

Note

The first port on a SuperNIC is 1.

0:0

First active port in the system.

0:y

Port y within the system.

x:0

First active port on SuperNIC x.

x:y

SuperNIC x, port y.

Examples

opafabricinfo
opafabricinfo -p '1:1 1:2 2:1 2:2'

Environment Variables

The following environment variables are also used by this command:

PORTS

List of ports, used in absence of -t and -p.

PORTS_FILE

File containing list of ports, used in absence of -t and -p.

For simple fabrics, the 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 SuperNICs to use with one of the following methods:

  • On the command line using the -p option.

  • In a file specified using the -t option.

  • Through the environment variables PORTS or PORTS_FILE.

  • Using the ports_file configuration option in opafastfabric.conf.

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.

Notes - Output Definitions

SM

Each subnet manager (SM) running in the fabric is listed along with its node name, port GUID, and present SM state (Primary, Secondary, etc.).

Note

The Fabric Manager is the subnet manager in Omni-Path.

Number of HFIs

Number of unique SuperNICs in the fabric. An FI with two connected ports is counted as a single FI.

Note

Fabric Interfaces include SuperNICs in servers as well as I/O Modules, Native Storage, etc.

Number of Switches

Number of connected switches in the fabric.

Number of Links

Number of links in the fabric. Note that a large switch may have internal links.

Number of HFI Links

Number of SuperNIC links (Internal and External) in the fabric.

Number of ISLs

Number of Interswitch Links (Internal and External) in the fabric.

Number of Degraded Links

Number of degraded links (HSI and ISL) in the fabric.

Number of Omitted Links

Number of omitted links (HSI and ISL) in the fabric.