PXE boot port issue Post: 302118252

Sponsored Content

Operating Systems HP-UX PXE boot port issue Post 302118252 by bluepluto on Monday 21st of May 2007 01:09:15 AM

05-21-2007

Registered User

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 !

bluepluto

View Public Profile for bluepluto

Find all posts by bluepluto

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

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

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: ...

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

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

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

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

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

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

LEARN ABOUT DEBIAN

nns_common

nameserv::common(3tcl)					       Name service facility					    nameserv::common(3tcl)

__________________________________________________________________________________________________________________________________________________

NAME

       nameserv::common - Name service facility, shared definitions

SYNOPSIS

       package require Tcl  8

       package require nameserv::common  ?0.1?

       ::nameserv::common::port

_________________________________________________________________

DESCRIPTION

       Please read Name service facility, introduction first.

       This  package is internal and of no interest to users. It provides the commands of the name service facility which are shared by the client
       and server implemented by the packages nameserv::server and nameserv (the client).

       This service is built in top of and for the package comm.  It has nothing to do with the Internet's Domain Name System. If  the	reader	is
       looking for a package dealing with that please see Tcllib's packages dns and resolv.

API

       The package exports a single command, as specified below:

       ::nameserv::common::port
	      The  result  returned  by  the  command is the id of the default TCP/IP port a nameservice server will listen on, and a name service
	      client will try to connect to.

BUGS, IDEAS, FEEDBACK
       This document, and the package it describes, will undoubtedly contain bugs and other problems.  Please report such in the category nameserv
       of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883].  Please also report any ideas for enhancements you may have for
       either package and/or documentation.

SEE ALSO

       nameserv::client(3tcl), nameserv::server(3tcl)

KEYWORDS

       client, name service, server

CATEGORY

       Networking

COPYRIGHT

       Copyright (c) 2007-2008 Andreas Kupries <andreas_kupries@users.sourceforge.net>

nns									0.1						    nameserv::common(3tcl)

10 More Discussions You Might Find Interesting

1. Solaris

Using LOM port to start boot solaris 10

Discussion started by: RottingBadger

2. UNIX for Dummies Questions & Answers

what is PXE boot bare-metal

Discussion started by: wagmare

3. UNIX for Advanced & Expert Users

Setting up a PXE Boot Server

Discussion started by: Colton

4. HP-UX

Auto-Port Aggregation startup fails on boot

Discussion started by: kknigga