Problems with a Failover Pair

[David Liedke]

Hi,

i have an Failover Pair with DHCPD Version 4.2.6 on openSUSE 13.2.

Primary:

#OMAPI
omapi-port 7911;
omapi-key primary;
key primary {
     algorithm hmac-md5;
     secret "XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX";
}

failover peer "noc" {
  primary; # declare this to be the primary server
  address XX.XX.XX.XX;
  port 519;
  peer address XX.XX.XX.XX;
  peer port 520;
  max-response-delay 40;
  max-unacked-updates 10;
  load balance max seconds 3;
  mclt 1800;
  split 128;
}


Secondary:

#OMAPI
omapi-port 7911;
omapi-key secondary;
key secondary {
     algorithm hmac-md5;
     secret "XXX";
}

failover peer "noc" {
  secondary; # declare this to be the primary server
  address XX.XX.XX.XX;
  port 520;
  peer address XX.XX.XX.XX;
  peer port 519;
  max-response-delay 40;
  max-unacked-updates 10;
  load balance max seconds 3;

}

On both Server we use a Cronjob to renew the DHCPD Configuration.
Normally there are only changes for the static configuration (for
example: new mac-adress).

Now we had the problem after we execute the script and reboot the dhcpd
server that the server go to the "recover" state. And he doesn´t came
back online (normal state).

Normally we execute the Cronjob on the primary server two times per
hour.  Two minutes after the primary server the cronjob on the secondary
will be executed.
In the last 5 years we use the method to renew the configuration without
any problems.

I want to test the option to send a shutdown signal via OMAPI to the
server i want to renew. But i get always "not connected oder peer
rejected connection".

Can anyone help me ?

Kind regards,
David


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4943 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150929/a3fca840/attachment.bin>