Before any target servers can be built from the JumpStart server, a number of steps must be taken in order to populate the server with the required media. It is possible to use media from a server other than the JET server, but at the minimum, the boot media must be installed on the JET server.
Solaris Media Installation
To provide basic JumpStart functionality, an image of the appropriate Solaris Operating System media must be installed on the JumpStart server.
The version or versions of Solaris to be copied onto the JumpStart server depend on those required by the target server(s), and indeed, multiple versions of the Solaris media can be installed on the same JumpStart server at the same time.
While it is recommended the media is copied to disk on the JumpStart server, it is not essential, and the CD-ROM can be shared appropriately to allow the target servers to boot of it. The configuration and use of a CD-ROM is beyond the scope of this document and will severely restrict the performance of the target server build, along with the ability to support multiple versions of Solaris.
JET also provides a module called JetISO which allows you to directly use iso images as Solaris media.
DO NOT SIMPLY COPY THE SOLARIS MEDIA, YOU MUST USE EITHER THE SCRIPTS ON THE SOLARIS DVD, OR THOSE PROVIDED BY THE TOOLKIT, OTHERWISE YOUR JUMPSTART MAY FAIL!
Copying the Solaris Image to Disk Using the Toolkit
Mount the Solaris DVD on the JumpStart server, either through a local DVD, or using a shared DVD on the network. If you have an ISO image, it can be lofimounted and the following commands could be used.
# lofiadm -a <full path to iso> # mount -F hsfs /dev/lofi/<n> /mnt
For a single installation where the Jumpstart server will only be hosting a single version or architecture of Solaris, use the copy_solaris_media command in the /opt/SUNWjet/bin directory with a single argument: the location of the media to copy.
# /opt/SUNWjet/bin/copy_solaris_media /cdrom/cdrom0
This utility will copy the media to an area under $JS_SOLARIS_DIR (defined in /opt/SUNWjet/etc/jumpstart.conf), and then add the location of the media into the toolkit. Once it has completed, it will output details of the image just copied. By default, with no arguments, JET will create a directory in $JS_SOLARIS_DIR based on the Solaris version. If multiple Solaris revisions and Solaris architectures are to be supported, it is recommended that copy_solaris_media be called with specific arguments so that the OS name and directory name are explicitly named.
# /opt/SUNWjet/bin/copy_solaris_media -d Solaris10_U6_x86 -n 10_u6x /cdrom/cdrom0
Please note, the time taken to copy the image depends on the speed of the media it is being copied from.
Copying an Image using 'setup_install_server'
You can also use the 'setup_install_server' script that is located on the Solaris DVD to copy the media to the JumpStart server. If the Solaris release consists of multiple media components, you may need need to also run the 'add_to_install_server' script that is found on the additional CDs/DVDs/ISOs.
Once completed, please register the location using the next procedure.
Using ISOs directly.
To save space and time, it is possible to use the Solaris Media ISOs directly. JET has provided the JetISO package to facilitate this. Simply edit the /opt/SUNWjet/etc/solaris_iso_locations to provide the location of the ISO, and the mountpoint of the ISO image. Once this file has been prepared, run
# /opt/SUNWjet/bin/share_isos
This will lofimount the isos and NFS share them. You will then need to register the Solaris image with JET using the following section.
Registering Existing Solaris Images
When using self copied or existing media locations, you need to take one further step, which is to inform the toolkit of the location of the media by using the '/opt/SUNWjet/bin/add_solaris_location' command.
# /opt/SUNWjet/bin/add_solaris_location <tag> <path to image>
The tag parameter allows you to refer to this image by a shortened or abbreviated name, rather than having to remember the complete path of the image. The tag is an arbitrary single word of text to describe the image; examples: 8_0202, 9_GA etc.
You can also tell JET about remote media using the add_solaris_location command:
# /opt/SUNWjet/bin/add_solaris_location <tag> <remote_server>:<path to image>
When the command is run in this fashion, JET will automatically create a boot server image on the JET server. You can use the jumpstart.conf variable JS_CLIENT_BOOT to define whether the client will initially boot off the JET server or the remote NFS server.
Checking for Existing Images
The toolkit provides a utility command 'list_solaris_locations' which will list each tag and its corresponding physical location on the JumpStart server.
The locations of the Solaris images are maintained in a simple flat file in the /opt/SUNWjet/etc directory - solaris_media_locations. If you remove an image, you can just edit this file and remove the entry for the image.
Solaris Recommended Patches
In order to install the recommended patch cluster you will first need to locate the tarball on either a SunSolve CD, or have previously downloaded the recommended patch cluster from the SunSolve online web site. Obtaining the recommended patch cluster is beyond the scope of this document.
Copying Recommended Patches Using the Toolkit
The toolkit provides a utility function '/opt/SUNWjet/bin/copy_solaris_patches' which will put the patches in the correct location, as defined by JS_PATCH_DIR in the configuration (/opt/SUNWjet/etc/jumpstart.conf) file.
# /opt/SUNWjet/bin/copy_solaris_patches <os version> <path to patch cluster>
The utility takes two arguments, the first being the version of the Solaris Operating Environment, examples 2.6, 7, 8 or 9; the second argument is the full path to the patch cluster itself. This could be the path to the file on the SunSolve CD, or the path to a downloaded online version.
If you are unsure about the correct value for 'os version', the argument is the prefix to the file, for example if the cluster is "9_Recommended.tar.gz", then 'os version' is "9".
Manually Populating Recommended Patches
The recommended patches are expected to reside in JS_PATCH_DIR, as defined in the configuration file (/opt/SUNWjet/etc/jumpstart.conf). The patch clusters should live directly under that directory, for example "/export/install/patches/10_Recommended" and be fully extracted from their tarball.
If you wish to add additional patches, there is a file called "patch_order" which defines which patches are installed and their associated order of installation.
Sign up or Log in to add a comment or watch this page.