How to Import an Existing Non-Global Zone as a Zone Resource in the N1 Service Provisioning System (What's New in the Sun N1 Advanced Architecture for SAP Solutions 5.2 Update 2 Release)

What's New in the Sun N1 Advanced Architecture for SAP Solutions 5.2 Update 2 Release

How to Import an Existing Non-Global Zone as a Zone Resource in the N1 Service Provisioning System

Before You Begin

When you import an existing non-global zone as a zone resource, you must assign the zone resource to an SAP resource group. If you need to create a new resource group, perform the steps described in Creating and Managing Groups in Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.

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

Click the Solaris Non-Global Zone as a Resource: Create link.

The Plan Details page is displayed.

Click Run.

The Plan Details Run page is displayed.

In the Plan Parameters table, select the variable settings for the LocalZone component.
- If the variable settings have been created for this component, select the appropriate settings from the drop-down menu.
- If the variable settings are not available from the drop-down menu, follow these steps.
  1. Click Select From List. The Select Variable Settings From List window displays.
    - To create a new variable settings set, click Create Set and type a Set Name.
      
      The following list provides commonly updated variables for the LocalZone component. To create a value for the component variable, click the check box in the component variable's row.
      
      Note –
      For information about component variables ending in UserExit, see User Exits in Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.
      groupName
      
      Required. Specifies the name of the resource group to which the zone resource will be assigned.
      
      In the Sun Cluster environment, the groupName must equal the Sun Cluster resource group name.
      
      Note –
      If you want to move your zone resource between systems in your N1 AA environment, the resource group to which you assign the zone resource must meet the following requirements.
      
      The group must contain a High Availability Storage component.
      
      The group must not contain a J2EE application server resource.
      
      groupDescription
      
      A description of the group.
      
      resourceName
      
      Required. Specifies the name of the non-global zone that you want to import.
      
      installPath
      
      Required. Specifies the path to the non-global zone.
      
      envType
      
      Required. Specifies whether this component will be deployed to a default or Sun Cluster environment. Value can be sc or default.
      
      createdBy
      
      Identifies the installer of the component.
      
      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.
      
      local_zone_filesystem
      
      Required. Specifies the type of file system for the non-global zone.
      
      globalZoneHostName
      
      Required. Specifies the name of the global zone on which the existing 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.
  2. Click Save.
- To use component variables from another component, click Import Set. For more information about importing variable sets, see How to Run a Plan in Sun N1 Service Provisioning System 5.2 Operation and Provisioning Guide.

Specify the target host from which you want to import the non-global zone as a zone resource.

Click Run Plan (Includes Preflight).

The plan imports the non-global zone into your N1 SPS environment as a zone resource.