Creating a jumpstart server, and flash archive. By admin 08 November 2008 at 6:06 pm and have

SETTING UP BOOT & INSTALL SERVERS
JumpStart clients install the Solaris Operating System from the installation image. For example, if you spool the Solaris 10 Operating System into a directory called /export/jumpstart, the installation image would be located in the /export/jumpstart/Solaris_10/Product directory.

#cd /cdrom/cdrom0/s0/Solaris_10/Tools

1.    First we use the setup_install_server command to install the software onto the hard drive

#../setup_install_server /export/jumpstart

2.    The system will start the installation and display a short message saying it is copying Solaris
3.    When the install server setup is complete, you must eject the CD

#eject cdrom

4.    Insert CD2 of your solaris release.
5.    To add additional discs

#./add_install_server

The products will be copied to the jumpstart directory.
This is done for each CD you would like to add to the install server.
CONFIGURATION SERVER
The configuration server holds all the custom jumpstart files including

Rules—-
•    Rules.ok—–
•    (class file)basic_pro—-
•    check —
•    Begin—
•    Finish—

To setup a configuration server you must setup a configuration directory.
1.    We will create and use the /export/jumpstart directory.

#mkdir  jumpstart

2.    The directory must be shared so it can be accessed across the network.
Edit the /etc/dfs/dfstab file to add an entry:

#shareall –F nfs –o ro,anon=0 /export/jumpstart

And for the config directory

#shareall -F nfs -o rw,anon=0 /export/config

Next we edit the files we will need for the configuration server to work.
CREATE A RULES FILE
1.    Create a rules file:

#vi rules

hostname bit                       -             basic_prof    finish1
hostname mind                      -             basic_prof    finish1
hostname frames                    -             basic_prof    finish1

The entries in the rules file will match target clients based on: network, hostname, architecture and memory. We will go by hostname  and our profile will be called basic_prof. We are also using a  finish script is called finish1,The finish script is used to copy the hosts file to each machine after installation has completed and set the password to root.
2.    After you create your rules file you must check it.
check rules file

# cd /jumpstart
#  ./check

Validating rules…
Validating profile basic_prof…
The custom JumpStart configuration is ok.

CREATING A PROFILE
Next create a profile based on the requirements for the station. We will use an initial installation and  set the partitioning to explicit.
1.    Create basic_prof:

#vi basic_prof

# —————–       —————–
# This profile keyword is required in every profile
install_type                initial_install
system_type                 standalone
partitioning                explicit
filesys                     rootdisk.s0     5000    /
filesys                     rootdisk.s1     2000    swap
filesys                     rootdisk.s3     5000    /home
cluster                    SUNWCXall

•    System type will be set as standalone for workstations.
•    Partitioning will be set to explicit.
•    Slice 0 will be given 5Gb
•    Slice 1 will be given 2Gb
•    Slice 3 will be given 5Gb

CREATE A SYSIDCFG FILE
Next we can create a sysidcfg file for the workstations.
1.    Create a Sysidcfg

system_locale=en_US
timezone=US/Pacific
timeserver=localhost
name_service=DNS {domain_name=thc.bitmindframes.info name_server=192.168.0.1}
root_password=kFWfYZ9gO60Jw
system_locale=C
network_interface=Primary {hostname=bit default_route=192.168.0.254 ip_address=192.168.0.213 netmask=255.255.255.0 protocol_ipv6=no}
security_policy=none
nfs4_domain=thc.bitmindframes.info

As an option you can create a begin and finish script,The finish script we created will copy the hosts file to the workstations and create a root password = password.

#!/bin/bash
##copy the /etc/hosts and /etc/ethers files from the config server to
##each of the clients
${SI_Config_Dir} /export/jumpstart /a /etc/hosts
${SI_Config_Dir} /etc/ethers /a /etc/ethers
set_root_pw=password

Now that the jumpstart directory is created and shared and we have created sysidcfg, profile, finish script and checked the rules file we can add an install client.

2.    Add an install clien t:

add_install_client -e 0:3:ba:cf:3e:c6 -s 192.168.0.8:/export/jumpstart  -c 192.168.0.8:/export/jumpstart -p 192.168.0.8:/export/config/bit bit sun4u

3.    We can now test the jumpstart process,
Enter STOP + A to enter the boot prompt.
At the ok prompt type:

ok boot net – install

The system will reboot and start the jumpstart process.

Creating a Flash archive for Flash archive installation

Login to the MASTER system as root.

1.    Run the system in single user mode

#init s

2.    To create the flash archive you must enter the command:

# flarcreate -n sb100 /export/flash /sb100.flar

3.    On the jumpstart server edit the sysidcfg file:
Edit these lines:

install_type= flash_install

4.    To update a differential install use:

install_type= flash_update
archive_location=export/flash

5.    Save and exit VI
6.    On the install server, add the clients:

./add_install_client -e 0:3:ba:cf:3e:c6 -s 192.168.0.8:/export/jumpstart  -c 192.268.0.8:/export/jumpstart -p 192.168.0.8:/export/config/bit bit sun4u

7.    Jumpstart the system using:
STOP + A
At the ok prompt type:

Boot net – install

Tags: guides, cisco, vlan, study, 802.1q, ip


Share and Enjoy: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • bodytext
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google
  • Furl
  • Live
  • Reddit
  • StumbleUpon
  • Technorati