Sun Management Center 4.0 Installation and Configuration Guide

JumpStart Configuration and Use

The following list summarizes the major steps required to set up the JumpStart software and install the Solaris operating environment, and the Sun Management Center base agent, on one or more install clients.

Create the JumpStart install and profile servers.
Create the Sun Management Center 4.0 base agent image on the JumpStart install server.
Generate the Sun Management Center 4.0 install and setup response files.
Create the JumpStart profiles.
Create the JumpStart finish scripts for Sun Management Center.
Create the JumpStart rules file.
Validate the JumpStart files.
Add install client information to the JumpStart server.

When all of the above steps have been completed, you can use the JumpStart server to perform a fresh Solaris operating environment and Sun Management Center base agent install on one or more install clients.

The procedures in this section assume the following situation:

The machine bootserver01 has been configured as a boot server, and is to be used as the JumpStart boot server, install server, and profile server. Machine bootserver01 has already been configured as the boot server.
You are using /export/home as the base directory for all JumpStart files.

Note –
You can specify any file system that has sufficient space for the Solaris operating environment install image, and for the Sun Management Center base agent install image. The file system should have a minimum of 500 Mbytes of free space.

If you have decided to use a different directory for the JumpStart base directory, replace /export/home in the following procedures with the name of the directory you have chosen for the JumpStart base directory.
You have selected Solaris version 8 for JumpStart installations.

If you are using Solaris version 9, replace Solaris_9 with Solaris_8 where appropriate in the following sections.
You have chosen the default location of /opt for Sun Management Center base agent installation.

To Create the JumpStart Install Server and Profile Directory

Create the JumpStart install server and Solaris operating environment image.

Insert the Solaris installation CD 1 of 2 in your CD-ROM drive.

Go to the Tools directory on the CD.
# cd /DiskMountDir/Solaris_2.8/Tools

Create the Solaris operating environment installation image.

Type the command ./setup_install_server /install-server-directory, where install-server-directory is the directory that is to be used to serve the install images. For example:

 
# ./setup_install_server /export/home/JumpStart/Solaris_9 
Verifying target directory... 
Calculating the required disk space for the Solaris_9 product
Copying the CD image to disk...
Install Server setup complete

Optional: Add the Solaris operating environment supplemental products to the JumpStart install server.

Insert the Solaris installation CD 2 of 2 in your CD-ROM drive, and go to the Tools directory on the CD.

Type the command ./add_to_install_server /install-server-directory, where install-server-directory is the directory that is to be used to serve the install images. For example:
# cd /DiskMountDir/s0/Solaris_9/Tools # ./add_to_install_server /export/home/JumpStart/Solaris_9

Create the JumpStart profile directory on the server.
# mkdir /export/home/JumpStart/jumpstart

Insert the Solaris installation CD 1 of 2 in your CD-ROM drive.

Copy the JumpStart samples from the CD directory Solaris_2.8/Misc/jumpstart_sample to the JumpStart profile directory /export/home/JumpStart/jumpstart. For example:
# cd /DiskMountDir/s0/Solaris_2.8/Misc # cp -r jumpstart_sample/* /export/home/JumpStart/jumpstart

Stop the Network File System daemon mountd.
# /etc/init.d/nfs.server stop

Make the JumpStart directory NFS-shared.

The JumpStart directory must be NFS-shared so that the install clients can access the files on the JumpStart server. Add the following line to the /etc/dfs/dfstab file, then save and close the file.

share -F nfs -o ro,anon=0 /export/home/JumpStart

Start the Network File System daemon mountd.
# /etc/init.d/nfs.server start

To Create the Base Agent Image on the JumpStart Install Server

Insert the Sun Management Center 4.0 DVD in your DVD drive.

Change to the directory /DiskMountDir/sbin.

Type the command ./es-makeagent to create the Sun Management Center base agent image.

You are prompted for the installation files source directory, and for the agent image target directory.

(SPARC) The source directory is /DiskMountDir/disk1/image/sunOS/sparc.

(x86) The source directory is /DiskMountDir/disk1/image/sunOS/i386

(Linux) The source directory is /DiskMountDir/disk1/image/Linux

The target directory is the directory on the JumpStart install server where the agent image is to be created, for example, /export/home/JumpStart/AgentImage.

Note –
If the target directory that you specify does not exist, you are asked whether you want to create the directory. Type y to create the directory.

Example:
# ./es-makeagent Installation files source directory: /DiskMountDir/image Please enter the target directory: /export/home/JumpStart/AgentImage
Note –
The image creation process can take over half an hour to complete.

Exclude add-on agents.

If you do not want to include the add-on agent components, rename the agent-image Addons directory.

# cd /export/home/JumpStart/AgentImage/disk1/image
# ls -p
Addons/     PE/         Patches/    Webserver/  db/
# mv Addons Addons-temp

To Generate the Sun Management Center 4.0 Install and Setup Response Files

Select a machine on which to install and set up the Sun Management Center base agent, and log in as root.

This is the prototype machine.

Tip –
Select a machine on which Sun Management Center has not been installed. If such a machine is not available, uninstall the Sun Management Center software from the prototype machine as directed by the installation manual for the Sun Management Center software. Do not save the configuration data from the previous version of Sun Management Center.

Insert the Sun Management Center 4.0 DVD in your DVD drive.

Change to the directory /DiskMountDir/sbin.

Create a directory on the machine in which to store the Sun Management Center install and setup response files.

For example:
# mkdir /response-files

Generate the Sun Management Center Install Response file.

To generate the install response file, you must install the base agent using the command format ./es-inst -C /response-file-dir/install-response-file.cfg where:

response-file-dir is the directory that you created in which to store the response files
install-response-file is the name of the response file

For example:

# ./es-inst -C /response-files/install.cfg

You are prompted for the directory in which to install Sun Management Center.

Provide the name of the directory in which to install Sun Management Center

You are prompted for the target directory. The default location is /opt.

Sun Management Center software can be installed in any location on your system where the minimum required disk space is available. If you want to install to a directory other than /opt, type the directory name.

Tip –
The command df -ak lists the used space and free space for each file system on the machine.

You are prompted to select the Sun Management Center components that you want to install.

Select only the agent component.

Type n when prompted to install the server component.

Type y when prompted to install the agent component.

Type n when prompted to install the console component.

3 component(s) are available for your selection:
  Do you want to install the Server component (y|n|q) n
  Do you want to install the Agent component (y|n|q) y
  Do you want to install the Console component (y|n|q) n

The install process checks for add-on components, and then prompts you to select add-ons.

Do not select any add-on components for installation.

Type n when prompted to select each add-on.

Select the products you want to install:
    Advanced System Monitoring (y|n|q) n
    Service Availability Manager (y|n|q) n
    Performance Reporting Manager (y|n|q) n
    Sun Fire Platform Administration (y|n|q) n
    System Reliability Manager (y|n|q) n
    Workgroup Server (y|n|q) n

You are asked whether you want to proceed. Type y to continue.

Check disk space.

The installation process checks whether there is enough disk space to install the Sun Management Center base agent.
- If there is enough disk space, the base agent is installed.
- If there is not enough disk space, you are asked to provide an alternate file system. The amount of space that is available and the amount of space that is needed are displayed.
  
  Tip –
  In a terminal window on the machine where you are installing the Sun Management Center agent, type df -ak to list the amount of used and free space for each file system on the machine.
When the agent installation completes, you are asked whether you want to run setup.

Caution –
Do not run setup. Type n to exit. Running setup from within the install process will not create the Sun Management Center setup response file needed by the JumpStart finish script.

Go to the directory /opt/SUNWsymon/sbin.

If you installed Sun Management Center in a different location, go to the /install-dir/SUNWsymon/sbin directory, where install-dir is the directory you specified in Step 4.

Generate the Sun Management Center 4.0 setup response file.

To generate the Sun Management Center setup response file, you must set up the base agent using the command format ./es-setup -C /response-file-dir/setup-response-file.cfg where:
- response-file-dir is the directory that you created in which to store the response files
- setup-response-file is the name of the response file
For example:
# ./es-setup -C /response-files/setup.cfg
You are prompted to provide a seed for security key generation,
1. Generate the security keys.
  
  An encrypted security key is needed for communications between all Sun Management Center processes. The key is generated based on the password seed that you provide. The seed must be between one and eight characters long, and contain no spaces. Entries that are greater than eight characters are truncated to eight characters.
  
  Caution –
  You must ensure that you use the same security seed for all the machines that you install in a single server context.
  
  Type the same password seed that you provided during Sun Management Center server setup in Step b in Setting Up Sun Management Center.
  
  Type the password seed again when prompted.
  
  Note –
  To ensure security, the password seed that you provide is not stored in the Sun Management Center setup response file. You can either hard-code the password seed in the JumpStart finish script, or configure the finish script so that the install client prompts for the password seed when the finish script runs on the install client. Both methods of specifying the password seed are provided in To Create the JumpStart Finish Script.
  
  You are prompted for the SNMPv1 community string.
2. Specify the SNMPv1 community security string.
  
  An SNMPv1 community string is required for security, and by default is set to public. For additional security, a customized string can be specified.
  
  Caution –
  You must ensure that you use the same SNMPv1 community string on all the machines that you install in a single server context.
  
  Provide the same community string that you provided during Sun Management Center server setup in Step c in Setting Up Sun Management Center.
  - If you used the default community string of public, press Return when prompted to submit the SNMPv1 community string.
  - If you specified a custom community text string, type the same community string that you provided during Sun Management Center server setup.
  Note –
  To ensure security, the community string that you provide is not stored in the Sun Management Center setup response file. You can either hard-code the community string in the JumpStart finish script, or configure the finish script so that the install client prompts for the community string when the finish script runs on the install client. Both methods of specifying the community string are provided in To Create the JumpStart Finish Script.
  
  You are prompted for the Sun Management Center server host name.
3. Specify the Sun Management Center server host name.
  
  Type the name of the machine on which the Sun Management Center server was installed.
  
  The setup process checks whether the SNMP port is in use.
  - If SNMP port 161 is not in use, you are asked whether you want to start the Sun Management Center agent. Go to Step e.
  - If SNMP port 161 is in use, you are prompted to assign an SNMP port number.
4. Resolve the SNMP port conflict.
  
  Type the same port number that you provided during Sun Management Center server setup in Step f in Setting Up Sun Management Center.
5. Start the Sun Management Center agent.
  
  Caution –
  If your network uses Network Address Translation (NAT), type n to exit setup without starting Sun Management Center. Use the es-config command-line utility described in To Enable NAT Support to configure the machine for NAT before you start Sun Management Center.
  - If you want to start the Sun Management Center base agent now, type y.
    
    The setup script starts the agent using es-start -A. See Starting Components Using es-start for information about es-start.
    
    Also, see Starting the Console for instructions on how to start the Sun Management Center console.
  - If you want to start Sun Management Center later, type n. See Chapter 8, Starting and Stopping Sun Management Center when you are ready to start the Sun Management Center agent on this machine.

Copy the install and setup response files to the JumpStart profile server.

As an example in the previous steps, the Sun Management Center install response file install.cfg was created on the prototype machine in the directory /response-files. The Sun Management Center setup response file setup.cfg was also created on the prototype machine in the directory /response-files.

Assume that your JumpStart profile server is named bootserver01, and the JumpStart profile directory on machine bootserver01 is /export/home/JumpStart/jumpstart. Also assume that you have enabled write-access to the JumpStart profile directory from the prototype machine. You would then copy the response files from the prototype machine to the JumpStart profiles directory on the JumpStart machine. For example:
# cd /response-files # cp install.cfg /net/bootserver01/export/home/JumpStart/jumpstart # cp setup.cfg /net/bootserver01/export/home/JumpStart/jumpstart

Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

Edit the Sun Management Center install response file.

You must edit the install response file so that it can be used by JumpStart. The install response file is the file name you specified in Step 4. Make the following changes to the install response file:
- Change the SOURCE_DIRECTORY value to /a/mnt/disk1/image. The /a/mnt/disk1/image corresponds to the $MNTDIR value specified in the JumpStart finish script.
- Change the TARGET_DIRECTORY value to /a/target_directory, where target_directory is the directory on each install client where the Sun Management Center base agent is to be installed.
- Change the value of the SETUP_NOW parameter to zero. Setting the value of the SETUP_NOW parameter to zero ensures that the Sun Management Center setup does not automatically run on each install client when the Sun Management Center base agent has been installed.
The following sample shows a basic Sun Management Center install response file after edits have been completed.
```
SUNMC_VERSION=4.0
ENVIRONMENT=1
SOURCE_DIRECTORY=/a/mnt/disk1/image
TARGET_DIRECTORY=/a/opt
OSVERS=8
PRTOUT= Sun Microsystems sun4u PCI (UltraSPARC-II 450MHz)
LAYER.SERVER=0
LAYER.AGENT=1
LAYER.CONSOLE=0
SETUP_NOW=0
```
The value of the PRTOUT parameter is not important because the base agent is platform independent. However, JumpStart requires this parameter to be present. Do not delete the PRTOUT parameter.

Edit the Sun Management Center setup response file.

You must edit the setup response file so that it can be used by JumpStart. The setup response file is the file name that you specified in Step 6. Make the following changes to the setup response file if needed:
- Make sure that the server name specified by the SUNMC_SERVER parameter is the name of the Sun Management Center 4.0 server machine.
- Make sure that the value of the START_SUNMC parameter is set to 1 (one). Setting the value of the START_SUNMC parameter to 1 ensures that the Sun Management Center base agent is started after it has been set up.
- Make sure that the agent_OPTIONAL_PORT parameter is present, and that the assigned value is either a valid port number, or the text string DEFAULT.
- Make sure that all of the parameters in the sample setup response file shown below are present.
The following examples show a Sun Management Center setup response file before and after JumpStart edits have been applied. In both examples, bootserver01 is the name of the Sun Management Center server machine.

Example 6–1 Setup Response File Before JumpStart Edits Are Applied

SUNMC_SERVER=bootserver01
agent_OPTIONAL_PORT=1161
START_SUNMC=1

Example 6–2 Setup Response File After JumpStart Edits Are Applied

DISABLE_SNMPDX_DAEMON=1
STOP_SNMPDX=1
SUNMC_SERVER=bootserver01
agent_OPTIONAL_PORT=1161
START_SUNMC=1

In this example, the line DISABLE_SNMPDX_DAEMON=1 disables the SNMP daemon. The line STOP_SNMPDX=1 stops the SNMP daemon. The line SUNMC_SERVER=bootserver01 specifies that the base agent Sun Management Center server host is the machine named bootserver01. The line agent_OPTIONAL_PORT=1161 assigns port 1161 to the agent. The line START_SUNMC=1 starts the base agent when base agent setup is complete.

To Create the JumpStart Profiles

Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

Create a JumpStart profile for each type of install client on which you will install the Sun Management Center base agent.

You can create a JumpStart profile either by copying an appropriate sample profile from the samples in the directory, or by using the following example as a template. Save each JumpStart profile that you create in the JumpStart profile server directory, and record the name of each profile you create.

Caution –
Do not use a sample profile as the actual profile. Edit the profile to meet the JumpStart requirements, as described in “Creating a Profile” in Solaris 9 9/04 Installation Guide.

The following examples show sample JumpStart profiles. The first example shows a profile that is used for a fresh Solaris operating environment install. The second example shows a profile that is used for Solaris operating environment upgrade.

Example 6–3 Sample JumpStart Profile: Fresh Solaris Operating Environment Install

#
# all_9000_t0+swap
#
install_type    initial_install
system_type     standalone
partitioning    explicit
#
filesys         c0t0d0s1        2024    swap
filesys         c0t0d0s0        6120    /
filesys         c0t0d0s7        free    /export/home
#
cluster         SUNWCall 
package         SUNWabe             delete
cluster         SUNWCapache         delete
cluster         SUNWCdhcp           delete
cluster         SUNWClux            delete
cluster         SUNWCfct            delete
cluster         SUNWCnet            delete
package         NSCPcom             delete

Example 6–4 Sample JumpStart Profile: Upgrade Solaris Operating Environment Install

install_type    upgrade

To Create the JumpStart Finish Script

Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

Create the JumpStart finish script.

Review Security Considerations for Finish Scripts. Then, depending on your security requirements, use either of the following sample finish scripts as a guideline to create the finish script in the JumpStart profile directory.

The first example shows a finish script in which the password seed and community string are hard coded. The second example shows a finish script that will prompt for the password seed and community string.

Save your finish script with the sh extension, for example, base_agent_finish.sh.

Example 6–5 Sample Finish Script: Security Password Seed and Community String Hard Coded

#!/bin/sh
#
# Program type      : Unix bourne shell script
# Description       : Standard finish script for installing and 
#                     setting up Sun Management Center core agent
#
#
#
ROOTDIR=${ROOTDIR:-/a}               # Root directory for new OS
MNTDIR=${ROOTDIR}/mnt
LOGDIR=${ROOTDIR}/var/tmp/sunmcfinish
SI_CONFIG_DIR=${SI_CONFIG_DIR:-/export/home/JumpStart/jumpstart}
INSTALL_RESP=${SI_CONFIG_DIR}/install.cfg
SETUP_RESP=${SI_CONFIG_DIR}/setup.cfg
#
#
# Begin Main Program
#
#
umask 022
mkdir -p $LOGDIR
#
# Copy the install and setup response file to target system
#
cp ${INSTALL_RESP} $LOGDIR
cp ${SETUP_RESP} $LOGDIR
#
# mount Sun Management Center image
#
mount -F nfs bootserver01:/export/home/JumpStart/AgentImage $MNTDIR
[ $? -ne 0 ] && exit 1
# 
# run es-inst with -a -R -T and -A options
# skip the next line for Flash Archive based deployment
# Do not use the -T option if you have specified the TARGET_DIRECTORY 
# tag in install.cfg
#
${MNTDIR}/disk1/sbin/es-inst -a -R /a -T /a/opt -A ${LOGDIR}/install.cfg
#
# Clean up any rc script with the same name if present
#
test -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart && \
rm -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart
rm -f /etc/init.d/SunMCJumpStart
#
# Place rc script in rc3.d and init.d to do setup
# Remember to access es-setup based on the target directory location
#
echo "Creating rc script..."
cat > ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart << EOF
#!/sbin/sh
#
rm /etc/rc3.d/S80SunMCJumpStart /etc/init.d/SunMCJumpStart
SECURITY_SEED=abc123
SNMPV1_STRING=private
export SECURITY_SEED SNMPV1_STRING
/opt/SUNWsymon/sbin/es-setup -e -A /var/tmp/sunmcfinish/setup.cfg
EOF
cp ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart \
     ${ROOTDIR}/etc/init.d/SunMCJumpStart
exit 0

Example 6–6 Sample Finish Script: Prompt for Security Password Seed and Community

#!/bin/sh
#
# Program type      : Unix bourne shell script
# Description       : Standard finish script for installing and 
#                     setting up Sun Management Center core agent
#
#
#
ROOTDIR=${ROOTDIR:-/a}               # Root directory for new OS
MNTDIR=${ROOTDIR}/mnt
LOGDIR=${ROOTDIR}/var/tmp/sunmcfinish
SI_CONFIG_DIR=${SI_CONFIG_DIR:-/export/home/JumpStart/jumpstart}
INSTALL_RESP=${SI_CONFIG_DIR}/install.cfg
SETUP_RESP=${SI_CONFIG_DIR}/setup.cfg
#
#
# Begin Main Program
#
#
umask 022
mkdir -p $LOGDIR
#
# Copy the install and setup response file to target system
#
cp ${INSTALL_RESP} $LOGDIR
cp ${SETUP_RESP} $LOGDIR
#
# mount Sun Management Center image
#
mount -F nfs bootserver01:/export/home/JumpStart/AgentImage $MNTDIR
[ $? -ne 0 ] && exit 1
#
# Read secure inputs from user who invoked boot net - install
#
echo "Enter Security seed:"
read SECURITY_SEED
echo "Enter SNMP string:"
read SNMPV1_STRING
#
# run es-inst with -a -R -T and -A options
# skip the next line for Flash Archive based deployment
# Do not use the -T option if you have specified the TARGET_DIRECTORY 
# tag in install.cfg
#
${MNTDIR}/disk1/sbin/es-inst -a -R /a -T /a/opt -A ${LOGDIR}/install.cfg
#
# create a temporary es-setup script to use the secure information 
# read earlier
# Remember to access es-setup based on the target directory location 
#
FILE2=/a/opt/SUNWsymon/sbin/es-setup
FILE=/a/opt/SUNWsymon/sbin/es-setup.jumpstart
mv $FILE2 $FILE
count=`wc -l $FILE`
count=`echo $count | cut -d' ' -f1`
ncount=$count
count_enter=`expr $ncount - 3`
while [ $ncount -gt 0 ] ; do
   k=`tail -$ncount $FILE | head -1`
   if [ $ncount -eq $count_enter ]
   then
       echo $k >> $FILE2
       echo "SECURITY_SEED=$SECURITY_SEED" >> $FILE2
       echo "SNMPV1_STRING=$SNMPV1_STRING" >> $FILE2
   else
       echo $k >> $FILE2
   fi
   ncount=`expr $ncount - 1`
done
chmod +x $FILE2
#
# Clean up any rc script with the same name if present
#
test -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart && \
rm  -f ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart \
rm -f /etc/init.d/SunMCJumpStart
#
# Place rc script in rc3.d and init.d to do setup and cleanup 
# Remember to access es-setup based on the target directory location
# 
echo "Creating rc script..."
cat > ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart << EOF
#!/sbin/sh
#
rm /etc/rc3.d/S80SunMCJumpStart /etc/init.d/SunMCJumpStart
/opt/SUNWsymon/sbin/es-setup -e -A /var/tmp/sunmcfinish/setup.cfg
mv /opt/SUNWsymon/sbin/es-setup.jumpstart /opt/SUNWsymon/sbin/es-setup
EOF
cp ${ROOTDIR}/etc/rc3.d/S80SunMCJumpStart \
   ${ROOTDIR}/etc/init.d/SunMCJumpStart
exit 0

To Create the JumpStart Rules File

Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

Create the JumpStart rules file.

Use the following example rules file as a template, and create the rules file in the JumpStart profile directory.

Example 6–7 Sample Rules File

#
# rule keywords and rule values   begin script   profile    finish  script 
# ------------------------------  ------------   -------    --------------
  
# This rule matches one system: 
#
hostname bootserver01            -         basic_prof  base_agent_finish.sh 
 
 
# This is a complex rule:
#
network 192.43.34.0 && ! model \ 
 SUNW,SPARCstation-20                 -         net_prof         - 
 
 
# This rule applies to all 
# SUNW,SPARCstation-LX:
#
model SUNW,SPARCstation-LX            -         lx_prof     complete.sh
 
 
# Another complex rule:
#
network 193.144.2.0 && karch i86pc   init.sh    IA_prof     done.sh
 
#
# You can use system attributes like RAM size and architecture to 
# classify targets:
#
memsize 16-32 && arch i386           -          prog_prof        -
 
 
# rules are matched top-down. If nothing matches, this rule will apply:
#
any                  -               -         generic_prof     -

To Validate Your JumpStart Files

Go to the JumpStart profile directory that you created in Step 2, in To Create the JumpStart Install Server and Profile Directory.

Type ./check to validate your JumpStart files.

# ./check  
Validating rules... 
Validating profile basic_prof... 
Validating profile net_prof... 
Validating profile lx_prof... 
Validating profile IA_prof... 
Validating profile prog_prof... 
Validating profile any_machine... 
The custom JumpStart configuration is ok. 
# cat rules.ok 
hostname bootserver01          -         basic_prof      base_agent_finish.sh 
network 192.43.34.0 && ! model \ 
 SUNW,SPARCstation-20                    -         net_prof        - 
model SUNW,SPARCstation-LX             -         lx_prof         complete.sh
network 193.144.2.0 && karch i86pc       init.sh   IA_prof         done.sh
memsize 16-32 && arch i386               -         prog_prof       -      
any -                                    -         generic_prof    -

To Add Install Client Information to the JumpStart Server

Insert the Solaris installation CD 1 of 2 in your CD-ROM drive.

Go to the Tools directory on the CD.
# cd /DiskMountDir/s0/Solaris_2.8/Tools

Determine the system identification information for each install client.

The JumpStart server requires the following information about each install client.
- Name
- Ethernet address
- IP address
- Architecture
Log on to each install client, and use the arp and uname commands as follows to display the install client's Ethernet address, IP address, name, and architecture.
> arp clienthost clienthost (111.222.123.124) at 8:0:80:e4:23:eb permanent published > uname -a SunOS clienthost 5.9 Generic_112233-01 sun4u sparc SUNW
In the above example, the clienthost install client Ethernet address is 8:0:80:e4:23:eb, the IP address is 111.222.123.124, and the architecture is sun4u.

Add the system identification information for each install client to the JumpStart server.

The add_install_client command is used to add the install client information to the JumpStart server as follows:

add_install_client \
-c JumpStart_profile_server:path_to_configuration_directory \
-s JumpStart_install_server:path_to_operating_environment_image \
-p JumpStart_profile_server:path_to_SYSIDCFG_file \
-e install_client_ethernet_address \
-i install_client_IP_address \
install_client_name install_client_architecture

For example, assume your systems are configured as follows.

Machine bootserver01 is your JumpStart boot server, profile server, and install server.
The JumpStart configuration directory on bootserver01 is /export/home/JumpStart/jumpstart.
The JumpStart operating environment image directory on bootserver01 is /export/home/JumpStart/Solaris_9.
The system identification configuration file sysidcfg is located in the JumpStart configuration directory /export/home/JumpStart/jumpstart.
The install client Ethernet address is 8:0:80:e4:23:eb, and the IP address is 111.111.123.124.
The install client's name is clienthost, and the install client's architecture is sun4u.

You would then add the install client clienthost using the add_install_client command as follows.

# ./add_install_client -c bootserver01:/export/home/JumpStart/jumpstart \
  -s bootserver01:/export/home/JumpStart/Solaris_9 \
  -p bootserver01:/export/home/JumpStart/jumpstart \
-e 8:0:80:e4:23:eb -i 111.111.123.124 \
  clienthost sun4u 
  Adding Ethernet number for clienthost to /etc/ethers
  making /tftpboot
  enabling tftp in /etc/inetd.conf
  starting rarpd
  starting bootparamd
  updating /etc/bootparams
  copying inetboot to /tftpboot

When you have finished adding install client system information to the JumpStart server, you can then use JumpStart to install the Solaris operating environment and the Sun Management Center base agent as described in the next step.

For further information about the add_install_client command and options, see the man page add_install_client(1m).

Boot each install client.
1. Logon as root on the client machine in single-user mode.
2. At the ok prompt, type the command boot net - install.
  
  For example:
  {2} ok boot net - install
  The client system boots from the JumpStart server. JumpStart installs the Solaris operating environment specified by the JumpStart profile assigned to the install client by the applicable rule in the rules file. When the operating environment has been installed, the Sun Management Center 4.0 base agent is installed. The install client then reboots.
  
  When the install client reboot completes, the Sun Management Center base agent is set up according to the specifications of the finish script assigned to the install client by the applicable rule in the rules file. If you hard coded the security password seed and the SNMP community string in the finish script, base agent setup is automatic. If you chose not to hard code the password seed and community string in the finish script, you must respond to the base agent setup prompts on each install client to complete base agent setup.