Provisioning the Solaris 10 Operating System
This section provides instructions for provisioning the Solaris 10 OS by using the browser interface or the command line. This procedure will familiarize you with the provisioning process and the most reliable method for performing aggregate server installations at any skill level.
The example that follows the procedure provides the command-line equivalents for provisioning the Solaris 10 OS. The command-line interface is the most efficient method for performing aggregate installations for more experienced system administrators.
To Provision
the Solaris 10 OS
Before You Begin
-
Read Discovering Servers.
-
Download the Solaris 10 DVD ISO file to a directory that is accessible by the management server.
Steps
-
Copy the Solaris 10 OS ISO file to the management server.
N1-ok> create os os file file-location
Note –This operation is CPU intensive and might take several minutes to complete.
A default OS profile is created on the management server. To view the list of OS profiles, type show osprofile all.
See To Copy an OS Distribution From ISO Files or To Copy an OS Distribution From CDs or a DVD for more information.
-
(Optional) Set up a flash archive file on the management server.
-
(Optional) Create a custom post-installation script to configure the bge1 data network interface when the server boots. Save the file on the management server.
The following sample script configures the provisionable server's bge1 data network interface at system boot using the data network DHCP server.
DEVICE=bge1 BOOTPROTO=dhcp ONBOOT=yes
-
(Optional) Customize the default OS profile so that it uses a flash archive and a post-installation script.
N1-ok> set osprofile osprofile flar flar
The flar attribute value is the full path and flash archive file name, for example, /jumpstart/Flash/archive1.flar.
N1-ok> add osprofile osprofile script script type type
The script attribute value is the full path and script file name, for example, /etc/sysconfig/network-scripts/ifcfg-bge1.
The type attribute specifies the time when the custom script will run during the installation. Valid values for the type attribute are:
-
pre– Run the script before the installation (for example, drivers).
-
post – Run the script after the installation.
-
postnochroot– Run the script after the installation. The script does not have to be run as superuser (root).
The OS profile is modified to use the designated post-installation script and the flash archive file.
-
-
Show the drag-and-drop OS profile icon on the Dashboard tab.
-
(Optional) Connect to the serial console of the provisionable server.
-
Choose Servers By Group from the View Selector menu.
The Server Groups table appears.
-
Drag and drop the OS profile icon from the Shortcuts pane to a server group.
The Load OS Profile wizard appears. Use the wizard steps to guide you through the screens.
-
To begin loading the OS profile on the selected servers, click the Finish button in the final step of the wizard.
The wizard window closes and a job number appears in the Command Line pane.
-
Track the OS profile installation by using any of the following methods:
-
View the Serial Console window output from Step 5.
-
Click the Jobs tab to view the OS Load job, and click the Job ID for details.
-
Click the Event Log tab to view any events generated by the job.
-
Example 3–1 Provisioning the Solaris 10 OS Through the Command Line
For the following example, assume that you have created a Solaris 10 OS on x86 platform flash archive file named archive1.flar and that you have created a post-installation script called ifcfg-bge1. Your management server is also assumed to be running the Solaris 10 OS on x86 platform software.
The following example shows how to copy an OS distribution from the /tmp/solarisdvd.iso file.
N1-ok> create os solaris_ver10 file /tmp/solarisdvd.iso Job "1" started. |
The following example shows how to add a line to the /etc/dfs/dfstab file, below the last comment, which creates the /jumpstart/Flash directory.
# vi /etc/dfs/dfstab |
# Put custom additions below (Do not change/remove this line) share -F nfs -o ro,anon=0 -d "Flash Share" /jumpstart/Flash |
The following example shows how to copy the flash archive to the /jumpstart/Flash directory.
# cp /tmp/archive1.flar /jumpstart/Flash/ |
The following example shows how to restart NFS.
# /etc/init.d/nfs.server stop # /etc/init.d/nfs.server start |
The following example shows how to create an OS profile that uses the flash archive.
N1-ok> create osprofile solaris_ver10 rootpassword admin flar /jumpstart/Flash/archive1.flar description "solaris 10with flar" os solx86 Job "2" started. |
The following example shows how to add a swap partition to the OS profile.
N1-ok> add osprofile solaris_ver10 partition swap sizeoption fixed size 2048 device c1t1d0s1 type swap |
The following example shows how to add a root partition to the OS profile.
N1-ok> add osprofile solaris_ver10 partition / sizeoption free device c1t1d0s0 type ufs |
The following example shows how to add a post-installation script to the OS profile.
N1-ok> add osprofile solaris_ver10 script /etc/sysconfig/network-scripts/ifcfg-bge1 type post |
The following example shows how to load the OS profile on a server group with the name devgroup.
N1-ok> load group devgroup osprofile solaris_ver10 excludeserver=192.168.73.205,192.168.73.31,192.168.73.14 networktype=static ip=192.168.72.201-192.168.73.214 Job "3" started. |
The excludeserver subcommand shows you how to exclude from the load operation, certain provisionable IP addresses. The networktype attribute specifies the static IP range to assign to the provisioned servers.
The following example shows how to view the job status.
N1-ok> show job 3 Job ID: 3 Date: 2005-06-01T13:11:46-0600 Type: OS Load Status: Completed (2005-06-01T13:11:59-0600) Owner: root Errors: 0 Warnings: 0 |
Troubleshooting
See Also
Next Steps
- © 2010, Oracle Corporation and/or its affiliates