How to Import a Non-Global Zone as a Physical Host in the N1 Service Provisioning System

1. In the Common Tasks section in the N1 SPS browser interface, click SAP.

2. Click the Solaris Non-Global Zone as a Physical Host: Attach link.

   The Plan Details page is displayed.

3. Click Run.

   The Plan Details Run page is displayed.

4. In the Plan Parameters section of the page, click the Select From List link in the Variable Settings column.

   The Select Variable Settings From List window is displayed.

5. Click the Create Set link at the bottom of the Select a Variable Setting table.

   A new variable set column is displayed in the Select a Variable Setting table.

6. Type the name of the container component variable set in the Set Name text field.

7. Edit the variable settings by selecting the check box for each variable that you want to modify, then typing the value in the text field.

   ---

   Note –

   Be sure to specify the name of the non-global zone that you want to import for the installPath variable.

   ---

   local_zone_base_path

   Required. Specifies the boot path to the non-global zone file system.

   local_zone_autoboot

   Required. Setting this variable value to TRUE specifies that the non-global zone should be booted during system boot. Setting this variable to FALSE specifies that the non-global zone should not be booted at system boot. Default is FALSE.

   local_zone_pool

   Specifies the resource pool to which this non-global zone is assigned.

   installPath

   Required. Specifies the name of the non-global zone that you want to import.

   local_zone_filesystem

   Required. Specifies the type of file system for the non-global zone.

   globalZoneHostName

   Required. Specifies the name of the global host on which the non-global zone is installed.

   zoneIfaceDetails

   Specifies the network interface information for the non-global zone. Use the pound sign (#) as a delimiter between multiple entries.

   Example: hme0,192.168.2.5/6#eri0,192.167.2.4/5

   zoneFsLayout

   Specifies the file systems in the global zone to mount in the non-global zone. Use the pound sign (#) as a delimiter between multiple entries.

   Example: dir=/usr/local special=/opt/local raw=/dev/rdsk/c0t0d0s7 type=lofs [ro,nodevices]#dir=/opt/mydir special=empty type=lofs ro

   inheritPkgDir

   Specifies the global zone directories to inherit on the non-global zone. Use the pound sign (#) as a delimiter between multiple entries.

   ---

   Note –

   You must set the local_zone_filesystem variable to SPARSE to use this variable.

   ---

   Example: /opt/sfw#/var/tmp

   device

   Specifies the device file systems for the non-global zone. Use the pound sign (#) as a delimiter between multiple entries.

   Example: /dev/sound#/dev/cdrom

   rctl

   Specifies the name value pairs for the resource controls to use with this non-global zone. Use the pound sign (#) as a delimiter between multiple entries.

   Example: zone.cpu-shares:priv=priveleged,limit=20,action=none#zone.max-lwps:priv=priveleged,limit=500,action=deny

   attributes

   Specifies the attributes for the non-global zone. Use the pound sign (#) as a delimiter between multiple entries.

   Example: audio:boolean:true#group:string:zoneUser

   For information about the zone information to include for each variable, see the zoneadm(1M) and zonecfg(1M) man pages.

8. Click the Save button.

   The Select Variable Settings From List window is displayed, with your new variable set included in the table.

9. Click the Select button at the bottom of the column for the variable set you created.

   The Plan > Details > Run page is displayed.

10. Specify the target host from which you want to import the non-global zone.

11. In the Plan Variables section, specify the install path of the non-global zone that you want to import.

12. If necessary, modify the values in the Limits section.

13. Click Run Plan (Includes Preflight).

    The non-global zone is imported into your N1 SPS environment from the target host. You can now manage the non-global zone as a zone host with the SAP plug-in.

Next Steps

Based on your business needs, you can create a Logical Host or High Availability Storage component for the non-global zone. When you create the Logical Host or High Availability Storage component, you must not change the default value of the globalZoneHostName. For more information, see Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.

After you create the Logical Host or Storage component for this non-global zone, you can provision SAP resources into this non-global zone. For more information, see Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.