clusterctl dhcp hosts
clusterctl dhcp hosts
clusterctl dhcp hosts
Show the DHCP entries of a node set
Synopsis
Show what the DHCP server hands each node: its address, hardware addresses, client identifier and boot file. A node with several interfaces has one row per declaration.
The MATCH column says how a declaration was found. “name” is the declaration named after the node or its fully qualified name, and the only one a boot address is taken from. “interface” is one named after the node followed by - or _, such as its BMC or a second port. “comment” is one whose comment names the node; it is shown to help find a misnamed declaration, and a node that has only those counts as missing.
clusterctl dhcp hosts -n exe[1-4] clusterctl dhcp hosts -n exe0001 -o yaml
clusterctl dhcp hosts [NODESET] [flags]Options
-h, --help help for hostsOptions 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 yesSEE ALSO
- clusterctl dhcp - Read what the DHCP server knows about the nodes