In certain circumstances, you might want to manually create the Solaris Provisioning profile, rather than generating a profile with JET. For example, if you have an existing custom JumpStart environment that you want to import into your N1 SPS environment, you need to manually create the OS Provisioning profile to include the information about your JumpStart files.
Make sure the Solaris image server exists and that the Solaris operating system software is available to that server. For more information about creating the Solaris image server, see Setting up the Solaris JET Server.
In the Common Tasks section of the provisioning software page, select OS Provisioning.
On the OS Provisioning Common Tasks page, click Create Profile in the Solaris Images section.
On the Plans Details page, click Run.
Choose variables to use for this plan.
To use an existing variables set, select a name from the drop-down menu in the SolarisImage component row of the Plan Parameters table.
To create a new variables set, click Select from List in the SolarisImage component row of the Plan Parameters table.
Click Create Set.
Type a name for the variables set.
Type the Solaris main version number into the version variable.
Type the Solaris minor version number into the release variable.
Verify variables and change them, if needed.
The following table describes the additional variables and their default values.
Variable Name |
Description |
Default Value/Example |
---|---|---|
architecture |
Architecture of the physical system, for example, SPARC or x86 |
sparc (Default) |
installPath |
Solaris image name to attach |
Solaris:[version]_:[release]_:[architecture] For example: Solaris9_u7_sparc |
image_path |
Path to location where image file resides |
/export/osp_image/:[installPath] (Default) |
image_subnet_addr |
Subnet address of the image server |
:[target(/):sys.ipAddress] (Default) |
image_subnet_mask |
Subnet mask of the image server |
255.255.255.0 (Default) |
media_src |
Path to the image files. | |
ISO_files |
List of ISO files located in the directory specified in the media_src variable |
Save the variables set.
Select the variables set that you just saved from the drop-down menu in the SolarisImage component row of the Plan Parameters table.
On the Plan Details Run page, select the Solaris image server on which to create the profile.
The host name of the Solaris image server ends in -solaris.
If needed, change the Profile Name.
If needed, change the Profile Description.
Deselect the checkbox for Use the Jet Modules Specified Above.
Click Run Plan (includes preflight).
To verify that the Solaris profile is created to the Solaris image server, click Components in the left pane of the N1 SPS browser interface.
You should find a provision component in the folder /com/sun/n1osp/autogen-server-name-solaris/provision/, where server-name is the Solaris server name that you provided in the variable set. For example: /com/sun/n1osp/autogen-Solaris9_u7_sparc-solaris/provision/.
(Optional) Change default profile values.
Navigate to the Solaris folder that contains the new Provision component.
For example, /com/sun/n1osp/autogen-biss1-jet/provision/.
Click the Solaris provisioning component name.
For example, Solaris10_0205_sparc.standard.
Edit default values.
For information about Solaris profile variables, see Appendix B, Solaris Profile Component Variables.
If you are provisioning the Solaris OS to an x86 target host, you must create a custom JumpStart profile that deletes all existing partitions on the target host. For the profile_base_config variable value, point to the location of this profile
Click the Edit button at bottom of Details page.
Change values.
If you want to use an existing JumpStart environment for your provisioning plan, set the values for the osp_profile_jumpstart_ip_address and osp_profile_jumpstart_directory variables to point to the directory and IP address of your JumpStart files.
Click the Check-in button at the bottom of the Details page.