Network Install using PXE Solaris 10 x86 NV 4/05
This is notes and procedure I used to do a Solaris 10 x86 network install using PXE.
This does not include the Jumpstart profile. 
dacrud@gmail.com - Derek Crudgington
-

INTRODUCTION
PART I: COPY CDS TO HARD DRIVE
PART II: CLIENT SETUP & DHCP
PART III: CLIENT BOOT & PROBLEMS I CAME ACROSS

------------------------------------------------------------------------------------

INTRODUCTION

This is the exact process I used to setup a Solaris 10 x86 network install
with PXE without Jumpstart profile.  This was a pretty hard task to accomplish and
I came to realize it was very picky in the setup.  If you dont follow these exact
steps it probably won't work for you.  The hardware setup I used was:

SERVER:

Generic x86 intel PC with SCSI disk
HOST: solaris
IP: 192.168.1.200

CLIENT:

Poweredge 750 with SCSI disks
NIC: Intel PRO CT1000
PXE: Intel Boot Agent GE v1.2.16 PXE 2.1 (build 083) (wfm 2.0)
IP: 192.168.1.214

------------------------------------------------------------------------------------

PART I: COPY CDS TO HARD DRIVE

On the server you are making the install server, make a directory to store the CD
contents:

# mkdir /export/home/installserver

Put in the Solaris 10 x86 CD 1 and goto the Tools folder (/cdrom/cdrom0/s2/Solaris_10.1/Tools),
run:

# ./setup_install_server /export/home/installserver

This will see if you have enough space there, and if so copy the CD image to the
disk.  It will take a while.  Eject the CD when it's done:

# eject              

Put in Solaris CD 2 and navigate to:

# cd /cdrom/cdrom0/Solaris_10.1/Tools/

Now run ./add_to_install_server to add Solaris 10 CD2 to the path:

You can repeat these steps for each Solaris 10 CD you want to install, I went ahead
and did all of them.

# ./add_to_install_server /export/home/installserver/

------------------------------------------------------------------------------------

PART II: CLIENT SETUP & DHCP

# cd /export/home/installserver/Solaris_10.1/Tools

# ./add_install_client -d -s 192.168.1.200:/export/home/installserver SUNW.i86pc i86pc
making /tftpboot
copying inetboot to /tftpboot
copying nbp to /tftpboot

To enable SUNW.i86pc in the DHCP server, ensure that
the following Sun vendor-specific options are defined
(SinstNM, SinstIP4, SinstPTH, SrootNM, SrootIP4,
SrootPTH, SbootURI and optionally SjumpCF and SsysidCF),
and add a macro to the server named SUNW.i86pc,
containing the following option values:

  Install server      (SinstNM)  : 192.168.1.200
  Install server IP   (SinstIP4) : ip-addr-for-192.168.1.200
  Install server path (SinstPTH) : /export/home/installserver
  Root server name    (SrootNM)  : solaris
  Root server IP      (SrootIP4) : 192.168.1.200
  Root server path    (SrootPTH) : /export/home/installserver/Solaris_10.1/Tools/Boot
  Boot file           (BootFile) : nbp.SUNW.i86pc

If not already configured, enable PXE boot by creating
a macro called PXEClient:Arch:00000:UNDI:002001
which contains the following values:
  Boot server IP      (BootSrvA) : 192.168.1.200
This macro will be explicitly requested by the PXE boot.

Above it says to add add the 'BootFile' option to the macro 'SUNW.i86pc' but this
didn't work for me and I had to add it to the 'PXEClient:Arch:00000:UNDI:002001'
macro as well.  Otherwise you will get "PXE-E53: no boot filename received" error
when the client trys to boot.

You can add all of this by using the DHCP Manager (/usr/sadm/admin/bin/dhcpmgr).
It's a GUI program and pretty easy to configure.  If you're running it for the first
time it will ask you a series of questions just use the defaults.  Once it is setup,
you can add the options by going to the 'Options' tab and going to 
Edit->Create.  After the options are added, add the macros 'SUNW.i86pc' and
'PXEClient:Arch:00000:UNDI:002001' with the right options above.

When adding the options Be sure to add them as 'SUNW.i86pc' Vendor Client Class
and use http://docs.sun.com/app/docs/doc/817-5504/6mkv4nh2d?a=view as a source
of information for what Code, Granutarity, and Maximum settings to use for each
option.

Also make sure all of your options are the correct paths or it will fail.

------------------------------------------------------------------------------------

PART III: CLIENT BOOT & PROBLEMS I CAME ACROSS

After all is setup correctly, tell your client to boot off the network card and
watch it go into the Solaris install process.

::RANDOM PROBLEMS I CAME ACROSS TO GET THIS WORKING::

If I didn't add the 'BootFile' option to the macro 'PXEClient:Arch:00000:UNDI:002001'
the client would not boot and error with: "PXE-E53: no boot filename received".