the address ranges that include SFLQ pools. Issuing the command will cause
the lease back end to discard and then rebuild the free lease data for the
given pool. Only a pool that exactly matches the start and end adddress
-given will rebuilt.
+given will be rebuilt.
-An example :isccmd:`sflq-pool4-rebuild` command for rebuiding an IPv4 SFLQ
+An example :isccmd:`sflq-pool4-rebuild` command for rebuilding an IPv4 SFLQ
Pool is shown below:
::
{
- "command": "sflq-pool4-create",
+ "command": "sflq-pool4-rebuild",
"arguments": {
"start-address": "192.0.2.0",
"end-address": "192.0.2.255"
::
{
- "command": "sflq-pool6-create",
+ "command": "sflq-pool6-rebuild",
"arguments": {
"start-address": "2001:db8:1::",
"end-address": "2001:db8:1::FFFF"
Deleting a pool when there are overlapping pools can produce holes in the
free lease data where the overlaps occur. If the overlapping pools are to
-remain in use, the ``sflq-poolX-create`` commands should be used to rebuild the
+remain in use, the ``sflq-poolX-rebuild`` commands should be used to rebuild the
free lease data for the remaining pools.
Alternatively, all of the overlapping pools can be deleted and the next
"SFLQ_POOL6_GET_BY_RANGE_FAILED", "sflq-pool6-get-by-range command failed, (parameters: %1, reason: %2)",
"SFLQ_POOL6_GET_BY_SUBNET", "sflq-pool6-get-by-subnet command succeeded, (parameters: %1) pools found: %2",
"SFLQ_POOL6_GET_BY_SUBNET_FAILED", "sflq-pool6-get-by-subnet command failed, (parameters: %1, reason: %2)",
- "SFLQ_POOL6_REBUILD", "sflq-pool6-rebuild command succeeded, (parameters: %1) pools rebuilt: %2",
+ "SFLQ_POOL6_REBUILD", "sflq-pool4-rebuild command succeeded, (parameters: %1) pools rebuilt: %2",
"SFLQ_POOL6_REBUILD_FAILED", "sflq-pool6-rebuild command failed, (parameters: %1, reason: %2)",
NULL
};
% SFLQ_POOL4_REBUILD sflq-pool4-rebuild command succeeded, (parameters: %1) pools rebuilt: %2
Logged at debug log level 20.
-The sflq-pool4-rebuild command was successful.
+The sflq-pool4-rebuild command was successful. It prints the command arguments
+along with the number of pools rebuilt.
% SFLQ_POOL4_REBUILD_FAILED sflq-pool4-rebuild command failed, (parameters: %1, reason: %2)
The sflq-pool4-rebuild command has failed. Both the reason as well as the
The sflq-pool4-del command has failed. Both the reason as well as the
parameters passed are logged.
-% SFLQ_POOL6_REBUILD sflq-pool6-rebuild command succeeded, (parameters: %1) pools rebuilt: %2
+% SFLQ_POOL6_REBUILD sflq-pool4-rebuild command succeeded, (parameters: %1) pools rebuilt: %2
Logged at debug log level 20.
-The sflq-pool6-rebuild command was successful.
+The sflq-pool6-rebuild command was successful. It prints the command arguments
+along with the number of pools rebuilt.
% SFLQ_POOL6_REBUILD_FAILED sflq-pool6-rebuild command failed, (parameters: %1, reason: %2)
The sflq-pool6-rebuild command has failed. Both the reason as well as the
/// @return an uint32_t value
/// @throw isc::dhcp::DhcpConfigError when it is not an uint32_t
uint32_t getUint32(isc::data::ConstElementPtr scope,
- const std::string& name) {
+ const std::string& name) {
return (getIntType<uint32_t>(scope, name));
}