How to Install a solaris Branded Zone and Perform the Initial Internal Zone Configuration - Oracle® Solaris Cluster Data Service for Oracle Solaris Zones Guide

Language:

How to Install a `solaris` Branded Zone and Perform the Initial Internal Zone Configuration

Perform this task on each node that is to host the solaris branded non-global zone. For complete information about installing a solaris branded non-global zone, see Creating and Using Oracle Solaris Zones .

Note - For procedures to install a solaris10 branded zone or a solaris-kz (kernel) zone, see How to Install a solaris10 Branded Zone and Perform the Initial Internal Zone Configuration or How to Install a solaris-kz Branded Zone and Perform the Initial Internal Zone Configuration.

Before You Begin

Consult Planning the HA for Solaris Zones Installation and Configuration and then determine the following requirements for the deployment of the zone with Oracle Solaris Cluster:
- The number of Solaris Zone instances that are to be deployed.
- The zpool containing the file system that is to be used by each Solaris Zone instance.
Ensure that the zone is enabled to run in a failover or multiple-masters configuration. See How to Enable a Zone to Run in a Failover Configuration or How to Enable a Zone to Run in a Multiple-Masters Configuration.
If the zone will run in a failover configuration and it is not set with the rootzpool zone property, ensure that the zone's zone path specifies a file system on a zpool that is managed by the SUNW.HAStoragePlus resource that you created in How to Enable a Zone to Run in a Failover Configuration.

For detailed information about configuring a solaris branded zone before installation of the zone, see Chapter 1, How to Plan and Configure Non-Global Zones, in Creating and Using Oracle Solaris Zones .

Note - This procedure assumes you are performing it on a two-node cluster. If you perform this procedure on a cluster with more than two nodes, perform on all nodes any steps that say to perform them on both nodes.

Assume the root role on one node of the cluster.
Alternatively, if your user account is assigned the System Administrator profile, issue commands as non-root through a profile shell, or prefix the command with the pfexec command.

Bring the resource group online.

phys-schost-1# clresourcegroup online -eM solaris-zone-resource-group

For zones that are not set with the rootzpool zone property, create a ZFS file-system dataset on the ZFS storage pool that you created.
You will use this file system as the zone root path for zone that you create later in this procedure.
```
phys-schost-1# zfs create pool/filesystem
```

Configure the zone on both nodes.
You must define the osc-ha-zone attribute in the zone configuration, setting type to boolean and value to true.

Note - If the zone is not set with the rootzpool zone property, set the zone root path to the file system that you created on the ZFS storage pool.
```
phys-schost# zonecfg -z zonename \
'create ; add attr; set name=osc-ha-zone; set type=boolean; set value=true; end;
set zonepath=/pool/filesystem/zonename ; set autoboot=false'
```

Verify the zone configuration.

phys-schost# zoneadm list -cv
ID NAME          STATUS        PATH                         BRAND    IP
0  global        running       /                            solaris  shared
-  zonename      configured    /pool/filesystem/zonename    solaris  shared

Install the zone.

(Only when rootzpool or zpool zone property is not set) Determine on which node the resource group is online.

phys-schost-1# clresourcegroup status solaris-zone-resource-group
=== Cluster Resource Groups ===

Group Name                   Node Name      Suspended   Status
----------                   ---------      ---------   ------
solaris-zone-resource-group  phys-schost-1  No          Online
…

Perform the rest of this step from the node that masters the resource group, or on all nodes for a multiple-master configuration.

Install the zone on each node where the resource group is online.
```
phys-schost-N# zoneadm -z zonename install
```

Verify that the zone is installed.

phys-schost-N# zoneadm list -cv
ID NAME           STATUS       PATH                         BRAND    IP
0  global         running      /                            solaris  shared
-  zonename       installed    /pool/filesystem/zonename    solaris  shared

Boot the zone that you created and verify that the zone is running.

phys-schost-N# zoneadm -z zonename boot
phys-schost-N# zoneadm list -cv
ID NAME           STATUS       PATH                         BRAND    IP
0  global         running      /                            solaris  shared
-  zonename       running      /pool/filesystem/zonename    solaris  shared

Open a new terminal window and log in to the zone console.
Follow the interactive steps to finish the zone configuration.
```
phys-schost-N# zlogin -C zonename
```
Halt the zone.
The zone's status should return to installed.
```
phys-schost-N# zoneadm -z zonename halt
```
Detach the zone.
The zone state changes from installed to configured.
- If the zone is not set with the rootzpool or zpool zone property, forcibly detach the zone.
```
phys-schost-N# zoneadm -z zonename detach -F
```
- If the zone is set with the rootzpool or zpool zone property, detach the zone.
```
phys-schost-N# zoneadm -z zonename detach
```

For a failover configuration, verify that the resource group can switch over.
For a multiple-master configuration, omit this step.
1. Switch the resource group to the other node.
  Input is similar to the following, where phys-schost-1 is the node that currently masters the resource group and phys-schost-2 is the node to which you switch the resource group.
```
phys-schost-1# clresourcegroup switch -n phys-schost-2 \
solaris-zone-resource-group
```
  Note - Perform the remaining steps in this procedure from the node to which you switch the resource group, phys-schost-2.
2. Attach the zone to the node to which you switched the resource group.
```
phys-schost-2# zoneadm -z zonename attach
```
3. Verify that the zone is installed on the node.
  Output is similar to the following:
```
phys-schost-2# zoneadm list -cv
ID NAME           STATUS       PATH                         BRAND      IP
0  global         running      /                            solaris    shared
-  zonename       installed    /pool/filesystem/zonename    solaris10  shared
```
4. Boot the zone.
```
phys-schost-2# zoneadm -z zonename boot
```
5. Open a new terminal window and log in to the zone.
  Perform this step to verify that the zone is functional.
```
phys-schost-2# zlogin -C zonename
```
6. Halt the zone.
```
phys-schost-2# zoneadm -z zonename halt
```
7. Detach the zone.
  The zone state changes from installed to configured.
  - If the zone is not set with the rootzpool or zpool zone property, forcibly detach the zone.
```
phys-schost-2# zoneadm -z zonename detach -F
```
  - If the zone is set with the rootzpool or zpool zone property, detach the zone.
```
phys-schost-1# zoneadm -z zonename detach
```