05-21-2007
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 package, it writes:
^^^^^^^^^^^^^^^^^^^^^^Gigabit Ethernet LAN/9000 Networking^^^^^^^^^^^^^^^^^^@#%
Timestamp : Fri Apr 27 EAT 2007 16:57:52.714302
Process ID : [ICS] Subsystem : IGELAN
User ID ( UID ) : -1 Trace Kind : PDU IN TRACE
Device ID : 0 Path ID : -1
Connection ID : 0
Location : 00123
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
=================================== Ethernet ====================================
Source : 00-18-fe-28-91-82 [I] [ ]
Dest : ff-ff-ff-ff-ff-ff [B] [ ] TRACED LEN: 590
Date : Fri Apr 27 16:57:52.714302 EAT 2007
================================ IP Header (inbound -- [ICS]) ================
Source: 0.0.0.0 (A) Dest: 255.255.255.255(E)
len: 576 ttl: 16 proto: 17 cksum: 0xf3ee id: 0xb4bf
flags: NONE tos: 0x0 hdrlen: 20 offset: 0x0 optlen: 0
-------------------------------- UDP Header ----------------------------------
sport: 68 --> dport: 4109 data len: 548 chksum: 0x3c04
-------------------------------- BOOTP Request -------------------------------
trans id : 0x13880000 seconds : 159 hops : 0
server IP: NULL client IP: NULL your IP: NULL
gateway IP: NULL h/w type : 1 flags : 32768
client h/w addr : 00-18-fe-28-91-82
server name : NULL
file name : NULL
vendor specific : VM_RFC1048
From the document, I got that the client port is 68, the server port should be 67, I mean the DHCP server listening port, while in the UDP package, it shows 4109.
Thanks !
10 More Discussions You Might Find Interesting
1. Solaris
Hi.
Hopefully a question with a very short answer.
Previously I have been using a windows hyperterminal to boot solaris 10 systems (SunFire) over a serial lom cable.
I want to perform the same operation from a solaris 8 machine to boot solaris 10. Can anyone tell me what commands I should... (2 Replies)
Discussion started by: RottingBadger
2 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. HP-UX
I have a machine running HP-UX 11.23 (PARISC) and APA startup fails on boot. This is found in /etc/rc.log:
Configure Auto-Port Aggregation(LAN Monitor) interfaces
Output from "/sbin/rc2.d/S343hplm start":
----------------------------
get_start_dlpi_version: failed, errno is 22
ERROR: ... (1 Reply)
Discussion started by: kknigga
1 Replies
5. UNIX for Advanced & Expert Users
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
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
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
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
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
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
LEARN ABOUT SUSE
dhcpdump
DHCPDUMP(1) General Commands Manual DHCPDUMP(1)
NAME
dhcpdump - DHCP packet dumper
SYNOPSIS
dhcpdump [-h regular-expression]
DESCRIPTION
This command parses the output of tcpdump to display the dhcp-packets for easier checking and debugging.
USAGE
tcpdump -lenx -s 1500 port bootps or port bootpc | dhcpdump
If you want to filter a specific Client Hardware Address (CHADDR), then you can specifiy it as a regular expressions:
tcpdump -lenx -s 1500 port bootps or port bootpc | dhcpdump -h ^00:c0:4f
This will display only the packets with Client Hardware Addresses which start with 00:c0:4f.
OUTPUT
TIME: 15:45:02.084272
IP: 0.0.0.0.68 (0:c0:4f:82:ac:7f) > 255.255.255.255.67 (ff:ff:ff:ff:ff:ff)
OP: 1 (BOOTPREQUEST)
HTYPE: 1 (Ethernet)
HLEN: 6
HOPS: 0
XID: 28f61b03
SECS: 0
FLAGS: 0
CIADDR: 0.0.0.0
YIADDR: 0.0.0.0
SIADDR: 0.0.0.0
GIADDR: 0.0.0.0
CHADDR: 00:c0:4f:82:ac:7f:00:00:00:00:00:00:00:00:00:00
SNAME: .
FNAME: .
OPTION: 53 ( 1) DHCP message type 3 (DHCPREQUEST)
OPTION: 54 ( 4) Server identifier 130.139.64.101
OPTION: 50 ( 4) Request IP address 130.139.64.143
OPTION: 55 ( 7) Parameter Request List 1 (Subnet mask)
3 (Routers)
58 (T1)
59 (T2)
At the option field, the first field is the value of the option, the second one (between brackets) is the length of the option-datafield,
the third field is the name of the option, the fourth field is the data of the option.
RETURN VALUES
Always 0.
NOTES
Privileged access is often needed for tcpdump.
BUGS
Not all the parameter options are printed verbose, because of lack of documentation. Not all the options are tested, because of lack of
clients/servers with these options. If you have a dump of one of them, please send them to me and I'll incorperate them.
THANKS TO
Ralph Droms and Ted Lemons "The DHCP Handbook", ISBN 1-57870-137-6.
Peter Apian-Bennewitz <apian@ise.fhg.de> for his Client Hardware Address filtering
AUTHOR
Edwin Groothuis, edwin@mavetju.org (http://www.mavetju.org)
SEE ALSO
dhcpd(8), tcpdump(1), RFC2132
November 21, 2003 November 21, 2003 DHCPDUMP(1)