Sponsored Content
Full Discussion: PXE boot port issue
Operating Systems HP-UX PXE boot port issue Post 302118252 by bluepluto on Monday 21st of May 2007 01:09:15 AM
Old 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

Using LOM port to start boot solaris 10

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

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. HP-UX

Auto-Port Aggregation startup fails on boot

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

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

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... (3 Replies)
Discussion started by: duckeggs01
3 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
EFIBOOTMGR(8)															     EFIBOOTMGR(8)

NAME
efibootmgr - manipulate the EFI Boot Manager SYNOPSIS
efibootmgr [ -a ] [ -A ] [ -b XXXX ] [ -B XXXX ] [ -c ] [ -d DISK ] [ -e 1|3|-1 ] [ -E NUM ] [ -g ] [ -H XXXX ] [ -i NAME ] [ -l NAME ] [ -L LABEL ] [ -n XXXX ] [ -N ] [ -o XXXX,YYYY,ZZZZ ... ] [ -O ] [ -p PART ] [ -q ] [ -t seconds ] [ -T ] [ -u ] [ -U XXXX ] [ -v ] [ -V ] [ -w ] [ -@ file ] DESCRIPTION
efibootmgr is a userspace application used to modify the Intel Extensible Firmware Interface (EFI) Boot Manager. This application can cre- ate and destroy boot entries, change the boot order, change the next running boot option, and more. Details on the EFI Boot Manager are available from the EFI Specification, v1.02 or later, available from: <URL:http://developer.intel.com> Note: efibootmgr requires that the kernel support access to EFI non-volatile variables (through /proc/efi/vars on 2.4 kernels, /sys/firmware/efi/vars on 2.6 kernels). modprobe efivars should do the trick. OPTIONS
The following is a list of options accepted by efibootmgr: -a | --active Sets bootnum active -A | --inactive Sets bootnum inactive -b | --bootnum XXXX Modify BootXXXX (hex) -B | --delete-bootnum Delete bootnum (hex) -c | --create Create new variable bootnum and add to bootorder -d | --disk DISK The disk containing the loader (defaults to /dev/sda) -e | --edd 1|3|-1 Force EDD 1.0 or 3.0 creation variables, or guess. -E | --device NUM EDD 1.0 device number (defaults to 0x80) -g | --gpt Force disk with invalid PMBR to be treated as GPT -H | --acpi_hid XXXX set the ACPI HID (used with -i) -i | --iface NAME create a netboot entry for the named interface -l | --loader NAME Specify a loader (defaults to \elilo.efi) -L | --label LABEL Boot manager display label (defaults to "Linux") -n | --bootnext XXXX Set BootNext to XXXX (hex) -N | --delete-bootnext Delete BootNext -o | --bootorder XXXX,YYYY,ZZZZ Explicitly set BootOrder (hex) -O | --delete-bootorder Delete BootOrder -p | --part PART Partition number containing the bootloader (defaults to 1) -q | --quiet Quiet mode - supresses output. --test filename Don't write to NVRAM, write to filename. -t | --timeout seconds Boot Manager timeout, in seconds. -T | --delete-timeout Delete Timeout variable. -u | --unicode | --UCS-2 pass extra command line arguments as UCS-2 (default is ASCII) -U | --acpi_uid XXXX set the ACPI UID (used with -i) -v | --verbose Verbose mode - prints additional information -V | --version Just print version string and exit. -w | --write-signature write unique signature to the MBR if needed -@ | --append-binary-args append extra variable args from file (use - to read from stdin). Data in file is appended as command line arguments to the boot loader command, with no modification to the data, so you can pass any binary or text data necessary. EXAMPLES
1. DISPLAYING THE CURRENT SETTINGS (MUST BE ROOT). [root@localhost ~]# efibootmgr BootCurrent: 0004 BootNext: 0003 BootOrder: 0004,0000,0001,0002,0003 Timeout: 30 seconds Boot0000* Diskette Drive(device:0) Boot0001* CD-ROM Drive(device:FF) Boot0002* Hard Drive(Device:80)/HD(Part1,Sig00112233) Boot0003* PXE Boot: MAC(00D0B7C15D91) Boot0004* Linux This shows: o BootCurrent - the boot entry used to start the currently running system o BootOrder - the boot order as would appear in the boot manager. The boot manager tries to boot the first active entry in this list. If unsuccessful, it tries the next entry, and so on. o BootNext - the boot entry which is scheduled to be run on next boot. This supercedes BootOrder for one boot only, and is deleted by the boot manager after first use. This allows you to change the next boot behavior without changing BootOrder. o Timeout - the time in seconds between when the boot manager appears on the screen until when it automatically chooses the startup value from BootNext or BootOrder. o Five boot entries (0000 - 0004), along with the active/inactive flag (* means active) and the name displayed on the screen. 2. CREATING A NEW BOOT OPTION An OS installer would call efibootmgr -c. This assumes that /boot/efi is your EFI System Partition, and is mounted at /dev/sda1. This creates a new boot option, called "Linux", and puts it at the top of the boot order list. Options may be passed to modify the default behavior. The default OS Loader is elilo.efi. 3. CHANGING THE BOOT ORDER Assuming the configuration in Example #1, efibootmgr -o 3,4 could be called to specify PXE boot first, then Linux boot. 4. CHANGING THE BOOT ORDER FOR THE NEXT BOOT ONLY Assuming the configuration in Example #1, efibootmgr -n 4 could be called to specify that the Linux entry be taken on next boot. 5. DELETING A BOOT OPTION Assuming the configuration in Example #1, efibootmgr -b 4 -B could be called to delete entry 4 and remove it from the BootOrder. 6. CREATING NETWORK BOOT ENTRIES A system administrator wants to create a boot option to network boot (PXE). Unfortunately, this requires knowing a little more information about your system than can be easily found by efibootmgr, so you've got to pass additional information - the ACPI HID and UID values. These can generally be found by using the EFI Boot Manager (in the EFI environment) to create a network boot entry, then using efibootmgr to print it verbosely. Here's one example: Boot003* Acpi(PNP0A03,0)/PCI(5|0)/Mac(00D0B7F9F510) ACPI(a0341d0,0)PCI(0,5)MAC(00d0b7f9f510,0) In this case, the ACPI HID is "0A0341d0" and the UID is "0". For the zx2000 gigE, the HID is "222F" and the UID is "500". For the rx2000 gigE, the HID is "0002" and the UID is "100". You create the boot entry with: efibootmgr -c -i eth0 -H 222F -U 500 -L netboot BUGS
Please direct any bugs, features, patches, etc. to Matt Domsch <Matt_Domsch@dell.com>. AUTHOR
This man page was generated by dann frazier <dannf@debian.org> for the Debian GNU/Linux operating system, but may be used by others. SEE ALSO
elilo(1) 11 August 2005 EFIBOOTMGR(8)
All times are GMT -4. The time now is 02:26 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy