Multiple ACK Issue

[Joey D.]

 Below is a diagram of what we witness is happening in the event of a
device reboot of a previously connected device (meaning the device is
already established in the leases db on both servers), as well as our
failover config.  Is there a configuration directive that can be used which
mandates that only the server sending the offer can send the ACK? (much
like what is done when allocating a fresh lease like in sec 3.2 in the
rfc).   I can detail a bit more as to the environment layout if necessary,
but I'm hoping there is an option I'm simply overlooking.



                Server A        Client          Server B

                  v               v              v
                  |               |              |
                  |     Begins initialization    |
                  |               |              |
                  | _____________/|\____________ |
                  |/DHCPDISCOVER  | DHCPDISCOVER\|
                  |               |              |
                  |               |              |
                  |               |  ___________/|
                  |               | /DHCPOFFER   |
                  |               |/             |
                  |     Selects configuration    |
                  |               |              |
                  | _____________/|\____________ |
                  |/ DHCPREQUEST  |  DHCPREQUEST\|
                  |               |              |
                  |               |              |
                  |               |              |
                  |\_____________ | ____________/|
                  |      DHCPACK \|/ DHCPACK     |
                  |               |              |
                  |    Initialization complete   |



SERVER A:
stash-agent-options true;

failover peer "iah-kcm" {
      primary;
      address x.x.1.248;
      port 647;
      peer address x.x.2.248;
      peer port 647;
      auto-partner-down 121;
      max-response-delay 120;
      max-unacked-updates 10;
      load balance max seconds 5;
      mclt 3600;
      split 128;

}
server-identifier x.x.1.248;
ping-check false;


SERVER B:
stash-agent-options true;

failover peer "iah-kcm" {

      secondary;
      address x.x.2.248;
      port 647;
      peer address x.x.1.248;
      peer port 647;
      auto-partner-down 121;
      max-response-delay 120;
      max-unacked-updates 10;
      load balance max seconds 5;
}
server-identifier x.x.2.248;
ping-check false;


- Joey D.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20140402/08970396/attachment.html>