test

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

Chapter 3 Solaris 10 Zones in an SAP Environment

This chapter describes how to use the N1 SPS SAP plug-in and the N1 Advanced Architecture web console to create and manage Solaris 10 zones in your SAP environment. This chapter explains the following topics.

Overview of Solaris 10 Zones Support in the N1 Advanced Architecture for SAP Solutions 5.2 Update 2 Release

The Sun N1 Advanced Architecture for SAP Solutions 5.2 Update 2 release provides support for the creation and management of Solaris 10 non-global zones in your SAP environment. The SAP plug-in now provides two different methods for modelling and managing Solaris 10 non-global zones.

Solaris 10 Zones Support Process Overview

Working with the Solaris 10 zones support in the Sun N1 Advanced Architecture for SAP Solutions 5.2 Update 2 release is a multi-step process.

  1. Install the Solaris 10 OS on the target hosts on which you want to manage Solaris 10 zones.

    If you want to move your zones resources between systems, the systems must support the zone attach and detach features. Starting with the Solaris 10 11/06 release, these features are supported.

  2. Install the N1 SPS remote agent software on the systems that you want to provision and manage zones.

    For more information, see Sun N1 Service Provisioning System 5.2 Installation Guide.

  3. Plan your Solaris 10 zones support environment.

    For more information, see Planning Your Configuration to Support Solaris Zones.

  4. Create your Solaris 10 non-global zones.

  5. Manage your Solaris 10 non-global zones in N1 Service Provisioning System or the N1 Advanced Architecture browser user interface.

    For more information, see the appropriate section.

Solaris 10 Zones Support Requirements

To create and manage non-global zones in your SAP environment, the Solaris 10 OS, or compatible version, must be installed on the systems that you want to manage.

Note –

If you want to move non-global zones between systems in your SAP environment, your systems must be running a Solaris release that supports the zone attach and detach features. Starting with the Solaris 10 11/06 release, the zone attach and detach features are supported.

For more information, see System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

You must also import the SAP plug-in version 1.3 into your N1 SPS environment. For more information, see Chapter 2, Installing and Configuring the Sun N1 Advanced Architecture for SAP Solutions 5.2 Update 2 Release.

Planning Your Configuration to Support Solaris Zones

With the N1 SPS SAP plug-in version 1.3, you can manage Solaris 10 non-global zones as either zone hosts or zone resources. Use the following matrix to help you decide on which approach to take.

Task 

Supported by Zone Hosts 

Supported by Zone Resources 

Creating non-global zones 

Yes 

Yes 

Importing existing non-global zones into N1 Service Provisioning System 

Yes 

Yes 

Deploying SAP resources on a non-global zone 

Yes 

No 

Deploying non-global zones with other SAP resources on a global zone 

No 

Yes 

Managing applications running in a non-global zone 

Yes 

No 

Starting and stopping a non-global zone 

Yes 

Yes 

Viewing online and offline status of a non-global zone 

No 

Yes 

Moving a non-global zone between systems in N1 Advanced Architecture 

No 

Yes 

Preparing Your Systems for Zones Support in N1 Service Provisioning System and N1 Advanced Architecture

Before you can create a non-global zone in your N1 SPS environment, the name of the non-global zone must be a resolvable name, paired with an IP address, on both the N1 SPS master server and the target host onto which you plan to deploy the non-global zone. You can specify the non-global zone name and IP address in the following locations.

For more information, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) and System Administration Guide: Naming and Directory Services (NIS+).

Creating and Managing Zone Hosts

The SAP plug-in version 1.3 enables you to create and manage Solaris non-global zones as zone hosts in your SAP environment. When you create a Solaris zone host, you essentially create a physical host onto which you can deploy SAP services.

This section explains the following topics.

Creating Zone Hosts

To create a zone host, perform the following tasks.

  1. Create a physical host record for the global zone host in N1 Service Provisioning System.

    For more information, see How to Create a Global Zone Host Record.

  2. (Optional) Create an SAP Logical Host component or Storage component for the global zone host.

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

    Note –

    When you create the Logical Host or Storage component for the global zone host, you must change the value for the globalZoneHostName variable to an empty string, or the component creation fails. For a non-global zone, you must not change the default value of the globalZoneHostName.

  3. Create the Container component variables for the zone host.

    For more information see How to Create Container Component Variables for a Zone Host.

  4. Create the zone host.

    You can create a zone host in the N1 SPS browser user interface or the N1 AA web console. For more information, see the appropriate procedure.

ProcedureHow to Create a Global Zone Host Record

This procedure describes how to create a new global zone host record. You can also edit an existing host and assign the host the com.sun.sap#global_zone host type.

  1. In the N1 SPS browser user interface, go to the Hosts page.

  2. In the Host text box, type a name for the new host.

  3. In the Host Type drop down menu, select the com.sun.sap#global_zone host type.

  4. In the Description text box, type a brief description of the new host.

  5. Click Create.

    The Edit page for the new host is displayed.

  6. Ensure that the host name, description, and host type display properly.

  7. Indicate that you are creating a physical host by selecting Physical Host.

  8. If necessary, change the host type attribute values for the target host.

    Verify that the local_zone_connection_type, local_zone_port, and local_zone_advanced_params attributes match the settings for the remote agent on the target host. If you need to change these values, select the check box next to the attribute value, then type in the new value in the text field.

  9. Select the check box next to Include Remote Agent on This Physical Host.

  10. Configure the connection type, network address, and parent information for this host.

    Note –

    For information on configuring SSL and SSH network connections, see Sun N1 Service Provisioning System 5.2 Installation Guide.

  11. (Optional) To add this host to a host set, click Add to Host Sets in the Host Relationships area of the page.

    In the window that appears, select the host set to which you want to add the host. For more information on host sets, see About Host Sets in Sun N1 Service Provisioning System 5.2 System Administration Guide.

  12. To hide the host, select Hidden at the bottom of the page.

  13. Verify that the check box beside the Update or Prepare Host With Most Recent System Updates or Services option is checked.

  14. Click Save.

  15. Repeat the previous procedure for each zone host you want to create.

Next Steps

After you create the global zone host records, you must create container component variables to install and configure the zone host on your target host. For more information, see How to Create Container Component Variables for a Zone Host.

Based on your business needs, you can create a Logical Host or High Availability Storage component for the global zone. If you create the Logical Host or Storage component for the global zone host, you must change the value for the globalZoneHostName variable to an empty string, or the component creation fails. For more information, see Sun N1 Service Provisioning System User’s Guide for SAP Plug-In 1.0.

If you want to provision SAP resources in this global zone, you must change the host type of this global zone from com.sun.sap#global_zone to com.sun.sap#SAPHT. For more information about how to modify host types in N1 Service Provisioning System, see About Hosts in Sun N1 Service Provisioning System 5.2 System Administration Guide.

ProcedureHow to Create Container Component Variables for a Zone Host

After you create a Zone Host record, you must create the container component variables to install and configure the zone host on your target host. Follow these steps.

  1. From the N1 SPS Common Tasks page, click Create New Component.

    The Components page is displayed.

  2. If necessary, change to the /com/sun/sap/components folder.

  3. In the Component table, click the Details link in the Actions column for the Container component.

    The Components > Details page is displayed.

  4. Scroll to the bottom of the page and click the Variable Settings button.

    The Components > Details > Variable Settings page is displayed.

  5. Click the Create Set link at the bottom of the Create and Edit Variable Settings table.

    A new variable set column is displayed in the Create and Edit Variable Settings table.

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

    Note the name of this variable set. The variable set name is required to create the zone host.

  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 –

    Do not specify values for the local_zone_pool or the installPath variables. You specify these values when you create the zone host, as described in How to Create Non-Global Zone as a Physical Host in the N1 Service Provisioning System.

    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

    Do not specify a value for this variable. If necessary, manually delete any value for this variable.

    local_zone_filesystem

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

    local_zone_connection_type

    Specifies the type of connection for the non-global zone. Valid values are raw, ssh, and ssl. Ensure that this value matches the value for the remote agent on the non-global zone.

    local_zone_port

    Specifies the port on which the non-global zone will listen. Ensure that this value matches the value for the remote agent on the non-global zone.

    local_zone_advanced_params

    Specifies any advanced parameters for the non-global zone. Ensure that this value matches the value for the remote agent on the non-global zone.

    n1sps_cli_host

    Specifies the name of the host on which the N1 SPS command line interface (CLI) is installed.

    n1sps_cli_path

    Specifies the path to the N1 SPS CLI on the target host.

    globalZoneHostName

    Do not specify a value for this variable. If necessary, manually delete any value for this variable.

    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 Components > Details > Variable Settings page is displayed, with your new variable set included in the table.

Next Steps

After you create the container component variables, you can create the zone host on a target host. For more information, see the appropriate procedure.

ProcedureHow to Create Non-Global Zone as a Physical Host in the N1 Service Provisioning System

Before You Begin

Before you can create a non-global zone host, you must first create a global zone host record and a container component variable set for the com/sun/sap/components/Container component. For more information, see the following procedures.

  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: Create 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, specify the target host that you want to set up as the non-global zone host.

    You can select an individual host, or all the members of a host set.

  5. Specify the plan variables for your zone host creation.

    • In the Name of the Container component variable setting field, specify the container component variable set you created in How to Create Container Component Variables for a Zone Host.

    • In the Name of the local Zone field, specify a name for the non-global zone that you want to create.

    • In the Name of the pool field, specify the resource pool that you want to associate with the zone host.

  6. Click Run Plan (Includes Preflight).

    The plan performs the following tasks on the physical host.

    • Creates a non-global zone on the host of the host type com.sun.sap#SAPHT.

    • Installs the N1 SPS Remote Agent software in the non-global zone.

    • Starts the non-global zone.

    • Checks the status of the non-global zone.

    • Stops the non-global zone.

Next Steps

After you create the non-global zone, you must start the non-global zone to bring the non-global zone online. For more information, see How to Start a Non-Global Zone on a Physical Host.

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.

Troubleshooting

If the N1 Service Provisioning System reports that the zone host creation plan failed, check the operating system to verify that the non-global zone was not indeed created. If the non-global zone is installed and configured on the target host, delete the non-global zone with the zonecfg delete command, then recreate the zone host in SPS. For more information, see the zonecfg(1M) man page.

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

ProcedureHow to Create Non-Global Zone as a Physical Host in the N1 Advanced Architecture

This procedure describes how to create a zone host in the N1 AA web console.

Before You Begin

Before you can create a non-global zone host, you must perform the following tasks.

  1. In the N1 AA web console, click the SunTM N1 Advanced Architecture for SAP Solutions link in the Systems section.

    The Sun N1 Advanced Architecture for SAP Solutions page is displayed.

  2. In the left pane, click the arrow for the appropriate server group.

  3. Click the arrow for the Builder entry for the server group.

  4. Click the Zone Provisioning link.

    The N1AA Builder - Zone Provisioning page is displayed.

    Figure 3–1 N1 AA Builder — Zone Provisioning Page

    This screen capture shows the N1 AA Zone Provisioning page. The context describes the page.

  5. In the Zone name field, type the name of the non-global zone host that you want to create.

  6. From the Global Zone Host drop-down menu, select the global zone on which you want to create a non-global zone host.

  7. From the Zone Parameters drop-down menu, select the name of the container component variable set that you created in How to Create Container Component Variables for a Zone Host.

  8. In the Zone Pool field, type the name of the resource pool that you want to associate with the non-global zone host.

    To include multiple resource pools, type the pool names, separated by the pound sign (#). For more information about using resource pools with non-global zones, see the zonecfg(1M) man page.

  9. Click the Create Zone button.

    The plan performs the following tasks on the global zone host.

    • Creates a non-global zone on the host of the host type com.sun.sap#SAPHT.

    • Installs the N1 SPS Remote Agent software in the non-global zone.

    • Starts the non-global zone.

    • Adds the newly created non-global zone host record to the list of N1AA Physical Hosts.

      Note –

      This new physical host is defined as a non-global zone host and as a non OS Provisionable host.

    • Checks the status of the non-global zone.

    • Stops the non-global zone.

Next Steps

After you create the non-global zone host, perform the following tasks.

Troubleshooting

If the N1 AA web console reports that the zone host creation plan failed, check the operating system to verify that the non-global zone was not indeed created. If the non-global zone is installed and configured on the target host, delete the non-global zone with the zonecfg delete command, then recreate the zone host in SPS. For more information, see the zonecfg(1M) man page.

ProcedureHow to Create Non-Global Zone as a Physical Host With the N1 AA Command Line Interface

This procedure describes how to create a zone host with the N1 AA command line interface (CLI). The N1 Advanced Architecture 5.2 Update 2 release includes two new commands for creating non-global zone hosts.

Before You Begin

Before you can create a non-global zone host, you must perform the following tasks.

  1. Check the identifier of the server group on which you want to create a zone host.


    # ./n1aa_exec GetServerGroups

    The output of the previous command lists the unique IDs and names of the server groups in your N1 AA environment.

  2. Check the names of the global zone hosts in your N1 SPS environment.


    # ./n1aa_exec deployment.ListSPSHosts com.sun.sap#global_zone

    The output of the previous command lists the names of all the global zone hosts in your N1 SPS environment.

  3. Create the non-global zone host.


    # ./n1aa_exec deployment.CreateZoneHost
servergroup=server-group-ID
globalzonename=global-zone-name
localzonename=local-zone-name
zonepool=zone-pool
zoneparamsetname=zone-param-set-name
    server-group-ID

    Specifies the server group ID that you identified in Step 1.

    global-zone-name

    Specifies the name of the global zone that you identified in Step 2.

    local-zone-name

    Specifies the name of the non-global zone host that you want to create.

    zone-pool

    Specifies the name of the resource pool that you want to associate with the non-global zone host.

    zone-param-set-name

    Specifies the name of the container component variable set that you created in How to Create Container Component Variables for a Zone Host.

    The plan performs the following tasks on the global zone host.

    • Creates a non-global zone on the host of the host type com.sun.sap#SAPHT.

    • Installs the N1 SPS Remote Agent software in the non-global zone.

    • Starts the non-global zone.

    • Adds the newly created non-global zone host record to the list of N1AA Physical Hosts.

      Note –

      This new physical host is defined as a non-global zone host and as a non OS Provisionable host.

    • Checks the status of the non-global zone.

    • Stops the non-global zone.

Next Steps

After you create the non-global zone host, perform the following tasks.

Troubleshooting

If the N1 AA CLI reports that the zone host creation plan failed, check the operating system to verify that the non-global zone was not indeed created. If the non-global zone is installed and configured on the target host, delete the non-global zone with the zonecfg delete command, then recreate the zone host in SPS. For more information, see the zonecfg(1M) man page.

Managing Zone Hosts

After you create zone hosts, you can perform the following management tasks through the N1 Service Provisioning System.

Viewing Zone Host Information in the N1 Advanced Architecture

The Physical Hosts table in the N1 AA – Customizing page now includes information about the presence of non-global zones on the physical hosts in your environment. The table now includes a Local Zone column that indicates if a non-global zone is installed on the physical host.

Figure 3–2 Physical Hosts Table of N1 AA – Customizing Page

This screen capture shows the Physical Hosts table of the N1 AA – Customizing page, which displays server status in an N1 AA environment.

You can access the Physical Hosts table by clicking on the Administration arrow in the left panel of the N1 AA web console, then clicking on the Customizing link.

For more information, see Physical Hosts in Sun N1 Advanced Architecture for SAP Solutions 5.2.1 User’s Guide.

ProcedureHow to Start a Non-Global Zone on a Physical Host

Before You Begin

To start a zone host, you need to know the install path of the non-global zone host that you want to start. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Physical Host section of the SAP plug-in page.

  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: Start 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, specify the target host on which you want to start the non-global zone.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

    The non-global zone is started on the target host.

ProcedureHow to Stop a Non-Global Zone on a Physical Host

Before You Begin

To stop a zone host, you need to know the install path of the non-global zone host that you want to stop. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Physical Host section of the SAP plug-in page.

  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: Stop 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, specify the target host on which you want to stop the non-global zone.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

    The non-global zone is halted on the target host.

Procedure How to Delete a Non-Global Zone From a Physical Host in the N1 Service Provisioning System

Before You Begin

To delete a zone host, you need to know the install path of the non-global zone host that you want to delete. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Physical Host section of the SAP plug-in page.

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

  2. Click the Solaris Non-Global Zone as a Physical Host: Delete 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, specify the target host on which you want to delete the non-global zone.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

Next Steps

To completely delete the non-global zone from the operating system, you must delete the non-global zone with the zonecfg delete command. For more information, see the zonecfg(1M) man page.

If you are using the N1 Advanced Architecture to manage your zone hosts, you must manually delete the zone host from your N1 AA environment after you delete the zone host in N1 SPS. For more information, see How to Delete a Non-Global Zone in the N1 Advanced Architecture.

ProcedureHow to Delete a Non-Global Zone in the N1 Advanced Architecture

This procedure explains how to delete a non-global zone host from your N1 AA environment.

Note –

This procedure does not delete a non-global zone from the N1 Service Provisioning System or the operating system.

  1. In the N1 AA web console, click the Sun N1 Advanced Architecture for SAP Solutions link in the Systems section.

    The Sun N1 Advanced Architecture for SAP Solutions page is displayed.

  2. In the left navigation pane, click the arrow next to the Administration section.

    The Administration section is expanded.

  3. Click the Customizing link.

    The N1AA - Customizing page is displayed.

  4. Click the Physical Hosts link the top of the N1AA - Customizing page.

  5. Click the radio button for the physical host entry on which you want to delete the non-global zone.

  6. Click the Delete button.

  7. If prompted, confirm the deletion by clicking the OK button in the confirmation pop-up window.

    The non-global zone host is removed from the Physical Hosts table. The non-global zone host is not deleted from the N1 Service Provisioning System, and it is not deleted from the operating system.

Next Steps

If you want to delete the non-global zone host from the N1 Service Provisioning System, but leave the non-global zone intact on the operating system, see How to Delete a Non-Global Zone From the N1 SPS Environment.

If you want to delete the non-global zone host from both the N1 Service Provisioning System and the operating system, see How to Delete a Non-Global Zone From a Physical Host in the N1 Service Provisioning System.

ProcedureHow to Delete a Non-Global Zone From the N1 SPS Environment

You can use the SAP plug-in to remove a non-global zone from your N1 SPS environment, without affecting the status of the non-global zone on the physical host. Follow these steps.

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

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

    The Plan Details page is displayed.

  3. Click Run.

    The Plan Details Run page is displayed.

  4. Specify the target host that includes the non-global zone that you want to delete from your N1 SPS environment.

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

  6. Click Run Plan (Includes Preflight).

    The non-global zone is deleted from your N1 SPS environment. The status on the non-global zone on the physical host is not affected.

Creating and Managing Zone Resources

You can use the SAP plug-in to model a non-global zone as an N1 SPS resource. With the SAP plug-in and N1 AA web console, you can perform the following tasks.

This section explains the following topics.

Creating Zone Resources in the N1 Service Provisioning System

To import an existing non-global zone as a zone resource, perform the following tasks.

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

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

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

    The Plan Details page is displayed.

  3. Click Run.

    The Plan Details Run page is displayed.

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

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

  6. Click Run Plan (Includes Preflight).

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

ProcedureHow to Create a Non-Global Zone as a Zone Resource in the N1 Service Provisioning System

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

  2. Click the Solaris Non-Global Zone as a Resource: Create (Deploy) link.

    The Plan Details page is displayed.

  3. Click Run.

    The Plan Details Run page is displayed.

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

          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 will be 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 will be 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.

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

  6. Click Run Plan (Includes Preflight).

    The plan creates a non-global zone on the target global zone.

Next Steps

After you install non-global zone as a zone resource, you must start the non-global zone to bring the non-global zone online. For more information, see How to Start a Zone Resource in the N1 Service Provisioning System.

Managing Zone Resources

After you create zone resources, you can perform the following management tasks.

ProcedureHow to Set Timeout Parameters in the N1 Advanced Architecture

In the N1 AA web console, you can modify the timeout parameters for the following tasks.

  1. In the N1 AA web console, click the Sun N1 Advanced Architecture for SAP Solutions link in the Systems section.

    The Sun N1 Advanced Architecture for SAP Solutions page is displayed.

  2. In the left pane, click the arrow for the Administration section.

  3. Click the arrow for the Deployer entry.

  4. Click the Customizing link.

    The N1AA Deployment - Customizing page is displayed.

  5. If necessary, scroll down the right page to view the Timeout Parameter section.

    The various timeout parameters are displayed in a three column table. The new parameters that control zone resource management tasks include the following

    none.deployment.generaltimeout.LocalZoneComponent.start

    This parameter sets the timeout value, in minutes, for starting a zone resource.

    none.deployment.generaltimeout.LocalZoneComponent.stop

    This parameter sets the timeout value, in minutes, for stopping a zone resource.

    none.deployment.generaltimeout.LocalZoneComponent.isoffline

    This parameter sets the timeout value, in minutes, for checking the offline status of a zone resource.

    none.deployment.generaltimeout.LocalZoneComponent.isonline

    This parameter sets the timeout value, in minutes, for checking the online status of a zone resource.

    For detailed information about the timeout parameters that are supported in the N1 Advanced Architecture, see Timeout Parameter in Sun N1 Advanced Architecture for SAP Solutions 5.2.1 User’s Guide.

  6. If necessary, click the arrow buttons at the bottom of the Timeout Parameter table to navigate to the parameter that you want to modify.

  7. Click the radio button for the parameter that you want to modify.

  8. Click the Edit button.

    The N1AA Deployment - Customizing page refreshes. The parameter and timeout value are displayed in writable text fields at the bottom of the page.

  9. Type the new timeout value in the Value text field.

  10. Click the Save button.

ProcedureHow to Start a Zone Resource in the N1 Service Provisioning System

This procedure describes how to start a zone resource in the N1 SPS browser user interface.

Before You Begin

To start a zone resource, you need to know the install path of the non-global zone resource that you want to start. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page.

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

  2. Click the Solaris Non-Global Zone as a Resource: Start 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, specify the target host on which you want to start the non-global zone.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

    The non-global zone is started on the target host.

ProcedureHow to Start a Zone Resource in the N1 Advanced Architecture

This procedure describes how to start a zone resource in the N1 AA web console.

Before You Begin

To start a zone resource in the N1 AA web console, you need to know the resource group for the zone resource that you want to start. You can view the resource group by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page, then clicking the variable set link for the zone resource.

  1. In the N1 AA web console, click the Sun N1 Advanced Architecture for SAP Solutions link in the Systems section.

    The Sun N1 Advanced Architecture for SAP Solutions page is displayed.

  2. In the left pane, click the arrow for the appropriate server group.

  3. Click the arrow for the Deployer entry for the server group.

  4. Click the Resource Groups link.

    The N1AA Deployer - Resource Groups page is displayed.

  5. In the Action column of the zone resource group, click the Start link.

    The zone resource is started. A secondary window displays the status of the zone resource.

ProcedureHow to Stop a Zone Resource in the N1 Service Provisioning System

This procedure describes how to start a zone resource in the N1 SPS browser user interface.

Before You Begin

To stop a zone resource, you need to know the install path of the non-global zone resource that you want to stop. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page.

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

  2. Click the Solaris Non-Global Zone as a Resource: Stop 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, specify the target host on which you want to stop the non-global zone.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

    The non-global zone is halted on the target host.

ProcedureHow to Stop a Zone Resource in the N1 Advanced Architecture

This procedure describes how to stop a zone resource in the N1 AA web console.

Before You Begin

To stop a zone resource in the N1 AA web console, you need to know the resource group for the zone resource that you want to stop. You can view the resource group by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page, then clicking the variable set link for the zone resource.

  1. In the N1 AA web console, click the Sun N1 Advanced Architecture for SAP Solutions link in the Systems section.

    The Sun N1 Advanced Architecture for SAP Solutions page is displayed.

  2. In the left pane, click the arrow for the appropriate server group.

  3. Click the arrow for the Deployer entry for the server group.

  4. Click the Resource Groups link.

    The N1AA Deployer - Resource Groups page is displayed.

  5. In the Action column of the zone resource group, click the Stop link.

    The zone resource is halted. A secondary window displays the status of the zone resource.

ProcedureHow to Delete a Zone Resource in the N1 Service Provisioning System

This procedure explains how to delete a non-global zone resource from the operating system and from the N1 Service Provisioning System.

Note –

If you want to delete a non-global zone resource from the N1 Service Provisioning System, but leave the non-global zone intact on the operating system, perform a markOnly uninstall of the Container component for the non-global zone.

Before You Begin

To delete a zone resource, you need to know the install path of the non-global zone resource that you want to delete from the operating system. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page.

Before you delete a non-global zone, you must first stop the zone. For more information, see How to Stop a Zone Resource in the N1 Service Provisioning System.

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

  2. Click the Solaris Non-Global Zone as a Resource: Delete 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, specify the target host on which you want to delete the non-global zone.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

    The non-global zone is deleted from the operating system on the target host. The non-global zone host record is also deleted from the N1 Service Provisioning System.

Next Steps

If you are using the N1 Advanced Architecture to manage your zone hosts, you must manually delete the zone resource from your N1 AA environment after you delete the zone resource in the N1 Service Provisioning System. For more information, see How to Delete a Non-Global Zone in the N1 Advanced Architecture.

ProcedureHow to View the Online Status of a Zone Resource in the N1 Service Provisioning System

Before You Begin

To view the online status of a zone resource, you need to know the install path of the non-global zone resource that you want to check. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page.

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

  2. Click the Solaris Non-Global Zone as a Resource: Online Status 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, specify the target host that you want to check.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

    The Deployment Results page is displayed. If the plan fails, error messages are displayed.

Next Steps

For instructions about how to stop an online zone resource, see How to Stop a Zone Resource in the N1 Service Provisioning System.

ProcedureHow to View the Offline Status of a Zone Resource in the N1 Service Provisioning System

Before You Begin

To view the offline status of a zone resource, you need to know the install path of the non-global zone resource that you want to check. You can view the install path by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page.

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

  2. Click the Solaris Non-Global Zone as a Resource: Offline Status 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, specify the target host that you want to check.

    You can select an individual host, or all the members of a host set.

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

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

  7. Click Run Plan (Includes Preflight).

    The Deployment Results page is displayed. If the plan fails, error messages are displayed.

Next Steps

For instructions about how to start an offline zone resource, see How to Start a Zone Resource in the N1 Service Provisioning System.

ProcedureHow to Move Zone Resources in the N1 Advanced Architecture

This procedure describes how to move a zone resource in the N1 AA web console.

Before You Begin

To move a zone resource, you need to know the resource group for the zone resource that you want to relocate. You can view the resource group by clicking the View All link in the Solaris Non-Global Zone as a Resource section of the SAP plug-in page, then clicking the variable set link for the zone resource.

To successfully move a zone resource to another system, your environment must meet the following requirements.

  1. In the N1 AA web console, click the Sun N1 Advanced Architecture for SAP Solutions link in the Systems section.

    The Sun N1 Advanced Architecture for SAP Solutions page is displayed.

  2. In the left pane, click the arrow for the appropriate server group.

  3. Click the arrow for the Deployer entry for the server group.

  4. Click the Resource Groups link.

    The N1AA Deployer - Resource Groups page is displayed.

  5. Click the radio button for the resource group that you want to move.

  6. In the Action column of the zone resource group, click the Move link.

  7. Specify the physical host name of the target host to which you want to move the zone resource.

    The following tasks are performed for the zone resource move.

    • The High Availability Storage device is unmounted from the first host.

    • The non-global zone is detached from the first host.

    • The High Availability Storage device is created and mounted on the target host.

    • The non-global zone is attached on the target host.

Troubleshooting

If the move of the non-global zone fails, verify that the following conditions are true.