JumpStart Server Configuration – Solaris 10

Introduction

The Solaris 10 Operating System offers an automatic installation process, Solaris JumpStart software. The Solaris JumpStart procedure enables you to install the Solaris OS automatically and configure it differently, depending on the characteristics of client systems. These identifying characteristics are used to select the correct configuration for each client system.

The following tasks are required to configure a single JumpStart server to provide basic software installation services using the JumpStart procedures:

1. Spool the operating system image.
2. Edit the sysidcfg file.
3. Edit the profile and rules.
4. Run the check script.
5. Run the add_install_client script.
6. Boot the client.

Step #1

To spool the Solaris 10 boot and installation images to a local disk, complete the following steps: Create a directory with at least 800 Mbytes of space available to hold the Solaris OS image. Usually the /export/install directory is used.

1. mkdir /export/install

Insert the Solaris 10 Software 1 of 2 CD-ROM in the CD-ROM drive or the Solaris 10 DVD in the DVD drive. Change the directory to the location of the setup_install_server script.

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

Run the setup_install_server script to copy the Solaris 10 OS installation images to the local disk.

1. ./setup_install_server /export/install

When the setup_install_server script finishes, change the directory to root (/), and eject the CD-ROM or DVD.

1. cd /
2. eject cdrom

If you use CD-ROM media, insert the Solaris 10 Software 2 of 2 CD-ROM in the CD-ROM drive. Change the directory to the location of the add_to_install_server script.

1. cd /cdrom/cdrom0/Solaris_10/Tools

Run the add_to_install_server script to copy the remainder of the installation image to the local disk.

1. ./add_to_install_server /export/install

When add_to_install_server finishes, change the directory to root (/), and eject the CD-ROM.

1. cd /
2. eject cdrom

Step #2

The sysidcfg file keeps the various types of system information such as locale, time_zone, and so on, and supplies the information to the client at the booting time. Create a directory to hold the sysidcfg file. Typically the /export/config directory holds the sysidcfg file.

1. mkdir /export/config

Change the directory to /export/config, and create a file called sysidcfg using a text editor.

1. cd /export/config
2. vi sysidcfg

In the sysidcfg file, add the following lines. Substitute values that are appropriate for your systems, location, and network.

network_interface=primary {protocol-ipv6=no netmask=255.255.255.0} security_policy=none name_service=none time_zone=US/Mountain system_locale=en_us Save the sysidcfg file, and exit your edit session.

Step #3
Rules

Create a directory to hold the rules file if this directory does not already exist. Usually, the /export/config directory holds the rules file.

1. mkdir /export/config

Change the directory to /export/config, and create a file called rules using a text editor.

1. cd /export/config
2. vi rules

In the rules file, add the following line: hostname client_name - profile1 - For client_name, substitute the name of your JumpStart client. For example: hostname sun1 - profile - Save the rules file, and exit your edit session.

Profiles

Usually, the /export/config directory holds the profile file.

Change the directory to /export/config, and create a file called profile using a text editor.

1. cd /export/config
2. vi profile1

Add the following lines to the profile1 file: install_type initial_install system_type standalone partitioning explicit filesys c0t0d0s0 free / filesys c0t0d0s1 128 swap cluster SUNWCXall Save the profile1 file, and exit your edit session.

Step #4

Before a JumpStart client can use a configuration provided by a JumpStart server, you must run the check script to produce a file called rules.ok. The check script validates the syntax of the rules file and the profile files. If the validation completes successfully, the check script creates the rules.ok file. Change the directory to the location of the check script.

1. cd /export/install/Solaris_10/Misc/JumpStart_sample

Copy the check script to the /export/config directory.

1. cp check /export/config

Change the directory to /export/config, and run the check script.

1. cd /export/config
2. ./check

Validating rules... Validating profile profile1... The custom JumpStart configuration is ok.

Step #5
Add a host entry

Edit the /etc/ethers file, and add an entry for the JumpStart client.

1. vi /etc/ethers

00-C0-26-84-34-A1 sun1 Save and exit from the ethers file.

Edit the /etc/inet/hosts file, and add an entry for the JumpStart client.

1. vi /etc/inet/hosts

192.168.1.1 sun1 Save and exit from the hosts file.

Add a client

Change the directory to the location of the add_install_client script on the server.

1. cd /export/install/Solaris_10/Tools

Run the add_install_client script, and specify server and client information as follows. (Note: The following line of code should all be entered on one line.)

1. ./add_install_client -c server_name:/export/config \

-p server_name:/export/config client_name platform_group

For example:

1. ./add-install-client -c sun:/export/config -p sun:/export/config sun1 sun4u

Edit the /etc/dfs/dfstab file to add the following line:

1. vi /etc/dfs/dfstab

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

share -F nfs -o ro, anon=0 /export/config Save and exit from the dfstab file.

Run the shareall command to share the /export/config and /export/install directories.

1. shareall

Verify that the /export/config and /export/install directories are currently shared.

1. share

Step #6

Booting the JumpStart Client

After the JumpStart server has been configured to provide all of the required services, you can initiate the installation process on the JumpStart client. To boot the JumpStart client, perform the following steps:

Bring the JumpStart client to run state 0

1. init 0

Boot the client to initiate the software installation using the JumpStart procedure

ok boot net - install

Adding record 10.198.89.166/pilotsparc166/0100144F96A0F0 into DHCP table ...
+ Server info was added to DHCP table on jumpstart server successfully.

Creating boot file /tftpboot/0100144F96A0F0 ... Done
Creating cfg file /opt/jumpstart/config/Solaris-10-UGA-sparc/10.198.89.166/sysidcfg ... DONE
Creating cfg-file /opt/jumpstart/config/Solaris-10-UGA-sparc/10.198.89.166/rules ...DONE
Creating cfg-file /opt/jumpstart/config/Solaris-10-UGA-sparc/10.198.89.166/rules.ok ...DONE
Creating cfg-file /opt/jumpstart/config/Solaris-10-UGA-sparc/10.198.89.166/finish.sh ...DONE
Creating cfg-file /opt/jumpstart/config/Solaris-10-UGA-sparc/10.198.89.166/any_machine ...DONE
Creating tarball /opt/jumpstart/config/Solaris-10-UGA-sparc/10.198.89.166/config.tar ... DONE
+ Jumpstart configuration file for your server is created successfully.

+ Please reboot sparc server with "init 0" (enter ok mode) and start installation with "boot net:dhcp -v - install".

any_machine

install_type    initial_install
system_type     standalone
partitioning    explicit
filesys         any free /
filesys         any 8192 swap
cluster         SUNWCXall
geo Asia
locale zh
locale                en_US
locale                en_CA
locale                ja_JP
locale                zh_CN
locale                zh_HK
locale                zh_TW

finish.sh

#!/bin/sh

# JumpStart finish script

#Modify nfs client version
echo NFS_CLIENT_VERSMAX=3 >> /a/etc/default/nfs

# Modify nsswitch.conf
echo "finish.sh: Changing /etc/nsswitch.conf ..."
perl -i -p -0777 -e 's/hosts:      files/hosts:      files dns/gs' /a/etc/nsswitch.conf
echo ""

# Modify login for remote login
echo "finish: Changing /etc/default/login file..."
perl -i -p -0777 -e 's/CONSOLE=/#CONSOLE=/gs' /a/etc/default/login
echo ""

# Create the resolv.conf
echo "finish.sh: Creating /etc/resolv.conf..."
echo "domain cdc.veritas.com"       > /a/etc/resolv.conf
echo "nameserver 10.198.88.18" >>/a/etc/resolv.conf
echo "nameserver 10.200.117.18" >>/a/etc/resolv.conf
echo "search cdc.veritas.com"       >>/a/etc/resolv.conf
echo ""

echo "finish.sh: Disabling NFSv4 domain..."
touch /a/etc/.NFS4inst_state.domain
ls -l /a/etc/.NFS4inst_state.domain
echo ""

echo "change dhcp to static ip"

sed -e "s/dhcp/ hostname=pilotsparc166.cdc.veritas.com ip_address=10.198.89.166 default_route=10.198.88.1 netmask=255.255.248.0/g" /a/etc/sysidcfg > /a/etc/sysidcfg-new
cp /a/etc/sysidcfg /a/etc/sysidcfg-bak
cp /a/etc/sysidcfg-new /a/etc/sysidcfg

BASE="/a"
IFNAME="`ls ${BASE}/etc/hostname.* |sed -e \"s:^${BASE}/etc/hostname.::\"`"
echo "pilotsparc166" > ${BASE}/etc/hostname.${IFNAME}
echo "pilotsparc166" > ${BASE}/etc/nodename
echo "10.198.88.0     255.255.248.0" >> ${BASE}/etc/netmasks
echo "10.198.88.1" >> ${BASE}/etc/defaultrouter
echo "10.198.89.166 pilotsparc166 loghost" >> ${BASE}/etc/hosts
/bin/rm -f  ${BASE}/etc/dhcp.${IFNAME}
cat /etc/inet/ipnodes > ${BASE}/etc/ipnodes-bak

# Disable power management
echo "finish.sh: Disabling power management..."
touch /a/noautoshutdown
ls -l /a/noautoshutdown
echo ""


# embed super lab
echo "
#!/bin/sh
useradd -g 0 -u 9876 -d /tmp labadmin
perl -i -pe \"s/labadmin:\*LK\*/labadmin:JP68IF1KRujYc/\" /etc/shadow
sleep 3
rm -rf /etc/rc2.d/S99addlab
" >/a/etc/rc2.d/S99addlab
chmod +x /a/etc/rc2.d/S99addlab

echo "finish.sh: DONE!"

echo "Reboot the system ..."
reboot



exit 0

rules

#
#       @(#)rules 1.12 94/07/27 SMI
#
# The rules file is a text file used to create the rules.ok file for
# a custom JumpStart installation. The rules file is a lookup table
# consisting of one or more rules that define matches between system
# attributes and profiles.
#
# This example rules file contains:
#   o syntax of a rule used in the rules file
#   o rule_keyword and rule_value descriptions
#   o rule examples
#
# See the installation manual for a complete description of the rules file.
#
#
#############################################################################
#
# RULE SYNTAX:
#
# [!]rule_keyword rule_value [&& [!]rule_keyword rule_value]... begin profile finish
#
#    "[ ]"  indicates an optional expression or field
#    "..."  indicates the preceding expression may be repeated
#     "&&"  used to "logically AND" rule_keyword and rule_value pairs together
#      "!"  indicates negation of the following rule_keyword
#
#  rule_keyword   a predefined keyword that describes a general system
#                 attribute. It is used with the rule_value to match a
#                 system with the same attribute to a profile.
#
#  rule_value     a value that provides the specific system attribute
#                 for the corresponding rule_keyword. A rule_value can
#                 be text or a range of values (NN-MM).
#                 To match a range of values, a system's value must be
#                 greater than or equal to NN and less than or equal to MM.
#
#  begin          a file name of an optional Bourne shell script
#                 that will be executed before the installation begins.
#                 If no begin script exists, you must enter a minus sign (-)
#                 in this field.
#
#  profile        a file name of a text file used as a template by the
#                 custom JumpStart installation software that defines how
#                 to install Solaris on a system.
#
#  finish         a file name of an optional Bourne shell script
#                 that will be executed after the installation completes.
#                 If no finish script exists, you must enter a minus sign (-)
#                 in this field.
#
# Notes:
# 1. You can add comments after the pound sign (#) anywhere on a line.
# 2. Rules are matched in descending order: first rule through the last rule.
# 3. Rules can be continued to a new line by using the backslash (\) before
#    the carriage return.
# 4. Don't use the "*" character or other shell wildcards, because the rules
#    file is interpreted by a Bourne shell script.
#
#
#############################################################################
#
# RULE_KEYWORD AND RULE_VALUE DESCRIPTIONS
#
#
# rule_keyword    rule_value Type       rule_value Description
# ------------    ---------------       ----------------------
#  any            minus sign (-)        always matches
#  arch           text                  system's architecture type
#  domainname     text                  system's domain name
#  disksize       text range            system's disk size
#                                          disk device name (text)
#                                          disk size (MBytes range)
#  hostname       text                  system's host name
#  installed      text text             system's installed version of Solaris
#                                          disk device name (text)
#                                          OS release (text)
#  karch          text                  system's kernel architecture
#  memsize        range                 system's memory size (MBytes range)
#  model          'text'                system's model number
#  network        text                  system's IP address
#  totaldisk      range                 system's total disk size (MBytes range)
#
#
############################################################################
#
# RULE EXAMPLES
#
# The following rule matches only one system:
#

# arch  i386    begin.sh        x86-class       finish.sh
# arch  sparc   -               sparc_profile  -
any      -      -               any_machine     finish.sh

rules.ok

any      -      -               any_machine     finish.sh
# version=2 checksum=3506

sysidcfg

terminal=xterm
system_locale=C
security_policy=NONE
name_service=NONE
auto_reg=disable
nfs4_domain=dynamic
network_interface=primary { dhcp protocol_ipv6=no }
root_password=TQJIWs6nKujsw
timezone=PRC
timeserver=localhost

Related White Papers and Webcasts

Related Content

solaris 10 zones thoughts (Blogs)

(Wiki) (Groups)

转载自–_Solaris_10