This procedure describes how to set up and deploy a flash archive on a server or a server group by using the command line.
Copy an OS distribution to the management server.
See To Copy an OS Distribution From ISO Files or To Copy an OS Distribution From CDs or a DVD.
Create a flash archive file appropriate for use by N1 System Manager. See To Create a Flash Archive.
Flash archives for complete Solaris installations might be too large to provision successfully if the management server is running Linux. Consider compressing the file or using a smaller flash archive with less content.
Log in to the management server as root.
See To Access the N1 System Manager Command Line in Sun N1 System Manager 1.3 Discovery and Administration Guide for details.
To make the shared flash archive directory available through NFS, perform one of the following actions:
If your management server is running the Solaris operating system, modify the /etc/dfs/dfstab file.
Add share -F nfs -o ro,anon=0 -d "Flash Share" /jumpstart/Flash below the last comment in the file.
For example:
# Put custom additions below (Do not change/remove this line) share -F nfs -o ro,anon=0 -d "Flash Share" /jumpstart/Flash |
If your management server is running Linux, modify the /etc/exports file.
Add /jumpstart/Flash *(ro,no_root_squash) below the last comment in the file.
For example:
# Put custom additions below (Do not change/remove this line) /jumpstart/Flash *(ro,no_root_squash) |
Copy the flash archive file to the /jumpstart/Flash directory.
To restart NFS, perform one of the following actions:
If your management server is running the Solaris OS version 9, type the following commands:
# /etc/init.d/nfs.server stop # /etc/init.d/nfs.server start |
If your management server is running the Solaris OS version 10 or later, type the following command:
# svcadm restart svc:/network/nfs/server:default |
If your management server is running Linux, type one of the following commands:
# /etc/init.d/nfs restart # /etc/rc3.d/S60nfs restart |
Create an OS profile that specifies the location of the flash archive file that you copied in Step 3.
N1-ok> create osprofile osprofile-name os os-name rootpassword rootpassword flar flar description description language language timezone timezone |
The flar attribute value is the path and flash archive file name, for example, /jumpstart/Flash/archive1.flar.
The OS profile is created.
To verify the OS profile settings, type the following command:
N1-ok> show osprofile osprofile-name |
The OS profile details appear. Check that the partition settings are appropriate for your business needs. See To Create an OS Profile for partition settings and examples.
Load the OS profile on a server or a server group.
The following example shows how to create an OS profile that uses a flash archive file.
N1-ok> create osprofile solaris9_flar rootpassword admin description "solaris 9 with flar" os solx86 flar /jumpstart/Flash/S9-u7-req-v20z.archive |
The following examples show how to add root and swap partitions to the OS profile.
N1-ok> add osprofile solaris9_flar partition / sizeoption free device c1t1d0s0 type ufs N1-ok> add osprofile solaris9_flar partition swap sizeoption fixed size 128 device c1t1d0s1 type swap |
The following example shows how to deploy the modified OS profile to a server.
N1-ok> load server 192.168.73.2 osprofile solaris9_flar networktype=static ip=192.168.73.244 |
The networktype attribute specifies that the installed host is assigned the 192.168.73.244 IP address.