Logo
Graphcore Command Line Tools
Version: 1.0.45
  • 1. Introduction
  • 2. gc-docker
  • 3. gc-exchangetest
  • 4. gc-hosttraffictest
  • 5. gc-info
  • 6. gc-inventory
  • 7. gc-iputraffictest
  • 8. gc-links
    • 8.1. Usage
      • 8.1.1. Allowed options
  • 9. gc-memorytest
  • 10. gc-monitor
  • 11. gc-powertest
  • 12. gc-reset
  • 13. Device IDs and Channel Map
  • 14. Trademarks & copyright
Graphcore Command Line Tools

8. gc-links

This tool displays the status and connectivity of each of the IPU-Links that connect the C2 IPU-Processor cards together. It does this by ‘training’ the links with some data, and then checking that the data can be retrieved across all the links. To use it, run:

gc-links -j

The output will look similar to the following example:

{
  "ipu to ipu": {
      "from pcie id": "5",
      "to pcie id": "7",
      "channel": {
          "from": "NLC_E_2A",
          "to": "NLC_E_3A",
          "status": "passed",
          "gen": "4",
          "lanes": "8"
      },
      "channel": {
          "from": "NLC_E_2B",
          "to": "NLC_E_3B",
          "status": "passed",
          "gen": "4",
          "lanes": "8"
      }
  },
  "num ipus": "16",
  "overall result": "passed",
  "training fails": "0"
}

The "status" field shows the training status for each link. The "lanes" field shows the number of lanes being trained, and the "gen" field shows what generation of link is tested.

When gc-links finds that a link fails to train, the output looks like this:

{
  "ipu to ipu": {
    "from pcie id": "7",
    "to pcie id": "6",
    "channel": {
        "from": "NLC_W_1B",
        "to": "NLC_W_1B",
        "status": "passed",
        "gen": "4",
        "lanes": "8"
    },
    "channel": {
        "from": "NLC_W_1C",
        "to": "NLC_W_1C",
        "status": "failed",
        "gen": "0",
        "lanes": "0"
    }
  }
}

This output shows that it failed to train device 7 to device 6, using link NLC_W_1C.

Running gc-inventory will show more info on devices 6 and 7:

Device:
  id: 6
  type: C2
  Firmware Major Version: 1
  Firmware Minor Version: 0
  Firmware Patch Version: 4
  IPU: 1
  IPU version: ipu0
  PCI Id: 0000:43:00.0
  link speed: 8 GT/s
  link width: 8
  physical slot: PCIe Slot 12
  serial number: 0020.0004.018471
Device:
  id: 7
  type: C2
  Firmware Major Version: 1
  Firmware Minor Version: 0
  Firmware Patch Version: 4
  IPU: 1
  IPU version: ipu0
  PCI Id: 0000:44:00.0
  link speed: 8 GT/s
  link width: 8
  physical slot: PCIe Slot 13
  serial number: 0027.0004.018481

You can see, in this example, that there’s an issue with the link between the card in slot 12 and 13.

When training a chassis full of IPUs the tool outputs additional info on IPU-Link failures, for example:

{
  "failures": [
    {
        "cable_id": "IPUL-00"
    },
    {
        "cable_id": "IPUL-24"
    },
    {
        "cable_id": "IPUL-25"
    }
  ]
}

The physical location of these failing cables is shown in IPU-Link channel mapping.

8.1. Usage

8.1.1. Allowed options

-j, --json-output

Emit JSON output

-n ARG, --num-retries ARG

Number of link training retries (default: 3)

-d ID, --device-id ID

Device id (default is largest group)

-i ARG, --num-iterations ARG

Number of times to train each link (default: 1)

-v, --verbose

Verbose output

-p, --phy-summary

Print PHY summary after all training runs

-h, --help

Produce help message

--version

Version number

Previous Next

Revision b5cca43a.