Glenn,<br><br>Thanks so much for pointing me to includes/failover.h. This is the first I've seen of it in my searching of the tubes.<br><br>I'd actually pulled '1' from 'man dhcpd', which has this list:<br>
<br>local-state integer examine, modify<br> Indicates the present state of the DHCP server in this failover relationship. Possible values for state are:<br><br> 1 - partner down<br> 2 - normal<br>
3 - communications interrupted<br> 4 - resolution interrupted<br> 5 - potential conflict<br> 6 - recover<br> 7 - recover done<br> 8 - shutdown<br>
9 - paused<br> 10 - startup<br> 11 - recover wait<br><br>The Release notes for "changes since 3.1.1" (we're running 3.1.1) says " Corrected list of failover state values in dhcpd man page." which is what burned me. I'll :%s/1/4 and give it another go. Thanks for the help!<br>
<br>Brian<br><br><div class="gmail_quote">On Wed, Jul 1, 2009 at 11:11 PM, Glenn Satchell <span dir="ltr"><<a href="mailto:Glenn.Satchell@uniq.com.au">Glenn.Satchell@uniq.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Brian,<br>
<br>
I think you need local-state set to 4 for partner-down, 1 *is* startup,<br>
so your script is doing what you told it to do.<br>
<br>
This is taken from includes/failover.h<br>
<br>
/* A failover peer's running state. */<br>
enum failover_state {<br>
unknown_state = 0, /* XXX: Not a standard state. */<br>
startup = 1,<br>
normal = 2,<br>
communications_interrupted = 3,<br>
partner_down = 4,<br>
potential_conflict = 5,<br>
recover = 6,<br>
paused = 7,<br>
shut_down = 8,<br>
recover_done = 9,<br>
resolution_interrupted = 10,<br>
conflict_done = 11,<br>
<br>
regards,<br>
-glenn<br>
<br>
>From: Brian Johnson <<a onclick="window.location='https://mail.google.com/mail/?view=cm&fs=1&to=voyager.106@gmail.com&su=&cc=&bcc=&body='; return false" href="mailto:voyager.106@gmail.com">voyager.106@gmail.com</a>><br>
>Date: Wed, 1 Jul 2009 15:25:18 -0400<br>
>Subject: yet another question about partner down<br>
>To: <a onclick="window.location='https://mail.google.com/mail/?view=cm&fs=1&to=dhcp-users@isc.org&su=&cc=&bcc=&body='; return false" href="mailto:dhcp-users@isc.org">dhcp-users@isc.org</a><br>
><br>
> Hello all,<br>
><br>
> We've recently deployed a new pair of failover dhcp servers, and I'm trying<br>
> to test their ability to go into partner-down state. This is what I've done:<br>
><br>
> 1) gone to my secondary dhcp server, stopped dhcp<br>
> 2) on my primary server, run a 'tail -f /var/log/messages | grep move', saw<br>
> it go into communications-interrupted state<br>
> 3) run the below script:<br>
> #!/bin/sh<br>
> omshell << EOF<br>
> server localhost<br>
> key itsomkey *<super-duper-secret key here>*<br>
> connect<br>
> new failover-state<br>
> set name = "name"<br>
> open<br>
> set local-state = 1<br>
> update<br>
> EOF<br>
> 4) watch my tail -f to see what happens.<br>
><br>
> And, what seems to happen is, my primary server (the one that still had dhcp<br>
> running....) goes from communications-interrupted to....startup. Eventually<br>
> it goes back to c-i. But it never goes into partner-down.<br>
><br>
> Can someone let me know what I'm missing? Thanks.<br>
><br>
> Brian<br>
><br>
><br>
> --<br>
> Brian Johnson<br>
> "And I will be even more undignified than this, and will be humble in my own<br>
> sight." (2 Samuel 6:22)<br>
<br>
_______________________________________________<br>
dhcp-users mailing list<br>
<a onclick="window.location='https://mail.google.com/mail/?view=cm&fs=1&to=dhcp-users@lists.isc.org&su=&cc=&bcc=&body='; return false" href="mailto:dhcp-users@lists.isc.org">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><br><br clear="all"><br>-- <br>Brian Johnson <br>"And I will be even more undignified than this, and will be humble in my own sight." (2 Samuel 6:22)<br>