From: Ralf van Dooren (ralf.van.dooren@asml.com)
Date: Fri May 09 2003 - 08:07:29 EDT
Hello,
Currently we are using jumpstart via rarp : a boot-server in every
network segment and a central jumpstart server.
We're migrating to jumpstart via DHCP: OBP = 3.25 . There are two
issues:
1) The inetboot_image is fetched from the tftp-server on the
DHCP-server, although I specify the root-server as vendor-specific
info. This is also sent to the client.
When I use dhcp-options "filname" and "next-server", this issue is
resolved, but I rather use the vendor-specific options. Why doesn't
it use this provided information?
2) After loading the inetboot_image, I get a the following message:
2ae00 - panic - boot: Could not mount filesystem
The filesystem which should be mounted is specified in
SUNW.root-path-name and is imho correctly shared. FYI: this is the same
directory as the 'jumpstart via rarp'.
The options I put in the vendor-specific options are taken from the NIS
bootparams.
DHCP-server is ISC DHCP v3.0 .
Any help is appreciated, i'm in a deadlock right now.
Please reply to me personally, I'll summarize to the list.
-- Ralf van Dooren e: ralf.van.dooren@asml.com _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:26:23 EDT