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. How to properly break DHCPd failover peer relationship
(Justin Sanderson)
----------------------------------------------------------------------
Message: 1
Date: Mon, 12 Mar 2018 16:23:18 -0500
From: Justin Sanderson <justin.sanderson...@gmail.com>
To: dhcp-users@lists.isc.org
Subject: How to properly break DHCPd failover peer relationship
Message-ID:
<CAMSrtT9r4D6h1ZoQVUHRbOtqdtfw=-wosooy0ecfjsm+zwp...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hi everyone. I'm new to the list and am in need of some advice.
I have 2 servers running RHEL 5.x using dhcp-3.0.5-23 that are running in a
peer relationship.
I'm looking for the best/easiest method to break this peer relationship and
reduce the dhcp server functionality back to just one server w/o
interrupting clients.
Again, any advice or past experiences would be helpful.
Here's a snippet of the conf files where the pool is being balanced/split.
================================================
PRIMARY SERVER
subnet 172.20.10.0 netmask 255.255.255.0 {
pool {
range 172.20.10.1 172.20.10.45;
range 172.20.10.47 172.20.10.95;
range 172.20.10.97 172.20.10.149;
ping-check true;
option subnet-mask 255.255.255.0;
option broadcast-address 172.20.10.255;
option routers 172.20.10.254;
deny dynamic bootp clients;
failover peer "xxxxx";
}
}
=======================================================
PRIMARY SERVER
failover peer "xxxxx" {
primary;
address 172.20.10.200;
port 520;
peer address 172.20.10.201;
peer port 521;
max-response-delay 120;
max-unacked-updates 10;
mclt 1800;
split 128;
load balance max seconds 3;
}
=========================================================
SECONDARY SERVER (the server i want to remove from the relationship)
subnet 172.20.10.0 netmask 255.255.255.0 {
pool {
range 172.20.10.1 172.20.10.45;
range 172.20.10.47 172.20.10.95;
range 172.20.10.97 172.20.10.149;
ping-check true;
option subnet-mask 255.255.255.0;
option broadcast-address 172.20.10.255;
option routers 172.20.10.254;
deny dynamic bootp clients;
failover peer "xxxxx";
}
}
==============================================================
SECONDARY SERVER
failover peer "adtran" {
secondary;
address 172.20.10.201;
port 521;
peer address 172.20.10.200;
peer port 520;
max-response-delay 120;
max-unacked-updates 10;
load balance max seconds 3;
}
ThankS in advance.
Regards,
Justin
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://lists.isc.org/pipermail/dhcp-users/attachments/20180312/8bbe9cb2/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 7
******************************************
