06-04-2010
But it should already have an IP address - it gets it during boot from DHCP....
(I see that happening at the beginning of boot - it gets the IP I assigned to its MAC address)
Last edited by yotamhc; 06-04-2010 at 02:29 PM..
10 More Discussions You Might Find Interesting
1. HP-UX
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
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
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. Boot Loaders
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
5. Solaris
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
6. Red Hat
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
7. Red Hat
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... (3 Replies)
Discussion started by: duckeggs01
3 Replies
8. Solaris
One of our T5220 servers fail to boot due to following error:
ERROR: The following devices are disabled:
XAUI1
XAUI0
I can't see any disabled components in SP console, any idea what is the problem? (1 Reply)
Discussion started by: belalr
1 Replies
9. Red Hat
Hi guys,
I've been trying to set up a server for disk-less booting of remote machines on a network. The server host OS is RHEL6 and I have configured dhcp, tftp and nfs services which are proven to be working since I am able to install RHEL6 through pxe boot. Now I want it to serve for disk-less... (0 Replies)
Discussion started by: aninmuk
0 Replies
10. Linux
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
dhcp(5) Standards, Environments, and Macros dhcp(5)
NAME
dhcp - Dynamic Host Configuration Protocol
DESCRIPTION
Dynamic Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they
boot. DHCP uses a client/server mechanism: servers store configuration information for clients, and provide that information upon a
client's request. The information can include the client's IP address and information about network services available to the client.
This manual page provides a brief summary of the Solaris DHCP implementation.
Solaris DHCP Client
The Solaris DHCP client is implemented as background daemon, dhcpagent(1M). This daemon is started automatically during bootup if there
exists at least one dhcp.interface file in /etc. Only interfaces with a corresponding /etc/dhcp.interface file are automatically configured
during boot. Network parameters needed for system configuration during bootup are extracted from the information recieved by the daemon
through the use of the dhcpinfo(1) command. The daemon's default behavior can be altered by changing the tunables in the /etc/default/dhc-
pagent file. The daemon is controlled by the ifconfig(1M) utility. Check the status of the daemon using the netstat(1M) and ifconfig(1M)
commands.
Solaris DHCP Server
The Solaris DHCP server is implemented as a background daemon, in.dhcpd(1M). This daemon can deliver network configuration information to
either BOOTP or DHCP clients. The Solaris DHCP service can be managed using the dhcpmgr(1M) GUI or the command line utilities dhcpcon-
fig(1M), dhtadm(1M), and pntadm(1M).
DHCP Configuration Tables
The Solaris DHCP server stores client configuration information in the following two types of tables:
dhcptab tables Contain macros and options (also known as symbols), used to construct a package of configuration information to
send to each DHCP client. There exists only one dhcptab for the DHCP service. The dhcptab(4) can be viewed and mod-
ified using the dhtadm(1M) command or dhcpmgr(1M) graphical utility. See dhcptab(4) for more information about the
syntax of dhcptab records. See dhcp_inittab(4) for more information about the DHCP options and symbols.
DHCP network tables DHCP network tables, which contain mappings of client IDs to IP addresses and parameters associated with those
addresses. Network tables are named with the IP address of the network, and can be created, viewed, and modified
using the pntadm command or dhcpmgr graphical utility. See dhcp_network(4) for more information about network
tables.
SEE ALSO
dhcpinfo(1), dhcpagent(1M), dhcpconfig(1M), dhcpmgr(1M), dhtadm(1M), ifconfig(1M), in.dhcpd(1M), netstat(1M), pntadm(1M), syslog(3C),
dhcp_network(4), dhcptab(4), dhcpsvc.conf(4), dhcp_inittab(4), dhcp_modules(5)
Solaris DHCP Service Developer's Guide
Alexander, S., and R. Droms. RFC 2132, DHCP Options and BOOTP Vendor Extensions. Silicon Graphics, Inc. Bucknell University. March 1997.
Droms, R. RFC 1534, Interoperation Between DHCP and BOOTP. Bucknell University. October 1993.
Droms, R. RFC 2131, Dynamic Host Configuration Protocol. Bucknell University. March 1997.
Wimer, W. RFC 1542, Clarifications and Extensions for the Bootstrap Protocol. Carnegie Mellon University. October 1993.
SunOS 5.10 13 Mar 2001 dhcp(5)