Softpanorama (slightly skeptical) Open Source Software Educational Society

May the source be with you, but remember the KISS principle ;-)

Install Server

The install server supplies the client with the Solaris OS.  It is an NFS share with the Solaris install image.  Any OS able to export NFS shares is able to serve as a Jumpstart Install Server. It is ususually doubles as a configuration server.

The configuration Sever is comprised of the rules file, profiles, and sysidcfg.  It allows the administrator to have available different custom jumpstart configurations based on rule sets.  This is very helpful when different groups within an organization require different system configurations.

Below are examples of a profile.  Profiles contain filesystem layout and package information.

Example:

# profile keywords        profile values

# -----------------       -----------------

# This profile keyword is required in every profile

install_type            initial_install

system_type             standalone

partitioning            default

filesys                 any 60 swap

filesys                 s_ref:/usr/share/man - /usr/share/man ro

filesys                 s_ref:/usr/openwin/share/man - 

                        /usr/openwin/share/man ro,quota

cluster                 SUNWCprog

package                 SUNWman delete

package                 SUNWolman delete

package                 SUNWxwman delete

package                 SUNWoldem add

package                 SUNWxwdem add

package                 SUNWoldim add

Example:

Profile values

Derived Profiles

A derived profile is a profile that is dynamically created by a begin script during a custom JumpStart installation. Derived profiles are needed when you cannot set up the rules file to match specific systems to a profile (when you need more flexibility than the rules file can provide).

Set the profile field to an equal sign (=) instead of a profile.

Note:  If a begin script is used to create a derived profile, make sure there are no errors in it. A derived profile is not verified by the check script because it is not created until the execution of the begin script.

Example:

#!/bin/sh

echo "install_type        initial_install"    > ${SI_PROFILE}

echo "system_type         standalone"        >> ${SI_PROFILE}

echo "partitioning        default"           >> ${SI_PROFILE}

echo "cluster             SUNWCprog"         >> ${SI_PROFILE}

echo "package       SUNWman     delete"      >> ${SI_PROFILE}

echo "package       SUNWolman   delete"      >> ${SI_PROFILE}

echo "package       SUNWxwman   delete"      >> ${SI_PROFILE}

Verify Profile

After you create a profile, use the pfinstall command to test the profile before you actually use it to install or upgrade a system. Testing a profile is especially useful when you are creating upgrade profiles that reallocate disk space.  Profiles should only be tested on systems with the same architecture (i386 or sparc) as the Jumpstart clients to ensure accurate results.

# /usr/sbin/install.d/pfinstall disk_configuration [-c path] profile

Sysidtool Suite

When you boot Solaris, a set of programs called sysidtool configures your system, prompting for information needed such as the client’s host name and IP address, the local date and time, the time zone and the netmask. NIS or NIS+ can provide this information, otherwise you have to enter it manually before JumpStart can install the OS and packages. It is also possible to create a sysidcfg file, which must be on either local media or a nfs exported filesystem.

The sysidcfg file is a file where, starting with Solaris 2.6, all the configuration information required during an OS installation can be specified.  A change needed to be made to the sysidcfg provided as part of the Jumpstart package in order for the process to work on your local network.

Default values needed

·        date & time

·        time zone

·        site netmask

·        language options

Sysidcfg Example:

Note: To use "name_service=NONE" with Solaris 2.6 you will need to load patch 106193-03 or greater.  Also to use network_interface=primary on Solaris 2.6, you need patch 106193-0 or greater. Solaris 7 and Solaris 8 do not need any patches

Note: Solaris 8 will prompt for two new options, ipv6, and kerberos.  To avoid user interaction you must include answers to these options in the sysidcfg file.

NIS/NIS+ can be used to supply system  information including:

• /etc/hosts
• /etc/timezone
• /etc/netmasks
• /etc/locale

Last modified: February 28, 2008