9 Replies Latest reply on Nov 23, 2011 8:48 AM by Bill Robinson

    Provisioning from one server to two networks

    Olli Matikainen

      We have one BBSA provisioning server (ver. 8.1.1.111) in a dedicated network. Same server is also a DHCP server and is located in that same network. Now we need to provision also to another datacenter and we have other network segment over there. We could configure DHCP server to give addresses to that network, but provisioning ends to PXE-E61 Media test failure, check cable and PXE-M0F Exiting Intel Boot Agent.

       

      Some people say that one server can't provision to multiple networks and we need to have multiple servers. Is that correct or do we have some kind of misconfiguration.

        • 1. Re: Provisioning from one server to two networks
          Bill Robinson

          You need to forward the dhcp broadcasts from the other network to both your dhcp server and the pxe server.  typically you would need to setup an ip-helper or similar configuration on your router or switch on the remote network.

          1 of 1 people found this helpful
          • 2. Provisioning from one server to two networks
            Olli Matikainen

            Thaks for quick reply.

             

            Ok, DHCP works, that we can forget. But do I need to configure something additional to forward bradcasts to pxe server?

             

            DHCP and PXE are in same server and ip-helper can broadcast dhcp-traffic already.

            • 3. Re: Provisioning from one server to two networks
              Bill Robinson

              Are you getting the same error now ?

              • 4. Provisioning from one server to two networks
                Olli Matikainen

                Sorry being inaccurate. We didn't even try to provision until DHCP was OK. So we get a correct ip-address to target, but then it stops. I have a screenshot where I had a provisioing job running and the target was rebooted.PXE_Error.jpg

                • 5. Provisioning from one server to two networks
                  Bill Robinson

                  the media failure is from the 2nd nic not being plugged in.  that error is probably irrelevant.

                   

                  the real problem is the 'Could not locate boot server'.

                   

                  are you setting the gateway and dns in the dhcp scope options ?

                  1 of 1 people found this helpful
                  • 6. Provisioning from one server to two networks
                    Olli Matikainen

                    No, we had gateway and dns misconfigured. I changed that, and now we have also gateway setting correct. It didn't get us any further, exactly same error messages. Only exception is that it now clearly displays the correct gateway.

                    • 7. Re: Provisioning from one server to two networks
                      Bill Robinson

                      Provisioning is working on the local network right?

                       

                      Can the target system reach the tftp server?  is there a firewall between the target and the tftp server?

                      • 8. Re: Provisioning from one server to two networks

                        Is the PXe set in broadcast mode or Multicast mode?

                         

                         

                        If you can set the pxe server in multicast mode + Configure the dhcp such that the target whenever it boots is asked to do a multicast for discovery of boot server + multicast request is enabled across the pxe and the target network, it should work fine.

                         

                        Eg. of how to have dhcp.conf (for linux boxes, you can find similar option for windows dhcp as well)

                         

                        One option is to have the DHCP set with option space PXE -

                         

                        option space PXE;

                        option PXE.mtftp-ip code 1 = ip-address;

                        option PXE.mtftp-cport code 2 = unsigned integer 16;

                        option PXE.mtftp-sport code 3 = unsigned integer 16;

                        option PXE.mtftp-tmout code 4 = unsigned integer 8;

                        option PXE.mtftp-delay code 5 = unsigned integer 8;

                        option PXE.discovery-control code 6 = unsigned integer 8;

                        option PXE.discovery-mcast-addr code 7 = ip-address;

                        option PXE.boot-server code 8 = { unsigned integer 16, unsigned integer 8, ip-address };

                        option PXE.boot-menu code 9 = { unsigned integer 16,unsigned integer 8,text};

                        option PXE.menu-prompt code 10 = { unsigned integer 8, text };

                         

                         

                        subnet 11.0.3.0 netmask 255.255.255.0 {

                               range 11.0.3.51 11.0.3.250;

                               option routers 11.0.3.49;

                               option subnet-mask 255.255.255.0;

                               option domain-name "private.com";

                               option domain-name-servers 11.0.3.20;

                               vendor-option-space PXE;

                               option PXE.discovery-control 0;

                               option PXE.discovery-mcast-addr 224.1.5.1;

                               option PXE.boot-server 10 1 10.0.3.23;  (irrelevant as multicast will be replied to by pxe server)

                               option PXE.boot-menu  1 1 "boot";

                               option PXE.menu-prompt 0 "try";

                                default-lease-time 7200;

                               max-lease-time 14400;

                        allow duplicates;

                        always-broadcast on;

                        }

                         

                        Hence, once the taget is booted it is aked by the dhcp server to do a multicast to ip - 224.1.5.1 (default one)

                        The pxe server if set in multicast mode will be replying to the target with default boot images.

                         

                        Let me know if this works (if feasible in your setup)

                        • 9. Re: Provisioning from one server to two networks
                          Bill Robinson

                          does't this assume they have their switches and routers setup to handle multicast?