C H A P T E R  3

Setting Up a Flash PROM Boot Server

The procedures in this chapter are optional. Use this chapter only if you want to set up a boot server so that clients can boot the Flash PROM utility from the network. This chapter does not contain the procedure for setting up a client server. See your software documentation for the client server setup procedure.



Note - These procedures apply only to networks running the Solaris Operating System.




3.1 Using Volume Manager to Install Flash PROM Packages

If Volume Manager is running on your system, you can use its automount CD feature when installing flash PROM packages to your server. Use the following procedure to determine whether Volume Manager is running on your system, then install the packages either with or without Volume Manager.

3.1.1 Checking Volume Manager Status

1. Use the operating system ps utility to determine whether Volume Manager (vold) is running.

Consult the man pages for ps if necessary.

2. If Volume Manager is not running, but you would like to use its automount CD feature:

a. Log in as superuser with the su command and your superuser password.

b. As superuser, start Volume Manager. Type:
/etc/init.d/volmgt start

3.1.2 Installing Packages With Volume Manager

1. Insert the Flash Update CD into the CD-ROM drive.

The CD is mounted automatically by Volume Manager.
The mount point is /cdrom.

2. To add a package, type:
/usr/sbin/pkgadd -d <device> -R <root_path> <package_name>


For example:
/usr/sbin/pkgadd -d
/cdrom/cdrom0/s0/SMCC -R /flash SUNWflnel

The <root_path> depends on how the partitions were set up. To determine your <root_path>, look at the root path that is specified in the server's
/etc/bootparams
file. In the example above, the packages would be directed to the previously nonexisting standalone flash directory.



caution icon

Caution - Always use the -R <root_path> option in the pkgadd command and specify a path other than "/" (top-level root directory). If the -R option is left out or if the "/" directory is specified then the system running the pkgadd command will no longer boot to the Solaris Operating System. That is, you will have to reload the Solaris Operating System completely, or recover from your backup resources.



3. Remove the CD from the CD-ROM drive. Type:

eject cdrom

3.1.3 Installing Packages Without Volume Manager



Note - You must run all of the commands in this procedure as superuser.



1. Use the su command and your superuser password to become superuser.

2. If the /cdrom directory is not already present, create it. Type:

mkdir /cdrom

3. Mount the CD. Type:
mount -o ro -F hsfs /dev/dsk/c0t6d0s0 /cdrom

4. Change directories to the CD. Type:

cd /cdrom/SMCC

5. To add a package, type:
/usr/sbin/pkgadd -d <device> -R <root_path> <package_name>


For example:
/usr/sbin/pkgadd -d /cdrom/cdrom0/s0/SMCC -R /flash SUNWflnel

The <root_path> depends on how the partitions were set up. To determine your <root_path>, look at the root path that is specified in the server's
/etc/bootparams
file. In the example illustrated above, the packages would be directed to the previously nonexisting standalone flash directory.



caution icon

Caution - Always use the -R <root_path> option in the pkgadd command and specify a path other than "/" (top-level root directory). If the -R option is left out or if the "/" directory is specified then the system running the pkgadd command will no longer boot to the Solaris Operating System. That is, you will have to reload the Solaris Operating System completely, or recover from your backup resources.



6. When finished, exit the cdrom directory. Type:

cd /

7. Unmount the CD. Type:

umount /cdrom

8. Remove the CD from the CD-ROM drive. Type:

eject cdrom


3.2 Booting the Utility From the Server



Note - Do not move files from the directories into which pkgadd has placed them.



3.2.1 Booting the Utility as a Client

The following instructions assume you copied the system binary for your platform into the root_path directory specified in the pkgadd command line:

single-step bulletSet up your clients to boot from the system binary for your platform.

3.2.2 Booting the Utility as a Server

If the flash PROM utility package was installed on a standalone basis, you must supply some or all of the root_path information in your boot command.


For example, if your boot disk is disk3 and your system is an Ultra 1 Creator 3D, Model 200E, to boot the utility from the PROM monitor, type:
boot disk3 flash/SUNW,501-4134-latest


This command is equivalent to typing:
boot disk3 /platform/sun4u/flash/SUNW,501-4134-latest

 


3.3 Package Names and Contents

Two packages are available for each hardware platform:

Typically, only the latest revisions are used, meaning that only the package ending with "l" is added. See "Invalid Cross-Reference Format" for platform numbers and packages.



Note - Do not add a "b" package or load old firmware revisions unless your system administrator directs you to do so.



If you are directed to load an old firmware revision, you must boot the image directly:

# boot cdrom flash/SUNW,501-xxxx-yy

In the above example, xxxx is a number that represents the platform, and yy is a number that indicates the specific firmware revision to be booted.

 


TABLE 3-1 Platform Numbers and Packages

Platform

Number

Packages

Ultra 1
Model 140

SUNW,501-2836

SUNWflnel

SUNWflneb

Ultra 1
Model 170

SUNW,501-3082

SUNWflnel

SUNWflneb

Ultra 1 Creator
Model 140E

SUNW,501-4291

SUNWfle1l

SUNWfle1b

Ultra 1 Creator
Model 170E

SUNW,501-2486

SUNWflell

SUNWflelb

Ultra 1 Creator
Model 200E

SUNW,501-4134

SUNWfle2l

SUNWfle2b

Ultra 1 Creator 3D
Model 140E

SUNW,501-4291

SUNWfle1l

SUNWfle1b

Ultra 1 Creator 3D
Model 170E

SUNW,501-2486

SUNWflell

SUNWflelb

Ultra 1 Creator 3D
Model 200E

SUNW,501-4134

SUNWfle2l

SUNWfle2b

Ultra Enterprise 1
Model 140

SUNW,501-2836

SUNWflnel

SUNWflneb

Ultra Enterprise 1
Model 170

SUNW,501-3082

SUNWflnel

SUNWflneb

Ultra 2 Creator,
all models

SUNW,501-3132

SUNWflpul

SUNWflpub

Ultra 2 Creator 3D,
all models

SUNW,501-3132

SUNWflpul

SUNWflpub

Ultra Enterprise 2,
all models

SUNW,501-3132

SUNWflpul

SUNWflpub

Ultra 5/Ultra 10,
all models

SUNW,375-0009

SUNWfldal

SUNWfldab

Ultra 30,
all models

SUNW,501-3139

SUNWflqul

SUNWflqub

Ultra 60/Sun Enterprise 220R,all models

SUNW,501-4450

SUNWfldel

SUNWfldeb

Ultra 80/Sun Enterprise 420R,all models

SUNW,501-5168

SUNWflqrl

SUNWflqrb

Sun Enterprise 250,
all models

SUNW,501-4681

SUNWfljal

SUNWfljab

Ultra Enterprise 450,
all models

SUNW,501-2996

SUNWfltal

SUNWfltab

Sun Blade 100

SUNW,501-0096

SUNWflgrb

SUNWflgrl

Sun Blade 1000

SUNW,501-4143

SUNWflexb

SUNWflexl

Sun Fire 280R

SUNW,501-4143

SUNWflexb

SUNWflexl

Sun Netra T4

SUNW,501-4143

SUNWflexb

SUNWflexl

Sun Fire V480

SUNW,501-5819

SUNWflchb

SUNWflchl

Sun Fire V490

SUNW,501-5819

SUNWflchb

SUNWflchl

Sun Fire V880

SUNW,501-4300

SUNWfldkb

SUNWfldkl

Sun Fire V890

SUNW,501-4300

SUNWfldkb

SUNWfldkl