mirror of
https://github.com/xcat2/confluent.git
synced 2024-11-22 09:32:21 +00:00
70 lines
2.6 KiB
Markdown
70 lines
2.6 KiB
Markdown
nodeconfig(8) -- Show or change node configuration
|
|
==================================================
|
|
|
|
## SYNOPSIS
|
|
|
|
`nodeconfig <noderange> [options] [<configuration>..]`
|
|
`nodeconfig <noderange> [options] [<configuration=value>..]`
|
|
|
|
## DESCRIPTION
|
|
|
|
**nodeconfig** manages the configuration of nodes managed by confluent.
|
|
Rather than manipulating the confluent database, this actually modifies the
|
|
running configuration on the node firmware. Calling without '=' will show the
|
|
current value, and '=' will change the value. Network information can be
|
|
given as a node expression, as documented in the man page for nodeattribexpressions(5).
|
|
|
|
Note that when using nodeconfig to submit changes, it will exit when the change
|
|
is accepted, but the endpoint may not have fully processed it. Doing a show
|
|
immediately after doing a set may reflect older information. Also, if changing
|
|
BIOS/UEFI settings, the change may appear in output, but generally won't
|
|
actually be in effect until a reboot.
|
|
|
|
## OPTIONS
|
|
|
|
* `-c`, `--comparedefault`:
|
|
Take the given settings and compare against default value, if available. If
|
|
no configuration values are specified, it will show only those that differ.
|
|
If combined with `-x`, will show all differing values except those indicated
|
|
by `-x`
|
|
|
|
* `-e`, `--extra`:
|
|
Read settings that are generally not needed, but may be slow to retrieve.
|
|
Notably this includes the IMM category of Lenovo systems. The most popular
|
|
IMM settings are available through faster 'bmc' attributes.
|
|
|
|
* `-x`, `--exclude`:
|
|
Rather than listing only the specified configuration parameters, list all
|
|
attributes except for the specified ones
|
|
|
|
* `-d`, `--detail`:
|
|
Provide detailed data as available. This can include help text and valid
|
|
values for a setting.
|
|
|
|
* `-r`, `--restoredefault`:
|
|
Request that the specified component of the targeted nodes will have its
|
|
configuration reset to default. Currently the only component implemented
|
|
is uefi.
|
|
|
|
* `-b`, '--batch':
|
|
Provide arguments as lines of a file, rather than the command line.
|
|
|
|
|
|
## EXAMPLES
|
|
* Showing the current IP configuration of noderange BMC/IMM/XCC:
|
|
`# nodeconfig s3,s4 bmc`
|
|
`s3: bmc.ipv4_address: 172.30.254.193/16`
|
|
`s3: bmc.ipv4_method: DHCP`
|
|
`s3: bmc.ipv4_gateway: 172.30.0.6`
|
|
`s4: bmc.ipv4_address: 172.30.254.192/16`
|
|
`s4: bmc.ipv4_method: DHCP`
|
|
`s4: bmc.ipv4_gateway: 172.30.0.6`
|
|
|
|
* Changing nodes `s3` and `s4` to have the ip addressess 10.1.2.3 and 10.1.2.4 with a 16 bit subnet mask:
|
|
`# nodeconfig s3,s4 bmc.ipv4_address=10.1.2.{n1}/16`
|
|
|
|
## SEE ALSO
|
|
|
|
nodeattribexpressions(5)
|
|
|