yet another question about partner down
Brian Johnson
voyager.106 at gmail.com
Thu Jul 2 12:42:27 UTC 2009
Glenn,
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.
I'd actually pulled '1' from 'man dhcpd', which has this list:
local-state integer examine, modify
Indicates the present state of the DHCP server in this failover
relationship. Possible values for state are:
1 - partner down
2 - normal
3 - communications interrupted
4 - resolution interrupted
5 - potential conflict
6 - recover
7 - recover done
8 - shutdown
9 - paused
10 - startup
11 - recover wait
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!
Brian
On Wed, Jul 1, 2009 at 11:11 PM, Glenn Satchell
<Glenn.Satchell at uniq.com.au>wrote:
> 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)
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
--
Brian Johnson
"And I will be even more undignified than this, and will be humble in my own
sight." (2 Samuel 6:22)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20090702/d4c0f455/attachment.html>
More information about the dhcp-users
mailing list