1 2 Previous Next 20 Replies Latest reply on Jul 6, 2011 9:44 PM by Ahmad Ramzi Jamjoom

    ProxyDHCP service did not reply

      Hello,

       

      I'm trying to setup an provisioning environment with PXE. I'm using BladeLogic Server Automation 8.0 SP6.

       

      The PXE, DHCP and TFTP server are on the host 192.168.2.1. They're all running fine without any error messages. The BladeLogic server is installed on 192.168.2.2. The BladeLogic server and the PXE/DHCP/TFTP server are hosted on a virtual machines (both SLES 10).

       

      I'm using the following DHCP configuration:


      option routers 192.168.2.200;
      option bl-server code 211 = ip-address;
      option bl-port code 212 = unsigned integer 16;
      option vendor-class-identifier "PXEClient";
      option bl-server 192.168.2.2;
      option bl-port 9831;
      max-lease-time 7200;
      allow booting;
      allow bootp;
      ddns-update-style none;
      ddns-updates off;
      authoritative;

      log-facility local7;
      default-lease-time 600;
      allow duplicates;
      always-broadcast on;

       

      subnet 192.168.2.0 netmask 255.255.255.0 {
        default-lease-time 14400;
        range 192.168.2.3 192.168.2.254;
        max-lease-time 172800;
      }

       

      After creating a new virtual machine and starting it, the virtual machine is trying to get the IP address from the DHCP server. Somehow it's kinda going into a loop, requesting and releasing the ip address about 4 or 5 times:

       

       

      dhcpd: DHCPDISCOVER from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPOFFER on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPREQUEST for 192.168.2.252 (192.168.2.1) from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPACK on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPRELEASE of 192.168.2.252 from 00:50:56:bb:00:1a via eth1 (found)
      dhcpd: DHCPDISCOVER from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPOFFER on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPREQUEST for 192.168.2.252 (192.168.2.1) from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPACK on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPRELEASE of 192.168.2.252 from 00:50:56:bb:00:1a via eth1 (found)
      dhcpd: DHCPDISCOVER from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPOFFER on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPREQUEST for 192.168.2.252 (192.168.2.1) from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPACK on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPRELEASE of 192.168.2.252 from 00:50:56:bb:00:1a via eth1 (found)
      dhcpd: DHCPDISCOVER from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPOFFER on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPREQUEST for 192.168.2.252 (192.168.2.1) from 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPACK on 192.168.2.252 to 00:50:56:bb:00:1a via eth1
      dhcpd: DHCPRELEASE of 192.168.2.252 from 00:50:56:bb:00:1a via eth1 (found)

       

      A look into the PXE server log is showing that the PXE server is receiving requests, too:

       

      [05 Nov 2010 13:08:17,070] [Thread-7] [INFO] [::] [] activity fd index:2
      [05 Nov 2010 13:08:17,070] [Thread-7] [INFO] [::] [] DatagramSocket received
      [05 Nov 2010 13:08:17,091] [Thread-11] [INFO] [::] [] RPacketProcessor Thread id= 49 started
      [05 Nov 2010 13:08:17,112] [Thread-11] [INFO] [::] [] It is a proxy DHCP packet from /255.255.255.255:68
      [05 Nov 2010 13:08:17,113] [Thread-11] [INFO] [::] [] Packet type is DHCP Discover setting up DHCP Offer packet for reply
      [05 Nov 2010 13:08:17,115] [Thread-11] [INFO] [::] [] makeBootMenu : type 1
      [05 Nov 2010 13:08:17,141] [Thread-11] [INFO] [::] [] Replying to /255.255.255.255:68
      [05 Nov 2010 13:08:17,142] [Thread-11] [INFO] [::] [] RPacketProcessor Thread id= 49 Finished
      [05 Nov 2010 13:08:17,142] [Thread-7] [INFO] [::] [] (U)FD:94
      [05 Nov 2010 13:08:17,142] [Thread-7] [INFO] [::] [] (M)FD:95
      [05 Nov 2010 13:08:17,142] [Thread-7] [INFO] [::] [] (M)FD:96
      [05 Nov 2010 13:08:17,142] [Thread-7] [INFO] [::] [] activity fd index:2
      [05 Nov 2010 13:08:17,142] [Thread-7] [INFO] [::] [] DatagramSocket received
      [05 Nov 2010 13:08:17,143] [Thread-12] [INFO] [::] [] RPacketProcessor Thread id= 50 started
      [05 Nov 2010 13:08:17,146] [Thread-12] [INFO] [::] [] It is a proxy DHCP packet from /255.255.255.255:68
      [05 Nov 2010 13:08:17,146] [Thread-12] [INFO] [::] [] Packet type is DHCP Discover setting up DHCP Offer packet for reply
      [05 Nov 2010 13:08:17,146] [Thread-12] [INFO] [::] [] makeBootMenu : type 1
      [05 Nov 2010 13:08:17,170] [Thread-12] [INFO] [::] [] Replying to /255.255.255.255:68
      [05 Nov 2010 13:08:17,170] [Thread-12] [INFO] [::] [] RPacketProcessor Thread id= 50 Finished
      [05 Nov 2010 13:08:17,170] [Thread-7] [INFO] [::] [] (U)FD:94
      [05 Nov 2010 13:08:17,170] [Thread-7] [INFO] [::] [] (M)FD:95
      [05 Nov 2010 13:08:17,170] [Thread-7] [INFO] [::] [] (M)FD:96

       

      (that repeats multiple times)

       

      At the end the client, who's trying to boot via network, outputs an error message: PXE-E55: ProxyDHCP service did not reply to request on port 4011.

       

      The UPD port 4011 is open, every component is running. The TFTP server shows no activity (no log entry except that is has been started). I'm not sure why the TFTP server is never called, since the requesting client is receiving an IP address and is obviously contacting the PXE server (log entries).

       

      Does anybody know what I'm missing here? Thanks alot in advance.

        1 2 Previous Next