问动态引导范围声明的DHCP服务器故障转移

EN

authoritative;
log-facility local7;
shared-network "vm-net" {
failover peer "failover-partner" {
     secondary;
     address 192.168.122.4;
     port 647;
     peer address 192.168.122.3;
     peer port 647;
     max-response-delay 60;
     max-unacked-updates 10;
     load balance max seconds 3;
}
  subnet 192.168.122.0 netmask 255.255.255.128 {
      pool {
          failover peer "failover-partner";
          max-lease-time 1800;
          range 192.168.122.0 192.168.122.127;
      }   
    deny unknown-clients;
  }
  subnet 192.168.122.128 netmask 255.255.255.128 {
      pool {
          failover peer "failover-partner";
          max-lease-time 1800;
          range dynamic-bootp 192.168.122.128 192.168.122.255;
      }   
    deny unknown-clients;
  }
}

Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: range declarations where there is a failover
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: peer in scope.   If you wish to declare an
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: address range from which dynamic bootp leases
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: can be allocated, please declare it within a
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: pool declaration that also contains the "no
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: failover" statement.   The failover protocol
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: itself does not permit dynamic bootp - this
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: is not a limitation specific to the ISC DHCP
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: server.   Please don't ask me to defend this
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: until you have read and really tried to understand
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: the failover protocol specification.
Dec  7 14:59:07 dhcpmaster1 dhcpd[4397]: Configuration file errors encountered -- exiting