test

Sun N1 Service Provisioning System User's Guide for OS Provisioning Plug-In 3.0

Creating Non-JET Solaris Provisioning Profiles

If you prefer to manually create the Solaris provisioning profiles, you can create the Solaris profile without using JET modules. This section describes how to create non-JET Solaris profiles.

If you prefer to use JET to generate your profiles, see Creating Solaris Provisioning Profiles With JET.

ProcedureHow to Create a Non-JET Solaris Provisioning Profile (Browser Interface)

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.

Before You Begin

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.

Steps

  1. In the Common Tasks section of the provisioning software page, select OS Provisioning.

  2. On the OS Provisioning Common Tasks page, click Create Profile in the Solaris Images section.

  3. On the Plans Details page, click Run.

  4. 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.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. Type the Solaris main version number into the version variable.

      4. Type the Solaris minor version number into the release variable.

      5. 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

        		 

      6. Save the variables set.

      7. Select the variables set that you just saved from the drop-down menu in the SolarisImage component row of the Plan Parameters table.

  5. On the Plan Details Run page, select the Solaris image server on which to create the profile.

    Tip –

    The host name of the Solaris image server ends in -solaris.

  6. If needed, change the Profile Name.

  7. If needed, change the Profile Description.

  8. Deselect the checkbox for Use the Jet Modules Specified Above.

  9. Click Run Plan (includes preflight).

  10. 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/.

  11. (Optional) Change default profile values.

    1. Navigate to the Solaris folder that contains the new Provision component.

      For example, /com/sun/n1osp/autogen-biss1-jet/provision/.

    2. Click the Solaris provisioning component name.

      For example, Solaris10_0205_sparc.standard.

    3. Edit default values.

      For information about Solaris profile variables, see Appendix B, Solaris Profile Component Variables.

      Note –

      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

      1. Click the Edit button at bottom of Details page.

      2. Change values.

        Note –

        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.

      3. Click the Check-in button at the bottom of the Details page.

ProcedureHow to Create a Non-JET Solaris Provisioning Profile (Command-Line Interface)

Steps

  1. To create a variable set for the SolarisImage component, type a command similar to the following example:


    # cr_cli -cmd cdb.vs.add -comp NM:/com/sun/n1osp/untyped/SolarisImage \
-name "solaris9" -u admin -p admin -vars "version=9;release=u7;architecture=sparc; \
image_path=/export/install/Solaris_9;image_subnet_addr=10.42.42.2; \
image_subnet_mask=255.255.255.0;media_src="

  2. To provide JET module information, create a file /tmp/solaris-profile that contains the following entries:

    standard-nojet
Standard Solaris
base_config spsra
false

    Where:

    • The first line in the file corresponds to the Profile Name field in the plan variables section of the browser interface.

    • The second line in the file corresponds to the Profile Description field in the plan variables section of the browser interface.

    • The third line in the file corresponds to the JET Module Name field in the plan variables section of the browser interface.

    • The fourth line in the file corresponds to the Use the Jet Modules Specified Above checkbox in the plan variables section of the browser interface

  3. To run the plan, type a command similar to the following example:


    # cr_cli -cmd pe.p.run -u admin -p admin
-PID NM:/com/sun/n1osp/untyped/SolarisImage-create-profile
-tar H:NM:biss1-jet -comp - -vs solaris9 -pto 30 -nto 10
-f /tmp/solaris-profile

    Note the default N1 SPS user value you specified with the -u option. This user must exist after the OS installation for the N1 SPS Remote Agent software to start on the target host.