clusterctl fabric state

Check whether the fabric ports of a node set are up

Synopsis

Ask the fabric about each node’s port.

A port is up only when its logical link state is Active. A port that is physically linked but still Initialize or Armed has no subnet manager configuration yet and carries no traffic, so it is reported down, with both states shown. A port the fabric does not answer for is reported as such. Any port that is not up makes the command fail.

The ports are asked about in one session to the fabric host, four at a time, and listed in the order of the nodes whatever order the answers come in.

When the fabric host stops before it has answered for every port, at the command’s timeout or because the connection dropped, the ports it answered for are shown and the others read no answer, and the command fails with the reason it stopped. It only reads, so –dry-run asks the fabric too.

clusterctl fabric state -n exe[1-10]

clusterctl fabric state [NODESET] [flags]

Options

  -h, --help   help for state

Options inherited from parent commands

      --config strings        configuration file or directory to read, repeatable (default: CLUSTERCTL_CONFIG or the search path)
      --context string        context to act on (default: the current one)
      --dry-run               report what would be done and change nothing
      --fanout int            how many hosts to work on at once, at least 1; caps the service processors and the names asked at once too, which fanout.max and CLUSTERCTL_FANOUT do not (default: from the configuration)
      --force                 allow protected hosts, and nodes the inventory does not know, to be touched
  -n, --nodes stringArray     node set to act on, for example 'exe[1-10],@rack:R02' (default: CLUSTERCTL_NODES)
  -o, --output string         output format: table, wide, json, yaml, nodeset, name, jq= (default "table")
      --progress string       how to show the progress of a command on standard error: auto, tty, counter, plain, none (default: CLUSTERCTL_PROGRESS, else auto, a live tree when standard error is a terminal; plain writes lines for a log)
      --progress-log string   append the progress events of a command to this file, one JSON object per line, created readable by you alone (default: CLUSTERCTL_PROGRESS_LOG; an empty one writes none)
      --set stringArray       override one configuration value as PATH=VALUE, repeatable
  -y, --yes                   answer the confirmation prompts with yes

clusterctl fabric state