Send dhcp-users mailing list submissions to
        dhcp-users@lists.isc.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/dhcp-users
or, via email, send a message with subject or body 'help' to
        dhcp-users-requ...@lists.isc.org

You can reach the person managing the list at
        dhcp-users-ow...@lists.isc.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of dhcp-users digest..."


Today's Topics:

   1. Migrating dhcpd from a "single" server to "failover peer"
      setup (Danny Kulchinsky)
   2. Recommendation for redundancy (Pereida, Alejandro)


----------------------------------------------------------------------

Message: 1
Date: Mon, 5 Mar 2018 15:29:21 -0500
From: Danny Kulchinsky <danny....@gmail.com>
To: dhcp-users@lists.isc.org
Subject: Migrating dhcpd from a "single" server to "failover peer"
        setup
Message-ID:
        <CACrQNsPMnB7cPCAjZ54=FskD9oU0q=9hl-ofsjprrb_jaaq...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello Everyone!

We are running for a while ISC DHCP (v4.2.5) on a single linux server and
we would like to migrate it a highly available setup using "failover peer".

It is not very clear to me what would be the imapct of adding the failover
peer configuration into an exisiting systems with leases that we obvisouly
can't lose, I'm hoping that the system will perform the necessary changes
but I don't feel confident about this.

Also, our ranges are defined under subnet and it is my understanding that
these should be defined under pools where the "failover peer" is to be
configured, is that correct? so, I guess same question here - can we move
the ranges to "pools" without affecting any of the lease data?

Here's a subnet example in our setup:

subnet xxx.xxx.68.0 netmask 255.255.254.0 {
  range  xx.xxx.68.50 xx.xxx.68.150;
  range  xx.xxx.69.50 xx.xxx.69.200;
  option routers xx.xxx.68.1;
  option subnet-mask 255.255.254.0;
  option broadcast-address xx.xxx.69.255;
  option domain-search "<domain a>", "<domain b>", "<domain c>";
  option domain-name-servers xx.xxx.64.6, xx.xxx.64.7;
  default-lease-time 2592000;
  max-lease-time 10368000;
}

Can we just change it to:

subnet xxx.xxx.68.0 netmask 255.255.254.0 {
  pool {
    range  xx.xxx.68.50 xx.xxx.68.150;
    range  xx.xxx.69.50 xx.xxx.69.200;
    }
  }
  option routers  xx.xxx.68.1;
  option subnet-mask 255.255.254.0;
  option broadcast-address xx.xxx.69.255;
  option domain-search "<domain a>", "<domain b>", "<domain c>";
  option domain-name-servers xx.xxx.64.6, xx.xxx.64.7;
  default-lease-time 2592000;
  max-lease-time 10368000;
}



I couldn't find anything in the documenation that describes how to setup
"failover peer" in a pre-exisiting server with leases, so any pointers
would be highly welcome.


Thanks!
Danny
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180305/5195ca10/attachment-0001.html>

------------------------------

Message: 2
Date: Mon, 5 Mar 2018 23:20:50 +0000
From: "Pereida, Alejandro" <apere...@iid.com>
To: "dhcp-users@lists.isc.org" <dhcp-users@lists.isc.org>
Subject: Recommendation for redundancy
Message-ID: <c863603508c342c385bd22c5b222d...@iid.com>
Content-Type: text/plain; charset="us-ascii"

Hello all:

We have been using a single Linux server as our DHCP server running ISC DHCP 
Server 4.3.1
We are building a "secondary datacenter" for disaster recovery purposes. What 
is the most recommended
Option for implementing a redundant DHCP server scenario in case the main 
datacenter (where the DHCP server resides)
goes dark?

Thanks in advance

Alex Pereida
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180305/5625dcfe/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
dhcp-users mailing list
dhcp-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/dhcp-users


------------------------------

End of dhcp-users Digest, Vol 113, Issue 2
******************************************

Reply via email to