Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Network Install PXE/BootP/TFTP Post 52006 by TioTony on Tuesday 8th of June 2004 12:14:07 AM
Old 06-08-2004
Trying to explain it all in a forum post is going to be very difficult but I will try to get you going in the write direction and give you some pointers.

First, understand how kickstart works. Redhat and other sites have plenty of docs on this subject.

Make sure you don't have a competing dhcp/bootp server on that segment of the network. If you do, you will never be able to guarantee your PXE clients get an address and boot from your server.

If you install RedHat, /root/anaconda-ks.cfg is a complete kickstart file based on the system you just installed. It's a helpful starting point

Once you have mastered that stuff, figure out how dhcp and tftp work. Not too difficult. I can't remember off the top of my head but certain tftp programs work better then others. Look at the PXE docs to see what is recommended.

H. Peter Anvin (spelling?) - you know the guy who's name pops up when ever you start linux - has some pretty detailed docs on the vmlinux and initrd stuff. I think there is a link off kernel.org. He also has a home page somewhere with tons of usefull stuff on building boot images (you know, for your PXE clients). Just search for his name.

At this point you should be ready to put all the pieces together. This is the hardest part. You have to build some images and serve them up. Basically you create a conf file that looks at the incoming DHCP/bootp request, decides if it should server out a menu or just grant an address, then "pushes" the image to the client.

I know this is not a step by step procedure but that would be pages and pages of material. Get started and when you hit a roadblock just post it and someone will be able to help you. There is a lot of trial and error in setting up a PXE server, but that is how you learn.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bootp/tftp

Hi, Setting up print queue, using SMIT on AIX And I have an option saying do I wish to make this a BOOTP/TFTP server. What exactly does this do? Thanks (3 Replies)
Discussion started by: maverick
3 Replies

2. HP-UX

HPUX -- Network Install

I have a HP box (PA RISC) rp3440. The machine does not have a CD-ROM. I need to re-install the OS. Basically a network install... How did I do a network install? Anybody know of a document for Network Installs for a HPUX 11.23? (1 Reply)
Discussion started by: truejack
1 Replies

3. SCO

Network PXE load for SCO 5.0.6

I have a Dell 1850 and trying to load OS and my applications using PXE. How can I stage new servers using Network drive. Want to move away from Tape and go towards network load. Thx Sean. (0 Replies)
Discussion started by: smoaref
0 Replies

4. Solaris

Install Solaris 10 through network

Hi all, I got a Fujitsu P650 server running on Solaris 9 and we are going to re-install Solaris 10 . W have a build server in a different IP segment. So we setup a boot server and /etc/ethers and /etc/bootparams are all updated. When I issue boot net -install, I'm getting the following... (3 Replies)
Discussion started by: mohzub
3 Replies

5. UNIX for Dummies Questions & Answers

How to install a network card

Hey guys, Sorry, this question might look stupid but I have no idea how to install a network card. My server is a Dell PowerEdge T105 with Debian 5.0 Lenny. My network card is a Broadcom NetXtreme BCM5722 Gigabit Ethernet PCI Express. I've plugged the card innside my server and I can see... (2 Replies)
Discussion started by: chebarbudo
2 Replies

6. Ubuntu

Install over network

Hello, I have a desktop with ubuntu installed and i want to install ubuntu also to the laptop over network. I have an iso image of the ubuntu and i want to use this as install source. So i installed tftpd-hpa apache2 and dhcp3-server. mkdir /var/lib/tftpboot/ubuntu mount - o loop ... (2 Replies)
Discussion started by: @dagio
2 Replies

7. Emergency UNIX and Linux Support

Disable up2date --register during PXE install

Hi folks, I really hope someone can help me (soon :) ) as I can't work out what I'm doing wrong and google is not helpful either. Basically I have to setup 20 Dell servers with RHEL 4.8 (no, not 5, must be 4.8). Of course I have tftp and I'm trying to install them via nfs with kickstart and... (4 Replies)
Discussion started by: columb
4 Replies

8. Red Hat

Disable up2date --register during PXE install

Hi, I really hope someone can help me (soon :) ) as I can't work out what I'm doing wrong and google is not helpful either. Basically I have to setup 20 Dell servers with RHEL 4.8 (no, not 5, must be 4.8). Of course I have tftp and I'm trying to install them via nfs with kickstart and PXE. OS... (0 Replies)
Discussion started by: columb
0 Replies

9. Solaris

Bootp/tftp issue neeeeeed help plz

i find a solution (2 Replies)
Discussion started by: shady_2005
2 Replies

10. Solaris

Using VM for Network Install Failing

If this question has been answered, please provide a link. We have several Old Solaris stations that don't have a DVD but a CD. We are required to upgrade the OS on these systems from Solaris 8 to Solaris 10, and since Solaris 10 no longer provides CD's we were thinking of doing a network... (3 Replies)
Discussion started by: Wrongway
3 Replies
PXE-KEXEC(8)							     PXE-Kexec							      PXE-KEXEC(8)

NAME
pxe-kexec - Read PXE configuration file and kexec entries SYNOPSIS
pxe-kexec [options] [tftp_server] DESCRIPTION
Overview pxe-kexec is a tool that fetches PXE configuration from a TFTP server, reads that PXE configuration file, prompts the user for an boot entry, downloads the specified kernel and initrd and finally tries to boot the kernel. The normal process to boot with kexec(8) is that pxe-kexec loads the kernel and invokes reboot(8). The shutdown script of the Linux distribution then executes "kexec -e" at the very end. That is not implemented everywhere. Therefore, pxe-kexec has a whitelist of Linux distributions that support reboot with kexec. If the distribution is not on that whitelist, the program quits with a warning. To bypass that warning, please use the "--igore-whitelist" parameter. You can also use the "--force" parameter to execute "kexec -e" to immediately boot the selected kernel, without invoking shutdown(8)/reboot(8). pxe-kexec meant to be used in an environment where pre-defined PXE configurations exist but the user wants to use kexec(8) instead of rebooting. Normally, the tftp_server must be specified as first argument. If there's no TFTP server specified, pxe-kexec looks in the DHCP info file for the DHCP server and uses this one as TFTP server. This only works when the TFTP server is running on the same machine as the DHCP server. ==> Please also read the section called "Update Info" <== Whitelist As mentioned previously, a whitelist of Linux distributions that support kexec-based rebooting is maintained. Currently following distributions are on the whitelist: o openSUSE, starting with version 11.0 o Ubuntu, starting with version 9.04 o Red Hat Enterprise Linux and CentOS, starting with version 5.3 o Fedora Linux, starting with version 11 o ARCH Linux Don't hesitate to send the author an email to add the distribution to the whitelist. Please include the output of "pxe-kexec --print-distribution" in that mail. OPTIONS
Following options can be specified: -h | --help Prints a short help. -v | --version Prints the version number to standard output. -f | --force Immediately load the kernel without invoking reboot(8). This does not execute shutdown scripts, i.e. does not terminate daemons, network connections etc. -L | --load-only When that option is specified, the new kernel is only loaded. No reboot is triggered and "kexec -e" is also not executed. -w | --ignore-whitelist Don't check if the detected Linux distribution is on the whitelist of distributions that have kexec(8) in their shutdown script. Please don't use that parameter without letting the author know which distribution you use and how to detect that distribution. Then the distribution can be added to the whitelist and other users profit from that experience. -l label | --label label Specifies the label that should be booted. Use that option if you already know which label you want to boot. This option implies "--quiet". -i | --interface netif Uses netif instead of the first (non-loopback and up) interface that is found. Example: "eth5". -n | --noconfirm Don't ask the user for confirmation before booting an entry. Use that option with care! -Y | --dry-run Don't execute call to kexec and don't switch the virtual console before running "kexec -e". Instead, print the information which program would be executed with which arguments to standard error. -q | --quiet Don't display the PXE messages that are added in the PXE configuration with the say keyword. Also don't display messages which PXE configuration files the downloader tries to fetch. -p | --print-distribution Only prints the detected Linux distribution and exits. For example: Type : Ubuntu Name : Ubuntu Release : 9.04 Codename : jaunty Description : Ubuntu 9.04 This option is very useful if your distribution is not on the whitelist of Linux distributions that support kexec(8) in the reboot scripts and you want to create a bugreport. This command does not require root privileges. -D | --debug Enable debugging output. That's good for finding (and fixing!) bugs. -d | --nodelete Keep downloaded files. -F | --ftp Always use FTP instead of TFTP. Useful for servers that share TFTP root and FTP root. (Passive) FTP has the advantage that it passes firewalls better than TFTP. UPDATE INFO
Updating from 0.1.x to 0.2 Compared to version 0.1.x, the syntax has changed: o The default label must now be set with the -l label option instead of the 2nd argument. Example: % pxe-kexec mydhcp.mydomain.com SLES10-install-auto is now % pxe-kexec -l SLES10-install-auto mydhcp.mydomain.com o pxe-kexec now uses the reboot mechanism by default: The kernel is loaded, then the reboot is triggered and the reboot script of the Linux distribution finally boots the kernel. This has the advantage of a clear shutdown. The program keeps a database of Linux distributions that support kexec-based reboot. If the currently active distribution is not on the whitelist, an error is printed. (That whitelist can be ignored with "--ignore-whitelist".) o To use the previous behaviour, i.e. just execute "kexec -e" in pxe-kexec at the end, you can still use the "--force" parameter. Example: % pxe-kexec mydhcp.mydomain.com is now % pxe-kexec --force mydhcp.mydomain.com o If you want to have the old "dry-run" behaviour back, which in fact only missed the last "kexec -e" step, you can use the option "--load-only". Example: % pxe-kexec --dry-run mydhcp.mydomain.com is now % pxe-kexec --load-only mydhcp.mydomain.com EXAMPLES
pxe-kexec mydhcp.mydomain.com Try to fetch the PXE configuration from mydhcp.mydomain.com, display the say messages from that configuration, prompt for an entry, letting the user confirm that entry and finally load that entry via kexec(8) and reboot via reboot(8). This only works if you distribution supports kexec-based rebooting, i.e. it is in the internal whitelist. pxe-kexec -n mydhcp.mydomain.com Same as the previous example, but omit the final confirmation step. pxe-kexec -l SLES10-install-auto mydhcp.mydomain.com Same as the first example, but don't prompt the user for the label to boot. Directly boot the SLES10-install-auto label, but letting the user confirm that he really wants to boot this! pxe-kexec -n -l SLES10-install-auto mydhcp.mydomain.com Same as the previous example, but without confirmation. pxe-kexec -f mydhcp.mydomain.com Same as the first example, but execute "kexec -e" at the end instead of invoking reboot(8). pxe-kexec -l mydhcp.mydomain.com Same as the first example, but don't trigger a reboot. Instead, the kernel is just loaded. If your distribution supports kexec-based rebooting, the kernel will be loaded on next reboot. You can also run "kexec -e" manually at any time. AUTHOR
The pxe-kexec program and documentation has been written by Bernhard Walle <bernhard@bwalle.de>. BUGS
This program has no bugs. If you find a feature that should be removed, please report to <bernhard@bwalle.de> if you don't want to create an account. SEE ALSO
kexec(8) 0.2.4 2011-03-26 PXE-KEXEC(8)
All times are GMT -4. The time now is 06:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy