1 2 Previous Next 18 Replies Latest reply on Apr 12, 2012 10:58 AM by Sandeep Bhutani

    Provisioning - PXE/TFTP/DHCP problem

      Hi all,


      I tried find resolution of my issue on bmc community forum but I still don't know where is problem.


      I have following BladeLogic Server Automation 8.1 environment (all servers are on wmware):

      1. Server Application  - RHEL 5.6 x86_64
      2. Core Database - Windows 2008 R2 64bit
        • Additional components:
          • DHCP Server
          • Routing and Remote Access (because I want provisioning server in separate VLAN)
          • 2 interfaces (LAN1 and LAN2 (separate VLAN))
      3. TFTP/PXE Server - Windows 2008 R2 64bit
      4. BladeLogic Console - Windows 2008 Rw 64bit


      I've configured everything but I'm not sure if all is well. When I boot bare metal machine I receive this error:




      When I boot bare metal machine I checked network packages.

      DHCP server send "DHCP Offer" package.

      Application Server received this package:


      11:52:46.197672 IP (tos 0x0, ttl 128, id 3254, offset 0, flags [none], proto: UDP (17), length: 329) > BOOTP/DHCP, Reply, length: 301, xid:0x2ad7c0ca, flags: [none] (0x0000)

                Your IP:

                Server IP:

                Client Ethernet Address: 00:0c:29:d7:c0:ca (oui Unknown) [|bootp]



      Below is a part pxe log:

      [02 Jun 2011 15:47:16,394] [Thread-9] [INFO] [::] [] activity fd index:2

      [02 Jun 2011 15:47:16,394] [Thread-9] [INFO] [::] [] DatagramSocket received

      [02 Jun 2011 15:47:16,410] [Thread-20] [INFO] [::] [] RPacketProcessor Thread id= 57 started

      [02 Jun 2011 15:47:16,550] [Thread-20] [INFO] [::] [] It is a proxy DHCP packet from /

      [02 Jun 2011 15:47:16,550] [Thread-20] [INFO] [::] [] Packet type is DHCP Discover setting up DHCP Offer packet for reply

      [02 Jun 2011 15:47:16,550] [Thread-20] [INFO] [::] [] makeBootMenu : type 1

      [02 Jun 2011 15:47:16,628] [Thread-20] [INFO] [::] [] Replying to /

      [02 Jun 2011 15:47:16,628] [Thread-20] [INFO] [::] [] RPacketProcessor Thread id= 57 Finished

      [02 Jun 2011 15:47:16,628] [Thread-9] [INFO] [::] [] (U)FD:2492

      [02 Jun 2011 15:47:16,628] [Thread-9] [INFO] [::] [] (M)FD:2496

      [02 Jun 2011 15:47:16,628] [Thread-9] [INFO] [::] [] (M)FD:2500

      [02 Jun 2011 15:47:19,944] [Thread-9] [INFO] [::] [] activity fd index:2

      [02 Jun 2011 15:47:19,944] [Thread-9] [INFO] [::] [] DatagramSocket received

      [02 Jun 2011 15:47:19,944] [Thread-21] [INFO] [::] [] RPacketProcessor Thread id= 58 started

      [02 Jun 2011 15:47:19,944] [Thread-21] [INFO] [::] [] It is a proxy DHCP packet from /

      [02 Jun 2011 15:47:19,944] [Thread-21] [INFO] [::] [] Packet type is DHCP Discover setting up DHCP Offer packet for reply

      [02 Jun 2011 15:47:19,944] [Thread-21] [INFO] [::] [] makeBootMenu : type 1

      [02 Jun 2011 15:47:19,959] [Thread-21] [INFO] [::] [] Replying to /

      [02 Jun 2011 15:47:19,959] [Thread-21] [INFO] [::] [] RPacketProcessor Thread id= 58 Finished

      [02 Jun 2011 15:47:19,959] [Thread-9] [INFO] [::] [] (U)FD:2492

      [02 Jun 2011 15:47:19,959] [Thread-9] [INFO] [::] [] (M)FD:2496

      [02 Jun 2011 15:47:19,959] [Thread-9] [INFO] [::] [] (M)FD:2500

      [02 Jun 2011 15:47:21,407] [Thread-7] [INFO] [::] [] [PxeServerMonitor]: Current Active RPacketProcessor Threads:0

      [02 Jun 2011 15:47:21,407] [Thread-7] [INFO] [::] [] [PxeServerMonitor]: Thread ID: 27|| Thread Name: Thread-9|| Thread Description: PxeNet Thread to read DHCP packets|| Alive status is:true

      [02 Jun 2011 15:47:21,407] [Thread-7] [INFO] [::] [] [PxeServerMonitor]: Thread ID: 28|| Thread Name: Thread-10|| Thread Description: ProvDeviceCreator Thread Adds New DEVICES|| Alive status is:true

      [02 Jun 2011 15:47:21,407] [Thread-7] [INFO] [::] [] [PxeServerMonitor]: [Total JVM Memory (B)96,436,224 - Free JVM Memory (B)38,477,472] = Used JVM Memory (B)57,958,752



      Does anyone know where is problem? Maybe this post has not enough information. Please ask about more information.


      Thanks -  Przemek

        • 1. Provisioning - PXE/TFTP/DHCP problem
          Jim Campbell

          Have you imported the MAC?  Does it have a valid boot image selected?

          • 2. Provisioning - PXE/TFTP/DHCP problem
            Bill Robinson

            is the pxe server on the same subnet as the target server?

            • 3. Re: Provisioning - PXE/TFTP/DHCP problem

              regarding Jim's question:


              You mean imported the MAC in tree: Deveice -> Imported ? Yes, I have MAC address in this tree.

              Maybe problem is image selected. In Configuration > Provisioning Configurations in Image Files tab I selected Default Boot Image "Linux gentoo32/gentord.gz" and "Linux gentoo64/gentord.gz. In tftproot directory  (\tftproot\X86PC\pxelinux\gentoo[32|64]) I copied recreated files gentord.gz for 32 and 64 bit. I'm not sure is that it what you ask?


              regarding Bill's question:

              1. PXE/TFTP server has 2 interfaces. First interface is configured eth3 -, second interface is configured eth9 - (this is same subnet as target server). Pxe server listening on eth9 interface.
              2. Core Dtabase (additional DHCP and Routing and Remote Access) has 2 interfaces either (,
              3. Server application has 2 interfaces either (,
              4. Target Server is 192.168.12.x subnet.



              • 4. Re: Provisioning - PXE/TFTP/DHCP problem
                Bill Robinson

                It looks like the dhcp broadcasts are not being seen by the pxe server.  it’s weird though – in the log I see it make the boot menu, but I don’t see the mac address from the target come across (I’d expect to see that)


                The pxe server is supposed to be sending back the ‘filename’ and ‘next-server’ dhcp options to the target (66 & 67 I think) and it looks like that’s not happening.  It looks like you had some packet captures – do you see those options being passed in the dhcp negeotiation?


                Another thing to check would be what scope options are set on the dhcp server – maybe something is being overridden?

                • 5. Re: Provisioning - PXE/TFTP/DHCP problem

                  I don't know exactly how these packages look like.


                  Bellow my dhcp options.


                  I think that when dhcp negotation with pxe server options 66 and 67 should sending each other. When I manualy added option 66 and 67, target host trying start boot file (of course path isn't exists).

                  It looks like application server doesn't give PXE or DHCP option 66 and 67. I don't know exacly how this process work.

                  The problem may result from the lack of sufficient knowledge on BladeLogic. This is my first configuration of BladeLogic and Provisioning Module.

                  • 6. Re: Provisioning - PXE/TFTP/DHCP problem
                    Bill Robinson

                    The process works like this:


                    DHCPdiscover -> PXE and DHCP server

                    DHCP server responds with scope options you have above (ip, dns, gateway, etc)

                    PXE server responds w/ filename and next-server (pxelinux.0 and ip of tftp server)

                    pxe boot process starts.


                    what seems to be happening is that the pxe server is not handing back the filename and next-server options.


                    in the pxe server log do you see the mac address of your target anywhere?

                    • 7. Re: Provisioning - PXE/TFTP/DHCP problem


                      I resolved this problem.

                      Solution was: I crated separate VLAN (on vmware), then put BladeLogic Servers to new-made subnet (after IP changed I had to generate new licence of Application Server). I did reconfiguration IP (TFTP, PXE, Database, etc.). And now works fine!


                      I still wonder why in the previous configuration it had been not working. Bill, do you heard ever about problems with interfaces mapping in BladeLogic? I mean if application server or pxe/tftp server or core database have more than one interfaces in different subnet. And maybe incoming and outcoming connection flowing by different interfaces? Is this possible?

                      • 8. Re: Provisioning - PXE/TFTP/DHCP problem
                        Bill Robinson

                        the pxe server might not have been binding to the eth9 interface properly.


                        in general i don't think multi-homing anything is a good idea, but blade should generally work in that type of setup.

                        • 9. Provisioning - PXE/TFTP/DHCP problem
                          Steffen Kreis



                          we are having some sort of similir problems in our environment but thiese are related to gPXE based Servers (HP Proliant G7 models)


                          As network team refuses to include the IP of the PXE server as an IP-Helper on the switches, we use the following DHCP option:

                          dhcp-server-identifier [IP OF THE PXE-CLUSTER].

                          This is some kind of hack, cause using this, the DHCP server gives the booting client the client related IP-Address and stuff, and also tells it, that the IP of the "DHCP-Server" is the one, that in reality is the IP of the PXE-Server.

                          Using this causes that the client sends another DHCP-REQ after it has received the first answer from the real DHCP-Server, to the PXE-Server.

                          When the DHCp-Server receives this request, which isn't a broadcast anymore, it gives the "next-server" and "boot-file" option back to the booting client.


                          Our BL PXE Server is running on a Microsoft Cluster behind a Virtual-Cluster interface.

                          Unfortunately on tht cluster, the default gateway of the OS is not on the interface that holds the virtual clusered IP address, but on one of the physical interfaces of the cluster-node


                          This environment is working as expected with default PXE based provisioning, but fails for gPXE based servers.


                          The error message we see, on the booting client is:

                          "no filename or root path specified"


                          Looking at the logs of the PXE and TFTP-Server, we see that the PXE servers receives the request from the booting client and according to the logs is answering to the Request.


                          To make the cluster work, the request comes against the virtual-cluster interface.

                          We believe due to the default gateway beeing set on another interface, the DHCP ACK gets send on this interface, which has a different IP from the clustered one.


                          We need to trace that with wireshark to fully proof that, but i'm pretty sure, that this is the case.


                          As the gPXE boot-rom seems to be a bit more clever, than the older PXE implementations, it realizes, that the DHCP-ACK from the PXE server is coming back from another address than the one it used by the "dhcp-server-identifier" option and therefore refuses to accept it.



                          To cut a long story short, we are looking for a method, to bind the PXE-service to a certain IP address on a Windows server, to make sure, it answers with the same IP, as it has received the request.

                          We have not found any option that would allow us to do that.




                          • 10. Provisioning - PXE/TFTP/DHCP problem
                            Bill Robinson

                            can you disable the dhcp-server-identifier setting in the dhcp scope?


                            we've had pxe boot from your hardware work successfully though i don't recall if the pxe and dhcp were different systems.

                            • 11. Provisioning - PXE/TFTP/DHCP problem
                              Steffen Kreis



                              unfortunately, disabling the dhcp-server-identfier will cause that the PXE Server doesn't receive a DHCP-Req at all,

                              as Network team is not giving as the IP-Helpers.



                              • 12. Provisioning - PXE/TFTP/DHCP problem
                                Bill Robinson

                                were you able to gather any evidence via wireshark?

                                • 13. Provisioning - PXE/TFTP/DHCP problem
                                  Bill Robinson

                                  also - so the cluster interface and the node interface are on the same VLAN but they have different default gateways set?


                                  because i don't see how the request could come in on one interface and then take a different network path back to the target.

                                  • 14. Re: Provisioning - PXE/TFTP/DHCP problem

                                    Hi Mantaj,

                                    I am facing a similar problem. Were you able to setup multiple vlans and remoting and routing service to work?

                                    1 2 Previous Next