Sponsored Content
Full Discussion: pxe boot server
Operating Systems Linux Red Hat pxe boot server Post 302620741 by duckeggs01 on Monday 9th of April 2012 06:06:05 AM
Old 04-09-2012
pxe boot server

Hi

Hoping someone can help ove setup a pxe/dhcp boot server for auto installs on centos My server seems to be providing dhcp fine but the installation fails to progress when it reaches the pxe boot menu. I make my selection and nothing happens. I am serving the media via http from the same system which is providing pxe/dhcp. Http seems to be working has i can open the url and get to the contents of the media.

Pxe Configuration
/var/lib/tftpboot

OS boot files (vmlinux/initrd.img)
/var/lib/tftpboot/rhel6.1

Dhcp config

default-lease-time 600;
max-lease-time 7200;

authoritative;

log-facility local7;

next-server 192.168.0.102;
filename "/pxelinux.0";
subnet 192.168.0.0 netmask 255.255.255.0 {
range dynamic-bootp 192.168.0.120 192.168.0.130;
option broadcast-address 192.168.0.255;
option routers 192.168.0.1;
allow booting;
allow bootp;
}

boot menu config (/var/lib/tftpboot/pxelinux.cfg/default)
default menu.c32
prompt 0
timeout 300

menu title ################ PXE BOOT MENU ##################

LABEL RHEL 6.1
MENU LABEL RHEL 6.1 KS
kernel rhel6.1/vmlinux append initrd=rhel6.1/initrd.img
method=http://192.168.0.102/rhel61
#ks=http://192.168.0.102/kickstart/test.cfg ksdevice=eth0 devfs=nomount

(ive commented out the kickstart stuff on purpose for now)

TFTP config

service tftp
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /var/lib/tftpboot
per_source = 11
cps = 100 2
flags = IPv4
}




The logs state the following when i boot the client;
Apr 9 12:02:35 senna dhcpd: DHCPDISCOVER from 00:0c:29:1f:24:7e via eth0
Apr 9 12:02:36 senna dhcpd: DHCPOFFER on 192.168.0.120 to 00:0c:29:1f:24:7e via eth0
Apr 9 12:02:38 senna dhcpd: DHCPREQUEST for 192.168.0.120 (192.168.0.102) from 00:0c:29:1f:24:7e via eth0
Apr 9 12:02:38 senna dhcpd: DHCPACK on 192.168.0.120 to 00:0c:29:1f:24:7e via eth0
Apr 9 12:02:38 senna in.tftpd[3162]: tftp: client does not accept options


I basically get to my pxe boot menu, but when i select the rhel option to do the install nothing happens??? Any ideas.
 

10 More Discussions You Might Find Interesting

1. HP-UX

PXE boot port issue

Hi,all: I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed ! It says : Client MAC Address: 00 18 FE 28 91 82 .....- PXE-E16: Valid PXE offer not received. Load of Core LAN Gb A failed: Not Found I use the nettl command to trace the UDP... (0 Replies)
Discussion started by: bluepluto
0 Replies

2. UNIX for Dummies Questions & Answers

what is PXE boot bare-metal

hi members i am reading RHEL and i am unable to under stand about PXE boot and bare metal (1 Reply)
Discussion started by: wagmare
1 Replies

3. UNIX for Advanced & Expert Users

Setting up a PXE Boot Server

I've set up a PXE boot server and I'm having a slight snag in the booting process. On the client machine, DHCP renders fine and TFTP seems to begin but then the system hangs. On the server, the error message "Client does not accept options" occurs -- which from reading online is a common message... (2 Replies)
Discussion started by: Colton
2 Replies

4. Solaris

boot server / install server

I have a compaq evo n400c. This computer has no cdrom or floppy drive. In order to boot from thumb drive i need to update bios. The only way to boot is network boot from my desktop. I am trying to follow a guide JumpStart Server Configuration ? Solaris 10 I am a bit confused at this steps. ... (3 Replies)
Discussion started by: kc2dws
3 Replies

5. UNIX for Advanced & Expert Users

PXE diskless boot fails

Hi, I am trying to setup a server for a diskless boot of a computer class (with ubuntu) I followed the guidelines in https://help.ubuntu.com/community/DisklessUbuntuHowto I have two computers: one is the server I installed and the other is my macbook on which I run a virtual machine... (8 Replies)
Discussion started by: yotamhc
8 Replies

6. Boot Loaders

PXE boot not taking the init= option

Hi Experts, I am doing PXE boot for my GNU/Linux device and pxelinux.0 loads the kernel as well as initrd images I have mentioned in the config file but it looks like it is not considering the init= option. Instead it starts the default INIT program. I wanted my customized init program to be... (3 Replies)
Discussion started by: learn more
3 Replies

7. Solaris

PXE boot problems in Solaris 10

Hi folks, I was trying to setup Network based NFS installation with PXE. I'm using virtual box for this purpose. I have one redhat (DHCP) server and Solaris 10 (Install server - Source) and on the other one am trying to install solaris using PXE. As in, dhcp address and boot file can be fetched... (2 Replies)
Discussion started by: vijaytrendz
2 Replies

8. Red Hat

Interactive PXE Boot Menu

I have been asked to modify our PXE server such that there will be only one entry in the pxelinux.cfg/default file, where the same kernel and initrd.img will be used regardless of what operating system is to be installed, and the user will type in the path to the kickstart file that will be used. ... (7 Replies)
Discussion started by: ceb
7 Replies

9. Red Hat

Moving boot SSD from a dead server to a new server

Hi all, We have a disk array that has the boot drive on an OCZ SSD on a PCIe card. Well, the motherboard died and we got a new motherboard. We moved the controllers, NICs, etc, to the exact same slots on the new motherboard, except now it won't boot. I guess it doesn't recognize the OS on the... (1 Reply)
Discussion started by: glowe57
1 Replies

10. Linux

Problem in displaying message on RHEL6 on EFI during PXE boot

Hi, I am doing PXE boot for RHEL6.4 on EFI and want to display custom messsage before loading vmlinuz and initrd.img, which is not working. boot server side (In case of BIOS client): In /var/lib/tftpboot/default file I am putting the message in below format: SAY hello world boot... (0 Replies)
Discussion started by: indus123
0 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 01:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy