X

News, tips, partners, and perspectives for the Oracle Solaris operating system

What is Flash archive Installation?

Guest Author
Flash archive installation is a method to clone a reference system (Master) and use the image to install any number of new systems (called clones) for the same architecture. It can be used with the Jumpstart installation method of Solaris OS. The following retrieval methods are available:
1.) HTTP 2.) NFS 3.) Local File 4.) Local Tape 5.) Local Device.
Flash archive installation can be used for deploying multiple clusters with a standard configuration (version, Apps & patches).
STEPS:
=====
\*To install systems with OS, sun cluster and boot it into cluster mode with a single reboot, follow the below mentioned procedure\*. Archive of an existing installation can be made even on a live system using flarcreate command.
eg) flarcreate -n chips.b72.flar /export/flars/chips.b72.flar
for more details, refer to the flarcreate man page.
The following procedure assumes knowledge of Jumpstart installation. In the following example, we assume that the install server and boot server are the same. For more details on install server and boot server, refer to the jumpstart installation guide.
Also determine the topology and the interconnect details. For simplicity, we'll configure a 2 node cluster with 2 interconnects between them.
1.) On the config server, create /tftpboot directory. (if there is no /tftpboot directory, Jumpstart option will be disabled)
2.) create a directory for the rules file and the check utility (/export/jumpstart).
3.) Copy the check utility from the solaris tools cd for the OS version that is to be used.
4.) cd to the Sun cluster image and run scinstall
bash-3.00# cd /cdrom/cdrom0/dvd.jas/Solaris_sparc/Product/sun_cluster/Solaris_10/Tools/
bash-3.00# ./scinstall
\*\*\* Main Menu \*\*\*
Please select from one of the following (\*) options:
1) Create a new cluster or add a cluster node
\* 2) Configure a cluster to be JumpStarted from this install server
\* 3) Manage a dual-partition upgrade
\* 4) Upgrade this cluster node
\* 5) Print release information for this cluster node
\* ?) Help with menu options
\* q) Quit
Option:2
\*\*\* Custom JumpStart \*\*\*
This option is used to configure each node in a cluster to be JumpStarted from this Solaris install server. Before this option can be used, this server must already be set up as a Solaris install server and configured to JumpStart each node as a Solaris install client. Refer to the Solaris documentation for more information on how to set up a Solaris install server, Solaris install clients, and a custom JumpStart directory.
You will be asked to provide all of the information usually needed to directly add each node to a cluster. This information will be stored for later use under whatever custom JumpStart directory you specify. The rules file will be updated to point to both default Solaris install profile and a special custom JumpStart finish script.
Press Control-d at any time to return to the Main Menu.
Do you want to continue (yes/no) [yes]?
>>> Custom JumpStart Directory <<<
In order to set up an install server to install and configure Sun Cluster nodes using custom JumpStart, each node must already be set up in the usual way for Solaris JumpStart installation. In particular, you must have already run add_install_client(1M) with a -c option specifying a JumpStart directory on this install server. In addition, this JumpStart directory must already exist and must contain the "check" utility. However, it is not necessary to create a "rules" file; scinstall will create or update this file with the necessary install rules for each cluster node.
For more information regarding JumpStart and setting up a Solaris install client, please refer to the install_scripts(1M) man page and the Solaris installation documentation.
What is your JumpStart directory name? /export/jumpstart
>>> Typical or Custom Mode <<<
This tool supports two modes of operation, Typical mode and Custom. For most clusters, you can use Typical mode. However, you might need to select the Custom mode option if not all of the Typical defaults can be applied to your cluster.
For more information about the differences between Typical and Custom modes, select the Help option from the menu.
Please select from one of the following options:
1) Typical
2) Custom
?) Help
q) Return to the Main Menu
Option [1]:
>>> Cluster Name <<<
Each cluster has a name assigned to it. The name can be made up of any characters other than whitespace. Each cluster name should be unique within the namespace of your enterprise.
What is the name of the cluster you want to establish [chips]?
>>> Cluster Nodes <<<
This Sun Cluster release supports a total of up to 16 nodes.
Please list the names of all cluster nodes planned for the initial cluster configuration. You must enter at least one node. List one node name per line. When finished, type Control-D:
Node name: pchips1
Node name: pchips2
Node name (Control-D to finish): \^D
This is the complete list of nodes:
pchips1
pchips2
Is it correct (yes/no) [yes]?
>>> Cluster Transport Adapters and Cables <<<
You must configure at least two cluster transport adapters for each node in the cluster. These are the adapters which attach to the private cluster interconnect.
For node "pchips1",
What is the name of the first cluster transport adapter [bge2]?
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
For node "pchips1",
What is the name of the second cluster transport adapter [bge3]?
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
For node "pchips2",
What is the name of the first cluster transport adapter [bge2]?
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
For node "pchips2",
What is the name of the second cluster transport adapter [bge3]?
Will this be a dedicated cluster transport adapter (yes/no) [yes]?
>>> Quorum Configuration <<<
Every two-node cluster requires at least one quorum device. By default, scinstall will select and configure a shared SCSI quorum disk device for you.
This screen allows you to disable the automatic selection and configuration of a quorum device.
The only time that you must disable this feature is when ANY of the shared storage in your cluster is not qualified for use as a Sun Cluster quorum device. If your storage was purchased with your cluster, it is qualified. Otherwise, check with your storage vendor to determine whether your storage device is supported as Sun Cluster quorum device.
If you disable automatic quorum device selection now, or if you intend to use a quorum device that is not a shared SCSI disk, you must instead use scsetup(1M) to manually configure quorum once both nodes have joined the cluster for the first time.
Do you want to disable automatic quorum device selection (yes/no) [no]?
>>> Confirmation <<<
Your responses indicate the following options to scinstall:
-----------------------------------------
For node "pchips1",
scinstall -c /export/jumpstart -h pchips1 \\
-C chips \\
-F \\
-T node=pchips1,node=pchips2,authtype=sys \\
-w netaddr=172.16.0.0,netmask=255.255.248.0,maxnodes=64,maxprivatenets=10 \\
-A trtype=dlpi,name=bge2 -A trtype=dlpi,name=bge3 \\
-B type=switch,name=switch1 -B type=switch,name=switch2 \\
-m endpoint=:bge2,endpoint=switch1 \\
-m endpoint=:bge3,endpoint=switch2 \\
-P task=quorum,state=INIT
Are these the options you want to use (yes/no) [yes]?
-----------------------------------------
For node "pchips2",
scinstall -c /export/jumpstart -h pchips2 \\
-C chips \\
-N pchips1 \\
-A trtype=dlpi,name=bge2 -A trtype=dlpi,name=bge3 \\
-m endpoint=:bge2,endpoint=switch1 \\
-m endpoint=:bge3,endpoint=switch2
Are these the options you want to use (yes/no) [yes]?
-----------------------------------------
Do you want to continue with JumpStart set up (yes/no) [yes]?
Created "/export/jumpstart/autoscinstall.d/nodes/../clusters/chips/pchips1"
Created "/export/jumpstart/autoscinstall.d/nodes/pchips1/autoscinstall.data"
Updating "rules" file for host "pchips1" ...
Running the "check" utility...
--------------------------------
Validating rules...
Validating profile autoscinstall.d/3.2/autoscinstall.class...
The custom JumpStart configuration is ok.
--------------------------------
Created "/export/jumpstart/autoscinstall.d/nodes/../clusters/chips/pchips2"
Created "/export/jumpstart/autoscinstall.d/nodes/pchips2/autoscinstall.data"
Updating "rules" file for host "pchips2" ...
Running the "check" utility...
--------------------------------
Validating rules...
Validating profile autoscinstall.d/3.2/autoscinstall.class...
The custom JumpStart configuration is ok.
--------------------------------
Press Enter to continue:
\*\*\* Main Menu \*\*\*
Please select from one of the following (\*) options:
1) Create a new cluster or add a cluster node
\* 2) Configure a cluster to be JumpStarted from this install server
\* 3) Manage a dual-partition upgrade
\* 4) Upgrade this cluster node
\* 5) Print release information for this cluster node
\* ?) Help with menu options
\* q) Quit
Option: q
Make the jumpstart directory a NFS share.
5.) Create a directory for storing the archives. Copy the archive to the directory and share the directory.
bash-3.00# ls -l /export/flars/
-rw-r--r-- 1 root root 4032363605 Nov 17 18:18 chips.b72.flar
6.) Modify the autoscinstall.class file to be identical to the one given below.
bash-3.00# vi /export/jumpstart/autoscinstall.d/3.2/autoscinstall.class
install_type flash_install
archive_location nfs pcauvery1:/export/flars/chips.b72.flar
partitioning explicit
filesys rootdisk.s0 free /
filesys rootdisk.s1 4096 swap
filesys rootdisk.s3 512 /globaldevices
filesys rootdisk.s7 20
7.) check validity of the file by running the ./check command.
8.) Modify the /etc/bootparams file on boot server to change the config server (install_config).
pchips1 root=ns:/export/OS_images/s10u3/solarisdvd.s10s_u3dvd/latest/Solaris_10/Tools/Boot install=ns:/export/OS_images/s10u3/solarisdvd.s10s_u3dvd/latest boottype=:in sysid_config=ns:/export/tools/jumpstart/sysid/sc/sparc/s10 install_config=pjoker2:/export/jumpstart rootopts=:rsize=8192 ns=":nis(255.255.255.0)" <== modified install_config
pchips2 root=ns:/export/OS_images/s10u3/solarisdvd.s10s_u3dvd/latest/Solaris_10/Tools/Boot install=ns:/export/OS_images/s10u3/solarisdvd.s10s_u3dvd/latest boottype=:in sysid_config=ns:/export/tools/jumpstart/sysid/sc/sparc/s10 install_config=pjoker2:/export/jumpstart rootopts=:rsize=8192 ns=":nis(255.255.255.0)" <=== Modified install_config
9.) Execute boot net - install on the bootprom of the target nodes.
Madhan Kumar Balasubramanian,
Sun Cluster Engineering

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.