Hmmmm... I've not done much in the way of testing the bootparamd behavior
in a long while.  Using DHCP is so much nicer if you've got it available.

This is only a workaround suggestion, but try using a dhcpd setup to see
if this relieves the problem.  If your bootserver is NetBSD based, edit
the dhcpd line in /etc/rc.conf to be dhcpd=YES.  You may also want to
disable the bootparamd daemon during the test, or at least the entries
specific to your VAXstation 3500.


--- An example /etc/dhcpd.conf follows ---

use-host-decl-names on;
server-name "vax-bootserver";
option domain-name "mydomain.com";
option domain-name-servers 192.168.123.4;

subnet 192.168.123.0 netmask 255.255.255.0 {
  option subnet-mask 255.255.255.0;
  option broadcast-address 192.168.123.255;
  option routers 192.168.123.1;
}

host vax-client1 {
  hardware ethernet 08:00:2b:12:34:56;
  fixed-address 192.168.123.10;
  option root-path "/export/vax-client1/root";
  option host-name "vax-client1";
}

host vax-client2 {
  hardware ethernet 08:00:2b:ab:cd:ef;
  fixed-address 192.168.123.11;
  option root-path "/export/vax-client2/root";
  option host-name "vax-client2";
} 

--- end of example /etc/dhcpd.conf ---


-brian.
---
Brian "JARAI" Chase | http://world.std.com/~bdc/ | VAXZilla LIVES!!!