test

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

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.