failover peer declaration with no referring pools.

[Glenn Satchell]

No need to copy the leases file at all. With failover, it will request a copy of 
the leases file from the peer. The lease file you copied over after starting 
would get overwritten anyway, so no harm done.

regards,
-glenn

>From: "Defryn, Guy" <G.P.Defryn at massey.ac.nz>
>To: "dhcp-users at isc.org" <dhcp-users at isc.org>
>Date: Wed, 19 Nov 2008 22:25:04 +1300
>Subject: RE: failover peer declaration with no referring pools.
>
>Hi,
>
>It seems like I just managed it to go. Looks like there was a problem with 
using the original leases file.
>I created an empty leases file and dhcpd started fine. Afterwards I stopped 
dhcpd, copied over original
>leases file and restarted without any issues.
>Not sure if this is the correct procedure but it seems to work now.
>Will get back to you if I have more problems
>
>cheers.
>
>
>
>
>
>Guy Defryn
>
>Infrastructure Development Engineer
>Information Technology Services
>Tennant Drive
>Palmerston North
>
>06-3505799 ext 2087
>________________________________________
>From: Glenn Satchell [Glenn.Satchell at uniq.com.au]
>Sent: Wednesday, 19 November 2008 10:18 p.m.
>To: Defryn, Guy
>Subject: Re: failover peer declaration with no referring pools.
>
>Are you using the same version of dhcp on both servers?
>
>Can you please post your dhcpd.conf, or at least a representative
>sample from it? We would need to see global declarations and, say, a
>couple of subnets if you have lots.
>
>regards,
>-glenn
>
>>From: "Defryn, Guy" <G.P.Defryn at massey.ac.nz>
>>To: "dhcp-users at isc.org" <dhcp-users at isc.org>
>>
>>Hi guys,
>>
>>Need some urgent help here.
>>
>>I am creating a new dhcp server. I copied over leases file from old one to new
>one
>>and stopped the server. My network and host file are in place too.
>>I updated the new server with the same IP address and hostname as the old
>server had.
>>My configuration file is still the same. When I start dhcp though I run into
>some problems
>>
>>Any ideas??
>>
>>cheers
>>
>>Log entry
>>
>>Nov 19 20:41:53 tur-net2 dhcpd: Internet Systems Consortium DHCP Server V3.1.0
>>Nov 19 20:41:53 tur-net2 dhcpd: Copyright 2004-2007 Internet Systems
>Consortium.
>>Nov 19 20:41:53 tur-net2 dhcpd: All rights reserved.
>>Nov 19 20:41:53 tur-net2 dhcpd: For info, please visit
>http://www.isc.org/sw/dhcp/
>>Nov 19 20:41:53 tur-net2 dhcpd: Internet Systems Consortium DHCP Server V3.1.0
>>Nov 19 20:41:53 tur-net2 dhcpd: Copyright 2004-2007 Internet Systems
>Consortium.
>>Nov 19 20:41:53 tur-net2 dhcpd: All rights reserved.
>>Nov 19 20:41:53 tur-net2 dhcpd: For info, please visit
>http://www.isc.org/sw/dhcp/
>>Nov 19 20:41:54 tur-net2 dhcpd: Wrote 0 class decls to leases file.
>>Nov 19 20:41:54 tur-net2 dhcpd: Wrote 0 deleted host decls to leases file.
>>Nov 19 20:41:54 tur-net2 dhcpd: Wrote 0 new dynamic host decls to leases file.
>>Nov 19 20:41:54 tur-net2 dhcpd: Wrote 13551 leases to leases file.
>>Nov 19 20:41:54 tur-net2 dhcpd: Listening on
>LPF/eth0/00:50:56:97:3a:bd/130.123.128/23
>>Nov 19 20:41:54 tur-net2 dhcpd: Sending on
>LPF/eth0/00:50:56:97:3a:bd/130.123.128/23
>>Nov 19 20:41:54 tur-net2 dhcpd: Sending on   Socket/fallback/fallback-net
>>Nov 19 20:41:54 tur-net2 dhcpd: failover peer wel-dhcp-failover: I move from
>communications-interrupted to startup
>>Nov 19 20:41:54 tur-net2 dhcpd: failover peer declaration with no referring
>pools.
>>Nov 19 20:41:54 tur-net2 dhcpd: In order to use failover, you MUST refer to
>your main failover declaration
>>Nov 19 20:41:54 tur-net2 dhcpd: in each pool declaration.   You MUST NOT use
>range declarations outside
>>Nov 19 20:41:54 tur-net2 dhcpd: of pool declarations.
>>Nov 19 20:41:54 tur-net2 dhcpd:
>>Nov 19 20:41:54 tur-net2 dhcpd: If you did not get this software from
>ftp.isc.org, please
>>Nov 19 20:41:54 tur-net2 dhcpd: get the latest from ftp.isc.org and install
>that before
>>Nov 19 20:41:54 tur-net2 dhcpd: requesting help.
>>Nov 19 20:41:54 tur-net2 dhcpd:
>>Nov 19 20:41:54 tur-net2 dhcpd: If you did get this software from ftp.isc.org
>and have not
>>Nov 19 20:41:54 tur-net2 dhcpd: yet read the README, please read it before
>requesting help.
>>Nov 19 20:41:54 tur-net2 dhcpd: If you intend to request help from the
>dhcp-server at isc.org
>>Nov 19 20:41:54 tur-net2 dhcpd: mailing list, please read the section on the
>README about
>>Nov 19 20:41:54 tur-net2 dhcpd: submitting bug reports and requests for help.
>>Nov 19 20:41:54 tur-net2 dhcpd:
>>Nov 19 20:41:54 tur-net2 dhcpd: Please do not under any circumstances send
>requests for
>>Nov 19 20:41:54 tur-net2 dhcpd: help directly to the authors of this software 
-
>please
>>Nov 19 20:41:54 tur-net2 dhcpd: send them to the appropriate mailing list as
>described in
>>Nov 19 20:41:54 tur-net2 dhcpd: the README file.
>>Nov 19 20:41:54 tur-net2 dhcpd:
>>Nov 19 20:41:54 tur-net2 dhcpd: exiting.
>>Nov 19 20:41:54 tur-net2 dhcpd: dhcpd startup failed
>>
>>
>>
>>Guy Defryn
>>
>>Infrastructure Development Engineer
>>Information Technology Services
>>Tennant Drive
>>Palmerston North
>>
>>06-3505799 ext 2087
>>_______________________________________________
>>Dhcp-users mailing list
>>Dhcp-users at lists.isc.org
>>https://lists.isc.org/mailman/listinfo/dhcp-users
>
>_______________________________________________
>Dhcp-users mailing list
>Dhcp-users at lists.isc.org
>https://lists.isc.org/mailman/listinfo/dhcp-users