No subject


Fri Feb 17 00:23:59 UTC 2012


failover peer "PEERNAME" state {
  my state normal at 4 2008/03/20 12:49:28;
  partner state normal at 1 2007/02/12 19:41:48;
  mclt 600;
}


Also it looks like when I get "pool request" messages the leases that seemed
to be moved go into a state that they are locked for awhile (same on both
servers)
lease aaa.bbb.ccc.ddd {
  starts 2 2008/04/01 20:08:04;
  ends 2 2008/04/01 18:23:13;
  tstp 2 2008/04/01 18:23:13;
  tsfp 2 2008/04/01 20:08:04;
  cltt 2 2008/04/01 18:13:13;
  binding state backup;
  hardware ethernet 00:c0:17:31:38:8b;
  uid "\001\000\300\02718\213";
}

I would assume due to state 4 or is this related to some of the failover bug
fixes since 3.0.3?

If this is related to failover recovery not working for over a year, what is
the best way to recover since the servers are "working" for most clients
most of the time.

-- 
Jonathan Brockmeier, CIT
Hope College
616-395-7670

------=_Part_27233_32488730.1207097933154
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think I have found out that I have been running with broken failover for over a year:<br><br>From Server A:<br>failover peer "PEERNAME" state {<br>  my state normal at 4 2008/03/20 12:49:19;<br>  partner state normal at 1 2007/02/12 19:41:32;<br>
}<br><br clear="all">From Server B:<br>failover peer "PEERNAME" state {<br>  my state normal at 4 2008/03/20 12:49:28;<br>  partner state normal at 1 2007/02/12 19:41:48;<br>  mclt 600;<br>}<br><br><br>Also it looks like when I get "pool request" messages the leases that seemed to be moved go into a state that they are locked for awhile (same on both servers)<br>
lease aaa.bbb.ccc.ddd {<br>  starts 2 2008/04/01 20:08:04;<br>  ends 2 2008/04/01 18:23:13;<br>  tstp 2 2008/04/01 18:23:13;<br>  tsfp 2 2008/04/01 20:08:04;<br>  cltt 2 2008/04/01 18:13:13;<br>  binding state backup;<br>
  hardware ethernet 00:c0:17:31:38:8b;<br>  uid "\001\000\300\02718\213";<br>}<br><br>I would assume due to state 4 or is this related to some of the failover bug fixes since 3.0.3?<br><br>If this is related to failover recovery not working for over a year, what is the best way to recover since the servers are "working" for most clients most of the time.<br>
<br>-- <br>Jonathan Brockmeier, CIT<br>Hope College<br>616-395-7670

------=_Part_27233_32488730.1207097933154--


More information about the dhcp-users mailing list