From JetResources
Revision as of 13:33, 3 September 2007 by Marty (Talk | contribs)

(diff) ←Older revision | view current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search

Frequently Asked Questions


What are these '.pkg'/'pkg.bz2' files ?

"I've just downloaded the packages from the website, and now have files with a .pkg suffix. What do I do next ?"

The files you have are datastream packages. To install them, run

     pkgadd -d filename.pkg

rather than the more usual pkgadd -d . [pkgname]

You can migrate the datastream format packages to regular directory based packages by using the pkgtrans(1m) command.

     pkgtrans filename.pkg . all

Basically, read up on pkgadd(1m) and pkgtrans(1m) !

A GUI Frontend for JET

Is there a Web Front End for JET ?

Probably the most frequently requested feature. The short answer is 'no, there is no generic web front end for JET'.

The long answer is that typically, web front ends are written to expose a subset of the features available in JET. For the case of 'standard builds', you may wish to have a pull down list of available builds and just plug in the MAC and IP addresses etc.

As these front ends, with only a subset of features presented, are very much customised for a particular use/customer, it's work you need to do!

If a 'generic web front end' was provided, it would need to be kept up to date with every modification to the toolkit. Quite frankly, it isn't going to be that useful to many people.

JET has been designed so it is pretty easy to front end yourself.

Getting Help with JET

There are a number of places you can go for help with JET; first up is obviously Sun themselves - Email the people who look after JET on the alias jet@sun.com and someone should get back to you pretty quickly (UK Timezone).

Sun have also put up information on the JET BigAdmin page at http://www.sun.com/bigadmin/content/jet/ and Mike Ramchand (one of the authors) tends to write things about JET in his blog at http://blogs.sun.com/roller/page/mramcha/20050826

External to Sun are a number of resources; there is a Yahoo group at http://groups.yahoo.com/group/JETJumpStart/ and of course, you can approach me (marty at Maui-Systems dot co dot uk) as the other author of the toolkit from when I used to work for Sun.

Whats in the Free Bundle ?

The JET bundle downloadable from http;//www.sun.com/downloads currently (as of May 2006) contains the following modules.

   * SUNWjet - The core JET product
   * SUNWjetd - The documentation - Please read
   * JetSDS - Configure SVM/SDS
   * JetVTS - Install the Test Suite
   * JetEXPLO - Install and configure Explorer
   * JetFLASH - Utilise flash archives for installation
   * JetSAN - Configure SANs
   * JetJASS - JASS toolkit install and configuration
   * JetZONES - Add local zones to your Solaris 10 global zones as part of the build
   * JetWanBoot - Plugin to allow JET to perform WANBOOTt installations
   * JetRBAC - Enables none root users to run JET using RBAC

Sun releases/refreshes the bundle on an ad-hoc basis and normally communicates this fact to the comp.unix.solaris and alt.solaris.x86 newsgroups.

Solaris 10 U1 (01/06) grub/newboot

With the release of Solaris 10 Update 1 (01/06), the x86/64 platform boot method was transitioned to 'grub', finally doing away with the old DCA pre-boot environment. This new boot method was refered to as "newboot" internally to Sun and the phrase seems to have stuck.

To deal with this a JetNEWBOOT module was developed to "plugin" to JET versions prior to JET 4.2 to support this new boot environment. When JET 4.2 is released, the 'grub' installation method will be part of the core JET product.

When using JetNEWBOOT, all you need to amend in your template is the

   * base_config_allocation_method="newboot"

As a guide to what to use:

   * With Solaris 10 GA (03/05)
         o base_config_allocation_method="dhcp"
   * With Solaris 10 Update 1 (01/06) and above, JET (< 4.2) and JetNEWBOOT
         o base_config_allocation_method="newboot"
   * With Solaris 10 Update 1 (01/06) and above, JET (>= 4.2)
         o base_config_allocation_method="grub"

JetNEWBOOT is now part of the downloadable bundle from Sun but will not be required once JET 4.2 is released.

==== Using 'iso' images instead of CD/DVDs

The following was derived from information at http://www.unix.com/showthread.php?t=18074

When using Solaris ISO images, the start of the image contains a hsfs (high sierra filesystem) with a couple of ufs filesystems appended to the end of it.

The problem, is that using lofiadm, only the hsfs image is spotted and made available; the ufs filesystems are not seen, so you end up with broken links to 's1' and the like.

To set up a JumpStart server using Solaris ISO images, you must have access to both slice 0 and slice 1 on the image.

To fix the problem, split the contents of slice 1 into it's own image file and then mount this image separately using lofi.

The following procedure describes how to do this. Code:

  1. ls -l sol-9*

-rw-r--r-- 1 root root 576364544 Jan 1 11:16 sol-9-u1-sparc-v1.iso -rw-r--r-- 1 root root 291962880 Jan 1 21:42 sol-9-u1-sparc-v2.iso

This only applies to CD 1, all other isos can be mounted using lofiadm in the normal way.

(1) Get a copy of the VTOC from the ISO image: Code:

  1. dd if=sol-9-u1-sparc-v1.iso of=vtoc bs=512 count=1

1+0 records in 1+0 records out

(2) Now find out where Slice 1 starts in the image and how long it is. The starting cylinder for slice 1 is located at offset 452 (decimal) into the VTOC; the length in blocks is at offset 456, with both being 4 bytes long. Code:

  1. od -D -j 452 -N 8 < vtoc

0000000 0000000888 0000546560 0000010

Slice 1 starts on cylinder 888, and is 546,560 blocks long. CD for the Solaris OS always have 640 blocks per cylinder, so you can find the starting block of slice 1 as follows: Code:

  1. echo 888*640 | bc


So now you know s1 starts at block 568320 and is 546560 blocks long.

(3) Copy slice one into a separate file: Code:

  1. dd if=sol-9-u1-sparc-v1.iso of=sol-9-u1-sparc-v1-s1.iso bs=512 skip=568320 count=546560

546560+0 records in 546560+0 records out

(4) Mount both slice 0 and slice 1 as follows: Code:

  1. mkdir /cd
  2. mkdir /cd/s0
  3. mkdir /cd/s1
  4. lofiadm -a /path_to/sol-9-u1-sparc-v1.iso


  1. lofiadm -a /path_to/sol-9-u1-sparc-v1-s1.iso


When you mount slice 1, remember that it is a UFS partition, not HSFS as is usual on a CD-ROM: Code:

  1. mount -F hsfs -o ro /dev/lofi/1 /cd/s0
  2. mount -F ufs -o ro /dev/lofi/2 /cd/s1
  3. cd /cd/s0/Solaris_9/Tools/
  4. ./setup_install_server /destination_dir

==== How To Upgrade JET

Upgrading JET is normally as easy as

   * pkgrm SUNWjet
   * pkgadd -d . SUNWjet

The JET packages were designed so that they don't remove your configs, templates or other 'configuration' settings when removed. However, if you hack the JET scripts etc, then this will remove your customisations - hence the reason hacking JET is frowned upon and you are recommended to look at writing your own modules instead.

However, if you are upgrading from JET 3.x to 4.x, then you need to do some additional work. The following was taken from Mike's Sun blog

   Things might be a little trickier if you've already got JET 3.7.3 installed, and you want to keep you existing templates etc. The easiest way to accomplish this is to pkgrm all your existing JET packages. (SUNWjet, and all the packages that start with JET), and then
       mv /opt/jet /opt/SUNWjet
   Finally install the new JET packages.If you've created you own custom modules or scripts, you may need to check them to ensure you haven't hard-coded any /opt/jet paths in them.

The extra bits are

   * remember to update your .profile with the new path (/opt/SUNWjet/bin)
   * if you have any existing clients, you will need to re-run 'make_client' on them, as /etc/bootparams and/or dhcp macro table will have the directory /opt/jet mentioned as the config directory, rather than the new /opt/SUNWjet

==== How to set up JET as a PXE (DHCP) Server

The easiest way of setting up JET to serve up PXE boot clients (or other DHCP clients) is to copy, edit and then run the "helper script".

cp /opt/SUNWjet/Products/base_config/solaris/make_dhcp /var/tmp

edit it to suit your network ie


   dhcpconfig -D -r SUNWfiles -p /var/tmp

   dhcpconfig -N ${NETWORK} -m ${NETMASK} -t ${ROUTER}

Then run it, /var/tmp/make_dhcp

JET will now "do the right thing" based on the allocation method in your template.

==== I noticed alot of docs for jumpstart setup for solaris8,9 I dont see one for solaris10. Why isnt there one for 10? i am interesting in setting up jumpstart for upgrades and clean install. is is safe to do jumpstart straioght from sol7 to sol10?

JET was originally developed in the era of Solaris 7, 8 and 9. As such whatever documentation there is, normally uses one of those in examples.

JET works fine with Solaris 10, and unless anything specific is said, it works in the same fashion with 10 (and indeed 11) in the same fashion as previous versions of Solaris.

JET doesn't deal with upgrades at all; if you want to upgrade using JumpStart, then you need to hand-craft something - there are too many risks for JET to be able to claim to work properly in every situation, so it doesn't claim to do upgrades at all.