DS700 Bootp

[Dieter Rossbach]

I have to change the download for some decserver 700 from mop to DHCP/BOOTP due to changes of the network infrastructure.
The VMS system runs with tcpip 5.4 ECO 4


DHCPCAP.; contains the following entry:


ds700:\
::\
:ht=Ethernet:\
:ha=08-00-2B-XX-XX-XX:\
:bf=/mom$system/wweng2.sys:\
:dn=my.domain.com:\
:ip=10.0.1.123:\
:sm=255.255.255.0:\
:ds=10.0.1.4:\
:sa=10.0.1.2:\
:ho=ds7001:


-----------


TCPIP$DHCP_RUN.LOG says

BOOTP packet from HW 08:00:2b:xx:xx:xx configured with IP 10.0.1.123
1108461925.556038 Packet arrived on Tuesday February 15 11:05:25

but no download of the image happens.

The image is at the right place and world readable:

$ dir mom$system:

Directory SYS$SYSROOT:[MOM$SYSTEM]

MNENG1.SYS;1 1152 2-SEP-1992 10:36:30.44
WWENG1.SYS;1 1156 12-FEB-2005 16:34:42.64
WWENG2.SYS;1 2023 12-FEB-2005 16:34:43.95
WWENG2T.SYS;1 3215 12-FEB-2005 16:34:45.95


I tried

:bf=mom$system:wweng2.sys
:bf=sys$sysroot:[mom$system]wweng2.sys

with the same results. The TCPIP documentation on the bf parameter is short and simple:

bf=mybootfile:

So, where is the problem?
Any ideas?

Regards

Dieter

[David B Sneddon]

Dieter,

The way we have it configured here is:

Using SYS$MANAGER:TCPIP$CONFIG
enable BOOTP, enable TFTP
move the load files into the directory pointed to
by the TCPIP$TFTP_ROOT logical (with W:RE)

Then using TCPIP, use SET BOOTP to define the
required entries in the BOOTP database.
HELP SET BOOTP within TCPIP will give you the
details about what is needed.

Regards
Dave

[Dieter Rossbach]

I tought about that, but BOOTP is not a solution for me. We run a DHCP server on that system. This requires that the bootp downloads have to be made but the DHCP server, a seperate BOOTP server is not possible (That's what I understand, reading the manuals)

Dieter

[David B Sneddon · Accepted solution]

I don't know about the DHCP side of things, but
with the BOOTP option, nothing will happen unless
the TFTP service is enabled. I think the BOOTP
service accepts the request and the TFTP service
does the work. Have you enabled TFTP?

Dave

[Martin Vorlaender]

I thought that someone would confuse things when they threw together the BOOTP and DHCP config files... ;-)

DHCP is about administration: IP address, hostname, netmasks, routes, etc.

BOOTP is about remote booting: MAC address, bootfile, etc. It utilizes TFTP as the file transfer protocol.

HTH,
Martin

[Dieter Rossbach]

Hi Martin,

I agreed. But:

1. when you configure the DHCP Server, all Bootp-parameters are intergrated into the DHCP setup and the bootp service is disabled.

2. TCPIP$DHCP_GUI let you configure a bootfile for a specific node and it:

Here an extract from the TCPIP$DHCP Manual:
-------------

8.5.3.4.3 BOOTP Parameters
The server version of DHCP fully supports the following BOOTP parameters. If a BOOTP client makes a request of the server, it acts as a BOOTP server.

Boot File
Specifies the fully qualified path name of the client's default boot image.
Boot File Server Address
Specifies the server address of the boot file.

Boot File Server Name
Specifies the host name of the server with the boot file.

Boot File Size
Specifies the length in 512-octet blocks of the default boot image for the client. Specify the file length as a number.
----------

I read this as: DHCP can act as a bootp server as well. The question is: do I need TFTP? Why are there no additional error messages?

Dieter

[David B Sneddon]

If you use the BOOTP server you have to enable TFTP
to do th eload so I would imagine that using DHCP
would be the same i.e. you have to enable TFTP.
TFTP is the protocol used for the load.

Dave

[Dieter Rossbach]

Thanks a lot:TFTP was missing. No it works, with these entries in the dhcp setup file.
Everything is easy - if you know how!

Dieter