- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ignite and the dreaded pxe-e05
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-22-2016 08:36 AM
04-22-2016 08:36 AM
Ignite and the dreaded pxe-e05
Let's see if I can get all the details listed...
- I'm trying to recover (ignite) a IVM
- I believe (ha) I have my ignite server configured correctly
- fwiw, I can push ignite 'backups' to the ignite server from all my hpux systems (including the vm in question (when it was running))
- (The VM is not running now because the disk drive on it's host failed...but the drive has been replaced and added back to the system)
Here's the actual error I see on the VM's console:
Running LoadFile()
CLIENT MAC ADDR: CA 71 F1 26 6D 1C
CLIENT IP: 10.84.3.25 MASK: 255.255.0.0 DHCP IP: 10.84.3.26
GATEWAY IP: 10.84.1.6
Running LoadFile()
TFTP..
PXE-E05: Download buffer is smaller than requested file.
The tail-end of what I get in syslog on my Ignite server is:
Apr 22 08:11:52 aramis tftpd[13851]: receive: RRQ /opt/ignite/boot/nbp.efi octet blksize 512
Apr 22 08:11:52 aramis tftpd[13851]: send: OACK blksize 512
Apr 22 08:11:52 aramis tftpd[13852]: receive: RRQ /opt/ignite/boot/nbp.efi octet blksize 512 tsize 0
Apr 22 08:11:52 aramis tftpd[13852]: send: OACK blksize 512 tsize 31232
Apr 22 08:11:52 aramis tftpd[13852]: tftp: client does not accept options
The lines of great interest from /etc/inetd.conf on the ignite server are:
tftp dgram udp wait root /usr/lbin/tftpd tftpd -l /opt/ignite /var/opt/ignite
bootps dgram udp wait root /usr/lbin/bootpd bootpd -d 9
#instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd
The pertinent lines from /etc/bootptab on the ignite server are:
ignite-ia-defaults:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=auto
verity:\
tc=ignite-ia-defaults:\
ds=10.84.2.10 10.84.3.15:\
gw=10.84.1.6:\
ha=ca71f1266d1c:\
ip=10.84.3.25:\
sm=255.255.0.0:\
dn=domain.com
The IP address of the ignite server is 10.84.3.26. tftpd has the latest patch installed:
$Revision: @(#) tftpd R11.31_BL2014_0826_1 PATCH_11.31 PHNE_44175
The networking line from hpvmstatus are:
[Network Interface Details]
Interface Adaptor Name/Num PortNum Bus Dev Ftn Mac Address
========= ========== ========== ======= === === === =================
vswitch avio_lan vlan 2 0 1 0 ca-71-f1-26-6d-1c
Looking through my notes, it appears that I had to ignite another IVM in my environment from this ignite server in the past....and gave up because I couldn't get past this hurdle:
The Ignite manuals are very adamant about using DHCP/PXE to install 11.31. This does work – provided enough time is spent to work out the details. In particular, if there is more than one DHCP server on the network being used (10.84.n.n) (which there are) – then this gets really tricky because the system to be installed will answer to the first DHCP that contacts it (which is probably not Aramis) and the installation will fail.
Is this still what I'm running into or is there another problem?