failover without any pool configured to failover

[Glenn Satchell]

Why not create a pool within an existing subnet but don't define a range,
so no hosts can get assigned?

subnet 192.168.8.64 netmask 255.255.255.192 {
       option domain-name-servers 192.168.1.3;
       option routers 192.168.8.126;
       pool {
#           failover peer "failover-partner";

            range 192.168.8.65 192.168.8.121;
            allow unknown clients;
            }
       pool {
            failover peer "failover-partner";
            }
}

regards,
-glenn

On Fri, December 18, 2015 1:57 am, Munroe Sollog wrote:
> We are looking to deploy the isc-dhcp-server failover feature, however
> we'd like to deploy it in a
> staged approach.  Is it possible to configure the failover pairs but *not*
> configure any pools to
> failover?  When I try I get:
>
> Dec 17 09:56:05 humpty isc-dhcp-server[14554]: Stopping ISC DHCP server:
> dhcpd.
> Dec 17 09:56:05 humpty dhcpd: Internet Systems Consortium DHCP Server
> 4.3.1
> Dec 17 09:56:05 humpty dhcpd: Copyright 2004-2014 Internet Systems
> Consortium.
> Dec 17 09:56:05 humpty dhcpd: All rights reserved.
> Dec 17 09:56:05 humpty dhcpd: For info, please visit
> https://www.isc.org/software/dhcp/
> Dec 17 09:56:05 humpty dhcpd: Internet Systems Consortium DHCP Server
> 4.3.1
> Dec 17 09:56:05 humpty dhcpd: Copyright 2004-2014 Internet Systems
> Consortium.
> Dec 17 09:56:05 humpty dhcpd: All rights reserved.
> Dec 17 09:56:05 humpty dhcpd: For info, please visit
> https://www.isc.org/software/dhcp/
> Dec 17 09:56:05 humpty dhcpd: Wrote 29 leases to leases file.
> Dec 17 09:56:05 humpty dhcpd: failover peer failover-partner: I move from
> normal to startup
> Dec 17 09:56:05 humpty dhcpd: failover peer declaration with no referring
> pools.
> Dec 17 09:56:05 humpty dhcpd: In order to use failover, you MUST refer to
> your main failover declaration
> Dec 17 09:56:05 humpty dhcpd: in each pool declaration.   You MUST NOT use
> range declarations outside
> Dec 17 09:56:05 humpty dhcpd: of pool declarations.
> Dec 17 09:56:05 humpty dhcpd:
> Dec 17 09:56:05 humpty dhcpd: If you think you have received this message
> due to a bug rather
> Dec 17 09:56:05 humpty dhcpd: than a configuration issue please read the
> section on submitting
> Dec 17 09:56:05 humpty dhcpd: bugs on either our web page at www.isc.org
> or in the README file
> Dec 17 09:56:05 humpty dhcpd: before submitting a bug.  These pages
> explain the proper
> Dec 17 09:56:05 humpty dhcpd: process and the information we find helpful
> for debugging..
> Dec 17 09:56:05 humpty dhcpd:
> Dec 17 09:56:05 humpty dhcpd: exiting.
> Dec 17 09:56:07 humpty isc-dhcp-server[14561]: Starting ISC DHCP server:
> dhcpdcheck syslog for
> diagnostics. ... failed!
> Dec 17 09:56:07 humpty isc-dhcp-server[14561]: failed!
> Dec 17 09:56:07 humpty systemd[1]: isc-dhcp-server.service: control
> process exited, code=exited status=1
> Dec 17 09:56:07 humpty systemd[1]: Failed to start LSB: DHCP server.
> Dec 17 09:56:07 humpty systemd[1]: Unit isc-dhcp-server.service entered
> failed state.
>
>
> My config looks like:
>
>
> failover peer "failover-partner" {
>         primary;
> ##MUST BE IP ADDRESSES
>
>         address 192.168.8.1;
>         port 519;
>         peer address 192.168.8.2;
>         peer port 520;
>         max-response-delay 60;
>         max-unacked-updates 10;
>         mclt 3600;
>         split 128;
>         load balance max seconds 3;
>     }
>
> subnet 192.168.8.0 netmask 255.255.255.192 {
> }
>
> subnet 192.168.8.64 netmask 255.255.255.192 {
>        option domain-name-servers 192.168.1.3;
>        option routers 192.168.8.126;
>        pool {
> #           failover peer "failover-partner";
>
>             range 192.168.8.65 192.168.8.121;
>             allow unknown clients;
>             }
> }
>
>
> --
> Munroe Sollog
> LTS - Network Analyst
> x85002
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>