Using this same configuration I've been able to create a custom 
jumpstart server with no issues on the Solaris 10 03/05 ....

my boot server is at 192.168.220.99/Install

ie the tools directory is at 192.168.220.99:/Install/Solaris_11/Tools
the boot directory is at 192.168.229.99:/Install/boot

my jumpstart server is at 192.168.220.99:/jumpstart

my sysidcfg server is at 192.168.220.99:/jumpstart

I added the client (Using /etc/bootparams) with the following commands:

cd /Install/Solaris_11/Tools

../add_install_client -I 192.168.220.10 -e 00:10:4b:6c:58:76 -s 
192.168.220.99:/Install \
-c 192.168.220.99:/jumpstart -p 192.168.220.99:/jumpstart test i86pc

The output of that command is below....

bash-3.00# ./bootparams_sol11.sh 
cleaning up preexisting install client "test"
removing test from bootparams
removing /etc/bootparams, since it is empty
rm: /tftpboot/ is a directory
updating /etc/bootparams
ln: cannot create /tftpboot//pxegrub.I86PC.Solaris_11-1: File exists

Create a grub floppy and edit GRUB menu to contain
the following entry:
title Solaris netinstall
  rarp
  kernel /I86PC.Solaris_11-1/multiboot kernel/unix -B install_media=ip-
addr-for-192.168.220.99:/Install,install_boot=
192.168.220.99:/Install/boot
  module /I86PC.Solaris_11-1/x86.miniroot
bash-3.00# 


I've had no luck trying to network boot from my 3C905b network card as 
when I try to rarp or ifconfig I get the following errors:

grub> ifconfig
Probing PCI nic...
[UNDI]
No Ethernet Card Found

Error 12: Invalid Device Requested

grub> rarp
Probing PCI nic...
[UNDI]

Error 12: Invalid Device Requested


When I boot from the Network Express nv_19 CD1 disk it does get most of 
the information from the nfs jumpstart server 

Unfortunately it installs from the CDRom instead of the 
Jumpstart/Install server at 192.168.220.99:/Install

I reviewed the /etc/dfs/dfstab (below)

share -F nfs -o ro,anon=0 /Install/boot
share -F nfs -o ro,anon=0 /jumpstart 

and tried changing the 1st line to:
share -F nfs -o ro,anon=0 /Install

and updating the /etc/bootparams but no difference in the install

here is my /etc/bootparams:

bash-3.00# more /etc/bootparams
test  root=sol11: install=192.168.220.99:/Install boottype=:in 
sysid_config=192.168.220.99:/jumpstart install_config=192.168.220.99:
/jumpstart rootopts=:rsize=8192 
bash-3.00# 

The jumpstart config and sysidcfg files work just find it is just that 
it installs from the wrong location

I've been able to reboot the jumpstart client and point it to the 
jumpstart server after changing the dfs mount and finish the 
installation but would prefer to do the whole installation via NFS.

Any information anyone could give me would be very much appreicated

Thx

Scott 

it should be:
client_hostname
root=jumpstart_server_hostname:/jump_package/.../../../Tools/Boot.....

In article <1123269284.393477.243020@g14g2000cwa.googlegroups.com>, 
cljlk@hotmail.com says...
> it should be:
> client_hostname
> root=jumpstart_server_hostname:/jump_package/.../../../Tools/Boot.....
> 
> 
OK I modified the mount point in /etc/dfs/dfstab to what it should be

share -F nfs -o ro,anon=0 /Install

and I modified the /etc/bootparams as per your suggestion:

bash-3.00# more /etc/bootparams
test  root=sol11:/Install/Solaris_11/Tools/Boot install=
192.168.220.99:/Install boottype=:in sysid_config=
192.168.220.99:/jumpstart 
install_config=192.168.220.99:/jumpstart rootopts=:rsize=8192 

Unfortunately the install still happens from CD instead of the NFS 
mount.

Is there anything else that needs to be modified to make the install 
happen from the NFS mount instead of the CD?

This problem only came up after the change to "Newboot" on Solaris 11.

Thx
Scott

Scott Mann <s@m.com> writes:

> In article <1123269284.393477.243020@g14g2000cwa.googlegroups.com>, 
> cljlk@hotmail.com says...
>> it should be:
>> client_hostname
>> root=jumpstart_server_hostname:/jump_package/.../../../Tools/Boot.....
>> 
>> 
> OK I modified the mount point in /etc/dfs/dfstab to what it should be
>
> share -F nfs -o ro,anon=0 /Install
>
> and I modified the /etc/bootparams as per your suggestion:
>
> bash-3.00# more /etc/bootparams
> test  root=sol11:/Install/Solaris_11/Tools/Boot install=
> 192.168.220.99:/Install boottype=:in sysid_config=
> 192.168.220.99:/jumpstart 
> install_config=192.168.220.99:/jumpstart rootopts=:rsize=8192 
>
> Unfortunately the install still happens from CD instead of the NFS 
> mount.

Is sol11 above the same as 192.168.220.99?

Here is a similar entry on our install server (sca):

lokrum  root=sca: install=sca:/export/home/jumpstart/se_nv19_i386 boottype=:in   rootopts=:rsize=8192 

and my grub entry for net install is

title Solaris netinstall
rarp
root (nd)
kernel /I86PC.Solaris_11-1/multiboot kernel/unix -B install_media=XX.YY.ZZ.UU:/export/home/jumpstart/se_nv19_i386
module /I86PC.Solaris_11-1/x86.miniroot

where XX.YY.ZZ.UU is the IP address of the install server.

Note: I am not doing jumpstart in my case, just a good old net-install.

HTH, Dragan

-- 
Dragan Cvetkovic, 

To be or not to be is true. G. Boole      No it isn't.  L. E. J. Brouwer

!!! Sender/From address is bogus. Use reply-to one !!!

In article <lmfytogm5s.fsf@privacy.net>, me@privacy.net says...
> Scott Mann <s@m.com> writes:
> 
> > In article <1123269284.393477.243020@g14g2000cwa.googlegroups.com>, 
> > cljlk@hotmail.com says...
> >> it should be:
> >> client_hostname
> >> root=jumpstart_server_hostname:/jump_package/.../../../Tools/Boot.....
> >> 
> >> 
> > OK I modified the mount point in /etc/dfs/dfstab to what it should be
> >
> > share -F nfs -o ro,anon=0 /Install
> >
> > and I modified the /etc/bootparams as per your suggestion:
> >
> > bash-3.00# more /etc/bootparams
> > test  root=sol11:/Install/Solaris_11/Tools/Boot install=
> > 192.168.220.99:/Install boottype=:in sysid_config=
> > 192.168.220.99:/jumpstart 
> > install_config=192.168.220.99:/jumpstart rootopts=:rsize=8192 
> >
> > Unfortunately the install still happens from CD instead of the NFS 
> > mount.
> 
> Is sol11 above the same as 192.168.220.99?
> 
> Here is a similar entry on our install server (sca):
> 
> lokrum  root=sca: install=sca:/export/home/jumpstart/se_nv19_i386 boottype=:in   rootopts=:rsize=8192 
> 
> and my grub entry for net install is
> 
> title Solaris netinstall
> rarp
> root (nd)
> kernel /I86PC.Solaris_11-1/multiboot kernel/unix -B install_media=XX.YY.ZZ.UU:/export/home/jumpstart/se_nv19_i386
> module /I86PC.Solaris_11-1/x86.miniroot
> 
> where XX.YY.ZZ.UU is the IP address of the install server.
> 
> Note: I am not doing jumpstart in my case, just a good old net-install.
> 
> HTH, Dragan
> 
> 

Yes sol11 is 192.168.220.99...

Part of the problem is how my network card works at the grub prompt..
(it doesn't and I'm not sure why).

The card I'm using is a 3C905b-tx card it works great once the operating 
system is up and running but I get nothing at the grub prompt???

if I type rarp or ifconfig at the grub menu I get the following..

grub> rarp
Probing pci nic... 
[UNDI]

Error 12: Invalid device requested

So what I've done is wait till the boot menu comes up and select 

2.	Custom Jumpstart 

It THEN configures the ip address of the nic using /etc bootparams it 
gets the sysidcfg file and profile to build the server with no issues. 

This shows that the ip address is set correct and the NFS client is 
working fine.

But then it starts the install and uses the CD as the install_media 
instead of the NFS server.

I will try adding the install_media switch at the grub menu but don't 
know if it will work as the nic is not working at that point (see 
problem above)

What kinds of nic's is everyone else using out there? I switched most of 
my nics to 3Com's because they were on the approved hardware list. 

Thx
Scott

In comp.unix.solaris Scott Mann <s@m.com> wrote:
> In article <1123269284.393477.243020@g14g2000cwa.googlegroups.com>, 
> cljlk@hotmail.com says...
>> it should be:
>> client_hostname
>> root=jumpstart_server_hostname:/jump_package/.../../../Tools/Boot.....
>> 
>> 
> OK I modified the mount point in /etc/dfs/dfstab to what it should be

> share -F nfs -o ro,anon=0 /Install

What was wrong with it before?  The ro, or the anon?

Is it still doing the 'cp failure' error?

If the 'ro' wasn't in place in the past and you're still getting that
error, then your jumpstart image may have been corrupted by a previous
jumpstart attempt.

You should redo the 'setup_install_server' to replace the image.

-- 
Darren Dunham                                           ddunham@taos.com
Senior Technical Consultant         TAOS            http://www.taos.com/
Got some Dr Pepper?                           San Francisco, CA bay area
         < This line left intentionally blank to confuse you. >

In article <WJTIe.773$Z87.619@newssvr14.news.prodigy.com>, 
ddunham@redwood.taos.com says...
> In comp.unix.solaris Scott Mann <s@m.com> wrote:
> > In article <1123269284.393477.243020@g14g2000cwa.googlegroups.com>, 
> > cljlk@hotmail.com says...
> >> it should be:
> >> client_hostname
> >> root=jumpstart_server_hostname:/jump_package/.../../../Tools/Boot.....
> >> 
> >> 
> > OK I modified the mount point in /etc/dfs/dfstab to what it should be
> 
> > share -F nfs -o ro,anon=0 /Install
> 
> What was wrong with it before?  The ro, or the anon?
> 
> Is it still doing the 'cp failure' error?
> 
> If the 'ro' wasn't in place in the past and you're still getting that
> error, then your jumpstart image may have been corrupted by a previous
> jumpstart attempt.
> 
> You should redo the 'setup_install_server' to replace the image.
> 
> 


when using the add_install_client command like below...

cd /Install/Solaris_11/Tools

../add_install_client -I 192.168.220.10 -e 00:10:4b:6c:58:76 -s 
192.168.220.99:/Install \
-c 192.168.220.99:/jumpstart -p 192.168.220.99:/jumpstart test i86pc

it created a line in the dfstab using the /Install/boot directory
share -F nfs -o ro,anon=0 /Install/boot

which means I can't do a mount to the /Install directory so I changed it 
to ...

share -F nfs -o ro,anon=0 /Install

At least that way I can reboot after CD1 and I can do the rest of the 
install via NFS it prompts when you reboot and I finish the rest of the 
install by pointing the install to 192.168.220.99:/Install it finishs 
the rest of the install with no problem

Scott