Ignite UX boot error

[Alexandre Sobral]

All,
I have an Itanium Server RX7640 with Hp-UX 11.23. I have an Ignite-UX Server and I am trying to boot a client by net.
I execute the follow command: vparboot -p "client_server" -I
I´ve already configured my /etc/booptab with IP address and MAC address but i am receiving the message:

blk8 : Acpi(HWP0002,PNP0A03,C)/Pci(1|1)/Scsi(Pun2,Lun0)
01 Acpi(HWP0002,PNP0A03,101)/Pci(1|0)/Pci(6|0)/Mac(001CC43AFA7A)
02 Acpi(HWP0002,PNP0A03,101)/Pci(1|0)/Pci(6|1)/Mac(001CC43AFA7B)
03 Acpi(HWP0002,PNP0A03,102)/Pci(1|0)/Pci(6|0)/Mac(0015605E1975)
04 Acpi(HWP0002,PNP0A03,104)/Pci(1|0)/Mac(001A4B06E8E2)
05 Acpi(HWP0002,PNP0A03,104)/Pci(1|1)/Mac(001A4B06E8E3)
06 Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(6|0)/Mac(001CC43AFA90)
07 Acpi(HWP0002,PNP0A03,1)/Pci(1|0)/Pci(6|1)/Mac(001CC43AFA91)
08 Acpi(HWP0002,PNP0A03,2)/Pci(1|0)/Pci(6|0)/Mac(0015605E1965)
09 Acpi(HWP0002,PNP0A03,4)/Pci(1|0)/Mac(001A4B06EB0A)
10 Acpi(HWP0002,PNP0A03,4)/Pci(1|1)/Mac(001A4B06EB0B)
Select Desired LAN: 09

Client MAC Address: 00 1A 4B 06 EB 0A .....-

PXE-E16: Valid PXE offer not received.

[Steven E. Protter]

Shalom,

Last I checked, Ignite doesn't support PXE though tis would be logical in the future.

I'm wondering if this vpar system is on the same subnet as the Ignite server or if you have set up a boothelper system to help the boot.

SEP

[Eric SAUBIGNAC]

Hi Alexandre

Don't forget to kill "bootpd" after each modification of /etc/bootptab.

Are the client and bootp server on the same LAN ? If not, you will have some more configuration to do.

If you are on the same lan, you can verify that the ignite/bootpd server "sees" the bootp request :

- boot client and stop at "select desired lan:"
- on bootp server, kill bootpd and do a "tail -f /var/adm/syslog/syslog.log"
- go back on the client and continue the process by selecting a lan card.
- you should see in syslog that bootp is executed when the request is received bye the server.

If you want more information in syslog, you may modify /etc/inetd.conf do add a more verbose option (-d) to bootpd. If you do so, don't forget "inetd -c"

Eric

[Prashanth.D.S]

Hi,

When the above error is seen during a PXE boot, one of the following may be true (this is not an exhaustive list):

The response from the DHCP server did not contain enough information to continue the PXE boot.
No PXE boot response was received.
Additional errors may be printed after this PXE error to show what the problem is related to. When using /etc/bootptab to define Ignite-UX boot services, a number of problems can be introduced resulting in this error. The following checklist can be used to isolate the problem:

Check inetd:
Check /etc/inetd.conf to make certain bootps and tftp entries have been un-commented. Make certain the tftp line contains /opt/ignite and /var/opt/ignite paths.
Signal inetd to reread the configuration files (inetd -c) after the files are edited. If the inetd process is not running, start it using:
# /sbin/init.d/inetd start

Check /var/adm/syslog/syslog.log to make certain inetd was restarted and no bad messages are found. Specifically check for messages from bootpd and tftpd.
Check for entries in /var/adm/inetd.sec that may cause inetd to deny service to certain clients.
Check bootpd:
Check the /etc/bootptab entry. Make certain the MAC address matches the client MAC address. Use dhcptools -v to validate the format of the /etc/bootptab file.
Check for entries in /etc/dhcpdeny to ensure that bootpd is not set to deny service for particular clients.
Check /var/adm/syslog/syslog.log for a message from bootpd that indicates it was started when a bootpd packet was received. If packets were not received, use a tool such as tcpdump to check for network packets. Verify that bootp packets are being seen by the system. If you do not have tcpdump on your system, you can download it for either HP-UX 11i v1 or HP-UX 11i v2 from the HP Internet Express Web site at:
https://h20293.www2.hp.com/portal/swdepot/try.do?productNumber=HPUXIEXP1111

or

http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?ProductNumber=HPUXIEXP1123

Check to see if there are other systems on the network that may also be replying to the booting client system.
Check to see if the system booting is on a different subnet to the bootp server to ensure that any router between the two allows the forwarding of bootp requests. The configuration is router specific.
Check tftpd:
Check the tftp line in /etc/inetd.conf to make certain that the /opt/ignite and /var/opt/ignite directories are listed.
Check the tftpd connection manually by using the tftp command, for example:
$ tftp [server-name]
tftp> get /opt/ignite/boot/nbp.efi /tmp/nbp.efi
Received [n ] bytes in [s] seconds

tftp> quit

Best Regards,
Prashanth