yet another question about partner down
Glenn Satchell
Glenn.Satchell at uniq.com.au
Thu Jul 2 03:11:53 UTC 2009
Hi Brian,
I think you need local-state set to 4 for partner-down, 1 *is* startup,
so your script is doing what you told it to do.
This is taken from includes/failover.h
/* A failover peer's running state. */
enum failover_state {
unknown_state = 0, /* XXX: Not a standard state. */
startup = 1,
normal = 2,
communications_interrupted = 3,
partner_down = 4,
potential_conflict = 5,
recover = 6,
paused = 7,
shut_down = 8,
recover_done = 9,
resolution_interrupted = 10,
conflict_done = 11,
regards,
-glenn
>From: Brian Johnson <voyager.106 at gmail.com>
>Date: Wed, 1 Jul 2009 15:25:18 -0400
>Subject: yet another question about partner down
>To: dhcp-users at isc.org
>
> Hello all,
>
> We've recently deployed a new pair of failover dhcp servers, and I'm trying
> to test their ability to go into partner-down state. This is what I've done:
>
> 1) gone to my secondary dhcp server, stopped dhcp
> 2) on my primary server, run a 'tail -f /var/log/messages | grep move', saw
> it go into communications-interrupted state
> 3) run the below script:
> #!/bin/sh
> omshell << EOF
> server localhost
> key itsomkey *<super-duper-secret key here>*
> connect
> new failover-state
> set name = "name"
> open
> set local-state = 1
> update
> EOF
> 4) watch my tail -f to see what happens.
>
> And, what seems to happen is, my primary server (the one that still had dhcp
> running....) goes from communications-interrupted to....startup. Eventually
> it goes back to c-i. But it never goes into partner-down.
>
> Can someone let me know what I'm missing? Thanks.
>
> Brian
>
>
> --
> Brian Johnson
> "And I will be even more undignified than this, and will be humble in my own
> sight." (2 Samuel 6:22)
More information about the dhcp-users
mailing list