From: Thomas Markwalder Date: Thu, 22 Dec 2016 14:24:35 +0000 (-0500) Subject: [5046] Added documentation to the admin guide for set-config X-Git-Tag: trac5030_base~1^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7289e65468262982cf3c1056b1678bb164d366fb;p=thirdparty%2Fkea.git [5046] Added documentation to the admin guide for set-config --- diff --git a/doc/guide/ctrl-channel.xml b/doc/guide/ctrl-channel.xml index 8db374be5f..e92340584f 100644 --- a/doc/guide/ctrl-channel.xml +++ b/doc/guide/ctrl-channel.xml @@ -161,6 +161,65 @@ will be sent to Kea and the responses received from Kea printed to standard outp +
+ set-config + + + The set-config command instructs the server to replace + its current configuration with the new configuration supplied in the + command's arguments. The supplied configuration is expected to be the full + configuration for the target server along with an optional Logger + configuration. While optional, the Logger configuration is highly + recommended as without it the server will revert to its default logging + configuration. The structure of the command is as follows: + + +{ + "command": "set-config", + "arguments": { + "<server>": { + }, + "Logging": { + } + } +} + + + where <server> is the configuration element name for a given server + such as "Dhcp4" or "Dhcp6". For example: + + +{ + "command": "set-config", + "arguments": { + "Dhcp6": { + : + }, + "Logging": { + : + } + } +} + + + If the new configuration proves to be invalid the server will retain + its current configuration. Please note that the new configuration is + retained in memory only. If the server is restarted or a configuration + reload is triggered via a signal, the server will use the configuration + stored in its configuration file. + + The server's response will contain a numeric code, "result" (0 for success, + non-zero on failure), and a string, "text", describing the outcome: + + {"result": 0, "text": "Configuration successful." } + + or + + {"result": 1, "text": "unsupported parameter: BOGUS (<string>:16:26)" } + + +
+
shutdown @@ -182,6 +241,8 @@ will be sent to Kea and the responses received from Kea printed to standard outp
+ + diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index 4c7c3efa4c..9771f3452f 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -3659,17 +3659,30 @@ src/lib/dhcpsrv/cfg_host_operations.cc --> Communication over control channel is conducted using JSON structures. - See the Control Channel section in the Kea Developer's Guide for more details. + See the Control Channel section in the Kea Developer's Guide for more + details. + + + The DHCPv4 server supports the following operational commands: + + leases-reclaim + list-commands + set-config + shutdown + + as described in . In addition, + it supports the following statistics related commands: + + statistic-get + statistic-reset + statistic-remove + statistic-get-all + statistic-reset-all + statistic-remove-all + + as described here . - The DHCPv4 server supports statistic-get, - statistic-reset, statistic-remove, - statistic-get-all, statistic-reset-all - and statistic-remove-all, specified in - . It also supports - list-commands and shutdown, - specified in and - , respectively.
diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml index 8fb04a40d1..3a509f68bb 100644 --- a/doc/guide/dhcp6-srv.xml +++ b/doc/guide/dhcp6-srv.xml @@ -4067,16 +4067,27 @@ If not specified, the default value is: See the Control Channel section in the Kea Developer's Guide for more details. - The DHCPv6 server supports statistic-get, - statistic-reset, statistic-remove, - statistic-get-all, statistic-reset-all - and statistic-remove-all, specified in - . It also supports - list-commands and shutdown, - specified in and - , respectively. -
+ The DHCPv6 server supports the following operational commands: + + leases-reclaim + list-commands + set-config + shutdown + + as described in . In addition, + it supports the following statistics related commands: + + statistic-get + statistic-reset + statistic-remove + statistic-get-all + statistic-reset-all + statistic-remove-all + + as described here . + +
User context in IPv6 pools