[Openstack] help - Fuel Community 11 - PXE

Remo Mattei remo at italy1.com
Thu Nov 2 21:02:03 UTC 2017


you could upgrade to Tripleo :)

Ciao,


On 11/2/17 11:18 AM, Ken Houle wrote:
>
> Evgeniy L.
>
>  
>
> Thank you for the information. I have rebuilt the Fuel Community 11
> server and left everything default with the exception of setting the
> PXE support to eth1. I am seeing the same issue.
>
> The Silicon Mechanics server with a Supermicro system board as been
> configured in every possible boot configuration that I can think of;
> and I’m still seeing the “PXE-E7B” error.
>
>  
>
>  
>
> I’m about to consign this server to another use.
>
>  
>
>  
>
>  
>
> Regards,
>
>  
>
> /Ken Houle/
> 469-634-4171 :
> khoule at developingsolutions.com<mailto:khoule at developingsolutions.com>
>
>  
>
> *From:* Evgeniy L [mailto:eli at mirantis.com]
> *Sent:* Tuesday, October 31, 2017 9:58 AM
> *To:* Ken Houle <khoule at developingsolutions.com>
> *Cc:* Openstack <openstack at lists.openstack.org>
> *Subject:* Re: [Openstack] help - Fuel Community 11 - PXE
>
>  
>
> I'm not sure if these options should be set, because they are required
> only if PXE server is on different host from DHCP server, which is not
> the case for Fuel.
>
>  
>
> On Thu, Oct 26, 2017 at 8:25 AM, Ken Houle
> <khoule at developingsolutions.com
> <mailto:khoule at developingsolutions.com>> wrote:
>
>     Evgeniy L:
>
>      
>
>     Thank you for the information. I have a few, possible silly/noob,
>     question. After your email I reviewed the tcpdump again and
>     identified that the “dhcp offer” does not contain options 66 and 67.
>
>     You can see from the excerpt of a bootp capture the highlighted
>     portions contain the IP address offered, next server, and boot file.
>
>      
>
>     However, in the options section there is not an option 66, tftp
>     server name, and option 67, bootfile name.
>
>      
>
>     SO here is the question, taking cobbler into account which file
>     should I be editing to attempt to add these options? Is the
>     “/etc/cobbler/dhcp.template” file the correct file; thought
>     “template” seems to  indicate that it is not?
>
>     If not, again silly/noob, which file should I be editing.
>
>      
>
>     Any assistance would be appreciated.
>
>      
>
>      
>
>     Frame 4138: 342 bytes on wire (2736 bits), 342 bytes captured
>     (2736 bits)
>
>     Ethernet II, Src: Dell_b9:6a:02 (d4:ae:52:b9:6a:02), Dst:
>     Broadcast (ff:ff:ff:ff:ff:ff)
>
>     Internet Protocol Version 4, Src: 10.10.30.10, Dst: 255.255.255.255
>
>     User Datagram Protocol, Src Port: 67, Dst Port: 68
>
>     Bootstrap Protocol (Offer)
>
>         Message type: Boot Reply (2)
>
>         Hardware type: Ethernet (0x01)
>
>         Hardware address length: 6
>
>         Hops: 0
>
>         Transaction ID: 0x906a77f9
>
>         Seconds elapsed: 18
>
>         Bootp flags: 0x8000, Broadcast flag (Broadcast)
>
>             1... .... .... .... = Broadcast flag: Broadcast
>
>             .000 0000 0000 0000 = Reserved flags: 0x0000
>
>         Client IP address: 0.0.0.0
>
>         Your (client) IP address: 10.10.30.21
>
>         Next server IP address: 10.10.30.10
>
>         Relay agent IP address: 0.0.0.0
>
>         Client MAC address: SuperMic_6a:77:f9 (00:25:90:6a:77:f9)
>
>         Client hardware address padding: 00000000000000000000
>
>         Server host name: boothost
>
>         Boot file name: pxelinux.0
>
>         Magic cookie: DHCP
>
>         Option: (53) DHCP Message Type (Offer)
>
>         Option: (54) DHCP Server Identifier
>
>         Option: (51) IP Address Lease Time
>
>         Option: (58) Renewal Time Value
>
>         Option: (59) Rebinding Time Value
>
>         Option: (1) Subnet Mask
>
>         Option: (28) Broadcast Address
>
>         Option: (15) Domain Name
>
>         Option: (6) Domain Name Server
>
>         Option: (3) Router
>
>         Option: (255) End
>
>         Padding: 00
>
>      
>
>     Regards,
>
>      
>
>     /Ken Houle/
>     469-634-4171 : khoule at developingsolutions.com
>     <mailto:khoule at developingsolutions.com>
>
>      
>
>     *From:* Evgeniy L [mailto:eli at mirantis.com <mailto:eli at mirantis.com>]
>     *Sent:* Wednesday, October 25, 2017 11:45 AM
>     *To:* Ken Houle <khoule at developingsolutions.com
>     <mailto:khoule at developingsolutions.com>>
>     *Cc:* Openstack <openstack at lists.openstack.org
>     <mailto:openstack at lists.openstack.org>>
>     *Subject:* Re: [Openstack] help - Fuel Community 11 - PXE
>
>      
>
>     Hi Ken,
>
>      
>
>     Fuel uses Cobbler which uses DNSMasq to provide DHCP and PXE boot,
>     if the issue is hardware specific, you can try to search if
>     anybody else had such problems with DNSMasq PXE boot and similar
>     hardware.
>
>      
>
>     Thanks,
>
>      
>
>     On Wed, Oct 25, 2017 at 7:12 AM, Ken Houle
>     <khoule at developingsolutions.com
>     <mailto:khoule at developingsolutions.com>> wrote:
>
>         All:
>
>          
>
>         First off not sure I am in the right place so if I am not
>         please be kind and point me in the correct direction. I am
>         attempting to build an Openstack system with Fuel Community 11
>         with a mix servers from different manufacturers. I have
>         successfully installed Fuel Community 11 on the master node
>         and am attempting to add nodes to the Openstack environment.
>         The “Dell” servers pxe boot fine, see the master node and can
>         be added to the system. However, I have an older “Silicon
>         Mechanics” server that will not pxe boot.
>
>          
>
>         I have upgraded the AMI BIOS on the “Supermicro” system board
>         to the latest release as well as the IPMI firmware. I have
>         attempted to use both legacy and UEFI boot from the BIOS and I
>         always see the same error. Please note that the Intel PXE
>         release is 1.5.13.
>
>          
>
>         “PXE-E7B: Missing MTFTP server IP address. This message is
>         displayed when the ROM did not receive any PXE discovery tags
>         or proxyDHCP offers and the DHCP SIADDR field is set to 0.0.0.0.”
>
>          
>
>         I have take a tcpdump and see the dhcp discover and the dhcp
>         offer. The Fuel master node is offering the server an IP
>         address and is telling it what its next server and file are.
>
>          
>
>         Any assistance and or information would be greatly appreciated.
>
>          
>
>          
>
>         Regards,
>
>          
>
>         logo <http://www.developingsolutions.com/>
>
>         	
>
>         /Ken Houle/
>         /Sales Engineering /
>         */Developing Solutions, Inc./*
>         <http://www.developingsolutions.com/>
>         469-634-4171 : khoule at developingsolutions.com
>         <mailto:khoule at developingsolutions.com>
>
>          
>
>          
>
>
>         _______________________________________________
>         Mailing list:
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>         Post to     : openstack at lists.openstack.org
>         <mailto:openstack at lists.openstack.org>
>         Unsubscribe :
>         http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>      
>
>  
>
>
>
> _______________________________________________
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20171102/b05fba77/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7829 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20171102/b05fba77/attachment.png>


More information about the Openstack mailing list