Hello Nils (and all the others :-)<br><br>as promised the summary of the trace.<br>No. Time Absolute Time Source Destination New Column Protocol Info New Column<br>
2 0.000097 16:29:13.308980 xxxxxxxxxx xxxxxxxxxx dhcp-failover TCP 32197 > dhcp-failover [ACK] Seq=1 Ack=13 Win=5530 Len=0 16:29:13.308980<br> 3 1.992243 16:29:15.301126 xxxxxxxxxx xxxxxxxxxx dhcp-failover DHCPFO Contact xid: a1 16:29:15.301126<br>
6 10.008093 16:29:23.316976 xxxxxxxxxx xxxxxxxxxx dhcp-failover TCP 32197 > dhcp-failover [ACK] Seq=13 Ack=25 Win=5530 Len=0 16:29:23.316976<br> 7 11.994244 16:29:25.303127 xxxxxxxxxx xxxxxxxxxx dhcp-failover DHCPFO Contact xid: a2 16:29:25.303127<br>
10 20.016121 16:29:33.325004 xxxxxxxxxx xxxxxxxxxx dhcp-failover TCP 32197 > dhcp-failover [ACK] Seq=25 Ack=37 Win=5530 Len=0 16:29:33.325004<br> 11 21.996225 16:29:35.305108 xServer 2xxx xServer 1xx dhcp-failover DHCPFO Contact xid: a3 16:29:35.305108<br>
14 30.020585 16:29:43.329468 xxxxxxxxxx xxxxxxxxxx dhcp-failover TCP 32197 > dhcp-failover [ACK] Seq=37 Ack=49 Win=5530 Len=0 16:29:43.329468<br> 15 36.125682 16:29:49.434565 xxxxxxxxxx xxxxxxxxxx 14619 TCP 7911 > 14619 [FIN, ACK] Seq=1 Ack=1 Win=730 Len=0 16:29:49.434565<br>
18 40.030602 16:29:53.339485 xxxxxxxxxx xxxxxxxxxx dhcp-failover TCP 32197 > dhcp-failover [ACK] Seq=37 Ack=61 Win=5530 Len=0 16:29:53.339485<br> 19 47.142748 16:30:00.451631 xxxxxxxxxx xxxxxxxxxx dhcp-failover TCP 32197 > dhcp-failover [RST, ACK] Seq=37 Ack=61 Win=5530 Len=0 16:30:00.451631<br>
21 52.144123 16:30:05.453006 xxxxxxxxxx xxxxxxxxxx 13880 TCP dhcp-failover > 13880 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0 16:30:05.453006<br> 23 57.148097 16:30:10.456980 xxxxxxxxxx xxxxxxxxxx 55083 TCP dhcp-failover > 55083 [RST, ACK] Seq=1 Ack=1 Win=0 Len=0 16:30:10.456980<br>
<br><br>Server 2 = the server that shuts down<br>Server 1 = Failover Primary<br><br>I set a filter of source server 2. Because this is the server that should inform the primary of the shut down. So that the partner-down state occurs. For me the tcp session is quite ok because it finnish with a FIN. But the DHCP-FO session suddenly breaks with a reset.<br>
<br>Is this normal? Or is this the reason why I cant see any shut down information for the primary?<br><br>What Version of ISC-DHCP do you run?<br>What OS and Version do you use?<br><br>thanx a lot for all your help,<br>cheers, Juergen<br>
<br><br><div class="gmail_quote">2011/2/24 Jürgen Dietl <span dir="ltr"><<a href="mailto:juergen.dietl@googlemail.com">juergen.dietl@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello,<br><br>thanx a lot for your help. I tried it with the following script:<br><br>#!/bin/bash<br><br>/usr/local/bin/omshell << END<br>server localhost<br>port 7911<br>key xxxxxxxxxxxxxxxxxxxxxxxxxxxxx<div class="im">
<br>connect<br>
new control<br>open<br>set state=2<br>update<br>END<br><br></div>The log file:<br><br>Feb 24 16:03:14 xxxxxxx dhcpd: peer xxxxxxxx: disconnected<br>Feb 24 16:03:14 xxxxxxx dhcpd: failover peer xxxxxxx: I move from normal to communications-interrupted<br>
<br><br>Feb 24 16:03:09 xxxxxxx dhcpd: Disabling output on LPF/eth0/00:00:00:00:00:00/<a href="http://10.2.220.0/24" target="_blank">10.2.220.0/24</a><br>Feb 24 16:03:09 xxxxxxx dhcpd: Disabling input on LPF/eth0/00:00:00:00:00:00/<a href="http://10.2.220.0/24" target="_blank">10.2.220.0/24</a><br>
Feb 24 16:03:09 xxxxxxx dhcpd: failover peer xxxxxxx: I move from normal to shutdown<br>Feb 24 16:03:14 xxxxxxx dhcpd: failover peer xxxxxxx: I move from shutdown to recover<br><br>I will do some trace soon and try to see how the 2 servers communicate. Till now it looks to me that the server that shuts down dont tell it to the other server.<br>
<br>cu later,<br>cheers,<br>Juergen<br><br><br><br><br><div class="gmail_quote">2011/2/24 Nils-Henner Krueger <span dir="ltr"><<a href="mailto:nhk@snhc-krueger.de" target="_blank">nhk@snhc-krueger.de</a>></span><div>
<div></div><div class="h5"><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Am 24.02.2011 14:56, schrieb Jürgen Dietl:<br>
<div>> My main problem is that when I stop the dhcp server I always will get a<br>
> "communication-interrupted". What I would like to have is a "partner-down".<br>
><br>
> So do any of you have a script or an idea how I can make the server to<br>
> make a graceful shutdown of dhcp service?<br>
<br>
</div>'man dhcpd' of version 4.11 says "To shut the server down, open its<br>
control object and set the state attribute to 2."<br>
<br>
I do it like this in a start/stop-Script:<br>
<br>
${PRODPATH}/bin/omshell << END<br>
server localhost<br>
port xxxx<br>
connect<br>
new control<br>
open<br>
set state=2<br>
update<br>
END<br>
<br>
This works fine, logging on the shutdown server:<br>
<br>
dhcpd: failover peer ha: I move from normal to shutdown<br>
dhcpd: failover peer ha: peer moves from normal to partner-down<br>
dhcpd: failover peer ha: I move from shutdown to recover<br>
<br>
Logging on the partner cluster member:<br>
<br>
dhcpd: failover peer ha: peer moves from normal to shutdown<br>
dhcpd: failover peer ha: I move from normal to partner-down<br>
dhcpd: peer ha: disconnected<br>
<br>
<br>
nils-henner<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a href="mailto:dhcp-users@lists.isc.org" target="_blank">dhcp-users@lists.isc.org</a><br>
<a href="https://lists.isc.org/mailman/listinfo/dhcp-users" target="_blank">https://lists.isc.org/mailman/listinfo/dhcp-users</a><br>
</blockquote></div></div></div><br>
</blockquote></div><br>