From 9730bc3c7aed748868a214cc345986d395bcc845 Mon Sep 17 00:00:00 2001 From: Marcin Siodelski Date: Tue, 17 Oct 2017 14:05:44 +0200 Subject: [PATCH] [5381] Explain why use explciit subnet identifiers with host reservations. --- doc/guide/dhcp4-srv.xml | 3 ++- doc/guide/dhcp6-srv.xml | 4 +++- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml index 14a21c66a5..11e525b5e1 100644 --- a/doc/guide/dhcp4-srv.xml +++ b/doc/guide/dhcp4-srv.xml @@ -3829,7 +3829,8 @@ subnets belonging to the same shared network. While not strictly mandatory, it is strongly recommended to use explicit "id" values for subnets if you plan to use database storage for host reservations. If ID is not specified, the values for it be autogenerated, -i.e. it will assign increasing integer values starting from 1. +i.e. it will assign increasing integer values starting from 1. Thus, the +autogenerated IDs are not stable across configuration changes. diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml index 101e985a07..572096a06b 100644 --- a/doc/guide/dhcp6-srv.xml +++ b/doc/guide/dhcp6-srv.xml @@ -3398,7 +3398,9 @@ subnets belonging to the same shared network. While not strictly mandatory, it is strongly recommended to use explicit "id" values for subnets if you plan to use database storage for host reservations. If ID is not specified, the values for it be autogenerated, -i.e. it will assign increasing integer values starting from 1. +i.e. it will assign increasing integer values starting from 1. Thus, the +autogenerated IDs are not stable across configuration changes. + -- 2.47.2