omshell and partner-down
Jeff A. Earickson
jaearick at colby.edu
Tue Dec 12 20:58:06 UTC 2006
Gang,
Setup: 3.0.5 on a pair of Sun boxes.
I'm reading up on omshell to put my failover/secondary into
partner-down status, so I can move my secondary to different
hardware. I followed the example on page 316 of the DHCP Handbook,
2nd edition, and I get strange behavior. On my primary server
(magma), I do thus with omshell:
% omshell
> server magma
> port [myport]
> key itsomkey [mykey]
> connect
obj: <null>
> new failover-state
obj: failover-state
> set name = "colby"
obj: failover-state
name = "colby"
> open
obj: failover-state
name = "colby"
partner-address = 00:10:1e:58
partner-port = 00:00:03:22
local-address = 00:10:1e:28
local-port = 00:00:03:21
max-outstanding-updates = 00:00:00:0a
mclt = 00:00:02:58
load-balance-max-secs = 00:00:00:03
load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00
partner-state = 00:00:00:02
local-state = 00:00:00:02
partner-stos = 43:a9:b3:1e
local-stos = 45:7f:12:82
hierarchy = 00:00:00:00
last-packet-sent = 00:00:00:00
last-timestamp-received = 00:00:00:00
skew = 00:00:00:00
max-response-delay = 00:00:00:3c
cur-unacked-updates = 00:00:00:00
> set local-state = 1
obj: failover-state
name = "colby"
partner-address = 00:10:1e:58
partner-port = 00:00:03:22
local-address = 00:10:1e:28
local-port = 00:00:03:21
max-outstanding-updates = 00:00:00:0a
mclt = 00:00:02:58
load-balance-max-secs = 00:00:00:03
load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00
partner-state = 00:00:00:02
local-state = 1
partner-stos = 43:a9:b3:1e
local-stos = 45:7f:12:82
hierarchy = 00:00:00:00
last-packet-sent = 00:00:00:00
last-timestamp-received = 00:00:00:00
skew = 00:00:00:00
max-response-delay = 00:00:00:3c
cur-unacked-updates = 00:00:00:00
> update
obj: failover-state
name = "colby"
partner-address = 00:10:1e:58
partner-port = 00:00:03:22
local-address = 00:10:1e:28
local-port = 00:00:03:21
max-outstanding-updates = 00:00:00:0a
mclt = 00:00:02:58
load-balance-max-secs = 00:00:00:03
load-balance-hba = ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00
partner-state = 00:00:00:02
local-state = 1
partner-stos = 43:a9:b3:1e
local-stos = 45:7f:12:82
hierarchy = 00:00:00:00
last-packet-sent = 00:00:00:00
last-timestamp-received = 00:00:00:00
skew = 00:00:00:00
max-response-delay = 00:00:00:3c
cur-unacked-updates = 00:00:00:00
> [control-d]
So here is what I see happen in the syslog on my primary:
Dec 12 15:39:25 magma dhcpd: [ID 702911 daemon.info] failover peer colby: I move from normal to partner-down
Dec 12 15:39:25 magma dhcpd: [ID 702911 daemon.info] failover peer colby: peer moves from normal to potential-conflict
Dec 12 15:39:25 magma dhcpd: [ID 702911 daemon.info] failover peer colby: I move from partner-down to potential-conflict
Dec 12 15:39:25 magma dhcpd: [ID 702911 daemon.info] failover peer colby: peer update completed.
Dec 12 15:39:25 magma dhcpd: [ID 702911 daemon.info] failover peer colby: I move from potential-conflict to normal
Dec 12 15:39:27 magma dhcpd: [ID 702911 daemon.info] failover peer colby: peer moves from potential-conflict to normal
Likewise on the secondary:
Dec 12 15:39:25 lava dhcpd: [ID 702911 daemon.info] failover peer colby: peer moves from normal to partner-down
Dec 12 15:39:25 lava dhcpd: [ID 702911 daemon.info] failover peer colby: I move from normal to potential-conflict
Dec 12 15:39:25 lava dhcpd: [ID 702911 daemon.info] failover peer colby: peer moves from partner-down to potential-conflict
Dec 12 15:39:25 lava dhcpd: [ID 702911 daemon.info] failover peer colby: peer moves from potential-conflict to normal
Dec 12 15:39:27 lava dhcpd: [ID 702911 daemon.info] failover peer colby: peer update completed.
Dec 12 15:39:27 lava dhcpd: [ID 702911 daemon.info] failover peer colby: I move from potential-conflict to normal
What gives??? both systems end up back in normal mode. What is wrong?
How to get the secondary into partner-down mode?
Jeff Earickson
Colby College
More information about the dhcp-users
mailing list