Discussion:
I64 Network boot failure after upgrading to MU V5.3
(too old to reply)
Eberhard Heuser-Hofmann
2009-09-14 09:09:07 UTC
Permalink
Hi,

It is possible to boot the Itanium machines through network (OVMS
8.3-1H1).

I've solved the problem that only VMS TCPIP package supports the remote
boot. Under Multinet V5.2 everything works like charm but after upgrading
to
V5.3 the boot process fails.

Here is the message I'll get on the console:

Booting over the network
Loading.: openvms ethernet
Client MAC Address: 00 30 6E F4 45 ED .-
Client IP Address: 134.34.109.7
Subnet Mask: 255.255.255.240
BOOTP Server IP Address: 134.34.109.9
DHCP Server IP Address: 0.240.0.0
Boot file name: DSA16:[SYS42.SYSCOMMON.sysexe]VMS_LOADER.EFI

Retrieving File Size.
Retrieving File (TFTP)..
PXE-E05: Download buffer is smaller than requested file.


This seems to be a bug of the tftp- or of the bootp-server of Multinet.

Here is the bootp-server.configuration file that work for me:#
MULTINET:BOOTP-SERVER.CONFIGURATION database for bootp server
# Last update Mon 11/7/88 18:03
# Blank lines and lines beginning with '#' are ignored.
#
# Legend:
#
# first field -- hostname
# (may be full domain name and probably should be)
#
# hd -- home directory
# bf -- bootfile
# cs -- cookie servers
# ds -- domain name servers
# gw -- gateways
# ha -- hardware address
# ht -- hardware type
# im -- impress servers
# ip -- host IP address
# lg -- log servers
# lp -- LPR servers
# ns -- IEN-116 name servers
# rl -- resource location protocol servers
# sa -- boot server address
# sm -- subnet mask
# tc -- template host (points to similar host entry)
# td -- tftp directory
# to -- time offset (seconds)
# ts -- time servers

#
# Be careful about including backslashes where they're needed. Weird
(bad)
# things can happen when a backslash is omitted where one is intended.
#


# First, we define a global entry which specifies the stuff every host
uses.

global.dummy:\
:sm=255.255.255.240:\
:bf=VMS_LOADER.EFI:\
:ds=134.34.3.2 134.34.3.3:\
:bs=4742:\
:to=18000:


# Next, we can define different master entries for each subnet. . .

subnet13.dummy:\
:tc=global.dummy:gw=134.34.109.1:


dg4:\
:hd="DSA16:[SYS42.SYSCOMMON.sysexe]":\
:tc=subnet13.dummy:\
:ht=ethernet:\
:ha=00306ef445ed:\
:ip=134.34.109.7:\
:sa=134.34.109.9:\
:vm=auto:


Eberhard
Richard Whalen
2009-09-14 14:51:19 UTC
Permalink
MultiNet V5.3 has updated to the TFTP server support larger transfer blocks,
and it supplies SYS$MANAGER:CCLCCL$ISV_CALLOUTS.COM to support the
configuration (via cluster_config.com) of the remote boot.

I'd recommend starting with a TCPDUMP of UDP and (port 67 or port 69) to see
what is happening during the boot process to possibly locate the source of
this problem.

You might also look at the configuration of the system requesting the
remote boot. VMS creates an in-memory "disk" to load the files that it needs
to start the boot and it's possible that this error message means that the
in-memory "disk" isn't large enough.

---------------------------
Richard Whalen
Process Software
Post by Eberhard Heuser-Hofmann
Hi,
It is possible to boot the Itanium machines through network (OVMS
8.3-1H1).
I've solved the problem that only VMS TCPIP package supports the remote
boot. Under Multinet V5.2 everything works like charm but after upgrading
to
V5.3 the boot process fails.
Booting over the network
Loading.: openvms ethernet
Client MAC Address: 00 30 6E F4 45 ED .-
Client IP Address: 134.34.109.7
Subnet Mask: 255.255.255.240
BOOTP Server IP Address: 134.34.109.9
DHCP Server IP Address: 0.240.0.0
Boot file name: DSA16:[SYS42.SYSCOMMON.sysexe]VMS_LOADER.EFI
Retrieving File Size.
Retrieving File (TFTP)..
PXE-E05: Download buffer is smaller than requested file.
This seems to be a bug of the tftp- or of the bootp-server of Multinet.
Here is the bootp-server.configuration file that work for me:#
MULTINET:BOOTP-SERVER.CONFIGURATION database for bootp server
# Last update Mon 11/7/88 18:03
# Blank lines and lines beginning with '#' are ignored.
#
#
# first field -- hostname
# (may be full domain name and probably should be)
#
# hd -- home directory
# bf -- bootfile
# cs -- cookie servers
# ds -- domain name servers
# gw -- gateways
# ha -- hardware address
# ht -- hardware type
# im -- impress servers
# ip -- host IP address
# lg -- log servers
# lp -- LPR servers
# ns -- IEN-116 name servers
# rl -- resource location protocol servers
# sa -- boot server address
# sm -- subnet mask
# tc -- template host (points to similar host entry)
# td -- tftp directory
# to -- time offset (seconds)
# ts -- time servers
#
# Be careful about including backslashes where they're needed. Weird
(bad)
# things can happen when a backslash is omitted where one is intended.
#
# First, we define a global entry which specifies the stuff every host
uses.
global.dummy:\
:sm=255.255.255.240:\
:bf=VMS_LOADER.EFI:\
:ds=134.34.3.2 134.34.3.3:\
:bs=4742:\
# Next, we can define different master entries for each subnet. . .
subnet13.dummy:\
dg4:\
:hd="DSA16:[SYS42.SYSCOMMON.sysexe]":\
:tc=subnet13.dummy:\
:ht=ethernet:\
:ha=00306ef445ed:\
:ip=134.34.109.7:\
:sa=134.34.109.9:\
Eberhard
Loading...