RE: PXE boot disks

From: MW Mike Weiner (5028) (MWeiner_at_ag.com)
Date: 06/16/05

  • Next message: Robert P. J. Day: "how to re-invoke firstboot on later reboots?"
    Date: Thu, 16 Jun 2005 14:13:50 -0400
    To: <marcel@mesa.nl>, "For users of Fedora Core releases" <fedora-list@redhat.com>
    
    

    On Thu, Jun 16, 2005 at 01:37:12PM -0400, MW Mike Weiner (5028) wrote:
    > Michael -
    >
    > Thanks for your response, I made the change and tested it remotely
    > using a tftp client and do see the pxelinux.0 there and can
    > successfully grab it. Also tested the dhcpd to ensure it truly is
    > working. That all works, so now to figure out why the client isnt
    > being told or isnt listening to dhcpd when being instructed about the
    > PXECLIENT stuff, as in the
    > following:
    >
    > group {
    > # option dhcp-class-identifier "PXEClient";
    > next-server 10.10.232.54;
    > filename "pxelinux.0";
    > }
    >
    > But never seems to get that information nor tftp the bootloader.

    For testing, just remove the 'group {' and matching '}'.
    I just have the next-server and filename lines as the first two in de
    dhcp conf file.

    --
    Marcel - 
    Excellent suggestion, thank you, that worked WELL. Strange though the
    group defs would stop if from working correctly, but in my case I can do
    without those definitions as any and all pxeboot clients WILL need to go
    through the same process. 
    OK, thanks to Marcel, I have it successfully pulling the pxelinux.0
    where its failing now, is at the following:
    Jun 16 13:54:40 yum1 dhcpd: DHCPDISCOVER from 00:03:47:11:3c:6b via eth0
    Jun 16 13:54:41 yum1 dhcpd: DHCPOFFER on 10.10.232.80 to
    00:03:47:11:3c:6b via eth0
    Jun 16 13:54:41 yum1 dhcpd: DHCPREQUEST for 10.10.232.80 (10.10.232.54)
    from 00:03:47:11:3c:6b via eth0
    Jun 16 13:54:41 yum1 dhcpd: DHCPACK on 10.10.232.80 to 00:03:47:11:3c:6b
    via eth0
    Jun 16 17:54:41 yum1 in.tftpd[9505]: tftp: client does not accept
    options 
    Jun 16 13:54:41 yum1 dhcpd: DHCPINFORM from 10.10.232.231 via eth0: not
    authoritative for subnet 10.10.232.0
    Jun 16 13:54:41 yum1 dhcpd: If this DHCP server is authoritative for
    that subnet,
    Jun 16 13:54:41 yum1 dhcpd: please write an `authoritative;' directive
    either in the
    Jun 16 13:54:41 yum1 dhcpd: subnet declaration or in some scope that
    encloses the
    Jun 16 13:54:41 yum1 dhcpd: subnet declaration - for example, write it
    at the top
    Jun 16 13:54:41 yum1 dhcpd: of the dhcpd.conf file.
    Jun 16 13:54:44 yum1 dhcpd: DHCPINFORM from 10.10.232.231 via eth0: not
    authoritative for subnet 10.10.232.0
    Jun 16 13:55:47 yum1 dhcpd: DHCPDISCOVER from 00:03:47:11:3c:6b via eth0
    Jun 16 13:55:47 yum1 dhcpd: DHCPREQUEST for 10.10.232.55 (10.10.1.13)
    from 00:03:47:11:3c:6b via eth0: unknown lease 10.10.232.55.
    Jun 16 13:55:48 yum1 dhcpd: DHCPOFFER on 10.10.232.80 to
    00:03:47:11:3c:6b via eth0
    I can see the server actually loading the bootloader and I can see this
    in the messages log now:
    Jun 16 14:11:48 yum1 rpc.mountd: authenticated mount request from
    10.10.232.80:750 for /repo/fedora/linux/core/2/i386/os (/repo)
    So it appears to find my kickstart config file. The /repo above is of
    course the install base (Fedora/images/etc under the OS tree). Here is
    my current ks-cf2.cfg file for completeness:
    install
    nfs --server 10.10.232.54 --dir /repo/fedora/linux/core/2/i386/os/
    lang en_US.UTF-8
    langsupport --default=en_US.UTF-8 en_US.UTF-8
    keyboard us
    xconfig --card "ATI Mach64" --videoram 8128 --hsync 30-107 --vsync
    48-160 --resolution 800x600 --depth 16 --startxonboot  --defaultdesktop
    gnome
    network --device eth0 --bootproto static --hostname yum1
    network --device eth1 --bootproto static --hostname yum1
    rootpw --iscrypted $1$uPGYqbg9$Oe3tBtou1zu8CqEg6rFUL1
    firewall --disabled
    selinux --enforcing
    authconfig --enableshadow --enablemd5
    timezone America/New_York
    bootloader --location=mbr --append="rhgb quiet"
    # The following is the partition information you requested
    # Note that any partitions you deleted are not expressed
    # here so unless you clear all partitions first, this is
    # not guaranteed to work
    clearpart --all --drives=sda
    part /boot --fstype "ext3" --size=100 --ondisk=sda
    part pv.5 --noformat --onpart sdd1
    part pv.4 --noformat --onpart sdc1
    part pv.11 --size=0 --grow --ondisk=sda
    part pv.3 --noformat --onpart sdb1
    volgroup VolGroup00 pv.11
    logvol swap --fstype swap --name=LogVol01 --vgname=VolGroup00
    --size=1000 --grow --maxsize=2000
    logvol / --fstype ext3 --name=LogVol00 --vgname=VolGroup00 --size=1024
    --grow
    %packages
    @ office
    @ engineering-and-scientific
    @ mysql
    @ editors
    @ system-tools
    @ text-internet
    @ legacy-network-server
    @ dns-server
    @ dialup
    @ authoring-and-publishing
    @ ftp-server
    @ network-server
    @ legacy-software-development
    @ smb-server
    @ graphics
    @ web-server
    @ mail-server
    @ server-cfg
    @ sound-and-video
    @ sql-server
    @ admin-tools
    @ news-server
    @ development-tools
    @ graphical-internet
    e2fsprogs
    grub
    lvm2
    kernel-smp
    %post
    # The Last Thing happening in Kickstart:
    # get a file via TFTP which indicates we are done.
    echo "get Kickstart_end" | /usr/bin/tftp 10.10.232.54
    Thanks for all your help, again, and responses - very helpful.
    Michael Weiner
    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Robert P. J. Day: "how to re-invoke firstboot on later reboots?"

    Relevant Pages

    • Re: problem with second NIC card.
      ... they are on the subnet. ... But it always use the first IP address to reply back the tftp ... >> client and this failed the tftp connection. ...
      (alt.os.linux)
    • installing Debian from local network
      ... I want to install Debian from local network. ... The client boots, connects dhcp, gets IP, ... connects tftp, but fails with "Error: Invalid header" traing to load image file. ...
      (Debian-User)
    • [SUMMARY]: tcpwrappers & tftpd
      ... Just to summarise that I discovered shortly after posting that it was ... due to the tftp command which i issued on my client. ...
      (SunManagers)
    • Re: My goal is a _really slow_ connection
      ... Helmut Giese wrote: ... > Below is tcpdump's result on the client. ... The timeout mechanism in TFTP is pretty dumb. ...
      (comp.os.linux.development.system)
    • Re: RIS auf dem ISA2004
      ... When ISA Server 2004 is installed, Remote Installation Services takes an extreme length of time to deploy an image. ... RIS uses Trivial File Transfer Protocol (TFTP). ... The predefined protocol has a secondary connection defined as all User Datagram Protocol ports, but this will only work when Firewall Client is installed on the client computer. ...
      (microsoft.public.de.german.isaserver)