test

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

Setting up the Solaris JET Server

The Solaris boot and install server is a JET server. To set up the JET server, you perform the following tasks.

ProcedureHow to Enable TFTP on a Solaris 10 JET Server

For JET servers that are running the Solaris 8 or 9 releases, JET automatically enables the TFTP service for your deployments. If your Solaris JET server is running the Solaris 10 OS, you must manually enable TFTP service on your JET server. Follow these steps.

Steps

  1. Log in to the Solaris 10 JET server as root.

  2. Type the command svcadm -v enable network/ftp.

    The TFTP service is enabled, and starts when the management server is rebooted. After the system is rebooted, you can verify whether the TFTP service has start using the inetadm command:


    # inetadm
enabled   online         svc:/network/telnet:default
enabled   online         svc:/network/nfs/server:default
disabled  disabled       svc:/network/echo:dgram
disabled  disabled       svc:/network/time:stream
enabled   online         svc:/network/ftp:default

  3. Verify that the /etc/hosts file has entries for loopback and the JET server.

    1. Make certain that either of the following loopback entries is in the /etc/hosts file.


      127.0.0.1    localhost

      or


      127.0.0.1    localhost.localdomain    localhost

    2. Make certain that an entry exists for the JET server and its IP address. For example:


      111.11.111.11 jet.domain jet.domain

      where 111.11.111.11 is the IP address of the Solaris 10 JET server, jet is the name of the JET server, and domain is your company domain name.

      Your /etc/hosts file should be similar to the following example:


      127.0.0.1    localhost.localdomain    localhost
10.5.157.123 biss-jet.company.com

    3. Save and close /etc/hosts.

  4. Reboot the JET server.

ProcedureHow to Enable NFS Services on a Solaris 10 JET Server

For JET servers that are running the Solaris 8 or 9 releases, JET automatically enables the NFS service for your deployments. If your Solaris JET server is running the Solaris 10 OS, you must manually enable NFS service on your JET server. Follow these steps.

Steps

  1. Log in to the Solaris 10 JET server as root.

  2. Type the command svcadm -v enable network/nfs/server.

    The NFS service is enabled, and starts when the management server is rebooted. After the system is rebooted, you can verify whether the NFS service has start using the svcs command:


    # svcs | grep nfs
online         Apr_08   svc:/network/nfs/cbd:default
online         Apr_08   svc:/network/nfs/client:default
online         14:03:18 svc:/network/nfs/status:default
online         14:03:18 svc:/network/nfs/nlockmgr:default
online         14:03:18 svc:/network/nfs/server:default
online         14:03:18 svc:/network/nfs/mapid:default
online         14:03:18 svc:/network/nfs/rquota:default

  3. Add entries to the /etc/dfs/dfstab file for each file system to be shared.

    Add one entry to the file for every file system that you want to be automatically shared. Each entry must be on a line by itself in the file and use this syntax:


    share [-F nfs] [-o specific-options] [-d description] pathname

    See the dfstab(4) man page for a description of /etc/dfs/dfstab and the share_nfs(1M) man page for a complete list of options.

  4. Share the file system.

    After the entry is in /etc/dfs/dfstab, you can share the file system by either rebooting the system or by using the shareall command.


    # shareall

  5. Verify that the information is correct.

    Run the share command to check that the correct options are listed:


    # share
-        /export/share/man   ro   ""
-        /usr/src     rw=eng   ""
-        /export/ftp    ro,public  ""

ProcedureHow to Create the JET Solaris Image Server

You can create a JET image server from the N1 SPS browser interface or command-line interface. To create the server from the command line, type a command similar to the following example:


# cr_cli -cmd pe.p.run -u admin -p admin -PID NM:/com/sun/n1osp/untyped/Jet-create \
-tar H:NM:biss1 -comp - -vs solaris8 + -pto 30 -nto 10

Substitute the appropriate release value for the solaris8 argument.

To create the server from the browser interface, follow these steps.

Steps

  1. Log into the system that is to be the Solaris boot and install server.

  2. If you currently use the JumpStart enterprise toolkit, remove those files.

    Use the following command: # pkgrm SUNWjet

  3. In the Common Tasks section of the N1 SPS browser interface, select OS Provisioning.

  4. On the OS Provisioning Common Tasks page, click Create in the JET Solaris Image Servers section.

  5. On the Plans Details page, click Run.

  6. Choose variables to use for this plan.

    • To use an existing variables set, select a name from the drop-down menu in the JET component row of the Plan Parameters table.

    • To create a new variables set, click Select from List in the JET component row of the Plan Parameters table.

      1. Click Create Set.

      2. Type a name for the variables set.

      3. Verify variables and change them, if needed.

        The image server component has only a few variables, most of which you are unlikely to change. See Solaris Image Server Component Variables for a list of those variables and their default values.

      4. Save the variables set.

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

    • If you want to use another component's variable settings, click Import Set From Component.

      The Import Variable Settings window displays.

      1. If necessary, navigate to the Folder that contains the component with the variable settings you want to import.

      2. Select the component version.

        Note –

        Variable settings can vary between component versions. Ensure that the current components and the component from which you want to import variable settings share common variables. If the component from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable settings are not imported.

      3. Click Import Variable Settings.

        The variables settings are imported, and are displayed in the table.

      4. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.

    • If you want to use component variable settings that are stored in a file, follow these steps.

      1. In the Import Sets from File text field, enter the path to the variable settings file that you want to use.

        To browse through the file system to find the appropriate file, click the Browse button.

      2. Click Import.

        The variables settings are imported, and are displayed in the table.

        Note –

        If the file from which you want to import variable settings does not share common variables with the component you want to use in your plan, the variable set is not imported.

      3. On the Plan Details Run page, select the variable settings that you imported from the Variable Settings drop-down list, then click Select.

  7. Select the host on which to create the JET image server.

  8. Click Run Plan (includes preflight).

  9. To verify that the JET image server is created successfully, click the Hosts link in the left side of the provisioning server window.

    You should see the name of the virtual host appended with -jet. For example, if you installed on host masterserver, the virtual host is masterserver-jet.

Troubleshooting

If your OS provisioning server is located on the same physical host as the boot and install server, you must configure the interfaces on the system before you provision any target hosts. The OS provisioning server does not automatically configure the interfaces of the boot and install server.

Solaris Image Server Component Variables

The following variables apply to the image server component.

Table 5–1 Solaris Image Server Component Variables

Variable Name 

Description 

Default Value 

installPath

Location to install JET package. 

/opt/SUNWjet

sps_cli

Location of N1 SPS command-line interface. 

/opt/SUNWn1sps/N1_Service_Provisioning_System_5.2/cli/bin/cr_cli

jetHost

Name to use for the virtual host name. By default, the virtual JET host name is set to the host name of the target host with -jet appended.

:[target]-jet

jetFolder

Folder where you want to store JET-specific information. By default, the JET folder is located in /com/sun/n1osp/autogen-:[jetHost], where :[jetHost] is the virtual JET host name defined in the previous step.

/com/sun/n1osp/autogen-:[jetHost]

templatePrefix

Value to use to identify the OS provisioning JET templates. 

OSP_TEMPLATE_

Importing Solaris Patches to the JET Solaris Image Server

If you have acquired Solaris patches, and the JET Solaris image server can access those patches through NFS, you can import those patches to the JET Solaris image server. You can then add these patches to your provisioning plans.

ProcedureHow to Import Solaris Patches to the JET Solaris Image Server

Steps

  1. In the Common Tasks section of the N1 SPS browser interface, select OS Provisioning.

  2. On the OS Provisioning Common Tasks page, click Manage in the JET Solaris Image Servers section.

  3. On the Component Details page, select the checkbox for import_product_patches in the Component Procedures table.

  4. In the import_product_patches row, click Run in the Actions column.

  5. On the Plan Details Run page, select the boot and install server to which you want to import the patches from the Current Installations list.

  6. Click Run Selected Installations.

  7. On the Plan Details Run page, specify the variables to use with this plan.

    1. In the JET Module Name field, specify the spsra module.

    2. Specify the product version.

      For example, 5.2.

  8. Specify the architecture of the patches.

  9. In the Media Path field, specify the path to the patches.

  10. Click Run (includes preflight).