Problema de failover DHCP DHCPDISCOVER via eth0: não respondendo (recuperando) [fechado]

1

Estou tentando configurar um servidor DHCP. Mas quando o host1 está ativo, se eu tentar o serviço DHCP no host2. falha ...

Se eu não adicionar comentários (desativar) na parte de configuração de failover, o log de mensagens mostrará:

Jun 8 07:31:12 dhcp01 dhcpd: DHCPDISCOVER from XXXXXXXXXXXXX (USER) via eth0: not responding (recovering)

Alguém tem alguma ideia? Eu acho que é a parte do failover.

configuração no failover:

arquivo dhcpd.conf no host1:

ddns-update-style interim;
ignore client-updates;
authoritative;
#option option-150 code 150 = text ;
option dhcp-server-identifier 10.58.79.232;
option dhcp-server-identifier 10.58.79.233;

failover peer "alamopeer" {
    primary;
    address [HOST1];
    port 1068;
    peer address [HOST2];
    peer port 1069;
    max-response-delay 180;
    max-unacked-updates 10;
    mclt 600;
split 120;
    load balance max seconds 3;
}


subnet 10.58.72.0 netmask 255.255.248.0 {

    option routers                 10.58.79.230;
    option subnet-mask             255.255.248.0;

    option nis-domain             "DOMAIN.es";
    option domain-name             "DOMAIN.es";
    option domain-name-servers     10.59.172.46, 10.59.173.47;

    #option time-offset             -18000; # Eastern Standard Time
    option ntp-servers             10.59.172.46;
option netbios-name-servers   HOST1.ine.es;

option netbios-node-type 8;
    #min-lease-time 43200;
    #default-lease-time 86400;
    #default-lease-time 259200;
    default-lease-time 2592000;
    #max-lease-time 86400;
    #max-lease-time 259200; 
    max-lease-time 2592000;   
    one-lease-per-client true;

    pool {

            range 10.58.72.1 10.58.72.253;
            range 10.58.73.1 10.58.73.253;
            range 10.58.74.1 10.58.74.253;
            range 10.58.75.1 10.58.75.253;
            range 10.58.76.1 10.58.76.150;

            deny dynamic bootp clients;
    }

}

arquivo dhcpd.conf no host 2:

ddns-update-style interim;
ignore client-updates;
authoritative;
#option option-150 code 150 = text ;

#log-facility local4;

option dhcp-server-identifier [IP HOST 2] ;

option dhcp-server-identifier [IP HOST 1];

failover peer "alamopeer" {
    secondary;
    address [IP HOST 2];
    port 1069;
    peer address 10.58.79.233;
    peer port 1068;
    max-response-delay 180;
    max-unacked-updates 10;
    #mclt 600;
    #split 120;
    load balance max seconds 3;
}

subnet 10.58.72.0 netmask 255.255.248.0 {

    option routers                 10.58.79.230;
    option subnet-mask             255.255.248.0;

    option nis-domain             "DOMAIN.es";
    option domain-name             "DOMAIN.es";
    option domain-name-servers     10.59.172.46, 10.59.173.47;

    #option time-offset             -18000; # Eastern Standard Time
    option ntp-servers             10.59.172.46;

    option netbios-name-servers   [HOST1];
    option netbios-node-type 8;
    #min-lease-time 43200;
    #default-lease-time 86400;
    #default-lease-time 259200;
    default-lease-time 2592000; 
    #max-lease-time 86400;
    #max-lease-time 259200;   
    max-lease-time 2592000;   
    one-lease-per-client true;


    pool {

            range 10.58.72.1 10.58.72.253;
            range 10.58.73.1 10.58.73.253;
            range 10.58.74.1 10.58.74.253;
            range 10.58.75.1 10.58.75.253;
            range 10.58.76.1 10.58.76.150;

            ##range 10.58.77.1 10.58.77.199;
            failover peer "alamopeer";
            deny dynamic bootp clients;
    }

}

No momento, o host1 está ativo e funciona ... mas no host2 o dhcp está desativado.

Achados:

  • o sistema operacional é o RHEL 6.9
  • o host1 foi migrado de outro host diferente. Instalando o pacote RHEL do dhcpd e copiando o dhcpd.conf (alterando os dados do host1)
por Ramos 08.06.2017 / 11:56

0 respostas